On Sat, Jan 11, 2014 at 4:46 AM, <[email protected]> wrote:
>>>>>> "EC" == Eric Covener <[email protected]> writes:
> EC> Try logging the envvar. Whether it's logged the way you want or not,
> EC> you can either focus on or remove the access control directives
>
> OK, I tried logging for the first time today. But I found that even at
> trace8 level, some things were never logged.
Log as in custom access log to see if the environment variable is
ultimately set. e.g. With %{envvar-name}e.
> Those are probably (?) things
> that don't actually get run and await documentation as per
> mentioned in https://issues.apache.org/bugzilla/show_bug.cgi?id=55957#c4
> On the other hand, the results of every <If> I was able to log with
> great clarity.
More likely you are conflating one recent anecdote with some currently
undiagnosed issue/question.
Is there even a subrequest involved in this failing test?
>
> EC> (also, use require env foo instead of order/allow/deny)
>
> Alas those along with <If> I cannot use, as I am trying to find a way to
> rewrite
>
> <If "%{HTTP_HOST} !~ /radioscanningtw\.jidanni\.org/i">
> Deny from all
> </If>
>
> so it will work in Apache 2.2.9!
There's no point in using a 2.2 compat directive inside a 2.4-only directive.
--
Eric Covener
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
