Clarifying Redirect of GET/POST.

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

diff --git a/docs/manual/mod/mod_alias.html.en b/docs/manual/mod/mod_alias.html.en
index a1cfd3614ccd25372b9ec77283a36d94bdf1f975..39e08574caeb2d14ac2cd1236e1f4f01f7e82d0c 100644 (file)
--- a/docs/manual/mod/mod_alias.html.en
+++ b/docs/manual/mod/mod_alias.html.en
@@ -290,7 +290,12 @@ a different URL</td></tr>
     <p>If the client requests <code>http://example.com/service/foo.txt</code>,
     it will be told to access
     <code>http://foo2.example.com/service/foo.txt</code>
-    instead.  Only complete path segments are matched, so the above
+       instead. This includes requests with <code>GET</code> parameters, such as
+    <code>http://example.com/service/foo.pl?q=23&amp;a=42</code>,
+    it will be redirected to 
+    <code>http://foo2.example.com/service/foo.pl?q=23&amp;a=42</code>.
+       Note that <code>POST</code>s will be discarded.<br />
+       Only complete path segments are matched, so the above
     example would not match a request for
     <code>http://example.com/servicefoo.txt</code>.  For more complex matching
     using regular expressions, see the <code class="directive"><a href="#redirectmatch">RedirectMatch</a></code> directive.</p>

diff --git a/docs/manual/mod/mod_alias.xml b/docs/manual/mod/mod_alias.xml
index 9e4717d445c4b3e6946b7468c606123777498fe2..48ea9eebcb1f162bfb355b548d1e9bf63dc23471 100644 (file)
--- a/docs/manual/mod/mod_alias.xml
+++ b/docs/manual/mod/mod_alias.xml
@@ -280,7 +280,12 @@ a different URL</description>
     <p>If the client requests <code>http://example.com/service/foo.txt</code>,
     it will be told to access
     <code>http://foo2.example.com/service/foo.txt</code>
-    instead.  Only complete path segments are matched, so the above
+       instead. This includes requests with <code>GET</code> parameters, such as
+    <code>http://example.com/service/foo.pl?q=23&amp;a=42</code>,
+    it will be redirected to 
+    <code>http://foo2.example.com/service/foo.pl?q=23&amp;a=42</code>.
+       Note that <code>POST</code>s will be discarded.<br />
+       Only complete path segments are matched, so the above
     example would not match a request for
     <code>http://example.com/servicefoo.txt</code>.  For more complex matching
     using regular expressions, see the <directive