]> granicus.if.org Git - apache/commitdiff
Slight clarification to the way rewrite works in per-directory context.
authorRich Bowen <rbowen@apache.org>
Wed, 26 Nov 2008 19:22:17 +0000 (19:22 +0000)
committerRich Bowen <rbowen@apache.org>
Wed, 26 Nov 2008 19:22:17 +0000 (19:22 +0000)
Suggested by Peter Kehl on the users mailing list.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@720955 13f79535-47bb-0310-9956-ffa450edef68

docs/manual/mod/mod_rewrite.html.en
docs/manual/mod/mod_rewrite.xml

index b2041606eab689bb8c4f8397ffb0a78758da20a2..679c5e701d3663110a19012db8c9dc6ce66d1e63 100644 (file)
@@ -215,7 +215,9 @@ Result:
               correct Apache internal processing. Because the
               per-directory rewriting comes late in the
               process, the rewritten request
-              has to be re-injected into the Apache kernel. 
+              has to be re-injected into the Apache kernel, as if it
+              were a new request. (See <a href="../rewrite/rewrite_tech.html">mod_rewrite technical
+              details</a>.)
               This is not the serious overhead it may seem to be - 
               this re-injection is completely internal to the 
               Apache server (and the same procedure is used by 
index 919f39870c3c238fe6368e804970ed8390040524..e16b7922fc08a4f12376dd667cc2357255b105e3 100644 (file)
@@ -631,7 +631,10 @@ Result:
               correct Apache internal processing. Because the
               per-directory rewriting comes late in the
               process, the rewritten request
-              has to be re-injected into the Apache kernel. 
+              has to be re-injected into the Apache kernel, as if it
+              were a new request. (See <a
+              href="../rewrite/rewrite_tech.html">mod_rewrite technical
+              details</a>.)
               This is not the serious overhead it may seem to be - 
               this re-injection is completely internal to the 
               Apache server (and the same procedure is used by