You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by sl...@apache.org on 2005/08/26 19:54:49 UTC
svn commit: r240299 - in /httpd/httpd/trunk/docs/manual/mod:
mod_alias.html.en mod_alias.xml
Author: slive
Date: Fri Aug 26 10:54:49 2005
New Revision: 240299
URL: http://svn.apache.org/viewcvs?rev=240299&view=rev
Log:
Make the arguments to the redirect directive clearer.
PR: 36166
Modified:
httpd/httpd/trunk/docs/manual/mod/mod_alias.html.en
httpd/httpd/trunk/docs/manual/mod/mod_alias.xml
Modified: httpd/httpd/trunk/docs/manual/mod/mod_alias.html.en
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/mod/mod_alias.html.en?rev=240299&r1=240298&r2=240299&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_alias.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_alias.html.en Fri Aug 26 10:54:49 2005
@@ -193,27 +193,32 @@
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Base</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_alias</td></tr>
</table>
- <p>The Redirect directive maps an old URL into a new one. The
- new URL is returned to the client which attempts to fetch it
- again with the new address. <var>URL-path</var> a (%-decoded)
- path; any requests for documents beginning with this path will
- be returned a redirect error to a new (%-encoded) URL beginning
- with <var>URL</var>.</p>
+ <p>The Redirect directive maps an old URL into a new one by asking
+ the client to refetch the resource at the new location.</p>
+
+ <p>The old <em>URL-path</em> is a (%-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 be
+ added.</p>
+
+ <p>Then any request beginning with <em>URL-Path</em> will return a
+ redirect request to the client at the location of the target
+ <em>URL</em>. Additional path information beyond the matched
+ <em>URL-Path</em> will be appended to the target URL.</p>
<div class="example"><h3>Example:</h3><p><code>
- Redirect /service http://foo2.bar.com/service
+ Redirect /service http://foo2.example.com/service
</code></p></div>
- <p>If the client requests http://myserver/service/foo.txt, it
- will be told to access http://foo2.bar.com/service/foo.txt
+ <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>
<div class="note"><h3>Note</h3> <p>Redirect directives take precedence over
Alias and ScriptAlias directives, irrespective of their ordering in
-the configuration file. Also, <var>URL-path</var> must be a fully
-qualified URL, not a relative path, even when used with .htaccess files or
-inside of <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code>
-sections.</p></div>
+the configuration file.</p></div>
<p>If no <var>status</var> argument is given, the redirect will
be "temporary" (HTTP status 302). This indicates to the client
Modified: httpd/httpd/trunk/docs/manual/mod/mod_alias.xml
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/mod/mod_alias.xml?rev=240299&r1=240298&r2=240299&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_alias.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_alias.xml Fri Aug 26 10:54:49 2005
@@ -184,27 +184,32 @@
<override>FileInfo</override>
<usage>
- <p>The Redirect directive maps an old URL into a new one. The
- new URL is returned to the client which attempts to fetch it
- again with the new address. <var>URL-path</var> a (%-decoded)
- path; any requests for documents beginning with this path will
- be returned a redirect error to a new (%-encoded) URL beginning
- with <var>URL</var>.</p>
+ <p>The Redirect directive maps an old URL into a new one by asking
+ the client to refetch the resource at the new location.</p>
+
+ <p>The old <em>URL-path</em> is a (%-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 be
+ added.</p>
+
+ <p>Then any request beginning with <em>URL-Path</em> will return a
+ redirect request to the client at the location of the target
+ <em>URL</em>. Additional path information beyond the matched
+ <em>URL-Path</em> will be appended to the target URL.</p>
<example><title>Example:</title>
- Redirect /service http://foo2.bar.com/service
+ Redirect /service http://foo2.example.com/service
</example>
- <p>If the client requests http://myserver/service/foo.txt, it
- will be told to access http://foo2.bar.com/service/foo.txt
+ <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>
<note><title>Note</title> <p>Redirect directives take precedence over
Alias and ScriptAlias directives, irrespective of their ordering in
-the configuration file. Also, <var>URL-path</var> must be a fully
-qualified URL, not a relative path, even when used with .htaccess files or
-inside of <directive type="section" module="core">Directory</directive>
-sections.</p></note>
+the configuration file.</p></note>
<p>If no <var>status</var> argument is given, the redirect will
be "temporary" (HTTP status 302). This indicates to the client