Return-Path: 
 <cvs-return-18543-apmail-httpd-cvs-archive=httpd.apache.org@httpd.apache.org>
Delivered-To: apmail-httpd-cvs-archive@www.apache.org
Received: (qmail 55200 invoked from network); 23 Mar 2004 04:23:27 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 23 Mar 2004 04:23:27 -0000
Received: (qmail 3660 invoked by uid 500); 23 Mar 2004 04:23:07 -0000
Delivered-To: apmail-httpd-cvs-archive@httpd.apache.org
Received: (qmail 3635 invoked by uid 500); 23 Mar 2004 04:23:06 -0000
Mailing-List: contact cvs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
list-help: <mailto:cvs-help@httpd.apache.org>
list-unsubscribe: <mailto:cvs-unsubscribe@httpd.apache.org>
list-post: <mailto:cvs@httpd.apache.org>
Delivered-To: mailing list cvs@httpd.apache.org
Received: (qmail 3622 invoked by uid 500); 23 Mar 2004 04:23:06 -0000
Delivered-To: apmail-httpd-2.0-cvs@apache.org
Received: (qmail 3618 invoked from network); 23 Mar 2004 04:23:06 -0000
Received: from unknown (HELO minotaur.apache.org) (209.237.227.194)
  by daedalus.apache.org with SMTP; 23 Mar 2004 04:23:06 -0000
Received: (qmail 55182 invoked by uid 1173); 23 Mar 2004 04:23:25 -0000
Date: 23 Mar 2004 04:23:25 -0000
Message-ID: <20040323042325.55181.qmail@minotaur.apache.org>
From: slive@apache.org
To: httpd-2.0-cvs@apache.org
Subject: cvs commit: httpd-2.0/docs/manual/mod mod_alias.html.en mod_alias.xml
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

slive       2004/03/22 20:23:25

  Modified:    docs/manual/mod mod_alias.html.en mod_alias.xml
  Log:
  Clarify the order of processing in mod_alias.
  
  PR: 21897
  
  Revision  Changes    Path
  1.25      +35 -1     httpd-2.0/docs/manual/mod/mod_alias.html.en
  
  Index: mod_alias.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_alias.html.en,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -d -b -u -r1.24 -r1.25
  --- mod_alias.html.en	21 Feb 2004 00:31:34 -0000	1.24
  +++ mod_alias.html.en	23 Mar 2004 04:23:25 -0000	1.25
  @@ -56,12 +56,46 @@
   <li><img alt="" src="../images/down.gif" /> <a href="#scriptalias">ScriptAlias</a></li>
   <li><img alt="" src="../images/down.gif" /> <a href="#scriptaliasmatch">ScriptAliasMatch</a></li>
   </ul>
  -<h3>See also</h3>
  +<h3>Topics</h3>
  +<ul id="topics">
  +<li><img alt="" src="../images/down.gif" /> <a href="#order">Order of Processing</a></li>
  +</ul><h3>See also</h3>
   <ul class="seealso">
   <li><code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code></li>
   <li><a href="../urlmapping.html">Mapping URLs to the filesystem</a></li>
   </ul></div>
  +<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
  +<div class="section">
  +<h2><a name="order" id="order">Order of Processing</a></h2>
  +
  +<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 <code class="directive"><a href="../mod/core.html#virtualhost">&lt;VirtualHost&gt;</a></code>
  +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 <code class="directive"><a href="#redirect">Redirect</a></code> or <code class="directive"><a href="#redirectmatch">RedirectMatch</a></code> 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>
  +
  +<div class="example"><p><code>
  +Alias /foo/bar /baz<br />
  +Alias /foo /gaq
  +</code></p></div>
   
  +<p>But if the above two directives were reversed in order, the
  +<code>/foo</code> <code class="directive"><a href="#alias">Alias</a></code>
  +would always match before the <code>/foo/bar</code> <code class="directive"><a href="#alias">Alias</a></code>, so the latter directive would be
  +ignored.</p>
  +
  +</div>
   <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
   <div class="directive-section"><h2><a name="Alias" id="Alias">Alias</a> <a name="alias" id="alias">Directive</a></h2>
   <table class="directive">
  
  
  
  1.17      +35 -0     httpd-2.0/docs/manual/mod/mod_alias.xml
  
  Index: mod_alias.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_alias.xml,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -d -b -u -r1.16 -r1.17
  --- mod_alias.xml	20 Feb 2004 18:41:18 -0000	1.16
  +++ mod_alias.xml	23 Mar 2004 04:23:25 -0000	1.17
  @@ -49,6 +49,41 @@
   <seealso><module>mod_rewrite</module></seealso> <seealso><a
   href="../urlmapping.html">Mapping URLs to the filesystem</a></seealso>
   
  +<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>
  +
  +</section>
  +
   <directivesynopsis>
   <name>Alias</name>
   <description>Maps URLs to filesystem locations</description>