diff options
Diffstat (limited to 'docs/manual/sections.html.en')
| -rw-r--r-- | docs/manual/sections.html.en | 31 |
1 files changed, 20 insertions, 11 deletions
diff --git a/docs/manual/sections.html.en b/docs/manual/sections.html.en index 565d4d3..36e2018 100644 --- a/docs/manual/sections.html.en +++ b/docs/manual/sections.html.en @@ -1,7 +1,7 @@ -<?xml version="1.0" encoding="ISO-8859-1"?> +<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head> -<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" /> +<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" /> <!-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT @@ -24,10 +24,10 @@ <a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="./">Version 2.4</a></div><div id="page-content"><div id="preamble"><h1>Configuration Sections</h1> <div class="toplang"> <p><span>Available Languages: </span><a href="./en/sections.html" title="English"> en </a> | -<a href="./fr/sections.html" hreflang="fr" rel="alternate" title="Français"> fr </a> | +<a href="./fr/sections.html" hreflang="fr" rel="alternate" title="Français"> fr </a> | <a href="./ja/sections.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | <a href="./ko/sections.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | -<a href="./tr/sections.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +<a href="./tr/sections.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> </div> <p>Directives in the <a href="configuring.html">configuration files</a> may apply to the entire server, or they may be restricted to apply only to particular @@ -269,7 +269,7 @@ and URLs to be referenced from within <a href="expr.html">expressions</a> and modules like <code class="module"><a href="./mod/mod_rewrite.html">mod_rewrite</a></code>.</p> <pre class="prettyprint lang-config"><DirectoryMatch "^/var/www/combined/(?<SITENAME>[^/]+)"> - require ldap-group "cn=%{env:MATCH_SITENAME},ou=combined,o=Example" + Require ldap-group "cn=%{env:MATCH_SITENAME},ou=combined,o=Example" </DirectoryMatch></pre> @@ -427,7 +427,8 @@ are interpreted, it is important to understand how this works.</p> <li><code class="directive"><a href="./mod/core.html#location"><Location></a></code> and <code class="directive"><a href="./mod/core.html#locationmatch"><LocationMatch></a></code> done simultaneously</li> - <li><code class="directive"><a href="./mod/core.html#if"><If></a></code> + <li><code class="directive"><a href="./mod/core.html#if"><If></a></code> sections, even when + they are enclosed in any of the preceding contexts. </li> </ol> @@ -460,6 +461,14 @@ are interpreted, it is important to understand how this works.</p> <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> + <li> Caution should be exercised when mixing related configuration + directives inside and outside of <code class="directive"><a href="./mod/core.html#if"><If></a></code> because of the effect on merging order. Explicit use + of <code class="directive"><a href="./mod/core.html#else"><Else></a></code> can help. + </li> + <li> When <code class="directive"><a href="./mod/core.html#if"><If></a></code> is + used in <code>.htaccess</code>, the enclosed directives in a parent + directory will be merged <em>after</em> non-enclosed directives in a + subdirectory.</li> </ul> <div class="note"><h3>Technical Note</h3> @@ -506,7 +515,7 @@ are interpreted, it is important to understand how this works.</p> <li><code class="directive">Directory</code> "/" matches and an initial configuration to set the <code>CustomHeaderName</code> header with the value <code>one</code> is created.</li> <li><code class="directive">Directory</code> "/example" matches, and since <code class="module"><a href="./mod/mod_headers.html">mod_headers</a></code> specifies in its code to override in case of a merge, a new configuration is created to set the <code>CustomHeaderName</code> header with the value <code>two</code>.</li> <li><code class="directive">FilesMatch</code> ".*" matches and another merge opportunity arises, causing the <code>CustomHeaderName</code> header to be set with the value <code>three</code>.</li> - <li>Eventually during the next steps of the HTTP request processing <code class="module"><a href="./mod/mod_headers.html">mod_headers</a></code> will be called and it will receive the configuration to set the <code>CustomHeaderName</code> header with the value <code>three</code>. <code class="module"><a href="./mod/mod_headers.html">mod_headers</a></code> normally uses this configuration to perfom its job, namely setting the foo header. This does not mean that a module can't perform a more complex action like discarding directives because not needed or deprecated, etc..</li> + <li>Eventually during the next steps of the HTTP request processing <code class="module"><a href="./mod/mod_headers.html">mod_headers</a></code> will be called and it will receive the configuration to set the <code>CustomHeaderName</code> header with the value <code>three</code>. <code class="module"><a href="./mod/mod_headers.html">mod_headers</a></code> normally uses this configuration to perform its job, namely setting the foo header. This does not mean that a module can't perform a more complex action like discarding directives because not needed or deprecated, etc..</li> </ul> <p>This is true for .htaccess too since they have the same priority as <code class="directive">Directory</code> in the merge order. The important concept to understand is that configuration sections like <code class="directive">Directory</code> and <code class="directive">FilesMatch</code> are not comparable to module specific directives like <code class="directive"><a href="./mod/mod_headers.html#header">Header</a></code> or <code class="directive"><a href="./mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> because they operate on different levels. @@ -567,11 +576,11 @@ other words, order of merging is important, so be careful!</p> </div></div> <div class="bottomlang"> <p><span>Available Languages: </span><a href="./en/sections.html" title="English"> en </a> | -<a href="./fr/sections.html" hreflang="fr" rel="alternate" title="Français"> fr </a> | +<a href="./fr/sections.html" hreflang="fr" rel="alternate" title="Français"> fr </a> | <a href="./ja/sections.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | <a href="./ko/sections.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | -<a href="./tr/sections.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> -</div><div class="top"><a href="#page-header"><img src="./images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our <a href="http://httpd.apache.org/lists.html">mailing lists</a>.</div> +<a href="./tr/sections.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p> +</div><div class="top"><a href="#page-header"><img src="./images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our <a href="https://httpd.apache.org/lists.html">mailing lists</a>.</div> <script type="text/javascript"><!--//--><![CDATA[//><!-- var comments_shortname = 'httpd'; var comments_identifier = 'http://httpd.apache.org/docs/2.4/sections.html'; @@ -589,7 +598,7 @@ var comments_identifier = 'http://httpd.apache.org/docs/2.4/sections.html'; } })(window, document); //--><!]]></script></div><div id="footer"> -<p class="apache">Copyright 2019 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> +<p class="apache">Copyright 2024 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p> <p class="menu"><a href="./mod/">Modules</a> | <a href="./mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="./glossary.html">Glossary</a> | <a href="./sitemap.html">Sitemap</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!-- if (typeof(prettyPrint) !== 'undefined') { prettyPrint(); |