Show all posts by user
Discussions in Russian
Page 1 of 1 Pages: 1
Results 1 - 4 of 4
Hi,
OK, I see. Now I agree that Accept-Ranges header should be removed anyway in slice module, and any plan to fix that?
by
webber
-
Nginx Mailing List - English
Hi,
Sorry to bother you, I rechange the patch as follow:
Previously, if an Accept-Ranges header was already present in the first slice
response, client received two copies of this header. Now, the slice filters
removes the Accept-Ranges header for partital request and if original server
response Accept-Ranges header, has from the response prior to setting the
r->allow_ranges flag.
by
webber
-
Nginx Mailing List - English
Hi,
Thanks for your reply. I have tried the patch that removes the original Accept-Ranges in slice filter module, but it is not work as my expected. Because I think response header `Accept-Ranges` should be added if client send a range request.
Actually, in my production environment, my upstream server is Apache TrafficServer, and according to RFC 7233, section 2.3: Accept-Ranges(https://to
by
webber
-
Nginx Mailing List - English
Hello,
Recently, we found if we use nginx slice module , and upstream server is such as a static file server, nginx will response duplicated `Accept-Ranges` headers if client request is not included range header.
the minimal config example as follow:
```
server {
listen 80;
server_name _;
default_type text/html;
by
webber
-
Nginx Mailing List - English