<section id="order"><title>Order of Processing</title>
-<p>Aliases and Redirects occuring in different contexts are processed
-like other directives according to standard <a
-href="../sections.html#mergin">merging rules</a>. But when multiple
-Aliases or Redirects occur in the same context (for example, in the
-same <directive type="section" module="core">VirtualHost</directive>
-section) they are processed in a particular order.</p>
-
-<p>First, all Redirects are processed before Aliases are processed,
-and therefore a request that matches a <directive
-module="mod_alias">Redirect</directive> or <directive
-module="mod_alias">RedirectMatch</directive> will never have Aliases
-applied. Second, the Aliases and Redirects are processed in the order
-they appear in the configuration files, with the first match taking
-precedence.</p>
-
-<p>For this reason, when two or more of these directives apply to the
-same sub-path, you must list the most specific path first in order for
-all the directives to have an effect. For example, the following
-configuration will work as expected:</p>
-
-<example>
-Alias /foo/bar /baz<br />
-Alias /foo /gaq
-</example>
-
-<p>But if the above two directives were reversed in order, the
-<code>/foo</code> <directive module="mod_alias">Alias</directive>
-would always match before the <code>/foo/bar</code> <directive
-module="mod_alias">Alias</directive>, so the latter directive would be
-ignored.</p>
+
<p>Aliases and Redirects occuring in different contexts are processed
+
like other directives according to standard <a
+ href="../sections.html#mergin">merging rules</a>. But when multiple
+ Aliases or Redirects occur in the same context (for example, in the
+ same <directive type="section" module="core">VirtualHost</directive>
+ section) they are processed in a particular order.</p>
+
+
<p>First, all Redirects are processed before Aliases are processed,
+ and therefore a request that matches a <directive
+ module="mod_alias">Redirect</directive> or <directive
+ module="mod_alias">RedirectMatch</directive> will never have Aliases
+ applied. Second, the Aliases and Redirects are processed in the order
+ they appear in the configuration files, with the first match taking
+ precedence.</p>
+
+
<p>For this reason, when two or more of these directives apply to the
+ same sub-path, you must list the most specific path first in order for
+ all the directives to have an effect. For example, the following
+ configuration will work as expected:</p>
+
+ <example>
+ Alias /foo/bar /baz<br />
+ Alias /foo /gaq
+ </example>
+
+
<p>But if the above two directives were reversed in order, the
+ <code>/foo</code> <directive module="mod_alias">Alias</directive>
+ would always match before the <code>/foo/bar</code> <directive
+ module="mod_alias">Alias</directive>, so the latter directive would be
+ ignored.</p>
</section>
<usage>
<p>The <directive>Alias</directive> directive allows documents to
- be stored in the local filesystem other than under the
+ be stored in the local filesystem other than under the
<directive module="core">DocumentRoot</directive>. URLs with a
(%-decoded) path beginning with <var>url-path</var> will be mapped
- to local files beginning with <var>directory-path</var>. The
- <var>url-path</var> is case-sensitive, even on case-insenitive
+ to local files beginning with <var>directory-path</var>. The
+ <var>url-path</var> is case-sensitive, even on case-insenitive
file systems.</p>
<example><title>Example:</title>
Alias /image /ftp/pub/image
</example>
- <p>A request for http://myserver/image/foo.gif would cause the
- server to return the file /ftp/pub/image/foo.gif.</p>
+ <p>A request for <code>http://myserver/image/foo.gif</code> would cause
+ the server to return the file <code>/ftp/pub/image/foo.gif</code>.</p>
<p>Note that if you include a trailing / on the
<var>url-path</var> then the server will require a trailing / in
- order to expand the alias. That is, if you use <code>Alias
- /icons/ /usr/local/apache/icons/</code> then the url
- <code>/icons</code> will not be aliased.</p>
+ order to expand the alias. That is, if you use</p>
+
+ <dl><dd><code>Alias /icons/ /usr/local/apache/icons/</code></dd></dl>
+
+ <p>then the url <code>/icons</code> will not be aliased.</p>
<p>Note that you may need to specify additional <directive
type="section" module="core">Directory</directive> sections which
<directivesynopsis>
<name>AliasMatch</name>
-<description>Maps URLs to filesystem locations using regular
+<description>Maps URLs to filesystem locations using regular
expressions</description>
<syntax>AliasMatch <var>regex</var>
<var>file-path</var>|<var>directory-path</var></syntax>
<usage>
<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 case-sensitive (%-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
Redirect /service http://foo2.bar.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 <code>http://myserver/service/foo.txt</code>, it
+ will be told to access <code>http://foo2.bar.com/service/foo.txt</code>
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>
+ <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>
<p>If no <var>status</var> argument is given, the redirect will
be "temporary" (HTTP status 302). This indicates to the client
<directivesynopsis>
<name>RedirectMatch</name>
-<description>Sends an external redirect based on a regular expression match
+<description>Sends an external redirect based on a regular expression match
of the current URL</description>
<syntax>RedirectMatch [<var>status</var>] <var>regex</var>
<var>URL</var></syntax>
This is necessary since multiple <var>URL-paths</var> can map
to the same filesystem location, potentially bypassing the
<directive>ScriptAlias</directive> and revealing the source code
- of the CGI scripts if they are not restricted by a
+ of the CGI scripts if they are not restricted by a
<directive module="core">Directory</directive> section.</note>
</usage>
projects / thirdparty / apache / httpd.git / commitdiff
