You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@httpd.apache.org by Steffen <in...@apachelounge.com> on 2012/05/10 20:13:33 UTC

Server Status Client IP

Running a reverse proxy in front of Apache 2.4.2 (known reason, to get more reliable networking in Windows).

The proxy supplies  the X-Forwarded-For header and using in Apache:
LoadModule remoteip_module modules/mod_remoteip.so
RemoteIPHeader X-Forwarded-For 

The mod-status page gives as client IP,  the reverse proxy IP.
The access log gives the good client/remote IP.

Is this by design ?

Steffen

Re: Server Status Client IP

Posted by Graham Leggett <mi...@sharp.fm>.

On 10 May 2012, at 8:13 PM, Steffen wrote:

> Running a reverse proxy in front of Apache 2.4.2 (known reason, to get more reliable networking in Windows).
>  
> The proxy supplies  the X-Forwarded-For header and using in Apache:
> LoadModule remoteip_module modules/mod_remoteip.so
> RemoteIPHeader X-Forwarded-For
>  
> The mod-status page gives as client IP,  the reverse proxy IP.
> The access log gives the good client/remote IP.
>  
> Is this by design ?

In the case of the access_log, yes. There are two separate variables representing each IP address, configure the access_log template as appropriate for your needs.

Ideally the mod_status page should give you both IPs, not sure if that is configurable at this point.

Regards,
Graham
--