You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by "J.Lance Wilkinson" <jl...@psulias.psu.edu> on 2011/01/28 18:27:10 UTC
[users@httpd] Incompatibilities between mod_remoteip and the server-info &
server-status handlers?
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: Lance.Wilkinson@psu.edu
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:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Incompatibilities between mod_remoteip and the
server-info & server-status handlers?
Posted by Jeroen Geilman <je...@adaptr.nl>.
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
server.
> 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
server.
> But if it SHOULD be working I'd like to know what I'm doing wrong.
>
--
J.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org