<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.
<Directory>is also allowed in
<Location>(except a sub-
<Files>section). Semantically however some things, and the most notable are
AllowOverrideand the two options
SymLinksIfOwnerMatch, make no sense in
<Location>. The same for
<Files>-- syntactically everything is fine, but semantically some things are different.
<Directory>(except regular expressions) and .htaccess done simultaneously (with .htaccess overriding
<Directory>with regular expressions
<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 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
Includedirective will be treated as if they where inside the including file at the location of the
<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).
<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
Note about .htaccess parsing:
<Location> and symbolic links:
Options FollowSymLinks" or "
Options SymLinksIfOwnerMatch" inside a
<LocationMatch>section (the options are simply ignored). Using the options in question is only possible inside a
<Directory>section (or a
Optionsdirective inside a
<Files>section has no effect.
<LocationMatch>sequence performed just before the name translation phase (where
DocumentRootsare used to map URLs to filenames). The results of this sequence are completely thrown away after the translation has completed.