Commit db311072 authored by Eric Covener's avatar Eric Covener
Browse files

Merge r1675426, r1675429 from trunk: 

PR57778

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



typoes



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

docs/manual/mod/core.xml

+14 −0
Changes for docs/manual/mod/core.xml: 14 added lines, 0 removed lines.
Original line number Diff line number Diff line
@@ -1856,6 +1856,20 @@ media type in the HTTP Content-Type header field</description> 
    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

    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>

    </note>



</usage>

</directivesynopsis>

<directivesynopsis>

docs/manual/mod/mod_mime.xml

+15 −0
Changes for docs/manual/mod/mod_mime.xml: 15 added lines, 0 removed lines.
Original line number Diff line number Diff line
@@ -606,6 +606,21 @@ type</description> 
    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

    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>

    </note>



</usage>

<seealso><directive module="core">ForceType</directive></seealso>

<seealso><module>mod_negotiation</module></seealso>