Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://neptun.sai.msu.su/manual/sections.html
Дата изменения: Fri Jun 21 02:09:45 2002 Дата индексирования: Mon Oct 1 19:43:15 2012 Кодировка: Поисковые слова: невооруженным глазом |
The sections <Directory>
,
<Location>
and <Files>
can
contain directives which only apply to specified directories,
URLs or files 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.
Everything that is syntactically allowed in
<Directory>
is also allowed in
<Location>
(except a
sub-<Files>
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.
The order of merging is:
<Directory>
(except regular
expressions) and .htaccess done simultaneously (with
.htaccess, if allowed, overriding
<Directory>
)<DirectoryMatch>
, and
<Directory>
with regular expressions<Files>
and
<FilesMatch>
done simultaneously<Location>
and
<LocationMatch>
done simultaneouslyApart 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 <Directory>
sections apply to
the same directory 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.
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).
Later sections override earlier ones.
The general guidelines are:
<Directory>
and/or
<Files>
.<Location>
But a notable exception is:
<Directory>
.
This is a legacy mistake because the proxy existed prior to
<Location>
. A future version of the config
language should probably switch this to
<Location>
.Note about .htaccess parsing:
<Location>
and symbolic links:
Options
FollowSymLinks
" or "Options
SymLinksIfOwnerMatch
" inside a
<Location>
,
<LocationMatch>
or
<DirectoryMatch>
section (the options are
simply ignored). Using the options in question is only
possible inside a <Directory>
section (or
a .htaccess
file).<Files>
and Options
:
Options
directive inside a
<Files>
section has no effect.Another note:
<Location>
/<LocationMatch>
sequence performed just before the name translation phase
(where Aliases
and DocumentRoots
are used to map URLs to filenames). The results of this
sequence are completely thrown away after the translation has
completed.