Question x-forwarded-for problem

[bosstds]

Hi,
Got a strange problem today.
There's a certain web app which runs behind reverse proxy. In the example below 1.1.1.1 is the client IP, 2.2.2.2 is the server IP.

If there is the line

proxy_set_header X-Forwarded-For  $proxy_add_x_forwarded_for;

in the nginx config, the web app shows that x-forwarded-for contains client IP twice, for example 1.1.1.1,1.1.1.1. The behaviour I would expect is to have 1.1.1.1,2.2.2.2 in this header, as x-forwarded for is supposed to contain all the proxies on the path to the backend.
If I remove this line, the x-forwarded-for contains only the server IP, for example 2.2.2.2. This is expected behaviour.


Am i missign something?

Product version: Plesk Onyx 17.0.17 Update #8
    Update date: 2016/12/03 03:29
     Build date: 2016/11/17 16:00
     OS version: CentOS 6.8
       Revision: ab6766191d3ba26e7b21255ab007fc7fc56d84c6
   Architecture: 64-bit
Wrapper version: 1.2

 

[Bitpalast]

This is not a Plesk issue.

Please see these two articles on the proxy_add_x_forwarded_for issue of Nginx:
http://stackoverflow.com/questions/29279084/nginx-proxy-add-x-forwarded-for-and-real-ip-header
http://serverfault.com/questions/314574/nginx-real-ip-header-and-x-forwarded-for-seems-wrong