<P>
Overrides are activated by the
<A
- HREF="core.html#allowoverrides"
+ HREF="core.html#allowoverride"
REL="Help"
- ><SAMP>AllowOverrides</SAMP></A>
+ ><SAMP>AllowOverride</SAMP></A>
directive, and apply to a particular scope (such as a directory) and
all descendants, unless further modified by other
- <SAMP>AllowOverrides</SAMP> directives at lower levels. The
+ <SAMP>AllowOverride</SAMP> directives at lower levels. The
documentation for that directive also lists the possible override
names available.
</P>
<P>
Overrides are activated by the
<A
- HREF="core.html#allowoverrides"
+ HREF="core.html#allowoverride"
REL="Help"
- ><SAMP>AllowOverrides</SAMP></A>
+ ><SAMP>AllowOverride</SAMP></A>
directive, and apply to a particular scope (such as a directory) and
all descendants, unless further modified by other
- <SAMP>AllowOverrides</SAMP> directives at lower levels. The
+ <SAMP>AllowOverride</SAMP> directives at lower levels. The
documentation for that directive also lists the possible override
names available.
</P>
<CODE><Location></CODE> (except a sub-<CODE><Files></CODE>
section, but the code doesn't test for that, Lars has an open bug
report on that). Semantically however some things, and the most
-notable is AllowOverrides, make no sense in
+notable is AllowOverride, make no sense in
<CODE><Location></CODE>. The same for
<CODE><Files></CODE> -- syntactically everything is fine, but
semantically some things are different.
<CODE><Location></CODE> (except a sub-<CODE><Files></CODE>
section, but the code doesn't test for that, Lars has an open bug
report on that). Semantically however some things, and the most
-notable is AllowOverrides, make no sense in
+notable is AllowOverride, make no sense in
<CODE><Location></CODE>. The same for
<CODE><Files></CODE> -- syntactically everything is fine, but
semantically some things are different.