You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by co...@apache.org on 2015/04/22 19:19:37 UTC
svn commit: r1675426 - in /httpd/httpd/trunk/docs/manual/mod: core.xml
mod_mime.xml
Author: covener
Date: Wed Apr 22 17:19:37 2015
New Revision: 1675426
URL: http://svn.apache.org/r1675426
Log:
PR57778
document legacy AddType/ForceType magic types as Handler names
for the curious.
Modified:
httpd/httpd/trunk/docs/manual/mod/core.xml
httpd/httpd/trunk/docs/manual/mod/mod_mime.xml
Modified: httpd/httpd/trunk/docs/manual/mod/core.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/core.xml?rev=1675426&r1=1675425&r2=1675426&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/core.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/core.xml Wed Apr 22 17:19:37 2015
@@ -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>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_mime.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_mime.xml?rev=1675426&r1=1675425&r2=1675426&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_mime.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_mime.xml Wed Apr 22 17:19:37 2015
@@ -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>