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 14:16:12 UTC
svn commit: r1201691 - in /httpd/httpd/branches/2.4.x/docs/manual/rewrite:
tech.html.en tech.xml
Author: covener
Date: Mon Nov 14 13:16:11 2011
New Revision: 1201691
URL: http://svn.apache.org/viewvc?rev=1201691&view=rev
Log:
Merge r1201690 from trunk:
followups on PR52175
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=1201691&r1=1201690&r2=1201691&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 13:16:11 2011
@@ -66,12 +66,18 @@ and URL matching.</p>
<p>In per-directory context (i.e., within <code>.htaccess</code> files
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 the directory path (including a trailing slash)
- before applying the rules. ) If a substitution is made, a new internal
+ this, the URL-path that mod_rewrite initially compares <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> directives against
+ is the full filesystem path to the translated filename with the current
+ directories path (including a trailing slash) removed from the front.</p>
+
+ <p> To illustrate: If rules are in /var/www/foo/.htaccess and a request
+ for /foo/bar/baz is being processed, an expression like ^bar/baz$ would
+ match.</p>
+
+ <p> If a substitution is made in per-directory context, 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.
+ request phases. If the substitution is a relative path, the <code class="directive"><a href="../mod/mod_rewrite.html#rewritebase">RewriteBase</a></code> directive
+ determines the URL-path prefix prepended 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.
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=1201691&r1=1201690&r2=1201691&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 13:16:11 2011
@@ -76,13 +76,20 @@ and URL matching.</p>
<p>In per-directory context (i.e., within <code>.htaccess</code> files
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 the directory path (including a trailing slash)
- before applying the rules. ) If a substitution is made, a new internal
+ this, the URL-path that mod_rewrite initially compares <directive
+ module="mod_rewrite">RewriteRule</directive> directives against
+ is the full filesystem path to the translated filename with the current
+ directories path (including a trailing slash) removed from the front.</p>
+
+ <p> To illustrate: If rules are in /var/www/foo/.htaccess and a request
+ for /foo/bar/baz is being processed, an expression like ^bar/baz$ would
+ match.</p>
+
+ <p> If a substitution is made in per-directory context, 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
+ request phases. If the substitution is a relative path, the <directive
module="mod_rewrite">RewriteBase</directive> directive
- determines the URL-path prefix appended to the substitution.
+ determines the URL-path prefix prepended 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.