Commit 7134d238 authored by Nilgun Belma Buguner's avatar Nilgun Belma Buguner
Browse files

some cosmetic improvements 

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

docs/manual/mod/mod_alias.xml

+19 −15
Changes for docs/manual/mod/mod_alias.xml: 19 added lines, 15 removed lines.
Original line number Diff line number Diff line
@@ -114,18 +114,20 @@ ignored.</p> 
      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.  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>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>.  Only

    complete path segments are matched, so the above alias would not match a

    request for <code>http://myserver/imagefoo.gif</code>.  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

    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
@@ -218,18 +220,20 @@ a different URL</description> 
      Redirect /service http://foo2.example.com/service

    </example>



    <p>If the client requests http://example.com/service/foo.txt, it

    will be told to access http://foo2.example.com/service/foo.txt

    <p>If the client requests <code>http://example.com/service/foo.txt</code>,

    it will be told to access

    <code>http://foo2.example.com/service/foo.txt</code>

    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

    <code>http://example.com/servicefoo.txt</code>.  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

the configuration file.</p></note>

    <note><title>Note</title>

    <p>Redirect directives take precedence over Alias and ScriptAlias

    directives, irrespective of their ordering in 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