I believe your problem is because, for keepalive sessions, HAproxy is only adding an X-Forwarded-For header on the first HTTP transaction of the keepalive session. This can be alleviated by using "option http-server-close", which allows keepalive on the client side, but uses Close mode on the server side. The X-Forwarded-For header will then be present on all HTTP transactions.
On 6 September 2011 12:59, Christophe Rahier <[email protected]>wrote: > Hi, > > I installed HAProxy on 2 Debian server for loadbalancing 6 webserver (IIS). > > All works fine but I've a small problem. > > In IIS, I added an ISAPI filter to read the X-Forwarded-For value. > > In the IIS log file, I've a mixed of my loadbalancer IP (192.168.0.3) but > also the official IP (xxx.xxx.xxx.xxx), for example: > > 2011-09-05 13:33:21 192.168.0.61 GET /v8/ - 80 - 87.67.52.233 > Opera/9.80+(Macintosh;+Intel+Mac+OS+X+10.7.1;+U;+en)+Presto/2.9.168+Version > /11.51 302 0 0 93 > 2011-09-05 13:33:21 192.168.0.61 GET /v8/login.cfm - 80 - 192.168.0.3 > Opera/9.80+(Macintosh;+Intel+Mac+OS+X+10.7.1;+U;+en)+Presto/2.9.168+Version > /11.51 200 0 0 140 > 2011-09-05 13:33:21 192.168.0.61 GET /CFIDE/scripts/cfform.js - 80 - > 192.168.0.3 > Opera/9.80+(Macintosh;+Intel+Mac+OS+X+10.7.1;+U;+en)+Presto/2.9.168+Version > /11.51 200 0 0 46 > 2011-09-05 13:33:21 192.168.0.61 GET /CFIDE/scripts/masks.js - 80 - > 192.168.0.3 > Opera/9.80+(Macintosh;+Intel+Mac+OS+X+10.7.1;+U;+en)+Presto/2.9.168+Version > /11.51 200 0 0 15 > 2011-09-05 13:33:21 192.168.0.61 GET /v8/styles.css - 80 - 192.168.0.3 > Opera/9.80+(Macintosh;+Intel+Mac+OS+X+10.7.1;+U;+en)+Presto/2.9.168+Version > /11.51 200 0 0 31 > > Do you have an idea? I don't understand where's the problem. > > Thanks for your help. > > > Christophe > > -- John Helliwell
