Re: "gzip on" duplicates Content-Encoding header if an empty one already exists

> On Wednesday, March 25, 2015 12:04:03 PM Jason Woods wrote: >> Hi, >> >> I have a (probably dodgy) application that is sending out uncompressed XML >> with the following header. That is, an empty Content-Encoding header. >> >> Content-Encoding: >> >> This works fine, until I enable gzip on Ngi

Re: "gzip on" duplicates Content-Encoding header if an empty one already exists

Hi Jason, Probably discarding the Content-Encoding directive from the upstream will resolve this: http://nginx.org/r/proxy_hide_header On Wednesday, March 25, 2015 12:04:03 PM Jason Woods wrote: > Hi, > > I have a (probably dodgy) application that is sending out uncompressed XML > with the foll

"gzip on" duplicates Content-Encoding header if an empty one already exists

Hi, I have a (probably dodgy) application that is sending out uncompressed XML with the following header. That is, an empty Content-Encoding header. Content-Encoding: This works fine, until I enable gzip on Nginx 1.6.2 latest (which is a proxy to the application.) Nginx compresses the XML, and