1 <?xml version="1.0" encoding="ISO-8859-1"?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head>
4 <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" />
6 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
7 This file is generated from xml source: DO NOT EDIT
8 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
10 <title>mod_access_compat - Apache HTTP Server Version 2.5</title>
11 <link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
12 <link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
13 <link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
14 <script src="../style/scripts/prettify.min.js" type="text/javascript">
17 <link href="../images/favicon.ico" rel="shortcut icon" /></head>
19 <div id="page-header">
20 <p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/quickreference.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p>
21 <p class="apache">Apache HTTP Server Version 2.5</p>
22 <img alt="" src="../images/feather.gif" /></div>
23 <div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div>
25 <a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.5</a> > <a href="./">Modules</a></div>
26 <div id="page-content">
27 <div id="preamble"><h1>Apache Module mod_access_compat</h1>
29 <p><span>Available Languages: </span><a href="../en/mod/mod_access_compat.html" title="English"> en </a> |
30 <a href="../fr/mod/mod_access_compat.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
31 <a href="../ja/mod/mod_access_compat.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a></p>
33 <table class="module"><tr><th><a href="module-dict.html#Description">Description:</a></th><td>Group authorizations based on host (name or IP
35 <tr><th><a href="module-dict.html#Status">Status:</a></th><td>Extension</td></tr>
36 <tr><th><a href="module-dict.html#ModuleIdentifier">Module Identifier:</a></th><td>access_compat_module</td></tr>
37 <tr><th><a href="module-dict.html#SourceFile">Source File:</a></th><td>mod_access_compat.c</td></tr>
38 <tr><th><a href="module-dict.html#Compatibility">Compatibility:</a></th><td>Available in Apache HTTP Server 2.3 as a compatibility module with
39 previous versions of Apache httpd 2.x. The directives provided by this module
40 have been deprecated by the new authz refactoring. Please see
41 <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code></td></tr></table>
44 <p>The directives provided by <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> are
45 used in <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code>,
46 <code class="directive"><a href="../mod/core.html#files"><Files></a></code>, and
47 <code class="directive"><a href="../mod/core.html#location"><Location></a></code> sections
48 as well as <code><a href="core.html#accessfilename">.htaccess</a>
49 </code> files to control access to particular parts of the server.
50 Access can be controlled based on the client hostname, IP address, or
51 other characteristics of the client request, as captured in <a href="../env.html">environment variables</a>. The <code class="directive"><a href="#allow">Allow</a></code> and <code class="directive"><a href="#deny">Deny</a></code> directives are used to
52 specify which clients are or are not allowed access to the server,
53 while the <code class="directive"><a href="#order">Order</a></code>
54 directive sets the default access state, and configures how the
55 <code class="directive"><a href="#allow">Allow</a></code> and <code class="directive"><a href="#deny">Deny</a></code> directives interact with each
58 <p>Both host-based access restrictions and password-based
59 authentication may be implemented simultaneously. In that case,
60 the <code class="directive"><a href="#satisfy">Satisfy</a></code> directive is used
61 to determine how the two sets of restrictions interact.</p>
63 <div class="warning"><h3>Note</h3>
64 <p>The directives provided by <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> have
65 been deprecated by the new authz refactoring. Please see
66 <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code>.</p>
69 <p>In general, access restriction directives apply to all
70 access methods (<code>GET</code>, <code>PUT</code>,
71 <code>POST</code>, etc). This is the desired behavior in most
72 cases. However, it is possible to restrict some methods, while
73 leaving other methods unrestricted, by enclosing the directives
74 in a <code class="directive"><a href="../mod/core.html#limit"><Limit></a></code> section.</p>
76 <div class="note"> <h3>Merging of configuration sections</h3>
77 <p>When any directive provided by this module is used in a new
78 configuration section, no directives provided by this module are
79 inherited from previous configuration sections.</p>
83 <div id="quickview"><h3 class="directives">Directives</h3>
85 <li><img alt="" src="../images/down.gif" /> <a href="#allow">Allow</a></li>
86 <li><img alt="" src="../images/down.gif" /> <a href="#deny">Deny</a></li>
87 <li><img alt="" src="../images/down.gif" /> <a href="#order">Order</a></li>
88 <li><img alt="" src="../images/down.gif" /> <a href="#satisfy">Satisfy</a></li>
92 <li><code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code></li>
93 <li><code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code></li>
94 <li><code class="module"><a href="../mod/mod_authz_core.html">mod_authz_core</a></code></li>
95 </ul><ul class="seealso"><li><a href="#comments_section">Comments</a></li></ul></div>
97 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
98 <div class="directive-section"><h2><a name="Allow" id="Allow">Allow</a> <a name="allow" id="allow">Directive</a></h2>
99 <table class="directive">
100 <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Controls which hosts can access an area of the
102 <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code> Allow from all|<var>host</var>|env=[!]<var>env-variable</var>
103 [<var>host</var>|env=[!]<var>env-variable</var>] ...</code></td></tr>
104 <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>directory, .htaccess</td></tr>
105 <tr><th><a href="directive-dict.html#Override">Override:</a></th><td>Limit</td></tr>
106 <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
107 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_access_compat</td></tr>
109 <p>The <code class="directive">Allow</code> directive affects which hosts can
110 access an area of the server. Access can be controlled by
111 hostname, IP address, IP address range, or by other
112 characteristics of the client request captured in environment
115 <p>The first argument to this directive is always
116 <code>from</code>. The subsequent arguments can take three
117 different forms. If <code>Allow from all</code> is specified, then
118 all hosts are allowed access, subject to the configuration of the
119 <code class="directive"><a href="#deny">Deny</a></code> and <code class="directive"><a href="#order">Order</a></code> directives as discussed
120 below. To allow only particular hosts or groups of hosts to access
121 the server, the <em>host</em> can be specified in any of the
122 following formats:</p>
125 <dt>A (partial) domain-name</dt>
128 <pre class="prettyprint lang-config">Allow from example.org
129 Allow from .net example.edu</pre>
131 <p>Hosts whose names match, or end in, this string are allowed
132 access. Only complete components are matched, so the above
133 example will match <code>foo.example.org</code> but it will not
134 match <code>fooexample.org</code>. This configuration will cause
135 Apache httpd to perform a double DNS lookup on the client IP
136 address, regardless of the setting of the <code class="directive"><a href="../mod/core.html#hostnamelookups">HostnameLookups</a></code> directive. It will do
137 a reverse DNS lookup on the IP address to find the associated
138 hostname, and then do a forward lookup on the hostname to assure
139 that it matches the original IP address. Only if the forward
140 and reverse DNS are consistent and the hostname matches will
141 access be allowed.</p></dd>
143 <dt>A full IP address</dt>
146 <pre class="prettyprint lang-config">Allow from 10.1.2.3
147 Allow from 192.168.1.104 192.168.1.205</pre>
149 <p>An IP address of a host allowed access</p></dd>
151 <dt>A partial IP address</dt>
154 <pre class="prettyprint lang-config">Allow from 10.1
155 Allow from 10 172.20 192.168.2</pre>
157 <p>The first 1 to 3 bytes of an IP address, for subnet
158 restriction.</p></dd>
160 <dt>A network/netmask pair</dt>
163 <pre class="prettyprint lang-config">Allow from 10.1.0.0/255.255.0.0</pre>
165 <p>A network a.b.c.d, and a netmask w.x.y.z. For more
166 fine-grained subnet restriction.</p></dd>
168 <dt>A network/nnn CIDR specification</dt>
171 <pre class="prettyprint lang-config">Allow from 10.1.0.0/16</pre>
173 <p>Similar to the previous case, except the netmask consists of
174 nnn high-order 1 bits.</p></dd>
177 <p>Note that the last three examples above match exactly the
178 same set of hosts.</p>
180 <p>IPv6 addresses and IPv6 subnets can be specified as shown
183 <pre class="prettyprint lang-config">Allow from 2001:db8::a00:20ff:fea7:ccea
184 Allow from 2001:db8::a00:20ff:fea7:ccea/10</pre>
187 <p>The third format of the arguments to the
188 <code class="directive">Allow</code> directive allows access to the server
189 to be controlled based on the existence of an <a href="../env.html">environment variable</a>. When <code>Allow from
190 env=<var>env-variable</var></code> is specified, then the request is
191 allowed access if the environment variable <var>env-variable</var>
192 exists. When <code>Allow from env=!<var>env-variable</var></code> is
193 specified, then the request is allowed access if the environment
194 variable <var>env-variable</var> doesn't exist.
195 The server provides the ability to set environment
196 variables in a flexible way based on characteristics of the client
197 request using the directives provided by
198 <code class="module"><a href="../mod/mod_setenvif.html">mod_setenvif</a></code>. Therefore, this directive can be
199 used to allow access based on such factors as the clients
200 <code>User-Agent</code> (browser type), <code>Referer</code>, or
201 other HTTP request header fields.</p>
203 <pre class="prettyprint lang-config">SetEnvIf User-Agent ^KnockKnock/2\.0 let_me_in
204 <Directory "/docroot">
207 Allow from env=let_me_in
208 </Directory></pre>
211 <p>In this case, browsers with a user-agent string beginning
212 with <code>KnockKnock/2.0</code> will be allowed access, and all
213 others will be denied.</p>
215 <div class="note"> <h3>Merging of configuration sections</h3>
216 <p>When any directive provided by this module is used in a new
217 configuration section, no directives provided by this module are
218 inherited from previous configuration sections.</p>
223 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
224 <div class="directive-section"><h2><a name="Deny" id="Deny">Deny</a> <a name="deny" id="deny">Directive</a></h2>
225 <table class="directive">
226 <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Controls which hosts are denied access to the
228 <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code> Deny from all|<var>host</var>|env=[!]<var>env-variable</var>
229 [<var>host</var>|env=[!]<var>env-variable</var>] ...</code></td></tr>
230 <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>directory, .htaccess</td></tr>
231 <tr><th><a href="directive-dict.html#Override">Override:</a></th><td>Limit</td></tr>
232 <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
233 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_access_compat</td></tr>
235 <p>This directive allows access to the server to be restricted
236 based on hostname, IP address, or environment variables. The
237 arguments for the <code class="directive">Deny</code> directive are
238 identical to the arguments for the <code class="directive"><a href="#allow">Allow</a></code> directive.</p>
241 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
242 <div class="directive-section"><h2><a name="Order" id="Order">Order</a> <a name="order" id="order">Directive</a></h2>
243 <table class="directive">
244 <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Controls the default access state and the order in which
245 <code class="directive">Allow</code> and <code class="directive">Deny</code> are
247 <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code> Order <var>ordering</var></code></td></tr>
248 <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>Order Deny,Allow</code></td></tr>
249 <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>directory, .htaccess</td></tr>
250 <tr><th><a href="directive-dict.html#Override">Override:</a></th><td>Limit</td></tr>
251 <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
252 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_access_compat</td></tr>
255 <p>The <code class="directive">Order</code> directive, along with the
256 <code class="directive"><a href="#allow">Allow</a></code> and
257 <code class="directive"><a href="#deny">Deny</a></code> directives,
258 controls a three-pass access control system. The first pass
259 processes either all <code class="directive"><a href="#allow">Allow</a></code> or all <code class="directive"><a href="#deny">Deny</a></code> directives, as specified
260 by the <code class="directive"><a href="#order">Order</a></code>
261 directive. The second pass parses the rest of the directives
262 (<code class="directive"><a href="#deny">Deny</a></code> or
263 <code class="directive"><a href="#allow">Allow</a></code>). The third
264 pass applies to all requests which do not match either of the first
267 <p>Note that all <code class="directive"><a href="#allow">Allow</a></code> and <code class="directive"><a href="#deny">Deny</a></code> directives are
268 processed, unlike a typical firewall, where only the first match is
269 used. The last match is effective (also unlike a typical firewall).
270 Additionally, the order in which lines appear in the configuration
271 files is not significant -- all <code class="directive"><a href="#allow">Allow</a></code> lines are processed as
272 one group, all <code class="directive"><a href="#deny">Deny</a></code> lines are considered as
273 another, and the default state is considered by itself.</p>
275 <p><em>Ordering</em> is one of:</p>
278 <dt><code>Allow,Deny</code></dt>
280 <dd>First, all <code class="directive"><a href="#allow">Allow</a></code> directives are
281 evaluated; at least one must match, or the request is rejected.
282 Next, all <code class="directive"><a href="#deny">Deny</a></code>
283 directives are evaluated. If any matches, the request is rejected.
284 Last, any requests which do not match an <code class="directive"><a href="#allow">Allow</a></code> or a <code class="directive"><a href="#deny">Deny</a></code> directive are denied
287 <dt><code>Deny,Allow</code></dt>
289 <dd>First, all <code class="directive"><a href="#deny">Deny</a></code> directives are
290 evaluated; if any match, the request is denied
291 <strong>unless</strong> it also matches an <code class="directive"><a href="#allow">Allow</a></code> directive. Any
292 requests which do not match any <code class="directive"><a href="#allow">Allow</a></code> or <code class="directive"><a href="#deny">Deny</a></code> directives are
295 <dt><code>Mutual-failure</code></dt>
297 <dd>This order has the same effect as <code>Order
298 Allow,Deny</code> and is deprecated in its favor.</dd>
301 <p>Keywords may only be separated by a comma; <em>no whitespace</em>
302 is allowed between them.</p>
304 <table class="bordered">
307 <th>Allow,Deny result</th>
308 <th>Deny,Allow result</th>
310 <th>Match Allow only</th>
311 <td>Request allowed</td>
312 <td>Request allowed</td>
314 <th>Match Deny only</th>
315 <td>Request denied</td>
316 <td>Request denied</td>
319 <td>Default to second directive: Denied</td>
320 <td>Default to second directive: Allowed</td>
322 <th>Match both Allow & Deny</th>
323 <td>Final match controls: Denied</td>
324 <td>Final match controls: Allowed</td>
328 <p>In the following example, all hosts in the example.org domain
329 are allowed access; all other hosts are denied access.</p>
331 <pre class="prettyprint lang-config">Order Deny,Allow
333 Allow from example.org</pre>
336 <p>In the next example, all hosts in the example.org domain are
337 allowed access, except for the hosts which are in the
338 foo.example.org subdomain, who are denied access. All hosts not
339 in the example.org domain are denied access because the default
340 state is to <code class="directive"><a href="#deny">Deny</a></code>
341 access to the server.</p>
343 <pre class="prettyprint lang-config">Order Allow,Deny
344 Allow from example.org
345 Deny from foo.example.org</pre>
348 <p>On the other hand, if the <code class="directive">Order</code> in the
349 last example is changed to <code>Deny,Allow</code>, all hosts will
350 be allowed access. This happens because, regardless of the actual
351 ordering of the directives in the configuration file, the
352 <code>Allow from example.org</code> will be evaluated last and will
353 override the <code>Deny from foo.example.org</code>. All hosts not in
354 the <code>example.org</code> domain will also be allowed access
355 because the default state is <code class="directive"><a href="#allow">Allow</a></code>.</p>
357 <p>The presence of an <code class="directive">Order</code> directive can
358 affect access to a part of the server even in the absence of
359 accompanying <code class="directive"><a href="#allow">Allow</a></code>
360 and <code class="directive"><a href="#deny">Deny</a></code>
361 directives because of its effect on the default access state. For
364 <pre class="prettyprint lang-config"><Directory "/www">
366 </Directory></pre>
369 <p>will Deny all access to the <code>/www</code> directory
370 because the default access state is set to
371 <code class="directive"><a href="#deny">Deny</a></code>.</p>
373 <p>The <code class="directive">Order</code> directive controls the order of access
374 directive processing only within each phase of the server's
375 configuration processing. This implies, for example, that an
376 <code class="directive"><a href="#allow">Allow</a></code> or <code class="directive"><a href="#deny">Deny</a></code> directive occurring in a
377 <code class="directive"><a href="../mod/core.html#location"><Location></a></code> section will
378 always be evaluated after an <code class="directive"><a href="#allow">Allow</a></code> or <code class="directive"><a href="#deny">Deny</a></code> directive occurring in a
379 <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> section or
380 <code>.htaccess</code> file, regardless of the setting of the
381 <code class="directive">Order</code> directive. For details on the merging
382 of configuration sections, see the documentation on <a href="../sections.html">How Directory, Location and Files sections
385 <div class="note"> <h3>Merging of configuration sections</h3>
386 <p>When any directive provided by this module is used in a new
387 configuration section, no directives provided by this module are
388 inherited from previous configuration sections.</p>
393 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
394 <div class="directive-section"><h2><a name="Satisfy" id="Satisfy">Satisfy</a> <a name="satisfy" id="satisfy">Directive</a></h2>
395 <table class="directive">
396 <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Interaction between host-level access control and
397 user authentication</td></tr>
398 <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>Satisfy Any|All</code></td></tr>
399 <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>Satisfy All</code></td></tr>
400 <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>directory, .htaccess</td></tr>
401 <tr><th><a href="directive-dict.html#Override">Override:</a></th><td>AuthConfig</td></tr>
402 <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
403 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_access_compat</td></tr>
405 <p>Access policy if both <code class="directive"><a href="#allow">Allow</a></code> and <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> used. The parameter can be
406 either <code>All</code> or <code>Any</code>. This directive is only
407 useful if access to a particular area is being restricted by both
408 username/password <em>and</em> client host address. In this case
409 the default behavior (<code>All</code>) is to require that the client
410 passes the address access restriction <em>and</em> enters a valid
411 username and password. With the <code>Any</code> option the client will be
412 granted access if they either pass the host restriction or enter a
413 valid username and password. This can be used to password restrict
414 an area, but to let clients from particular addresses in without
415 prompting for a password.</p>
417 <p>For example, if you wanted to let people on your network have
418 unrestricted access to a portion of your website, but require that
419 people outside of your network provide a password, you could use a
420 configuration similar to the following:</p>
422 <pre class="prettyprint lang-config">Require valid-user
428 Another frequent use of the <code class="directive">Satisfy</code> directive
429 is to relax access restrictions for a subdirectory:
432 <pre class="prettyprint lang-config"><Directory "/var/www/private">
436 <Directory "/var/www/private/public">
439 </Directory></pre>
442 <p>In the above example, authentication will be required for the
443 <code>/var/www/private</code> directory, but will not be required
444 for the <code>/var/www/private/public</code> directory.</p>
446 <p>Since version 2.0.51 <code class="directive">Satisfy</code> directives can
447 be restricted to particular methods by <code class="directive"><a href="../mod/core.html#limit"><Limit></a></code> and <code class="directive"><a href="../mod/core.html#limitexcept"><LimitExcept></a></code> sections.</p>
449 <div class="note"> <h3>Merging of configuration sections</h3>
450 <p>When any directive provided by this module is used in a new
451 configuration section, no directives provided by this module are
452 inherited from previous configuration sections.</p>
458 <li><code class="directive"><a href="#allow">Allow</a></code></li>
459 <li><code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code></li>
463 <div class="bottomlang">
464 <p><span>Available Languages: </span><a href="../en/mod/mod_access_compat.html" title="English"> en </a> |
465 <a href="../fr/mod/mod_access_compat.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
466 <a href="../ja/mod/mod_access_compat.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a></p>
467 </div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our <a href="http://httpd.apache.org/lists.html">mailing lists</a>.</div>
468 <script type="text/javascript"><!--//--><![CDATA[//><!--
469 var comments_shortname = 'httpd';
470 var comments_identifier = 'http://httpd.apache.org/docs/trunk/mod/mod_access_compat.html';
472 if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
473 d.write('<div id="comments_thread"><\/div>');
474 var s = d.createElement('script');
475 s.type = 'text/javascript';
477 s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
478 (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
481 d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
483 })(window, document);
484 //--><!]]></script></div><div id="footer">
485 <p class="apache">Copyright 2015 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
486 <p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/quickreference.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
487 if (typeof(prettyPrint) !== 'undefined') {