[PATCH] HTTP: gzip resources upstream has flagged as sdch encoded.

[Tom Thorogood]

Hi,

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
<https://github.com/baranov1ch/connect-sdch>.

Regards,
Tom Thorogood.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nginx-sdch-gzip.patch
Type: text/x-patch
Size: 2417 bytes
Desc: not available
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20150430/0e266fb2/attachment.bin>