</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>
+<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
+ <p>Aliases and Redirects occurring 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"><VirtualHost></a></code>
<p>The <code class="directive">Alias</code> directive allows documents to
be stored in the local filesystem other than under the
<code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>. URLs with a
- (%-decoded) path beginning with <var>url-path</var> will be mapped
+ (%-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-insensitive
+ <var>URL-path</var> is case-sensitive, even on case-insensitive
file systems.</p>
<div class="example"><h3>Example:</h3><p><code>
matching using regular expressions, see the <code class="directive"><a href="#aliasmatch">AliasMatch</a></code> directive.</p>
<p>Note that if you include a trailing / on the
- <var>url-path</var> then the server will require a trailing / in
+ <var>URL-path</var> then the server will require a trailing / in
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, as it lacks
+ <p>then the URL <code>/icons</code> will not be aliased, as it lacks
that trailing /. Likewise, if you omit the slash on the
- <var>url-path</var> then you must also omit it from the
+ <var>URL-path</var> then you must also omit it from the
<var>file-path</var>.</p>
<p>Note that you may need to specify additional <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> sections which
<p>The full range of <a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular expression</a>
power is available. For example,
it is possible to construct an alias with case-insensitive
- matching of the url-path:</p>
+ matching of the URL-path:</p>
<div class="example"><p><code>
AliasMatch (?i)^/image(.*) /ftp/pub/image$1
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
+ <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>
+ <em>URL-path</em> will be appended to the target URL.</p>
<div class="example"><h3>Example:</h3><p><code>
Redirect /service http://foo2.example.com/service
<p>As for AliasMatch, the full range of <a class="glossarylink" href="../glossary.html#rexex" title="see glossary">regular
expression</a> power is available.
For example, it is possible to construct an alias with case-insensitive
- matching of the url-path:</p>
+ matching of the URL-path:</p>
<div class="example"><p><code>
ScriptAliasMatch (?i)^/cgi-bin(.*) /usr/local/apache/cgi-bin$1