You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by hu...@apache.org on 2012/04/12 09:09:33 UTC
svn commit: r1325141 - /httpd/httpd/trunk/docs/manual/mod/mod_rewrite.xml
Author: humbedooh
Date: Thu Apr 12 07:09:33 2012
New Revision: 1325141
URL: http://svn.apache.org/viewvc?rev=1325141&view=rev
Log:
Fix up some wordings and grammar.
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=1325141&r1=1325140&r2=1325141&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_rewrite.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_rewrite.xml Thu Apr 12 07:09:33 2012
@@ -909,10 +909,11 @@ RewriteRule ^/$ /homepa
<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 applied to the (%-decoded)
- <a href="./directive-dict.html#Syntax">URL-path</a> of the request;
- subsequent patterns are applied to the output of the last matched
- RewriteRule.</p>
+ expression</a>. On the first RewriteRule that matches, it is applied to
+ 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 applied to the
+ output of the last matched 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,
@@ -921,7 +922,7 @@ RewriteRule ^/$ /homepa
<p>In <directive module="core">Directory</directive> and htaccess context,
the <em>Pattern</em> will initially be matched against the
- <em>filesystem</em> path, after removing the prefix that lead the server
+ <em>filesystem</em> path, after removing the prefix that led the server
to the current <directive>RewriteRule</directive> (e.g. "app1/index.html"
or "index.html" depending on where the directives are defined).</p>