1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org" />
<title>How Directory, Location and Files sections work</title>
</head>
<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
<body bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#000080" alink="#FF0000">
<div align="CENTER">
<img src="images/sub.gif" alt="[APACHE DOCUMENTATION]" />
<h3>Apache HTTP Server</h3>
</div>
<h1 align="CENTER">How Directory, Location and Files sections
work</h1>
<p>The sections <a
href="mod/core.html#directory"><code><Directory></code></a>,
<a
href="mod/core.html#location"><code><Location></code></a>
and <a
href="mod/core.html#files"><code><Files></code></a> 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.</p>
<h2>Directives allowed in the sections</h2>
<p>Everything that is syntactically allowed in
<code><Directory></code> is also allowed in
<code><Location></code> (except a
sub-<code><Files></code> section). Semantically, however
some things, most notably <code>AllowOverride</code> and the
two options <code>FollowSymLinks</code> and
<code>SymLinksIfOwnerMatch</code>, make no sense in
<code><Location></code>,
<code><LocationMatch></code> or
<code><DirectoryMatch></code>. The same for
<code><Files></code> -- syntactically everything is fine,
but semantically some things are different.</p>
<h2>How the sections are merged</h2>
<p>The order of merging is:</p>
<ol>
<li><code><Directory></code> (except regular
expressions) and .htaccess done simultaneously (with
.htaccess, if allowed, overriding
<code><Directory></code>)</li>
<li><code><DirectoryMatch></code>, and
<code><Directory></code> with regular expressions</li>
<li><code><Files></code> and
<code><FilesMatch></code> done simultaneously</li>
<li><code><Location></code> and
<code><LocationMatch></code> done simultaneously</li>
</ol>
<p>Apart from <code><Directory></code>, each group is
processed in the order that they appear in the configuration
files. <code><Directory></code> (group 1 above) is
processed in the order shortest directory component to longest.
If multiple <code><Directory></code> 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 <code>Include</code> directive will be treated as if
they were inside the including file at the location of the
<code>Include</code> directive.</p>
<p>Sections inside <code><VirtualHost></code> sections
are applied <em>after</em> 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 <em>before</em> the
main server).</p>
<p>Later sections override earlier ones.</p>
<h2>Notes about using sections</h2>
<p>The general guidelines are:</p>
<ul>
<li>If you are attempting to match objects at the filesystem
level then you must use <code><Directory></code> and/or
<code><Files></code>.</li>
<li>If you are attempting to match objects at the URL level
then you must use <code><Location></code></li>
</ul>
<p>But a notable exception is:</p>
<ul>
<li>proxy control is done via <code><Directory></code>.
This is a legacy mistake because the proxy existed prior to
<code><Location></code>. A future version of the config
language should probably switch this to
<code><Location></code>.</li>
</ul>
<p>Note about .htaccess parsing:</p>
<ul>
<li>Modifying .htaccess parsing during Location doesn't do
anything because .htaccess parsing has already occurred.</li>
</ul>
<p><code><Location></code> and symbolic links:</p>
<ul>
<li>It is not possible to use "<code>Options
FollowSymLinks</code>" or "<code>Options
SymLinksIfOwnerMatch</code>" inside a
<code><Location></code>,
<code><LocationMatch></code> or
<code><DirectoryMatch></code> section (the options are
simply ignored). Using the options in question is only
possible inside a <code><Directory></code> section (or
a <code>.htaccess</code> file).</li>
</ul>
<p><code><Files></code> and <code>Options</code>:</p>
<ul>
<li>Apache won't check for it, but using an
<code>Options</code> directive inside a
<code><Files></code> section has no effect.</li>
</ul>
<p>Another note:</p>
<ul>
<li>There is actually a
<code><Location></code>/<code><LocationMatch></code>
sequence performed just before the name translation phase
(where <code>Aliases</code> and <code>DocumentRoots</code>
are used to map URLs to filenames). The results of this
sequence are completely thrown away after the translation has
completed.</li>
</ul>
<hr />
<h3 align="CENTER">Apache HTTP Server</h3>
<a href="./"><img src="images/index.gif" alt="Index" /></a>
</body>
</html>
|
