duplicate Vary: Accept-Encoding header

4extramails · 2014-01-19T19:50:00+00:00

Hello! On Fri, Jan 17, 2014 at 8:37 AM, <i...@ecsystems.nl> wrote: > \src\ngx_http_lua_directive.c > Line 937; > [...] > ngx_http_l...

duplicate Vary: Accept-Encoding header

4extramails

Hello,

I use nginx/1.4.4 with gunzip = on and gzip_vary = on. This leads to a duplicate Vary Header.

gzip_vary should do nothing if the header is already present:

moki@mysrv:~$ curl -I http://213.223.158.196/home.html
HTTP/1.1 200 OK
Server: nginx/1.4.4
Date: Sun, 19 Jan 2014 11:30:59 GMT
Content-Type: text/html
Connection: keep-alive
Vary: Accept-Encoding
Vary: Accept-Encoding
Location: home.html

I have no control of the upstream server it may send a Vary header or not, in order to be safe I would like to use gzip_vary = on in order to prevent any problems here.

Thanks,
Makailol

agentzh

Hello!

On Sun, Jan 19, 2014 at 3:49 AM, Makailol Charls wrote:
> I use nginx/1.4.4 with gunzip = on and gzip_vary = on. This leads to a
> duplicate Vary Header.
>
> gzip_vary should do nothing if the header is already present:
>

This is an issue in the standard Nginx core, and it is in the standard
ngx_http_header_filter_module, to be more specific.

The header filter there blindly inserts the response header without
checking the existing response headers at all.

I suggest you should report this issue to the nginx mailing list instead:

    http://mailman.nginx.org/mailman/listinfo/nginx

Best regards,
-agentzh

4extramails

Thanks!

I have reported this issue to the nginx mailing list.

Meanwhile could you suggest any alternate solution(if any) to handle this?

Regards,
Makailol

On Monday, January 20, 2014 7:08:04 AM UTC+5:30, agentzh wrote:

Hello!

On Sun, Jan 19, 2014 at 3:49 AM, Makailol Charls wrote:
> I use nginx/1.4.4 with gunzip = on and gzip_vary = on. This leads to a
> duplicate Vary Header.
>
> gzip_vary should do nothing if the header is already present:
>

This is an issue in the standard Nginx core, and it is in the standard
ngx_http_header_filter_module, to be more specific.

The header filter there blindly inserts the response header without
checking the existing response headers at all.

I suggest you should report this issue to the nginx mailing list instead:

http://mailman.nginx.org/mailman/listinfo/nginx

Best regards,
-agentzh