diff options
| author | Eric Covener <covener@apache.org> | 2010-11-30 22:09:06 +0000 |
|---|---|---|
| committer | Eric Covener <covener@apache.org> | 2010-11-30 22:09:06 +0000 |
| commit | c03ff50c16ffe4cc7dd967a6b754d213d64302c0 (patch) | |
| tree | 133e68edf899571cffff1f4b9fcfb0be87c2a0e5 /docs/manual/mod | |
| parent | 09aef046e912f91ccee4424d743a6a5ba6e93230 (diff) | |
| download | httpd-c03ff50c16ffe4cc7dd967a6b754d213d64302c0.tar.gz | |
PR50375: <Location> has bad example in sections.xml and never actually explains what's matched
in core.xml.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1040808 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'docs/manual/mod')
| -rw-r--r-- | docs/manual/mod/core.xml | 30 |
1 files changed, 29 insertions, 1 deletions
diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml index b75f715a2b..fd40492e12 100644 --- a/docs/manual/mod/core.xml +++ b/docs/manual/mod/core.xml @@ -1081,7 +1081,7 @@ in case of an error</description> anyone other than the user that starts the server.</p> <note type="warning"><title>Note</title> <p>When entering a file path on non-Unix platforms, care should be taken - to make sure that only forward slashed are used even though the platform + to make sure that only forward slashes are used even though the platform may allow the use of back slashes. In general it is a good idea to always use forward slashes throughout the configuration files.</p> </note> @@ -2287,6 +2287,34 @@ URLs</description> locations. Since several different URLs may map to the same filesystem location, such access controls may by circumvented.</p> + <p>The enclosed directives will be applied to the request if the path component + of the URL meets <em>any</em> of the following criteria: + <ul> + <li>The specified location matches exactly the path component of the URL. + </li> + <li>The specified location, which ends in a forward slash, is a prefix + of the path component of the URL (treated as a context root). + </li> + <li>The specified location, with the addition of a trailing slash, is a + prefix of the path component of the URL (also treated as a context root). + </li> + </ul> + In the example below, where no trailing slash is used, requests to + /private1, /private1/ and /private1/file.txt will have the enclosed + directives applied, but /private1other would not. + <example> + <Location /private1> + ... + </example> + In the example below, where a trailing slash is used, requests to + /private2/ and /private2/file.txt will have the enclosed + directives applied, but /private2 and /private2other would not. + <example> + <Location /private2<em>/</em>> + ... + </example> + </p> + <note><title>When to use <directive type="section">Location</directive></title> |