Hi, I'm using HAproxy 1.4.8 on RHEL5 (fully up-to-date). I'm using the 'option forwardfor'
In certain circumstances, the client has already got an X-Forwarded-For header in the request. HAproxy in this instance adds a second X-Forwarded-For header rather than extending the existing header. This causes a problem on our Tomcat backend because the RemoteIP valve (part of Tomcat) that is used appears to examine only the first header. 1. Is there some way to get HAproxy to extend the existing X-Forwarded-For header rather than adding a new one 2. Does the stunnel patch do the same thing or does it extend the existing X-Forwarded-For header? Thanks, -- Best Regards, Brett Delle Grazie
