[PATCH] HTTP: gzip resources upstream has flagged as sdch encoded.
me at tomthorogood.co.uk
Thu Apr 30 11:39:09 UTC 2015
This is ultimately a pretty simply change. When an proxied resource has
been sdch encoded, currently the gzip module refuses to run. This change
causes gzip to run on sdch resources and ensures that gzip is appended
to the Content-Encoding header, keeping the sdch flag.
For a working sdch server implementation, see
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 2417 bytes
Desc: not available
More information about the nginx-devel