Adds a recommendation that rewrite logging be consulted for more details

on how rewrite is looking at URIs. refs https://issues.apache.org/bugzilla/show_bug.cgi?id=30021

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

diff --git a/docs/manual/rewrite/tech.html.en b/docs/manual/rewrite/tech.html.en
index 9d577b90cf4e57ab80926ccfc4a63f96a2bb4b76..1c1c92ebeef6184f914c2a41642e150d8afe4934 100644 (file)
--- a/docs/manual/rewrite/tech.html.en
+++ b/docs/manual/rewrite/tech.html.en
@@ -39,7 +39,7 @@ and URL matching.</p>
     content, and logging. (These is not an exhaustive list.)</p>
 
     <p>mod_rewrite acts in two of these phases (or "hooks", as they are
-    sometimes called) to influence how URLs may be rewritten.</p>
+    often called) to influence how URLs may be rewritten.</p>
 
     <p>First, it uses the URL-to-filename translation hook, which occurs
     after the HTTP request has been read, but before any authorization
@@ -104,6 +104,10 @@ and URL matching.</p>
 
     </table>
 
+    <p>For even more insight into how mod_rewrite manipulates URIs in
+    different contexts, you should consult the <a href="../mod/mod_rewrite.html#logging">log entries</a> made during 
+    rewriting.</p>
+
 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
 <div class="section">
 <h2><a name="InternalRuleset" id="InternalRuleset">Ruleset Processing</a></h2>

diff --git a/docs/manual/rewrite/tech.xml b/docs/manual/rewrite/tech.xml
index 5aa5408cba75c514cef98c6c2d68ae2c9a3cbcd1..835eafa6a910ac9652a64da7b94d8aa83dcb7d08 100644 (file)
--- a/docs/manual/rewrite/tech.xml
+++ b/docs/manual/rewrite/tech.xml
@@ -48,7 +48,7 @@ and URL matching.</p>
     content, and logging. (These is not an exhaustive list.)</p>
 
     <p>mod_rewrite acts in two of these phases (or "hooks", as they are
-    sometimes called) to influence how URLs may be rewritten.</p>
+    often called) to influence how URLs may be rewritten.</p>
 
     <p>First, it uses the URL-to-filename translation hook, which occurs
     after the HTTP request has been read, but before any authorization
@@ -114,6 +114,11 @@ and URL matching.</p>
 
     </table>
 
+    <p>For even more insight into how mod_rewrite manipulates URIs in
+    different contexts, you should consult the <a
+    href="../mod/mod_rewrite.html#logging">log entries</a> made during 
+    rewriting.</p>
+
 </section>
 
 <section id="InternalRuleset"><title>Ruleset Processing</title>