> proxy_store has this functionality if not proxy_cache ?
You would not have this problem with local files (rsync'ing them to your
server, as was previsouly suggested in the other thread).


What nginx release are you using? You probably need at least 1.5.13 as
per:
http://mailman.nginx.org/pipermail/nginx/2014-June...

Hi,


> Connection: keep-alive
> Last-Modified: Fri, 20 Jun 2014 11:04:11 GMT
> ETag: "53a4152b-184468a"
> Expires: Fri, 27 Jun 2014 13:36:05 GMT
> Cache-Control: max-age=604800
> X-Cache-Status: HIT
> Content-Range: bytes 16-25446025/25446026
>
> Could you tell me how can i check using curl that if nginx downloading
> the whole file each time the user seek the video with mp4 psuedo
> module  i.e http://url/files/videos/test-360.mp4?start=39.

Check the Content-Length header in the response.


Regards,

Lukas

On 19 Jun 2014, at 10:12, shahzaib shahzaib <shahzaib.cb@gmail.com>
wrote:

>
>       we're using two servers (one proxy and one backend). Proxy server is using
proxy_cache to cache mp4 files from backend server and working fine. When i 
stream
a full video from cache, the header response gives me the cache-status: HIT but
whenever i seek the mp4 file i.e http://url/test.mp4?start=33 , the Cache-status
changes to : MISS . Does that mean, the proxy server is again downloading the 
same
file after the 33 seconds ?

Since default proxy_cache_key has $args in it, your second request has a
different cache key, so the
file is downloaded again.

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.

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.

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,251037,251108#msg-251108

On 23 Jun 2014, at 16:47, shahzaib shahzaib <shahzaib.cb@gmail.com>
wrote:

> @Roman thanks for reply,
>
> >> your second request has a different cache key, so the
> file is downloaded again.
>
> Means, if a user seeks through the video i.e http://url/test.mp4?start=99 , the
whole file again gets downloaded or the partial part of the file from 99sec to
onward gets downloaded ? If the whole file downloaded again each time, does 
nginx
support something like, if user seeks through the video start=99 and the rest of
the file gets download instead of the whole file ? Is the rsync only solution if
not nginx?

If you have mp4 module enabled at the upstream, then partial mp4 (well,
its not partial actually,
but transformed) is downloaded and cached.  If not then you should
configure a proper proxy_cache_key
to download the whole file once from the upstream and serve the whole
mp4 from the cache.

On 23 Jun 2014, at 17:15, itpp2012 <nginx-forum@nginx.us> wrote:

> 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 cant play
it directly
without stripping headers.