From: Eric Covener Date: Thu, 3 Jun 2021 12:29:28 +0000 (+0000) Subject: xform X-Git-Tag: 2.5.0-alpha2-ci-test-only~930 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7df1cef1a2b2303050cd52b536bcce15330f73be;p=thirdparty%2Fapache%2Fhttpd.git xform git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1890426 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/core.html.en.utf8 b/docs/manual/mod/core.html.en.utf8 index 6f7db58c5d8..4612afa7a6d 100644 --- a/docs/manual/mod/core.html.en.utf8 +++ b/docs/manual/mod/core.html.en.utf8 @@ -3141,10 +3141,12 @@ URLs URL it appears. People may be used to its behavior in the filesystem where multiple adjacent slashes are frequently collapsed to a single slash (i.e., /home///foo is the same as - /home/foo). In URL-space this is not necessarily true. + /home/foo). In URL-space this is not necessarily true if + directive MergeSlashes has been set + to "OFF". The <LocationMatch> directive and the regex version of <Location> require you to explicitly specify multiple - slashes if that is your intention.

+ slashes if the slashes are not being merged.

For example, <LocationMatch "^/abc"> would match the request URL /abc but not the request URL @@ -3209,15 +3211,17 @@ matching URLs </LocationMatch> -

Note about / (slash)

+

Note about / (slash)

The slash character has special meaning depending on where in a URL it appears. People may be used to its behavior in the filesystem where multiple adjacent slashes are frequently collapsed to a single slash (i.e., /home///foo is the same as - /home/foo). In URL-space this is not necessarily true. + /home/foo). In URL-space this is not necessarily true if + directive MergeSlashes has been set + to "OFF". The <LocationMatch> directive and the regex version of <Location> require you to explicitly specify multiple - slashes if that is your intention.

+ slashes if the slashes are not being merged.

For example, <LocationMatch "^/abc"> would match the request URL /abc but not the request URL @@ -3643,11 +3647,13 @@ resource significant. However, URL's handled other ways, such as by CGI or proxy, might prefer to retain the significance of multiple consecutive slashes. In these cases MergeSlashes can be set to - OFF to retain the multiple consecutive slashes. In these - configurations, regular expressions used in the configuration file that match + OFF to retain the multiple consecutive slashes, which is the legacy behavior.

+

+ When set to "OFF", regular expressions used in the configuration file that match the path component of the URL (LocationMatch, RewriteRule, ...) need to take into account multiple - consecutive slashes.

+ consecutive slashes. Non regular expression based Location always + operate against a URL with merged slashes and cannot differentiate between multiple slashes.

top
@@ -4089,10 +4095,13 @@ directory The protocol is used to determine which module should handle a request and to apply protocol specific optimizations with the AcceptFilter directive.

- -

You only need to set the protocol if you are running on non-standard ports; - otherwise, http is assumed for port 80 and https - for port 443.

+ +

This directive not required for most + configurations. If not specified, https is the default for + port 443 and http the default for all other ports. The + protocol is used to determine which module should handle a request, and + to apply protocol specific optimizations with the + AcceptFilter directive.

For example, if you are running https on a non-standard port, specify the protocol explicitly:

@@ -4490,16 +4499,16 @@ of a request or the last 63, assuming the request itself is greater than Status:Core Module:core -

mod_status with ExtendedStatus On +

mod_status with ExtendedStatus On displays the actual request being handled. For historical purposes, only 63 characters of the request are actually stored for display purposes. This directive - controls whether the 1st 63 characters are stored (the previous + controls whether the first 63 characters are stored (the previous behavior and the default) or if the last 63 characters are. This is only applicable, of course, if the length of the request is 64 characters or greater.

-

If Apache httpd is handling GET /disk1/storage/apache/htdocs/images/imagestore1/food/apples.jpg HTTP/1.1 mod_status displays as follows: +

If Apache httpd is handling GET /disk1/storage/apache/htdocs/images/imagestore1/food/apples.jpg HTTP/1.1 mod_status displays as follows:

@@ -5383,7 +5392,7 @@ var comments_identifier = 'http://httpd.apache.org/docs/trunk/mod/core.html'; } })(window, document); //-->