On Wed, Nov 10, 2010 at 7:32 AM, Maxim Dounin <mdounin@mdounin.ru> wrote:
> "Some download clients" probably have to be fixed, as 200 is
> allowed response for range requests.
>
>> Is there a workaround for this problem?
>
> You may pass Range requests to backends with something like
>
>    proxy_set_header Range $http_range;
>    proxy_set_header If-Range $http_if_range;
>
> and don't cache responses to these requests at all:
>
>    proxy_no_cache $http_range $http_if_range;
>

Should nginx honor "Range" requests for files that are in cache
locally? 0.7.67 doesn't seem to do so in my testing. In fact, it
always seems to send 200 with the entire file, even for static files
that are hosted on the local file system.

Is Range support unimplemented?

--
RPM

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx