You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by co...@apache.org on 2016/08/23 00:15:45 UTC
svn commit: r1757289 - /httpd/httpd/trunk/docs/manual/mod/mod_rewrite.xml
Author: covener
Date: Tue Aug 23 00:15:44 2016
New Revision: 1757289
URL: http://svn.apache.org/viewvc?rev=1757289&view=rev
Log:
more PR60024 feedback re: consistent terminology.
Modified:
httpd/httpd/trunk/docs/manual/mod/mod_rewrite.xml
Modified: httpd/httpd/trunk/docs/manual/mod/mod_rewrite.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_rewrite.xml?rev=1757289&r1=1757288&r2=1757289&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_rewrite.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_rewrite.xml Tue Aug 23 00:15:44 2016
@@ -1057,18 +1057,17 @@ RewriteRule "^/$" "/hom
URL after the hostname and port, and before the query string (e.g. "/app1/index.html").
This is the (%-decoded) <a href="directive-dict.html#Syntax">URL-path</a>.</p></li>
- <li><p>In <directive module="core">Directory</directive> and htaccess context,
+ <li><p>In per-directory context (<directive module="core">Directory</directive> and .htaccess),
the <em>Pattern</em> is matched against only a partial path, for example a request
of "/app1/index.html" may result in comparison against "app1/index.html"
or "index.html" depending on where the <directive>RewriteRule</directive> is
defined.</p>
- <p>In this context, only the trailing portion of the currently mapped
- filesystem is compared against. The directory path where the rule is defined
- is stripped before comparison (up to and including a trailing slash).
+ <p>The directory path where the rule is defined is stripped from the currently mapped
+ filesystem path before comparison (up to and including a trailing slash).
The net result of this per-directory prefix stripping is that rules in
- this context only match against the portion of the currently mapped path
- "below" where they are defined.</p>
+ this context only match against the portion of the currently mapped filesystem path
+ "below" where the rule is defined.</p>
<p>Directives such as <directive
>DocumentRoot</directive> and <directive>Alias</directive>, or even the