From: Nilgun Belma Buguner Date: Sat, 19 Jul 2008 05:09:51 +0000 (+0000) Subject: some cosmetic improvements X-Git-Tag: 2.0.64~142 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d49c7a569af20551de6f90f9ab8874c3d8673542;p=thirdparty%2Fapache%2Fhttpd.git some cosmetic improvements git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x@678101 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_alias.xml b/docs/manual/mod/mod_alias.xml index 67c1f7187d7..37e52cf2618 100644 --- a/docs/manual/mod/mod_alias.xml +++ b/docs/manual/mod/mod_alias.xml @@ -59,36 +59,36 @@ href="../urlmapping.html">Mapping URLs to the filesystem
Order of Processing -

Aliases and Redirects occuring in different contexts are processed -like other directives according to standard merging rules. But when multiple -Aliases or Redirects occur in the same context (for example, in the -same VirtualHost -section) they are processed in a particular order.

- -

First, all Redirects are processed before Aliases are processed, -and therefore a request that matches a Redirect or RedirectMatch 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.

- -

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:

- - -Alias /foo/bar /baz
-Alias /foo /gaq - - -

But if the above two directives were reversed in order, the -/foo Alias -would always match before the /foo/bar Alias, so the latter directive would be -ignored.

+

Aliases and Redirects occuring in different contexts are processed + like other directives according to standard merging rules. But when multiple + Aliases or Redirects occur in the same context (for example, in the + same VirtualHost + section) they are processed in a particular order.

+ +

First, all Redirects are processed before Aliases are processed, + and therefore a request that matches a Redirect or RedirectMatch 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.

+ +

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:

+ + + Alias /foo/bar /baz
+ Alias /foo /gaq + + +

But if the above two directives were reversed in order, the + /foo Alias + would always match before the /foo/bar Alias, so the latter directive would be + ignored.

@@ -103,25 +103,27 @@ ignored.

The Alias directive allows documents to - be stored in the local filesystem other than under the + be stored in the local filesystem other than under the DocumentRoot. URLs with a (%-decoded) path beginning with url-path will be mapped - to local files beginning with directory-path. The - url-path is case-sensitive, even on case-insenitive + to local files beginning with directory-path. The + url-path is case-sensitive, even on case-insenitive file systems.

Example: Alias /image /ftp/pub/image -

A request for http://myserver/image/foo.gif would cause the - server to return the file /ftp/pub/image/foo.gif.

+

A request for http://myserver/image/foo.gif would cause + the server to return the file /ftp/pub/image/foo.gif.

Note that if you include a trailing / on the url-path then the server will require a trailing / in - order to expand the alias. That is, if you use Alias - /icons/ /usr/local/apache/icons/ then the url - /icons will not be aliased.

+ order to expand the alias. That is, if you use

+ +
Alias /icons/ /usr/local/apache/icons/
+ +

then the url /icons will not be aliased.

Note that you may need to specify additional Directory sections which @@ -152,7 +154,7 @@ ignored.

AliasMatch -Maps URLs to filesystem locations using regular +Maps URLs to filesystem locations using regular expressions AliasMatch regex file-path|directory-path @@ -196,7 +198,7 @@ a different URL

The Redirect directive maps an old URL into a new one by asking the client to refetch the resource at the new location.

- +

The old URL-path is a case-sensitive (%-decoded) path beginning with a slash. A relative path is not allowed. The new URL should be an absolute URL beginning with a scheme and @@ -206,16 +208,17 @@ a different URL Redirect /service http://foo2.bar.com/service -

If the client requests http://myserver/service/foo.txt, it - will be told to access http://foo2.bar.com/service/foo.txt +

If the client requests http://myserver/service/foo.txt, it + will be told to access http://foo2.bar.com/service/foo.txt instead.

-Note

Redirect directives take precedence over -Alias and ScriptAlias directives, irrespective of their ordering in -the configuration file. Also, URL-path must be a fully -qualified URL, not a relative path, even when used with .htaccess files or -inside of Directory -sections.

 + Note +

Redirect directives take precedence over + Alias and ScriptAlias directives, irrespective of their ordering in + the configuration file. Also, URL-path must be a fully + qualified URL, not a relative path, even when used with .htaccess files or + inside of Directory + sections.

If no status argument is given, the redirect will be "temporary" (HTTP status 302). This indicates to the client @@ -262,7 +265,7 @@ sections.

RedirectMatch -Sends an external redirect based on a regular expression match +Sends an external redirect based on a regular expression match of the current URL RedirectMatch [status] regex URL @@ -377,7 +380,7 @@ target as a CGI script This is necessary since multiple URL-paths can map to the same filesystem location, potentially bypassing the ScriptAlias 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 Directory section.