httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeroen Geilman <>
Subject Re: [users@httpd] Incompatibilities between mod_remoteip and the server-info & server-status handlers?
Date Sat, 29 Jan 2011 11:55:58 GMT
On 1/28/11 6:27 PM, J.Lance Wilkinson wrote:
> I've got a set of identical webservers, all Apache 2.2.6, with 
> configurations such that authorized IP addresses are allowed access to 
> locations handled by the server-info and server-status handlers.
> These work fine when visiting the individual servers.
> Now I put a load balancer in front of them all, and incorporate the 
> mod_remoteip module into them to accept the load balancer inserted 
> X-Forwarded-For header as the actual requesting IP address.

Meaning the load "balancer" has to do double work because unacceptable 
IPs are not blocked at the front gate. That's weird.

> Users from acceptable IP addresses coming in through the load balancer 
> get either a 404, a 403 or a blank page (and the error log shows an 
> aborting child process in that case).

Put an apache load balancer in front and move the access lists to that 

> If there's a basic incompatibility between these handlers and 
> mod_remoteip, like for example, maybe they do their thing BEFORE 
> mod_remoteip appears in the processing stack, I'll accept that.   
> After all, the main reason I want to do it from the load balancer is 
> to just see which server is being handed any arbitrary request; it's a 
> trivial thing.

Put an apache load balancer in front and move the access lists to that 

> But if it SHOULD be working I'd like to know what I'm doing wrong.


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message