From: Rich Bowen <rbowen@apache.org>
Date: Mon, 10 Oct 2011 13:06:56 +0000 (+0000)
Subject: Adds a recommendation that rewrite logging be consulted for more details
X-Git-Tag: 2.3.15~135
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=fa2106252c977fef478c9b711bf35b530a60f298;p=thirdparty%2Fapache%2Fhttpd.git

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 9d577b90cf4..1c1c92ebeef 100644
--- 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 5aa5408cba7..835eafa6a91 100644
--- 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>