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/13 17:56:46 UTC
svn commit: r1201456 - in /httpd/httpd/branches/2.4.x/docs/manual/rewrite:
tech.html.en tech.xml
Author: covener
Date: Sun Nov 13 16:56:46 2011
New Revision: 1201456
URL: http://svn.apache.org/viewvc?rev=1201456&view=rev
Log:
Merge r1201455 from trunk:
clarify looping issue for PR52171.
-This line, and those below, will be ignored--
M rewrite/tech.html.en
M rewrite/tech.xml
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=1201456&r1=1201455&r2=1201456&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 Sun Nov 13 16:56:46 2011
@@ -69,11 +69,13 @@ and URL matching.</p>
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.) Then, a new
- internal subrequest is issued with the new URL. This restarts
- processing of the request phases. (Be careful to avoid rules that
- can cause looping. See <a href="http://wiki.apache.org/httpd/RewriteLooping">RewriteLooping</a>
- for further discussion of this problem.</p>
+ 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
+ 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>
+ for further discussion of this problem.)</p>
<p>Because of this further manipulation of the URL in per-directory
context, you'll need to take care to craft your rewrite rules
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=1201456&r1=1201455&r2=1201456&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 Sun Nov 13 16:56:46 2011
@@ -79,11 +79,13 @@ and URL matching.</p>
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.) Then, a new
- internal subrequest is issued with the new URL. This restarts
- processing of the request phases. (Be careful to avoid rules that
- can cause looping. See <a href="http://wiki.apache.org/httpd/RewriteLooping">RewriteLooping</a>
- for further discussion of this problem.</p>
+ 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
+ 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>
+ for further discussion of this problem.)</p>
<p>Because of this further manipulation of the URL in per-directory
context, you'll need to take care to craft your rewrite rules