Re: [us...@httpd] Negation of Remote_Addr in SetEnvIf directive

2010-04-22 Thread Krzysztof Dajka
> Apache 2.0 and later uses PCRE, and neither of those expressions mean > what you're describing. SetEnvIf itself doesn't negate the result of > the regex match with a flag. > > I don't fully understand your logic, but If you want your SetEnvIf to > only take action when the remote address doesn't

Re: [us...@httpd] Negation of Remote_Addr in SetEnvIf directive

2010-04-22 Thread Eric Covener
> SetEnvIf Remote_Addr !^10\. HOSTNAME=foo.bar.com > Header add X-Server-Name "%{HOSTNAME}e" > but negation of network didn't work, I have also tried: > SetEnvIf Remote_Addr [^(10\.)] HOSTNAME=foo.bar.com > but it didn't worked either. > Has anyone used negation inĀ SetEnvIf Remote_Addr ? > Document

[us...@httpd] Negation of Remote_Addr in SetEnvIf directive

2010-04-22 Thread Krzysztof Dajka
Hi, I have a bunch of apache servers which are load balanced. I have configured them in such manner that each server adds header X-Server-Name with proper hostname. In my apache.conf I have: PassEnv HOSTNAME Header add X-Server-Name "%{HOSTNAME}e" I have exported HOSTNAME before launching apach