From: Eric Covener
Date: Tue, 6 Nov 2012 18:25:47 +0000 (+0000)
Subject: comment#435 -- Redirect didn't always take a url-path in 2.2.x
X-Git-Tag: 2.2.24~98
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=32331680551b2b9fb8a6482088148719ae7cfb2d;p=thirdparty%2Fapache%2Fhttpd.git
comment#435 -- Redirect didn't always take a url-path in 2.2.x
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@1406262 13f79535-47bb-0310-9956-ffa450edef68
---
diff --git a/docs/manual/mod/mod_alias.xml b/docs/manual/mod/mod_alias.xml
index 18a15cf25eb..a2e18ae2ec5 100644
--- a/docs/manual/mod/mod_alias.xml
+++ b/docs/manual/mod/mod_alias.xml
@@ -254,6 +254,8 @@ a different URL
server configvirtual host
directory.htaccess
FileInfo
+Support for specifying a URL-path as the final argument was
+added in Apache HTTP Server 2.2.6
The Redirect directive maps an old URL into a new one by asking
@@ -262,9 +264,9 @@ a different URL
The old URL-path is a case-sensitive (%-decoded) path
beginning with a slash. A relative path is not allowed. The new
URL 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
- be added.
+ hostname. In Apache HTTP Server 2.2.6 and later, a URL-path beginning
+ with a slash may also be used, in which case the scheme and hostname
+ of the current server will be added.
Then any request beginning with URL-path will return a
redirect request to the client at the location of the target