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.
+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.
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.