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/14 12:36:55 UTC
svn commit: r1786895 - /httpd/httpd/branches/2.4.x/docs/manual/sections.xml
Author: elukey
Date: Tue Mar 14 12:36:55 2017
New Revision: 1786895
URL: http://svn.apache.org/viewvc?rev=1786895&view=rev
Log:
Merge r1786709 from trunk:
Add a note in the docs about evaluation of Location sections
The sections.html doc was missing, in my opinion, a direct
reference to the fact multiple Location blocks matching
a HTTP request will be evaluated in the order in which they
appear in the configuration files (same as Ifs, etc..).
Reworked a bit a single block of text to be a bit more readable.
Modified:
httpd/httpd/branches/2.4.x/docs/manual/sections.xml
Modified: httpd/httpd/branches/2.4.x/docs/manual/sections.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/sections.xml?rev=1786895&r1=1786894&r2=1786895&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/sections.xml (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/sections.xml Tue Mar 14 12:36:55 2017
@@ -483,32 +483,40 @@ are interpreted, it is important to unde
</ol>
- <p>Apart from <directive type="section"
- module="core">Directory</directive>, each group is processed in
- the order that they appear in the configuration files. <directive
- type="section" module="core">Directory</directive> (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 <directive
- type="section" module="core">Directory</directive> sections apply
- to the same directory they are processed in the configuration file
- order. Configurations included via the <directive
- module="core">Include</directive> directive will be treated as if
- they were inside the including file at the location of the
- <directive module="core">Include</directive> directive.</p>
-
- <p>Sections inside <directive type="section"
- module="core">VirtualHost</directive> 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 <module>mod_proxy</module>, the
- <directive module="mod_proxy" type="section">Proxy</directive>
- container takes the place of the <directive module="core"
- type="section">Directory</directive> container in the processing
- order.</p>
+ <p>Some important remarks:</p>
+ <ul>
+ <li>Apart from <directive type="section"
+ module="core">Directory</directive>, 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><directive type="section" module="core">Directory</directive>
+ (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 <directive
+ type="section" module="core">Directory</directive> sections apply
+ to the same directory they are processed in the configuration file
+ order.</li>
+ <li>Configurations included via the <directive
+ module="core">Include</directive> directive will be treated as if
+ they were inside the including file at the location of the
+ <directive module="core">Include</directive> directive.</li>
+ <li>Sections inside <directive type="section"
+ module="core">VirtualHost</directive> 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 <module>mod_proxy</module>, the
+ <directive module="mod_proxy" type="section">Proxy</directive>
+ container takes the place of the <directive module="core"
+ type="section">Directory</directive> container in the processing
+ order.</li>
+ </ul>
<note><title>Technical Note</title>
There is actually a