From: Eric Covener <covener@apache.org>
Date: Sun, 10 May 2015 15:38:45 +0000 (+0000)
Subject: sync note with trunk
X-Git-Tag: 2.4.13~114
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=212547ced435283769fbb4cbdb5a2c0a4fd68bfd;p=apache

sync note with trunk


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

diff --git a/docs/manual/mod/mod_mime.xml b/docs/manual/mod/mod_mime.xml
index cf93dc2462..bb38b19b8b 100644
--- a/docs/manual/mod/mod_mime.xml
+++ b/docs/manual/mod/mod_mime.xml
@@ -608,17 +608,25 @@ type</description>
 
 
     <note><title>Note</title>
-    <p>When explicit directives such as 
-    <directive module="core" >SetHandler</directive> or 
-    <directive module="mod_mime">AddHandler</directive> do not apply 
+    <p>If no handler is explicitly set for a request, the specified content
+    type will also be used as the handler name. </p>
+
+    <p>When explicit directives such as
+    <directive module="core" >SetHandler</directive> or
+    <directive module="mod_mime">AddHandler</directive> do not apply
     to the current request, the internal handler name normally set by those
-    directives is set to match the content type specified by this directive.  
-    This is a historical behavior that some third-party modules 
-    (such as mod_php) may use "magic" content types used only to signal the 
-    module to take responsibility for the matching request.  Configurations
-    that rely on such "magic" types should be avoided by the use of 
-    <directive module="core" >SetHandler</directive> or 
-    <directive module="mod_mime">AddHandler</directive>. </p>
+    directives is instead set to the content type specified by this directive.
+    </p>
+    <p>
+    This is a historical behavior that may be used by some third-party modules
+    (such as mod_php) for taking responsibility for the matching request.
+    </p>
+
+    <p>Configurations that rely on such "synthetic" types should be avoided.
+    Additionally, configurations that restrict access to
+    <directive module="core" >SetHandler</directive> or
+    <directive module="mod_mime">AddHandler</directive> should
+    restrict access to this directive as well.</p>
     </note>
 
 </usage>