Bug in supporting Quality zero (negate) parameter in Accept-Encoding
radek at pinkbike.com
Fri Jul 29 17:53:28 UTC 2011
Spent the last day chasing down a corner case with Nginx and Level3
CDN. It turns out that some requests that they send have the
following Accept-Encoding header.
"Accept-Encoding: compress, gzip;q=0"
Based on this RFC
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html this is a
valid way to say "NO gzip encoding"
Nginx ignores this and actually sends a gziped version. This causes
the CDN to error, as defined by the RFC.
This should NOT return compressed data, as defined by the RFC
curl -I http://cs.pinkbike.org/127/sprt/c/top.css -H "Accept-Encoding: gzip;q=0"
HTTP/1.1 200 OK
Date: Fri, 29 Jul 2011 17:06:14 GMT
Last-Modified: Fri, 15 Jul 2011 20:13:20 GMT
Expires: Thu, 31 Dec 2037 23:55:55 GMT
Is there a parameter/idea that I am missing or is this a bug?
More information about the nginx