>> 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@nginx.com> wrote:

>
> On 23 Jun 2014, at 17:15, itpp2012 <nginx-forum@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@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx