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) 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.To
make sure I took capture and I see the duplicate one.
Is this is bug or am I missing something?

>From client end:-


>From haproxy LB:-


>From Backend:-


-Habeeb

Reply via email to