Tom Evans wrote:
According to the docs on mod_remoteip, it should work as you expect:
The module replaces the apparent remote (client) IP/hostname for the
request with the IP address reported in the request header configured
with the RemoteIPHeader directive.
Once replaced as instructed, this
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
On Mon, Jan 31, 2011 at 12:50 PM, J.Lance Wilkinson
jl...@psulias.psu.edu 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
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
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
