ALINK="#FF0000"
>
<!--#include virtual="header.html" -->
+
<H1 ALIGN="CENTER">How Directory, Location and Files sections work</H1>
-The sections <A
HREF="mod/core.html#directory"><CODE><Directory></CODE></A>, <A
HREF="mod/core.html#location"><CODE><Location></CODE></A> and <A
HREF="mod/core.html#files"><CODE><Files></CODE></A> can contain
apply directives to that directory. This document explains how these
different sections differ and how they relate to each other when
Apache decides which directives apply for a particular directory or
-request URL.
+request URL.</p>
<H2>Directives allowed in the sections</H2>
-Everything that is syntactically allowed in
+<p>Everything that is syntactically allowed in
<CODE><Directory></CODE> is also allowed in
<CODE><Location></CODE> (except a sub-<CODE><Files></CODE>
-section). Semantically however some things, and the most
-notable are <CODE>AllowOverride</CODE> and the two options
+section). Semantically, however some things, most
+notably <CODE>AllowOverride</CODE> and the two options
<CODE>FollowSymLinks</CODE> and <CODE>SymLinksIfOwnerMatch</CODE>,
make no sense in <CODE><Location></CODE>,
<CODE><LocationMatch></CODE> or <CODE><DirectoryMatch></CODE>.
The same for <CODE><Files></CODE> -- syntactically everything
-is fine, but semantically some things are different.
+is fine, but semantically some things are different.</p>
<H2>How the sections are merged</H2>
-The order of merging is:
+<p>The order of merging is:</p>
<OL>
<LI>
<CODE><Directory></CODE> (except regular expressions) and
- .htaccess done simultaneously (with .htaccess overriding
+ .htaccess done simultaneously (with .htaccess, if allowed, overriding
<CODE><Directory></CODE>)
</LI>
</OL>
-Apart from <CODE><Directory></CODE>, each group is processed in
+<p>Apart from <CODE><Directory></CODE>, each group is processed in
the order that they appear in the configuration
files. <CODE><Directory></CODE> (group 1 above) is processed in
the order shortest directory component to longest. If multiple
configuration files are read in the order httpd.conf, srm.conf and
access.conf. Configurations included via the <CODE>Include</CODE>
directive will be treated as if they were inside the including file
-at the location of the <CODE>Include</CODE> directive.
-
-<P>
+at the location of the <CODE>Include</CODE> directive.</p>
-Sections inside <CODE><VirtualHost></CODE> sections are applied
+<p>Sections inside <CODE><VirtualHost></CODE> sections are applied
<EM>after</EM> the corresponding sections outside the virtual host
definition. This allows virtual hosts to override the main server
-configuration. (Note: this only works correctly from 1.2.2 and 1.3a2
-onwards. Before those releases sections inside virtual hosts were
-applied <EM>before</EM> the main server).
+configuration.</p>
-<H2>Notes about using sections</H2>
+<p>Later sections override earlier ones.</p>
-The general guidelines are:
+<H2>Notes about using sections</H2>
-<P>
+<p>The general guidelines are:</p>
<UL>
<LI>
</LI>
</UL>
-But a notable exception is:
+<p>But a notable exception is:</p>
<UL>
<LI>
</LI>
</UL>
-<P>
-Note about .htaccess parsing:
-</P>
+<p>Note about .htaccess parsing:</p>
+
<UL>
<LI>
Modifying .htaccess parsing during Location doesn't do
anything because .htaccess parsing has already occurred.
</UL>
-<P>
-<CODE><Location></CODE> and symbolic links:
-</P>
+<p><CODE><Location></CODE> and symbolic links:</p>
+
<UL>
<LI>
It is not possible to use "<CODE>Options FollowSymLinks</CODE>"
<CODE><Directory></CODE> section (or a <CODE>.htaccess</CODE> file).
</UL>
-<P>
-<CODE><Files></CODE> and <CODE>Options</CODE>:
-</P>
+<p><CODE><Files></CODE> and <CODE>Options</CODE>:</p>
+
<UL>
<LI>
Apache won't check for it, but using an <CODE>Options</CODE>
directive inside a <CODE><Files></CODE> section has no effect.
</UL>
-<P>
-Another note:
-</P>
+<p>Another note:</p>
<UL>
<LI>
</UL>
<!--#include virtual="footer.html" -->
-</BODY></HTML>
+</BODY>
+</HTML>
ALINK="#FF0000"
>
<!--#include virtual="header.html" -->
+
<H1 ALIGN="CENTER">How Directory, Location and Files sections work</H1>
-The sections <A
HREF="mod/core.html#directory"><CODE><Directory></CODE></A>, <A
HREF="mod/core.html#location"><CODE><Location></CODE></A> and <A
HREF="mod/core.html#files"><CODE><Files></CODE></A> can contain
apply directives to that directory. This document explains how these
different sections differ and how they relate to each other when
Apache decides which directives apply for a particular directory or
-request URL.
+request URL.</p>
<H2>Directives allowed in the sections</H2>
-Everything that is syntactically allowed in
+<p>Everything that is syntactically allowed in
<CODE><Directory></CODE> is also allowed in
<CODE><Location></CODE> (except a sub-<CODE><Files></CODE>
-section). Semantically however some things, and the most
-notable are <CODE>AllowOverride</CODE> and the two options
+section). Semantically, however some things, most
+notably <CODE>AllowOverride</CODE> and the two options
<CODE>FollowSymLinks</CODE> and <CODE>SymLinksIfOwnerMatch</CODE>,
make no sense in <CODE><Location></CODE>,
<CODE><LocationMatch></CODE> or <CODE><DirectoryMatch></CODE>.
The same for <CODE><Files></CODE> -- syntactically everything
-is fine, but semantically some things are different.
+is fine, but semantically some things are different.</p>
<H2>How the sections are merged</H2>
-The order of merging is:
+<p>The order of merging is:</p>
<OL>
<LI>
<CODE><Directory></CODE> (except regular expressions) and
- .htaccess done simultaneously (with .htaccess overriding
+ .htaccess done simultaneously (with .htaccess, if allowed, overriding
<CODE><Directory></CODE>)
</LI>
</OL>
-Apart from <CODE><Directory></CODE>, each group is processed in
+<p>Apart from <CODE><Directory></CODE>, each group is processed in
the order that they appear in the configuration
files. <CODE><Directory></CODE> (group 1 above) is processed in
the order shortest directory component to longest. If multiple
configuration files are read in the order httpd.conf, srm.conf and
access.conf. Configurations included via the <CODE>Include</CODE>
directive will be treated as if they were inside the including file
-at the location of the <CODE>Include</CODE> directive.
-
-<P>
+at the location of the <CODE>Include</CODE> directive.</p>
-Sections inside <CODE><VirtualHost></CODE> sections are applied
+<p>Sections inside <CODE><VirtualHost></CODE> sections are applied
<EM>after</EM> the corresponding sections outside the virtual host
definition. This allows virtual hosts to override the main server
-configuration. (Note: this only works correctly from 1.2.2 and 1.3a2
-onwards. Before those releases sections inside virtual hosts were
-applied <EM>before</EM> the main server).
+configuration.</p>
-<H2>Notes about using sections</H2>
+<p>Later sections override earlier ones.</p>
-The general guidelines are:
+<H2>Notes about using sections</H2>
-<P>
+<p>The general guidelines are:</p>
<UL>
<LI>
</LI>
</UL>
-But a notable exception is:
+<p>But a notable exception is:</p>
<UL>
<LI>
</LI>
</UL>
-<P>
-Note about .htaccess parsing:
-</P>
+<p>Note about .htaccess parsing:</p>
+
<UL>
<LI>
Modifying .htaccess parsing during Location doesn't do
anything because .htaccess parsing has already occurred.
</UL>
-<P>
-<CODE><Location></CODE> and symbolic links:
-</P>
+<p><CODE><Location></CODE> and symbolic links:</p>
+
<UL>
<LI>
It is not possible to use "<CODE>Options FollowSymLinks</CODE>"
<CODE><Directory></CODE> section (or a <CODE>.htaccess</CODE> file).
</UL>
-<P>
-<CODE><Files></CODE> and <CODE>Options</CODE>:
-</P>
+<p><CODE><Files></CODE> and <CODE>Options</CODE>:</p>
+
<UL>
<LI>
Apache won't check for it, but using an <CODE>Options</CODE>
directive inside a <CODE><Files></CODE> section has no effect.
</UL>
-<P>
-Another note:
-</P>
+<p>Another note:</p>
<UL>
<LI>
</UL>
<!--#include virtual="footer.html" -->
-</BODY></HTML>
+</BODY>
+</HTML>
projects / apache / commitdiff