httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J.Lance Wilkinson" <>
Subject [users@httpd] Incompatibilities between mod_remoteip and the server-info & server-status handlers?
Date Fri, 28 Jan 2011 17:27:10 GMT
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.

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).

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.

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

J.Lance Wilkinson ("Lance")		InterNet:
Systems Design Specialist - Lead	Phone: (814) 865-4870
Digital Library Technologies		FAX:   (814) 863-3560
E3 Paterno Library
Penn State University
University Park, PA 16802

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