Hi, On Mon, Apr 26, 2010 at 03:41:03PM +0200, Cyril Bonté wrote: > > Can you please explain in more detail what server makes wrong and why > > haproxy > > adds Connection: Close header > > (and why Firefox successfully uses HTTP keep-alive with the same server > > without > > haproxy).
If you can get a trace of what firefox exchanges with the server, it would help a lot, because here your server clearly does not permit keep-alive. > HAProxy can't accept the connection to be keep-alived as it doesn't provide a > Content-Length (nor the communication allows chunked transfer). > Try to add a Content-Length header equal to your data length and Keep-Alive > should be accepted. Indeed, and it's not haproxy-specific, it's HTTP. Haproxy just sets the "Connection: close" in the response for the sake of correctness, and in order to avoid having two agents on the same connection disagree. Willy
