On Wed, May 13, 2009 at 04:53:15PM -0400, Tom Potwin wrote: > Thanks Alex for the info. Unfortunately, I'm already using 'option > httpclose'. Here's my current cfg: > global > log 127.0.0.1 local0 > log 127.0.0.1 local1 notice > #log loghost local0 info > maxconn 4096 > #debug > #quiet > user haproxy > group haproxy > defaults > log global > mode http > option httplog > option dontlognull > retries 3 > redispatch > maxconn 2000 > contimeout 5000 > clitimeout 50000 > srvtimeout 50000 > > listen webfarm 192.168.31.100:80 > mode http > stats enable > stats auth netadmin:5bgr+bdd1WbA > stats refresh 5s > balance roundrobin > cookie JSESSIONID prefix > option httpclose > option forwardfor > option httpchk HEAD /check.txt HTTP/1.0 > server web1 192.168.31.202:80 cookie w01 check inter 2000 rise 2 fall > 2 > server web2 192.168.31.212:80 cookie w02 check inter 2000 rise 2 fall > 2 > option persist > redispatch > contimeout 5000
you can try to add "option forceclose". If this works with that option, it means that one of the sides (browser or server) is incorrectly ignoring "Connection: close" (already encountered a long time ago). Do you reach haproxy through a proxy or directly ? maybe this proxy would enforce keep-alive. Hoping this helps, Willy
