httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Whit Blauvelt <>
Subject [users@httpd] So AllowOverride None in Directory should still allow Location to override?
Date Mon, 27 Oct 2003 21:19:13 GMT
Since it seems Location can override even when AllowOverride None is set in
Directory ... isn't this kind of fishy design? Can a Location statement, for
instance, go in an .htaccess file and give access where the Directory
directives would be thought to lock it out? 

With the evaluation order being Directory -> Location it would seem that
AllowOverrides None in Directory would preclude overrides in a normal Set ->
Subset logical relationship. That is, the subset might have exceptions, but
only those that are allowed it by the superset. Directory being at the
system level whould be the broader, more fundamental set.

Of course, there's no necessary reason to obey the norms of set theory -
except that many of us have been educated in it and take it for granted in
design logic.


On Mon, Oct 27, 2003 at 03:31:03PM -0500, Joshua Slive wrote:

> You'll see that <Location> sections are evaluated after <Directory>
> sections and therefore override them.

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message