enabling SPDY (patch 42) +nginx 1.3.2 breaks gzip
pgndev
pgnet.dev+nginx at gmail.com
Tue Jun 26 19:43:15 UTC 2012
hi
On Tue, Jun 26, 2012 at 12:23 PM, Valentin V. Bartenev <ne at vbart.ru> wrote:
> Actually, Firefox doesn't* send the "Accept-Encoding" header over SPDY
I'm not clear as to that statement's implication ... Can you please
clarify what's not working with Firefox+SPDY ? Do I need to
change/add something to headers in FF config as well?
Fwiw, I already have installed this extension:
https://github.com/chengsun/moz-spdy-indicator
Does that not address this issue?
> and Nginx doesn't add it when proxying to backend.
ok
> * Note, that Firebug isn't accurate about the headers have actually been sent.
That's useful to know. Do you have some more detail on this? I can
take it up @firebug if it hasn't been already
> The issue is clear enough and will be fixed in the future revision. Currently,
> you can use something like this:
>
> map $spdy $spdy_ae {
> default $http_accept_encoding;
> 2 "gzip, deflate";
> }
>
> proxy_set_header Accept-Encoding $spdy_ae;
I've added that stanza to my nginx "http{..." conf. Cleared
all-caches & restarted server.
I'm still seeing no gzip headers:
Response Headers
Age 42
Cache-Control public, max-age=300
Content-Language en
Content-Type text/html; charset=utf-8
Date Tue, 26 Jun 2012 19:35:27 GMT
Expires Sun, 19 Nov 1978 05:00:00 GMT
Last-Modified Tue, 26 Jun 2012 19:34:41 GMT
Link <https://test.svr06.loc/>; rel="canonical"
Server nginx
Vary Accept-Encoding,User-Agent
Via 1.1 varnish
X-Cache-Hits 1
X-Drupal-Cache MISS
X-Firefox-Spdy 1
X-Varnish 1136383481 1136383476
X-Varnish-Cache HIT
x-ua-compatible IE=Edge,chrome=1
> or enable compression in Nginx.
Compression is, atm, handled at my stack's Apache 24X backend.
More information about the nginx-devel
mailing list