Does Nginx supports If-Range ?
nelsonmarcos at gmail.com
Tue Jul 4 14:29:45 UTC 2017
Thanks Zhang and Maxim!
I'm checking how to fix that on my backend.
2017-07-04 9:21 GMT-03:00 Maxim Dounin <mdounin at mdounin.ru>:
> On Mon, Jul 03, 2017 at 05:09:28PM -0300, Nelson Marcos wrote:
> > I don't know if it is an expected behaviour or a bug:
> > Scenario 1(OK): If I perform a request *with the header Range*, Nginx
> > serves the *partial content(HTTP 206)*.
> > Scenario 2 (NOT OK): If I perform a request *with the header Range AND
> > header "If-Range" *with the Etag, Nginx serves the *entire file*(200).
> > not serve the partial content if its cached version matches the If-Range
> > header?
> > In both scenarios the file is already cached.
> > Here is my conf: https://pastebin.com/gQQ0GSg6
> > Here are my requests and my files: https://pastebin.com/rxLwYaSK
> The "ETag" header in the response is invalid, as well as
> "If-Range" in the request. Quoting from the second link:
> : Etag: 345a2dd5c8f22e9ffaf250151ea820df
> : If-Range: 345a2dd5c8f22e9ffaf250151ea820df
> In both cases entity tag should be in double quotes, see
> Fixing your backend to return correct ETag will make things work.
> Alternatively, you can use Last-Modified date in the If-Range
> request header instead.
> Maxim Dounin
> nginx mailing list
> nginx at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx