Clarifies (I hope) what RewriteRule patterns are matched against. See

bz53153 for context.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1673529 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/mod_rewrite.xml b/docs/manual/mod/mod_rewrite.xml
index 99d8a406da7f143573e61c07902aa4dcce208b0b..75f35a43db774ed31cb0d6676d460312c679de4d 100644 (file)
--- a/docs/manual/mod/mod_rewrite.xml
+++ b/docs/manual/mod/mod_rewrite.xml
@@ -1013,10 +1013,11 @@ RewriteRule  ^/$                 /homepage.std.html  [L]
       <p><a id="patterns" name="patterns"><em>Pattern</em></a> is
       a perl compatible <a id="regexp" name="regexp">regular
       expression</a>. On the first RewriteRule, it is matched against
-      the (%-decoded) <a href="./directive-dict.html#Syntax">URL-path</a> (or 
-      <a href="./directive-dict.html#Syntax">file-path</a>, depending 
-      on the context) of the request. Subsequent patterns are matched against the 
-      output of the last matching RewriteRule.</p>
+      the (%-decoded) <a href="directive-dict.html#Syntax">URL-path</a>
+      of the request, or, in per-directory context (see below), the URL
+      path relative to that per-directory context. Subsequent patterns
+      are matched against the output of the last matching RewriteRule.</p>
+
 
 <note><title><a id="what_is_matched" name="what_is_matched">What is matched?</a></title>
       <p>In <directive module="core">VirtualHost</directive> context,