Jeff Nokes wrote:
Thanks for the reply!
Yes, that is correct.
But since I cannot use arbitrary headers, these options aren't viable for
me.
Load Balancers should be able to set the X-Forwarded-For header (I know F5
can do it, no idea about NetScaler, but I'm fairly sure it should be
Hi,
I'm running a mod_perl/Mason app at a fairly large company. We have two pools
of machines, each pool with it's own pair of load balancers. One pool uses F5
BigIP, and the other uses Netscaler. The problem that I'm having is that the
Apache variable REMOTE_ADDR seems to correctly
On 4/24/06, Jeff Nokes [EMAIL PROTECTED] wrote:
LocationMatch ^/+(marketing/report.*)$
order deny,allow
deny from all
allow from 10 172.16 192.168
/LocationMatch
mod_rewrite or mod_setenvif can do access control based on arbitrary
headers. So
PROTECTED]
To: users@httpd.apache.org; Jeff Nokes [EMAIL PROTECTED]
Sent: Monday, April 24, 2006 2:09:37 PM
Subject: Re: [EMAIL PROTECTED] mod_access and Client IP's from Load Balancers
On 4/24/06, Jeff Nokes [EMAIL PROTECTED] wrote:
LocationMatch ^/+(marketing/report.*)$
order
On 4/24/06, Jeff Nokes [EMAIL PROTECTED] wrote:
Thanks for the reply!
Yes, that is correct.
But since I cannot use arbitrary headers, these options aren't viable for me.
Basically, I need to restrict the same Location, via a single restriction
(preferably via IP subnets), using an
