From b02c38bdebc2b8c983674bce536a6ff4c3eec118 Mon Sep 17 00:00:00 2001 From: Eric Covener Date: Sun, 10 May 2015 15:38:52 +0000 Subject: [PATCH] xforms git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1678568 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mod_mime.html.en | 28 ++++++++++++++++++---------- 1 file changed, 18 insertions(+), 10 deletions(-) diff --git a/docs/manual/mod/mod_mime.html.en b/docs/manual/mod/mod_mime.html.en index d446352d0b..238c7e7998 100644 --- a/docs/manual/mod/mod_mime.html.en +++ b/docs/manual/mod/mod_mime.html.en @@ -597,17 +597,25 @@ type

Note

-

When explicit directives such as - SetHandler or - AddHandler do not apply +

If no handler is explicitly set for a request, the specified content + type will also be used as the handler name.

+ +

When explicit directives such as + SetHandler or + AddHandler 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 - SetHandler or - AddHandler.

+ directives is instead set to the content type specified by this directive. +

+

+ This is a historical behavior that may be used by some third-party modules + (such as mod_php) for taking responsibility for the matching request. +

+ +

Configurations that rely on such "synthetic" types should be avoided. + Additionally, configurations that restrict access to + SetHandler or + AddHandler should + restrict access to this directive as well.

-- 2.40.0