Clarify that the target of a Redirect may be either a full URL including

scheme and hostname, or just a URI path beginning with a slash.

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

diff --git a/docs/manual/mod/mod_alias.html.en b/docs/manual/mod/mod_alias.html.en
index 14c5b2e7b74f5609e56c4eafe674d7bc58a7ffd8..e5ec8e5b209e8c9a2f29dced4399d5eca44999f6 100644 (file)
--- a/docs/manual/mod/mod_alias.html.en
+++ b/docs/manual/mod/mod_alias.html.en
@@ -214,10 +214,11 @@ a different URL</td></tr>
     the client to refetch the resource at the new location.</p>
 
     <p>The old <em>URL-path</em> is a case-sensitive (%-decoded) path
-    beginning with a slash.  A relative path is not allowed.  The new
-    <em>URL</em> should be an absolute URL beginning with a scheme and
-    hostname, but a URL-path beginning with a slash may also be used,
-    in which case the scheme and hostname of the current server will
+    beginning with a slash.  A relative path is not allowed.</p>
+    
+    <p>The new <em>URL</em> may be either an absolute URL beginning 
+    with a scheme and hostname, or a URL-path beginning with a slash.
+    In this latter case the scheme and hostname of the current server will
     be added.</p>
 
     <p>Then any request beginning with <em>URL-Path</em> will return a
@@ -226,7 +227,10 @@ a different URL</td></tr>
     <em>URL-Path</em> will be appended to the target URL.</p>
 
     <div class="example"><h3>Example:</h3><p><code>
-      Redirect /service http://foo2.example.com/service
+      Redirect /service http://foo2.example.com/service<br />
+      <br />
+      # Redirect to a URL on the same host<br />
+      Redirect /one /two
     </code></p></div>
 
     <p>If the client requests <code>http://example.com/service/foo.txt</code>,

diff --git a/docs/manual/mod/mod_alias.xml b/docs/manual/mod/mod_alias.xml
index c4ade0965582c19c85c76a34c515357576560ff1..cc5f1615d1bba8b377c5fdcbc14b9971748e2659 100644 (file)
--- a/docs/manual/mod/mod_alias.xml
+++ b/docs/manual/mod/mod_alias.xml
@@ -205,10 +205,11 @@ a different URL</description>
     the client to refetch the resource at the new location.</p>
 
     <p>The old <em>URL-path</em> is a case-sensitive (%-decoded) path
-    beginning with a slash.  A relative path is not allowed.  The new
-    <em>URL</em> should be an absolute URL beginning with a scheme and
-    hostname, but a URL-path beginning with a slash may also be used,
-    in which case the scheme and hostname of the current server will
+    beginning with a slash.  A relative path is not allowed.</p>
+    
+    <p>The new <em>URL</em> may be either an absolute URL beginning 
+    with a scheme and hostname, or a URL-path beginning with a slash.
+    In this latter case the scheme and hostname of the current server will
     be added.</p>
 
     <p>Then any request beginning with <em>URL-Path</em> will return a
@@ -217,7 +218,10 @@ a different URL</description>
     <em>URL-Path</em> will be appended to the target URL.</p>
 
     <example><title>Example:</title>
-      Redirect /service http://foo2.example.com/service
+      Redirect /service http://foo2.example.com/service<br />
+      <br />
+      # Redirect to a URL on the same host<br />
+      Redirect /one /two
     </example>
 
     <p>If the client requests <code>http://example.com/service/foo.txt</code>,