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 2011/11/14 02:58:59 UTC

svn commit: r1201572 - in /httpd/httpd/branches/2.4.x/docs/manual/rewrite: tech.html.en tech.xml

Author: covener
Date: Mon Nov 14 01:58:59 2011
New Revision: 1201572

URL: http://svn.apache.org/viewvc?rev=1201572&view=rev
Log:
Merge r1201571 from trunk:

PR52175: RewriteBase is what applies to relative substitutions, not
the stripping of the per-directory prefix.


Reviewed by: covener

Modified:
    httpd/httpd/branches/2.4.x/docs/manual/rewrite/tech.html.en
    httpd/httpd/branches/2.4.x/docs/manual/rewrite/tech.xml

Modified: httpd/httpd/branches/2.4.x/docs/manual/rewrite/tech.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/rewrite/tech.html.en?rev=1201572&r1=1201571&r2=1201572&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/rewrite/tech.html.en (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/rewrite/tech.html.en Mon Nov 14 01:58:59 2011
@@ -67,11 +67,12 @@ and URL matching.</p>
     and <code>Directory</code> blocks), these rules are being applied
     after a URL has already been translated to a filename. Because of
     this, mod_rewrite temporarily translates the filename back into a URL,
-    by stripping off directory path before appling the rules. (See the
-    <code class="directive"><a href="../mod/mod_rewrite.html#rewritebase">RewriteBase</a></code> directive to
-    see how you can further manipulate how this is handled.) If a substitution
-    is made, a new internal subrequest is issued with the new URL, which restarts
-    processing of the request phases. In this context, care must be taken to 
+    by stripping off the directory path (including a trailing slash) 
+    before applying the rules. ) If a substitution is made, a new internal 
+    subrequest is issued with the new URL, which restarts processing of the 
+    request phases. If the substution is a relative path, the <code class="directive"><a href="../mod/mod_rewrite.html#rewritebase">RewriteBase</a></code> directive 
+    determines the URL-path prefix appended to the substitution.
+    In per-directory context, care must be taken to 
     create rules which will eventually (in some future "round" of per-directory
     rewrite processing) not perform a substitution to avoid looping.
     (See <a href="http://wiki.apache.org/httpd/RewriteLooping">RewriteLooping</a>

Modified: httpd/httpd/branches/2.4.x/docs/manual/rewrite/tech.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/rewrite/tech.xml?rev=1201572&r1=1201571&r2=1201572&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/rewrite/tech.xml (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/rewrite/tech.xml Mon Nov 14 01:58:59 2011
@@ -77,11 +77,13 @@ and URL matching.</p>
     and <code>Directory</code> blocks), these rules are being applied
     after a URL has already been translated to a filename. Because of
     this, mod_rewrite temporarily translates the filename back into a URL,
-    by stripping off directory path before appling the rules. (See the
-    <directive module="mod_rewrite">RewriteBase</directive> directive to
-    see how you can further manipulate how this is handled.) If a substitution
-    is made, a new internal subrequest is issued with the new URL, which restarts
-    processing of the request phases. In this context, care must be taken to 
+    by stripping off the directory path (including a trailing slash) 
+    before applying the rules. ) If a substitution is made, a new internal 
+    subrequest is issued with the new URL, which restarts processing of the 
+    request phases. If the substution is a relative path, the <directive 
+    module="mod_rewrite">RewriteBase</directive> directive 
+    determines the URL-path prefix appended to the substitution.
+    In per-directory context, care must be taken to 
     create rules which will eventually (in some future "round" of per-directory
     rewrite processing) not perform a substitution to avoid looping.
     (See <a href="http://wiki.apache.org/httpd/RewriteLooping">RewriteLooping</a>