https://issues.apache.org/bugzilla/show_bug.cgi?id=55990
--- Comment #2 from Dan Jacobson ---
Yes except for case 4.
In case 4 we find the startling results that SetEnv actually does get read,
IF the following operator is "=!".
--
You are receiving this mail because:
You are the assignee for th
https://issues.apache.org/bugzilla/show_bug.cgi?id=55990
--- Comment #3 from Eric Covener ---
(In reply to Dan Jacobson from comment #2)
> Yes except for case 4.
> In case 4 we find the startling results that SetEnv actually does get read,
> IF the following operator is "=!".
I get the expected
https://issues.apache.org/bugzilla/show_bug.cgi?id=55990
--- Comment #4 from Dan Jacobson ---
These are my results. Please test with these *exact* lines.
No need to look at the parent, just attempt to browse the directory itself.
With a .htaccess of
Order Deny,Allow
Deny from all
Allow from env=
https://issues.apache.org/bugzilla/show_bug.cgi?id=55990
--- Comment #5 from Eric Covener ---
2.2.3 did not contain env=!foo. It's not mentioned in the changelog or in the
compatibility support of the manual, but it looks like it was first relased in
2.2.10.
Without support for =!let_me_in this
https://issues.apache.org/bugzilla/show_bug.cgi?id=55990
Dan Jacobson changed:
What|Removed |Added
Version|2.4.6 |2.4.7
--- Comment #6 from Dan Jacob
https://issues.apache.org/bugzilla/show_bug.cgi?id=55990
--- Comment #7 from Dan Jacobson ---
$ ${EDITOR} abj.jidanni.org/images/abj/.htaccess
$ HEAD -dP http://abj.jidanni.org/images/abj/
is what I used to test.
--
You are receiving this mail because:
You are the assignee for the bug.
-
