From: Chris Pepper Date: Tue, 6 Feb 2001 16:31:17 +0000 (+0000) Subject: Added note about later sections overriding earlier. X-Git-Tag: APACHE_2_0_2001_02_09~35 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=40d82b9a7aa93d168af57677e5e4af697beed292;p=apache Added note about later sections overriding earlier. Removed note about order reversal in 1.2-1.3a versions. Fixed a couple typos. Matched up

&

. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@87993 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/sections.html b/docs/manual/sections.html index 08a93b5b59..7d91191a6c 100644 --- a/docs/manual/sections.html +++ b/docs/manual/sections.html @@ -12,9 +12,10 @@ ALINK="#FF0000" > +

How Directory, Location and Files sections work

-The sections The sections <Directory>, <Location> and <Files> can contain @@ -23,31 +24,31 @@ respectively. Also htaccess files can be used inside a directory to apply directives to that directory. This document explains how these different sections differ and how they relate to each other when Apache decides which directives apply for a particular directory or -request URL. +request URL.

Directives allowed in the sections

-Everything that is syntactically allowed in +

Everything that is syntactically allowed in <Directory> is also allowed in <Location> (except a sub-<Files> -section). Semantically however some things, and the most -notable are AllowOverride and the two options +section). Semantically, however some things, most +notably AllowOverride and the two options FollowSymLinks and SymLinksIfOwnerMatch, make no sense in <Location>, <LocationMatch> or <DirectoryMatch>. The same for <Files> -- syntactically everything -is fine, but semantically some things are different. +is fine, but semantically some things are different.

How the sections are merged

-The order of merging is: +

The order of merging is:

  1. <Directory> (except regular expressions) and - .htaccess done simultaneously (with .htaccess overriding + .htaccess done simultaneously (with .htaccess, if allowed, overriding <Directory>)
    2. @@ -68,7 +69,7 @@ The order of merging is:
-Apart from <Directory>, each group is processed in +

Apart from <Directory>, each group is processed in the order that they appear in the configuration files. <Directory> (group 1 above) is processed in the order shortest directory component to longest. If multiple @@ -77,22 +78,18 @@ they they are processed in the configuration file order. The configuration files are read in the order httpd.conf, srm.conf and access.conf. Configurations included via the Include directive will be treated as if they were inside the including file -at the location of the Include directive. - -

+at the location of the Include directive.

-Sections inside <VirtualHost> sections are applied +

Sections inside <VirtualHost> sections are applied after the corresponding sections outside the virtual host definition. This allows virtual hosts to override the main server -configuration. (Note: this only works correctly from 1.2.2 and 1.3a2 -onwards. Before those releases sections inside virtual hosts were -applied before the main server). +configuration.

-

Notes about using sections

+

Later sections override earlier ones.

-The general guidelines are: +

Notes about using sections

-

+

The general guidelines are:

-But a notable exception is: +

But a notable exception is:

-

-Note about .htaccess parsing: -

+

Note about .htaccess parsing:

+ -

-<Location> and symbolic links: -

+

<Location> and symbolic links:

+ -

-<Files> and Options: -

+

<Files> and Options:

+ -

-Another note: -

+

Another note:

- + + diff --git a/docs/manual/sections.html.en b/docs/manual/sections.html.en index 08a93b5b59..7d91191a6c 100644 --- a/docs/manual/sections.html.en +++ b/docs/manual/sections.html.en @@ -12,9 +12,10 @@ ALINK="#FF0000" > +

How Directory, Location and Files sections work

-The sections The sections <Directory>, <Location> and <Files> can contain @@ -23,31 +24,31 @@ respectively. Also htaccess files can be used inside a directory to apply directives to that directory. This document explains how these different sections differ and how they relate to each other when Apache decides which directives apply for a particular directory or -request URL. +request URL.

Directives allowed in the sections

-Everything that is syntactically allowed in +

Everything that is syntactically allowed in <Directory> is also allowed in <Location> (except a sub-<Files> -section). Semantically however some things, and the most -notable are AllowOverride and the two options +section). Semantically, however some things, most +notably AllowOverride and the two options FollowSymLinks and SymLinksIfOwnerMatch, make no sense in <Location>, <LocationMatch> or <DirectoryMatch>. The same for <Files> -- syntactically everything -is fine, but semantically some things are different. +is fine, but semantically some things are different.

How the sections are merged

-The order of merging is: +

The order of merging is:

  1. <Directory> (except regular expressions) and - .htaccess done simultaneously (with .htaccess overriding + .htaccess done simultaneously (with .htaccess, if allowed, overriding <Directory>)
    2. @@ -68,7 +69,7 @@ The order of merging is:
-Apart from <Directory>, each group is processed in +

Apart from <Directory>, each group is processed in the order that they appear in the configuration files. <Directory> (group 1 above) is processed in the order shortest directory component to longest. If multiple @@ -77,22 +78,18 @@ they they are processed in the configuration file order. The configuration files are read in the order httpd.conf, srm.conf and access.conf. Configurations included via the Include directive will be treated as if they were inside the including file -at the location of the Include directive. - -

+at the location of the Include directive.

-Sections inside <VirtualHost> sections are applied +

Sections inside <VirtualHost> sections are applied after the corresponding sections outside the virtual host definition. This allows virtual hosts to override the main server -configuration. (Note: this only works correctly from 1.2.2 and 1.3a2 -onwards. Before those releases sections inside virtual hosts were -applied before the main server). +configuration.

-

Notes about using sections

+

Later sections override earlier ones.

-The general guidelines are: +

Notes about using sections

-

+

The general guidelines are:

-But a notable exception is: +

But a notable exception is:

-

-Note about .htaccess parsing: -

+

Note about .htaccess parsing:

+ -

-<Location> and symbolic links: -

+

<Location> and symbolic links:

+ -

-<Files> and Options: -

+

<Files> and Options:

+ -

-Another note: -

+

Another note:

- + +