www/apache
1
0
Fork 0
mirror of https://github.com/apache/httpd.git synced 2025-07-30 20:03:10 +03:00
Code Activity

xforms

Browse Source 
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1675493 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Eric Covener
2015-04-22 20:28:29 +00:00
parent 1c92bd5a1c
commit e62bccb24d
9 changed files with 36 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
docs/manual/mod/mod_mime.html.en
View File

@ -596,17 +596,26 @@ type</td></tr>
<div class="note"><h3>Note</h3>
<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
<code class="directive"><a href="../mod/core.html#sethandler">SetHandler</a></code> or
<code class="directive"><a href="#addhandler">AddHandler</a></code> 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>
<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
<code class="directive"><a href="../mod/core.html#sethandler">SetHandler</a></code> or
<code class="directive"><a href="#addhandler">AddHandler</a></code>. </p>
<code class="directive"><a href="#addhandler">AddHandler</a></code> should
restrict access to this directive as well.</p>
</div>