13 messages in ru.sysoev.nginxRe: nginx not setting REMOTE_ADDR pro...| From | Sent On | Attachments |
|---|---|---|
| Mohammad Kolahdouzan | Feb 23, 2009 4:01 pm | |
| mike | Feb 23, 2009 4:23 pm | |
| Mohammad Kolahdouzan | Mar 4, 2009 6:52 pm | |
| Abhishek Singh | Mar 4, 2009 7:05 pm | |
| Mohammad Kolahdouzan | Mar 4, 2009 8:29 pm | |
| Abhishek Singh | Mar 4, 2009 8:38 pm | |
| Mohammad Kolahdouzan | Mar 5, 2009 7:24 am | |
| Igor Sysoev | Mar 5, 2009 7:28 am | |
| Mohammad Kolahdouzan | Mar 5, 2009 9:17 am | |
| Igor Sysoev | Mar 5, 2009 11:53 am | |
| Mohammad Kolahdouzan | Mar 11, 2009 10:37 pm | |
| Mohammad Kolahdouzan | Mar 11, 2009 10:50 pm | |
| Mohammad Kolahdouzan | Apr 19, 2009 9:43 pm |
| Subject: | Re: nginx not setting REMOTE_ADDR properly? | |
|---|---|---|
| From: | Mohammad Kolahdouzan (moha...@yahoo.com) | |
| Date: | Mar 4, 2009 8:29:34 pm | |
| List: | ru.sysoev.nginx | |
I monitored the HTTP headers of the requests that are forwarded to Nginx by the
load balancer using tcpdump, and I can clearly see that the remote IP is added
to the headers as a new header "REMOTE ADDR:", still use $http_x_forwarded_for
it?
Thanks, -M
________________________________ From: Abhishek Singh <abhi...@gmail.com> To: ngi...@sysoev.ru Sent: Wednesday, March 4, 2009 7:06:18 PM Subject: Re: nginx not setting REMOTE_ADDR properly?
Use "$http_x_forwarded_for" to log client real ip address.
On Thu, Mar 5, 2009 at 8:22 AM, Mohammad Kolahdouzan <moha...@yahoo.com>
wrote:
My nginx is getting requests through a (NetScaler) load balancer, and
$remote_addr is returning the load balancer's IP and not the real user's IP
(which the load balancer sets as REMOTE_ADDR in the header). Any other attribute
I should use to get the real user's IP?
-M