From: Eric Covener <covener@apache.org>
Date: Wed, 22 Apr 2015 19:37:03 +0000 (+0000)
Subject: reword per feedback
X-Git-Tag: 2.5.0-alpha~3228
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=85b8169b177d447d5206e42f608c3b3692a3e692;p=apache

reword per feedback


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

diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml
index 80e5b92676..a53fd1b1f0 100644
--- a/docs/manual/mod/core.xml
+++ b/docs/manual/mod/core.xml
@@ -1892,18 +1892,27 @@ ForceType image/gif
     static files, where the generator of the response typically specifies
     a Content-Type, this directive has no effect.</p>
 
+
     <note><title>Note</title>
+    <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.
+    directives is instead set to the content type specified by this directive.
+    <p>
     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
+    (such as mod_php) may look for a "synthetic" content type used only to 
+    signal the module to take 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>. </p>
+    <directive module="mod_mime">AddHandler</directive> should
+    restrict access to this directive as well.</p>
     </note>
 
 </usage>
diff --git a/docs/manual/mod/mod_mime.xml b/docs/manual/mod/mod_mime.xml
index bbb9524592..3c79b73b66 100644
--- a/docs/manual/mod/mod_mime.xml
+++ b/docs/manual/mod/mod_mime.xml
@@ -610,17 +610,25 @@ AddType application/rss+xml;qs=0.8 .xml
 
 
     <note><title>Note</title>
+    <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.  
+    directives is instead set to the content type specified by this directive.  
+    <p>
     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 
+    (such as mod_php) may look for a "synthetic" content type used only to 
+    signal the module to take 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>. </p>
+    <directive module="mod_mime">AddHandler</directive> should
+    restrict access to this directive as well.</p>
     </note>
 
 </usage>