On Mon, Jan 06, 2014 at 04:03:11PM +0000, Thomas Sheppard wrote: > Hi Baptiste > > That is what I thought however shouldn't it be sending the keep alive > header in order to conform with 1.0?
It does so if either the client or the server are in 1.0. Otherwise it removes the unneeded and confusing header. > Also it doesn't seem any of the connections are kept alive anyway. > > If I run - ab -kc 1000 -n 10000 https://ipaddress against the HAProxy > server. Strange, given that "ab -k" is precisely what I use to test keep-alive. > The netstat -o on the server running HAProxy shows Time-Wait instead of > Keep-Alive. I'm just unconvinced the connection is being kept alive as > expected. What does your configuration look like ? Keep-alive does not preempt load balancing (fortunately!) so by default, load balancing will still apply and may switch to a different server if the algorithm decides so. But you can force to reuse the same server as the previous one with "option prefer-last-server". Maybe this is what you need ? Willy
