Re: http-server-close problem (also with Tomcat backend)

Hi,

2010/3/30 Óscar Frías Barranco <ofrias#gmail.com>: <...>
> It seems to me that when http-server-close option is enabled, haproxy
> replaces the original request header "Connection: Keep-Alive" by
> "Connection: close".  And this change is making Tomcat change its behavior:
> when it receives a "Connection: close" it does not use chunked transfer
> encoding.  Instead, Tomcat replies with a "Connection: close" response
> header and a non-chunked response whose length is indicated by closing the
> connection.

Are you only seeing this problem for responses with chunked transfer encoding in Tomcat? In Jetty, we are seeing a similar issue with simple responses with a Content-length header. If there is a "Connection: close" header in the request, Jetty returns a response without the Content-length header.

Thanks,

Patrik Received on 2010/04/01 11:32