Hello, On Tue, Jan 26, 2010 at 10:58:21AM -0500, Zachary Goldberg wrote: > Greetings! > > I am presently using HAProxy "development" 1.4 branch and the new > http-server-close && client side keepalives feature. This feature has > definitely helped my latencies a lot vs. HAProxy 1.3 so thank you very > much for your hard word on this great feature so far!
I'm glad it helped ! > I have, > however, run into a bit of an issue with client side keep alives. In > the case where an error occurs, such as a 503 error in haproxy (no > machines alive in the backend) haproxy serves an error file as I > defined in my configuration. However, in this scenario, haproxy > closes the connection on each error and does not keep the client side > session alive. Yes, currently, only the redirects have been adapted to support keep-alive, and only if the Location begins with a slash (same server). > It is important to note that in this particular scenario a 503 is an > *expected* error that I handle gracefully with the custom error file > and it is important for me that I can keep the connection open after > such a request to reduce latencies. Is there an option perhaps that I > am overlooking to enable this capability? It's not planned yet because I don't see a big advantage in keeping a session alive after a timeout error or things like this. I suspect that in fact you're diverting the 503 to use an errorfile directive to return some specific data. This won't be needed anymore once we implement the "return" directive to return raw messages or files, so I'd not want to complexify the error handling a lot just for some tricks. Regards, Willy
