Wedge
Public area => The Pub => Bug reports => Topic started by: Pandos on May 23rd, 2014, 11:39 AM
-
Server is behind a remote proxy. Logs already got the right X-FORWARDED-FOR IP.
In Wedge all users got the IP from the remote proxy (192.168.x.x). Also putting the proxy IP in settings did not change this value.
-
Dig a bit deeper into it. The real IP is saved in DB as IP2. IP1 is the proxy IP :)
-
So, it's not for the Bug Reports board but for some FAQ, right...? ;)
-
No?
If users are behind a reverse proxy the IP should display the right way? Not due to changes to the core?
-
Just created a little script to determine the real IP:
<?php
echo 'Server IP: ' . $_SERVER['SERVER_ADDR'] . '<br />';
echo 'Your IP: ' . $_SERVER['REMOTE_ADDR'];
if(isset($_SERVER['HTTP_X_FORWARDED_FOR']))
{
echo '<br />Forwarded For: ' . $_SERVER['HTTP_X_FORWARDED_FOR'];
}
echo getenv('HTTP_VIA'),"\n";
?>
And here's the output from one user:
Server IP: 192.168.148.9
Your IP: 192.168.148.6
Forwarded For: 87.152.XXX.XXX
VIA:
So enabling forwarded for should do read the forwarded IP, right?
You can test it. You've got access to this server :)
-
I understand, but I was just asking, what's best for users? What do you want me to do exactly..?
-
Change it, that the Forwarded IP is displayed and not 192.168.148.6 behind reverse proxys. :)