Download full mp4 file with proxy_cache or proxy_store !!

[shahzaib shahzaib]

mp4 seeking is filling up disk rapidly on edge server using proxy_cache and
also incoming bandwidth is always higher than outgoing bandwidth (nload).
Maybe, people are seeking to mp4 files and full videos are getting download
again and again.

How can i manage the mp4 seeking on edge server ? will proxy_store resolve
the issue ?  I really need to find the solution.

Btw, nginx version is 1.6

Regards.



On Mon, Jun 23, 2014 at 11:06 PM, shahzaib shahzaib <shahzaib.cb at gmail.com>
wrote:

> >> You can use proxy_store with the mp4 module.
> So, proxy_store is able to download whole mp4 file once and than server
> that file locally without fetching each time from the origin if users seek
> through the video ?
>
>
> On Mon, Jun 23, 2014 at 7:43 PM, Roman Arutyunyan <arut at nginx.com> wrote:
>
>>
>> On 23 Jun 2014, at 17:15, itpp2012 <nginx-forum at nginx.us> wrote:
>>
>> > Roman Arutyunyan Wrote:
>> > -------------------------------------------------------
>> >> Moreover the mp4 module does not work over proxy cache.  That means
>> >> even if you fix the cache key issue
>> >> mp4 seeking will not work.  You need to have a local mp4 file to be
>> >> able to seek mp4 like that.
>> >
>> > Hmm, what about a hack, if the file is cached keep a link to the cached
>> file
>> > and its original name, if the next request matches a cached file and its
>> > original name and a seek is requested then pass the cache via its
>> original
>> > name to allow seeking on the local (but cached) file.
>>
>> You can use proxy_store with the mp4 module.
>>
>> Having a link to a nginx cache file is wrong since cache file has
>> internal header and
>> HTTP headers.  Cached mp4 entry is not a valid mp4 meaning you can’t play
>> it directly
>> without stripping headers.
>> _______________________________________________
>> nginx mailing list
>> nginx at nginx.org
>> http://mailman.nginx.org/mailman/listinfo/nginx
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140725/8b4160ef/attachment.html>