From: Eric Covener <covener@apache.org>
Date: Wed, 22 Apr 2015 17:19:37 +0000 (+0000)
Subject: PR57778
X-Git-Tag: 2.5.0-alpha~3237
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=904c2e776cde7eb6e1b305c91d8a9c4359afef5e;p=thirdparty%2Fapache%2Fhttpd.git

PR57778

document legacy AddType/ForceType magic types as Handler names
for the curious.



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

diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml
index da9be22cb27..85b2f9a141e 100644
--- a/docs/manual/mod/core.xml
+++ b/docs/manual/mod/core.xml
@@ -1892,6 +1892,20 @@ 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>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
+    diretives 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 user of
+    <directive module="core" >SetHandler</directive> or
+    <directive module="mod_mime">AddHandler</directive>. </p>
+    </note>
+
 </usage>
 </directivesynopsis>
 <directivesynopsis>
diff --git a/docs/manual/mod/mod_mime.xml b/docs/manual/mod/mod_mime.xml
index 8d900072961..374e1057fcb 100644
--- a/docs/manual/mod/mod_mime.xml
+++ b/docs/manual/mod/mod_mime.xml
@@ -608,6 +608,21 @@ AddType application/rss+xml;qs=0.8 .xml
     static files, where the generator of the response typically specifies
     a Content-Type, this directive has no effect.</p>
 
+
+    <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 
+    to the current request, the internal handler name normally set by those
+    diretives 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 user of 
+    <directive module="core" >SetHandler</directive> or 
+    <directive module="mod_mime">AddHandler</directive>. </p>
+    </note>
+
 </usage>
 <seealso><directive module="core">ForceType</directive></seealso>
 <seealso><module>mod_negotiation</module></seealso>