Document Roy's recent discovery that plain Alias/Redirect only

match complete path segments.  I haven't tested the examples,
but they seem to be right according to the code.

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

diff --git a/docs/manual/mod/mod_alias.xml b/docs/manual/mod/mod_alias.xml
index 2b40b8bc082c399723a7c2fdabd56ca8d988159f..bfc76a5d4bcd48fc1890e19e3ba48ffda453381d 100644 (file)
--- a/docs/manual/mod/mod_alias.xml
+++ b/docs/manual/mod/mod_alias.xml
@@ -113,7 +113,11 @@ ignored.</p>
     </example>
 
     <p>A request for http://myserver/image/foo.gif would cause the
-    server to return the file /ftp/pub/image/foo.gif.</p>
+    server to return the file /ftp/pub/image/foo.gif.  Only complete
+    path segments are matched, so the above alias would not match a
+    request for http://myserver/imagefoo.gif.  For more complex
+    matching using regular expressions, see the <directive
+    module="mod_alias">AliasMatch</directive> directive.</p>
 
     <p>Note that if you include a trailing / on the
     <var>url-path</var> then the server will require a trailing / in
@@ -206,7 +210,12 @@ a different URL</description>
 
     <p>If the client requests http://example.com/service/foo.txt, it
     will be told to access http://foo2.example.com/service/foo.txt
-    instead.</p>
+    instead.  Only complete path segments are matched, so the above
+    example would not match a request for
+    http://example.com/servicefoo.txt.  For more complex matching
+    using regular expressions, see the <directive
+    module="mod_alias">RedirectMatch</directive> directive.</p>
+
 
 <note><title>Note</title> <p>Redirect directives take precedence over
 Alias and ScriptAlias directives, irrespective of their ordering in