diff options
| author | Luca Toscano <elukey@apache.org> | 2017-03-14 12:39:04 +0000 |
|---|---|---|
| committer | Luca Toscano <elukey@apache.org> | 2017-03-14 12:39:04 +0000 |
| commit | 248edbd3e41b897f87eda3d346b7f27a4e6ea815 (patch) | |
| tree | d9585dc1c615cea2955b48173c22ca734865957d /docs/manual/sections.html.en | |
| parent | de48452300bbeda7411d4c7dc70bb7cdfd91e851 (diff) | |
| download | httpd-248edbd3e41b897f87eda3d346b7f27a4e6ea815.tar.gz | |
Documentation rebuild
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1786896 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'docs/manual/sections.html.en')
| -rw-r--r-- | docs/manual/sections.html.en | 49 |
1 files changed, 29 insertions, 20 deletions
diff --git a/docs/manual/sections.html.en b/docs/manual/sections.html.en index 7bad305c8c..e5c1534dd4 100644 --- a/docs/manual/sections.html.en +++ b/docs/manual/sections.html.en @@ -431,26 +431,35 @@ are interpreted, it is important to understand how this works.</p> </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 |