On Wed, Sep 26, 2012 at 8:25 AM, Willy Tarreau <[email protected]> wrote: [snip]
>> what I'm seeing right now is that Apache (final destination for the >> requests I'm trying to log) outputs in its access_log a chain of XFFs >> with 3-4 IPs per HTTP request, but haproxy emits only the last IP in >> the XFF chain to syslog when using "capture request header >> X-Forwarded-For len 63" (again, with haproxy-1.4.16) > > Have you had a look at the request haproxy is receiving ? It would be > nice to know whether it already receives multiple headers (eg: due to > other components in the chain before it) or all of them at once. upstream -> haproxy -> Apache I can see in the apache logs the chain of 3-4 IPs in the XFF header, and when I run tcpdump on an haproxy host I can also see multiple IPs in the XFF there - they just aren't being emitted by haproxy to the logs. (but the entire header, including all IPs, is being properly passed along to the backend Apache instances). (unrelated: the haproxy mailing list archives appear to have stopped updating in late 2011; a quick Google search didn't turn up any information about this, but I'm sure the question has been asked before - when should we see current discussion threads appear in the list archives? I'd like to be able to reference URLs for this thread in discussions with co-workers.) thanks, /sf
