Re: Duplicate X-Forwarded-For

On 2012-02-01 20:00, habeeb rahman wrote: > I know that apache comma separates the values for X-Forwarded-For and I > thought haproxy behaves the same. Both types are semantically the same. So for an application, it shouldn't matter if you get these headers X-Forwarded-For: 10.10.10.10 X-Forwarde

Re: Duplicate X-Forwarded-For

(Thanks Holger for quick response) I know that apache comma separates the values for X-Forwarded-For and I thought haproxy behaves the same. We do not want to delete X-Forwarded-Forand then add X-Forwarded-For because the developers want to look at the proxy chain. Having said that I am still not

Re: Duplicate X-Forwarded-For

Hey, On 2012-02-01 17:41, habeeb rahman wrote: > When there is X-Forwarded-For added by the client(I used chrome rest > client) I can see haproxy is sending two X-Forwarded-For to the backend > instead of appending the values. > One is client sent and the other one is the one haproxy created newly

Duplicate X-Forwarded-For

Hi All, The backend application depends on the X-Forwarded-For value and today we noticed an interesting problem. I have enabled 'option forwardfor' and it works fine when no X-Forwarded-For header is added by the client. When there is X-Forwarded-For added by the client(I used chrome rest client