Merge r1905716 from trunk:

mention some non-inuititive <If> stuff

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1905717 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/sections.xml b/docs/manual/sections.xml
index 67e98481735536e7fd3a746ad08f71d1678b1a92..a24cd23c4db5dc61e60dfd9c22ac0be49c1111a6 100644 (file)
--- a/docs/manual/sections.xml
+++ b/docs/manual/sections.xml
@@ -480,7 +480,8 @@ are interpreted, it is important to understand how this works.</p>
       and <directive type="section"
       module="core">LocationMatch</directive> done simultaneously</li>
 
-      <li><directive type="section" module="core">If</directive>
+      <li><directive type="section" module="core">If</directive> sections, even when
+      they are enclosed in any of the preceding contexts.
       </li>
 
     </ol>
@@ -518,6 +519,15 @@ are interpreted, it is important to understand how this works.</p>
         container takes the place of the <directive module="core"
         type="section">Directory</directive> container in the processing
         order.</li>
+        <li> Caution should be exercised when mixing related configuration
+        directives inside and outside of <directive type="section" module="core"
+        >If</directive> because of the effect on merging order.  Explicit use
+        of <directive type="section" module="core" >Else</directive> can help.
+        </li>
+        <li> When <directive type="section" module="core" >If</directive> 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>
 
     <note><title>Technical Note</title>