Re: Tricky X-Forwarded-For header

On Fri, 22 Feb 2008, Jean-Baptiste Quenot wrote:

> Hi there,

Hi,

> All my HTTP requests go through haproxy 1.3.14.2, and I have a reqirep
> statement in the config to rename the inbound X-Forwarded-For header
> to X-Orig-Forwarded-For, so that I only have one IP in the
> X-Forwarded-For header.
>
> This works fine, and *most of the time* I receive the X-Forwarded-For
> header correctly. But on some occasions, this header is missing from
> the HTTP request. Is it possible that somewhere in the haproxy code
> this header is discarded under certain conditions?
>
> Please find below a tcpdump-captured excerpt of the HTTP conversation
> for one of the requests that is missing the valuable header:
<CUT>

Haproxy does not support keep-alives (yet) so you have to add "option httpclose" or else it is only able to analyze/process the first request of each connection.

> Oh and BTW, I heard that haproxy is not configured to support
> keep-alive by default, so I wonder why I see the keep-alive header in
> the logs. I didn't add any keep-alive-related option in the
> configuration.

Does not support means that it passes a keep-alive traffic between a client and a server but is not able to deal with it properly.

Best regards,

                                 Krzysztof Olêdzki Received on 2008/02/23 01:35