From ecb9f26d7755e3595e11d06fef512e9ed40c391c Mon Sep 17 00:00:00 2001
From: =?utf8?q?Igor=20Gali=C4=87?= <igalic@apache.org>
Date: Sun, 16 May 2010 11:07:59 +0000
Subject: [PATCH] Clarifying Redirect of GET/POST.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@944795 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/mod/mod_alias.html.en | 7 ++++++-
 docs/manual/mod/mod_alias.xml     | 7 ++++++-
 2 files changed, 12 insertions(+), 2 deletions(-)

diff --git a/docs/manual/mod/mod_alias.html.en b/docs/manual/mod/mod_alias.html.en
index a1cfd3614c..39e08574ca 100644
--- 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 9e4717d445..48ea9eebcb 100644
--- 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
-- 
2.50.1