PR50376 clarify that <Directory> applies to the files under the Directory, not just...

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1040494 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml
index 96f9105d69b4aecd331b5066c6e12f1e4f5c3b48..b75f715a2b6f06bfde11f9e9f0910556e96bd45b 100644 (file)
--- a/docs/manual/mod/core.xml
+++ b/docs/manual/mod/core.xml
@@ -554,7 +554,7 @@ which no other media type configuration could be found.
 <directivesynopsis type="section">
 <name>Directory</name>
 <description>Enclose a group of directives that apply only to the
-named file-system directory and sub-directories</description>
+named file-system directory, sub-directories, and their contents.</description>
 <syntax>&lt;Directory <var>directory-path</var>&gt;
 ... &lt;/Directory&gt;</syntax>
 <contextlist><context>server config</context><context>virtual host</context>
@@ -563,8 +563,9 @@ named file-system directory and sub-directories</description>
 <usage>
     <p><directive type="section">Directory</directive> and
     <code>&lt;/Directory&gt;</code> are used to enclose a group of
-    directives that will apply only to the named directory and
-    sub-directories of that directory. Any directive that is allowed
+    directives that will apply only to the named directory,
+    sub-directories of that directory, and the files within the respective 
+    directories.  Any directive that is allowed
     in a directory context may be used. <var>Directory-path</var> is
     either the full path to a directory, or a wild-card string using
     Unix shell-style matching. In a wild-card string, <code>?</code> matches
@@ -695,7 +696,7 @@ named file-system directory and sub-directories</description>
 <directivesynopsis type="section">
 <name>DirectoryMatch</name>
 <description>Enclose directives that apply to
-file-system directories matching a regular expression.</description>
+the contents of file-system directories matching a regular expression.</description>
 <syntax>&lt;DirectoryMatch <var>regex</var>&gt;
 ... &lt;/DirectoryMatch&gt;</syntax>
 <contextlist><context>server config</context><context>virtual host</context>
@@ -704,7 +705,7 @@ file-system directories matching a regular expression.</description>
 <usage>
     <p><directive type="section">DirectoryMatch</directive> and
     <code>&lt;/DirectoryMatch&gt;</code> are used to enclose a group
-    of directives which will apply only to the named directory, 
+    of directives which will apply only to the named directory (and the files within), 
     the same as <directive module="core" type="section">Directory</directive>. 
     However, it takes as an argument a 
     <glossary ref="regex">regular expression</glossary>.  For example:</p>

diff --git a/docs/manual/sections.xml b/docs/manual/sections.xml
index bc22aa696ddcb8d66098a85c49acc4a0a8f94d4a..a28d2c0e893ee1b5a944e9e395d40e923aeb3ea9 100644 (file)
--- a/docs/manual/sections.xml
+++ b/docs/manual/sections.xml
@@ -156,7 +156,8 @@ counterparts, apply directives to
 parts of the filesystem.  Directives enclosed in a <directive
 type="section" module="core">Directory</directive> section apply to
 the named filesystem directory and all subdirectories of that
-directory.  The same effect can be obtained using <a
+directory (as well as the files in those directories).  
+The same effect can be obtained using <a
 href="howto/htaccess.html">.htaccess files</a>.  For example, in the
 following configuration, directory indexes will be enabled for the
 <code>/var/web/dir1</code> directory and all subdirectories.</p>