Addresses https://bz.apache.org/bugzilla/show_bug.cgi?id=53108

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@1906615 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/rewrite/intro.xml b/docs/manual/rewrite/intro.xml
index 0a61d231ac49c6d9a9083dcfcbceb9ac87dd43d8..b624cad6cffa05eef6310c0e4b6cb9a83a0a5fd5 100644 (file)
--- a/docs/manual/rewrite/intro.xml
+++ b/docs/manual/rewrite/intro.xml
@@ -193,7 +193,7 @@ value.
 <p>The <var>Substitution</var> can itself be one of three things:</p>
 
 <dl>
-<dt>A full filesystem path to a resource</dt>
+<dt>1. A full filesystem path to a resource</dt>
 <dd>
 <example>
 RewriteRule ^/games.* /usr/local/games/web
@@ -202,7 +202,7 @@ RewriteRule ^/games.* /usr/local/games/web
 like the <directive module="mod_alias">Alias</directive> directive.</p>
 </dd>
 
-<dt>A web-path to a resource</dt>
+<dt>2. A web-path to a resource</dt>
 <dd>
 <example>
 RewriteRule ^/foo$ /bar
@@ -213,7 +213,7 @@ map requests for <code>http://example.com/foo</code> to the
 path <code>/usr/local/apache2/htdocs/bar</code>.</p>
 </dd>
 
-<dt>An absolute URL</dt>
+<dt>3. An absolute URL</dt>
 <dd>
 <example>
 RewriteRule ^/product/view$ http://site2.example.com/seeproduct.html [R]
@@ -222,6 +222,8 @@ RewriteRule ^/product/view$ http://site2.example.com/seeproduct.html [R]
 </dd>
 </dl>
 
+<note type="warning">Note that <strong>1</strong> and <strong>2</strong> have exactly the same syntax. The difference between them is that in the case of <strong>1</strong>, the top level of the target path (i.e., <code>/usr/</code>) exists on the filesystem, where as in the case of <strong>2</strong>, it does not. (i.e., there's no <code>/bar/</code> as a root-level directory in the filesystem.)</note>
+
 <p>The <var>Substitution</var> can also
 contain <em>back-references</em> to parts of the incoming URL-path
 matched by the <var>Pattern</var>. Consider the following:</p>