From e62bccb24df0a64ddf04193ab1f29e2dcb812e2c Mon Sep 17 00:00:00 2001 From: Eric Covener Date: Wed, 22 Apr 2015 20:28:29 +0000 Subject: [PATCH] xforms git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1675493 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/core.html.en | 20 +++++++++++++++----- docs/manual/mod/core.xml.de | 2 +- docs/manual/mod/core.xml.es | 2 +- docs/manual/mod/core.xml.fr | 2 +- docs/manual/mod/core.xml.ja | 2 +- docs/manual/mod/core.xml.tr | 2 +- docs/manual/mod/mod_authnz_ldap.xml.fr | 2 +- docs/manual/mod/mod_mime.html.en | 19 ++++++++++++++----- docs/manual/mod/mod_mime.xml.ja | 2 +- 9 files changed, 36 insertions(+), 17 deletions(-) diff --git a/docs/manual/mod/core.html.en b/docs/manual/mod/core.html.en index 7c172ce142..83adf96e9a 100644 --- a/docs/manual/mod/core.html.en +++ b/docs/manual/mod/core.html.en @@ -1880,18 +1880,28 @@ 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

+

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. + directives is instead set to 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 + (such as mod_php) may look for a "synthetic" content type used only to + signal the module to take responsibility for the matching request. +

+ +

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

+ AddHandler should + restrict access to this directive as well.

diff --git a/docs/manual/mod/core.xml.de b/docs/manual/mod/core.xml.de index a95b5437a0..b4a14b8b79 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/core.xml.ja b/docs/manual/mod/core.xml.ja index 8c1b717751..b2cbbacf6b 100644 --- a/docs/manual/mod/core.xml.ja +++ b/docs/manual/mod/core.xml.ja @@ -1,7 +1,7 @@ - + + + diff --git a/docs/manual/mod/mod_mime.html.en b/docs/manual/mod/mod_mime.html.en index de87ca97c0..21e4e0d712 100644 --- a/docs/manual/mod/mod_mime.html.en +++ b/docs/manual/mod/mod_mime.html.en @@ -596,17 +596,26 @@ type

Note

+

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. + directives is instead set to 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 + (such as mod_php) may look for a "synthetic" content type used only to + signal the module to take responsibility for the matching request. +

+ +

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

+ AddHandler should + restrict access to this directive as well.

diff --git a/docs/manual/mod/mod_mime.xml.ja b/docs/manual/mod/mod_mime.xml.ja index 05d433f98d..a1b394bf40 100644 --- a/docs/manual/mod/mod_mime.xml.ja +++ b/docs/manual/mod/mod_mime.xml.ja @@ -1,7 +1,7 @@ - +