From 89b4dc788367c1ba18ed890df6fe11e9cc84dd3a Mon Sep 17 00:00:00 2001 From: Eric Covener Date: Wed, 22 Apr 2015 17:27:13 +0000 Subject: [PATCH] xforms git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1675433 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/core.html.en | 14 ++++++++++++++ docs/manual/mod/core.xml.de | 2 +- docs/manual/mod/core.xml.es | 2 +- docs/manual/mod/core.xml.ja | 2 +- docs/manual/mod/core.xml.tr | 2 +- docs/manual/mod/mod_mime.html.en | 15 +++++++++++++++ docs/manual/mod/mod_mime.xml.fr | 2 +- docs/manual/mod/mod_mime.xml.ja | 2 +- 8 files changed, 35 insertions(+), 6 deletions(-) diff --git a/docs/manual/mod/core.html.en b/docs/manual/mod/core.html.en index 163c62474f3..1f16b4888e1 100644 --- a/docs/manual/mod/core.html.en +++ b/docs/manual/mod/core.html.en @@ -1866,6 +1866,20 @@ media type in the HTTP Content-Type header field static files, where the generator of the response typically specifies a Content-Type, this directive has no effect.

+

Note

+

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.

+
+
top
diff --git a/docs/manual/mod/core.xml.de b/docs/manual/mod/core.xml.de index a00988ec976..dbae269f80c 100644 --- a/docs/manual/mod/core.xml.de +++ b/docs/manual/mod/core.xml.de @@ -1,7 +1,7 @@ - + + + + + diff --git a/docs/manual/mod/mod_mime.xml.ja b/docs/manual/mod/mod_mime.xml.ja index 9a3efa41cd8..0a7cc3ac5ea 100644 --- a/docs/manual/mod/mod_mime.xml.ja +++ b/docs/manual/mod/mod_mime.xml.ja @@ -1,7 +1,7 @@ - +