From 6d61d34e8923795653031c0bdfa982820da6818f Mon Sep 17 00:00:00 2001 From: Rainer Jung Date: Tue, 22 Jan 2019 10:09:58 +0000 Subject: [PATCH] Xforms. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1851800 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/core.html.en | 19 +++++++++++++++++++ docs/manual/mod/core.html.fr.utf8 | 2 ++ docs/manual/mod/core.html.tr.utf8 | 1 + 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.meta | 4 ++-- docs/manual/mod/core.xml.tr | 2 +- docs/manual/mod/mod_ssl.html.en | 18 +++++++++++++++++- 10 files changed, 46 insertions(+), 8 deletions(-) diff --git a/docs/manual/mod/core.html.en b/docs/manual/mod/core.html.en index d41c80966f8..74644d8240a 100644 --- a/docs/manual/mod/core.html.en +++ b/docs/manual/mod/core.html.en @@ -3122,6 +3122,25 @@ matching URLs </LocationMatch> +

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. + The <LocationMatch> + directive and the regex version of <Location> require you to explicitly specify multiple + slashes if that is your intention.

+ +

For example, <LocationMatch "^/abc"> would match + the request URL /abc but not the request URL + //abc. The (non-regex) <Location> directive behaves similarly when used for + proxy requests. But when (non-regex) <Location> is used for non-proxy requests it will + implicitly match multiple slashes with a single slash. For example, + if you specify <Location "/abc/def"> and the + request is to /abc//def then it will match.

+
+

See also