I had a similar experience. It seemed to happen most often when I was
accessing the site from inside a private network that had some kind of web
filtering at the internet gateway.
From: Balvinder
Sent: Monday, December 23, 2019 11:52 PM
To: users@httpd.apache.org
Subject: [users@httpd] Apache
Thanks Eric; I will try that.
-Original Message-
From: Eric Covener
Sent: Friday, October 25, 2019 2:33 PM
To: users@httpd.apache.org
Subject: Re: [users@httpd] SentEnvIf and multiple X-Fowarded-For headers
> the problem is that Apache seems to run the SetEnvIf only against the
> first
I asked a similar question some weeks ago (in respect of -ipmatch and
X-Forwarded-For) , but received no response.
Original question reproduced here:
---
I am certain I’m missing something important about the directive and the
-ipmatch operator whe
I am certain I'm missing something important about the directive and the
-ipmatch operator when used in conjunction with %{HTTP:X-Forwarded-For}.
Please permit me to illustrate the problem by way of example:
LogMessage "Got IP match [%{HTTP:X-Forwarded-For}]"
LogMessage "No IP match [%{
