ssi, reverse-proxy and compression

Igor Sysoev is at rambler-co.ru
Wed Jan 28 16:30:18 MSK 2009


On Wed, Jan 28, 2009 at 06:35:39PM +0530, Arvind Jayaprakash wrote:

> On Jan 28, Olivier B. wrote:
> > Hello,
> >
> > we're using ssi with reverse-proxy on NginX 0.6.34, but have a problem when 
> > contents is compressed on the fly by the backend.
> > As we can't disable this on the backend, we would like setup NginX to don't 
> > send the "Accept-Encoding" header to it, or to decompress this contents 
> > before processing ssi tags.
> >
> > I don't find how to set up that, so actually I simply replace the 
> > Accept-Encoding this way :
> >    proxy_set_header Accept-Encoding none
> >
> > Is there a "better" way to do that ?
> 
> HTTP compression requires HTTP 1.1 and from what I know, nginx uses HTTP
> 1.0 for proxying. In that case, there should be no compression in a HTTP
> 1.0 response. So it sounds like the backend is sending compressed
> response when it should not do so.
> 
> http://tools.ietf.org/html/rfc2616#section-14.3

Actually, HTTP/1.0 clients usually understand compression.


-- 
Igor Sysoev
http://sysoev.ru/en/





More information about the nginx mailing list