You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by el...@apache.org on 2017/03/13 15:24:45 UTC
svn commit: r1786710 - /httpd/httpd/trunk/docs/manual/sections.html.en
Author: elukey
Date: Mon Mar 13 15:24:45 2017
New Revision: 1786710
URL: http://svn.apache.org/viewvc?rev=1786710&view=rev
Log:
Documentation rebuild
Modified:
httpd/httpd/trunk/docs/manual/sections.html.en
Modified: httpd/httpd/trunk/docs/manual/sections.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/sections.html.en?rev=1786710&r1=1786709&r2=1786710&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/sections.html.en (original)
+++ httpd/httpd/trunk/docs/manual/sections.html.en Mon Mar 13 15:24:45 2017
@@ -431,26 +431,35 @@ are interpreted, it is important to unde
</ol>
- <p>Apart from <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code>, each group is processed in
- the order that they appear in the configuration files. <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> (group 1 above)
- is processed in the order shortest directory component to longest.
- So for example, <code><Directory "/var/web/dir"></code> will
- be processed before <code><Directory
- "/var/web/dir/subdir"></code>. If multiple <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> sections apply
- to the same directory they are processed in the configuration file
- order. Configurations included via the <code class="directive"><a href="./mod/core.html#include">Include</a></code> directive will be treated as if
- they were inside the including file at the location of the
- <code class="directive"><a href="./mod/core.html#include">Include</a></code> directive.</p>
-
- <p>Sections inside <code class="directive"><a href="./mod/core.html#virtualhost"><VirtualHost></a></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.</p>
-
- <p>When the request is served by <code class="module"><a href="./mod/mod_proxy.html">mod_proxy</a></code>, the
- <code class="directive"><a href="./mod/mod_proxy.html#proxy"><Proxy></a></code>
- container takes the place of the <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> container in the processing
- order.</p>
+ <p>Some important remarks:</p>
+ <ul>
+ <li>Apart from <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code>, within each group the sections are
+ processed in the order they appear in the configuration files.
+ For example, a request for <em>/foo</em> will match
+ <code><Location "/foo/bar"></code> and
+ <code><Location "/foo"></code> (group 4 in this case):
+ both sections will be evaluated
+ but in the order they appear in the configuration files.</li>
+ <li><code class="directive"><a href="./mod/core.html#directory"><Directory></a></code>
+ (group 1 above) is processed in the order shortest directory
+ component to longest. For example,
+ <code><Directory "/var/web/dir"></code> will be processed before
+ <code><Directory "/var/web/dir/subdir"></code>.</li>
+ <li>If multiple <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> sections apply
+ to the same directory they are processed in the configuration file
+ order.</li>
+ <li>Configurations included via the <code class="directive"><a href="./mod/core.html#include">Include</a></code> directive will be treated as if
+ they were inside the including file at the location of the
+ <code class="directive"><a href="./mod/core.html#include">Include</a></code> directive.</li>
+ <li>Sections inside <code class="directive"><a href="./mod/core.html#virtualhost"><VirtualHost></a></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.</li>
+ <li>When the request is served by <code class="module"><a href="./mod/mod_proxy.html">mod_proxy</a></code>, the
+ <code class="directive"><a href="./mod/mod_proxy.html#proxy"><Proxy></a></code>
+ container takes the place of the <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> container in the processing
+ order.</li>
+ </ul>
<div class="note"><h3>Technical Note</h3>
There is actually a