If I wanted to add client side keep-alive support for HAProxy behind an Apache httpd SSL configuration, how should I set this up?
Maybe someone who has this successfully setup already could share their httpd and haproxy setup? Is it just as simple as turning on KeepAlive in httpd and adding option http-server-close to my HAProxy frontend? I want to ensure that the IP address will always be correct once it gets to the web servers and that I won't receive any mod_proxy error messages due to premature closing of server connections. My current httpd config: KeepAlive Off MaxKeepAliveRequests 100 KeepAliveTimeout 5 <VirtualHost ...> ... Redirect stuff to redirect https://mysite.com/ to https://www.mysite.com/ ... SSL stuff ... ProxyPass / http://www.mysite.com/ retry=2 ProxyPassReverse / http://www.mysite.com/ SetEnvIf User-Agent ".*MSIE.*" \ nokeepalive ssl-unclean-shutdown \ downgrade-1.0 force-response-1.0 ... Log stuff ... </VirtualHost> Thanks, Bradford On Thu, Aug 4, 2011 at 3:34 PM, Willy Tarreau <w...@1wt.eu> wrote: > On Thu, Aug 04, 2011 at 03:06:21PM -0400, Guillaume Bourque wrote: > > Thnaks for the precision. > > > > Maybe we can add some other string and not bother with the stunnel one > when > > it is there ! > > > > Like this: > > > > > > option forwardfor header X-Forwarded-For-Haproxy > > Yes if you want. > > > Or I see that It can be a network so this should be fine if all my > stunnel > > are in this subnet > > > > option forwardfor except 10.222.0.0/27 > > That's exactly the principle. Most often it's on the same host so you > can use 127.0.0.0/8. It's also quite common to see the proxies on the > same subnet or on a known subnet and you can proceed as above. > > > Again thanks for youre great support Willy. > > You're welcome :-) > Thanks to the other helpful participants to ! > > Willy > > >
