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 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
5 This file is generated from xml source: DO NOT EDIT
6 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
8 <title>mod_access_compat - Apache HTTP Server Version 2.5</title>
9 <link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
10 <link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
11 <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" />
12 <script src="../style/scripts/prettify.min.js" type="text/javascript">
15 <link href="../images/favicon.ico" rel="shortcut icon" /></head>
17 <div id="page-header">
18 <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>
19 <p class="apache">Apache HTTP Server Version 2.5</p>
20 <img alt="" src="../images/feather.gif" /></div>
21 <div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div>
23 <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>
24 <div id="page-content">
25 <div id="preamble"><h1>Apache Module mod_access_compat</h1>
27 <p><span>Available Languages: </span><a href="../en/mod/mod_access_compat.html" title="English"> en </a> |
28 <a href="../fr/mod/mod_access_compat.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
29 <a href="../ja/mod/mod_access_compat.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a></p>
31 <table class="module"><tr><th><a href="module-dict.html#Description">Description:</a></th><td>Group authorizations based on host (name or IP
33 <tr><th><a href="module-dict.html#Status">Status:</a></th><td>Extension</td></tr>
34 <tr><th><a href="module-dict.html#ModuleIdentifier">Module Identifier:</a></th><td>access_compat_module</td></tr>
35 <tr><th><a href="module-dict.html#SourceFile">Source File:</a></th><td>mod_access_compat.c</td></tr>
36 <tr><th><a href="module-dict.html#Compatibility">Compatibility:</a></th><td>Available in Apache HTTP Server 2.3 as a compatibility module with
37 previous versions of Apache httpd 2.x. The directives provided by this module
38 have been deprecated by the new authz refactoring. Please see
39 <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code></td></tr></table>
42 <p>The directives provided by <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> are
43 used in <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code>,
44 <code class="directive"><a href="../mod/core.html#files"><Files></a></code>, and
45 <code class="directive"><a href="../mod/core.html#location"><Location></a></code> sections
46 as well as <code><a href="core.html#accessfilename">.htaccess</a>
47 </code> files to control access to particular parts of the server.
48 Access can be controlled based on the client hostname, IP address, or
49 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
50 specify which clients are or are not allowed access to the server,
51 while the <code class="directive"><a href="#order">Order</a></code>
52 directive sets the default access state, and configures how the
53 <code class="directive"><a href="#allow">Allow</a></code> and <code class="directive"><a href="#deny">Deny</a></code> directives interact with each
56 <p>Both host-based access restrictions and password-based
57 authentication may be implemented simultaneously. In that case,
58 the <code class="directive"><a href="#satisfy">Satisfy</a></code> directive is used
59 to determine how the two sets of restrictions interact.</p>
61 <div class="warning"><h3>Note</h3>
62 <p>The directives provided by <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> have
63 been deprecated by the new authz refactoring. Please see
64 <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code>.</p>
67 <p>In general, access restriction directives apply to all
68 access methods (<code>GET</code>, <code>PUT</code>,
69 <code>POST</code>, etc). This is the desired behavior in most
70 cases. However, it is possible to restrict some methods, while
71 leaving other methods unrestricted, by enclosing the directives
72 in a <code class="directive"><a href="../mod/core.html#limit"><Limit></a></code> section.</p>
74 <div class="note"> <h3>Merging of configuration sections</h3>
75 <p>When any directive provided by this module is used in a new
76 configuration section, no directives provided by this module are
77 inherited from previous configuration sections.</p>
81 <div id="quickview"><h3 class="directives">Directives</h3>
83 <li><img alt="" src="../images/down.gif" /> <a href="#allow">Allow</a></li>
84 <li><img alt="" src="../images/down.gif" /> <a href="#deny">Deny</a></li>
85 <li><img alt="" src="../images/down.gif" /> <a href="#order">Order</a></li>
86 <li><img alt="" src="../images/down.gif" /> <a href="#satisfy">Satisfy</a></li>
90 <li><code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code></li>
91 <li><code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code></li>
92 <li><code class="module"><a href="../mod/mod_authz_core.html">mod_authz_core</a></code></li>
93 </ul><ul class="seealso"><li><a href="#comments_section">Comments</a></li></ul></div>
94 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
95 <div class="directive-section"><h2><a name="Allow" id="Allow">Allow</a> <a name="allow" id="allow">Directive</a></h2>
96 <table class="directive">
97 <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Controls which hosts can access an area of the
99 <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code> Allow from all|<var>host</var>|env=[!]<var>env-variable</var>
100 [<var>host</var>|env=[!]<var>env-variable</var>] ...</code></td></tr>
101 <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>directory, .htaccess</td></tr>
102 <tr><th><a href="directive-dict.html#Override">Override:</a></th><td>Limit</td></tr>
103 <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
104 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_access_compat</td></tr>
106 <p>The <code class="directive">Allow</code> directive affects which hosts can
107 access an area of the server. Access can be controlled by
108 hostname, IP address, IP address range, or by other
109 characteristics of the client request captured in environment
112 <p>The first argument to this directive is always
113 <code>from</code>. The subsequent arguments can take three
114 different forms. If <code>Allow from all</code> is specified, then
115 all hosts are allowed access, subject to the configuration of the
116 <code class="directive"><a href="#deny">Deny</a></code> and <code class="directive"><a href="#order">Order</a></code> directives as discussed
117 below. To allow only particular hosts or groups of hosts to access
118 the server, the <em>host</em> can be specified in any of the
119 following formats:</p>
122 <dt>A (partial) domain-name</dt>
125 <pre class="prettyprint lang-config">Allow from example.org
126 Allow from .net example.edu</pre>
128 <p>Hosts whose names match, or end in, this string are allowed
129 access. Only complete components are matched, so the above
130 example will match <code>foo.example.org</code> but it will not
131 match <code>fooexample.org</code>. This configuration will cause
132 Apache httpd to perform a double DNS lookup on the client IP
133 address, regardless of the setting of the <code class="directive"><a href="../mod/core.html#hostnamelookups">HostnameLookups</a></code> directive. It will do
134 a reverse DNS lookup on the IP address to find the associated
135 hostname, and then do a forward lookup on the hostname to assure
136 that it matches the original IP address. Only if the forward
137 and reverse DNS are consistent and the hostname matches will
138 access be allowed.</p></dd>
140 <dt>A full IP address</dt>
143 <pre class="prettyprint lang-config">Allow from 10.1.2.3
144 Allow from 192.168.1.104 192.168.1.205</pre>
146 <p>An IP address of a host allowed access</p></dd>
148 <dt>A partial IP address</dt>
151 <pre class="prettyprint lang-config">Allow from 10.1
152 Allow from 10 172.20 192.168.2</pre>
154 <p>The first 1 to 3 bytes of an IP address, for subnet
155 restriction.</p></dd>
157 <dt>A network/netmask pair</dt>
160 <pre class="prettyprint lang-config">Allow from 10.1.0.0/255.255.0.0</pre>
162 <p>A network a.b.c.d, and a netmask w.x.y.z. For more
163 fine-grained subnet restriction.</p></dd>
165 <dt>A network/nnn CIDR specification</dt>
168 <pre class="prettyprint lang-config">Allow from 10.1.0.0/16</pre>
170 <p>Similar to the previous case, except the netmask consists of
171 nnn high-order 1 bits.</p></dd>
174 <p>Note that the last three examples above match exactly the
175 same set of hosts.</p>
177 <p>IPv6 addresses and IPv6 subnets can be specified as shown
180 <pre class="prettyprint lang-config">Allow from 2001:db8::a00:20ff:fea7:ccea
181 Allow from 2001:db8::a00:20ff:fea7:ccea/10</pre>
184 <p>The third format of the arguments to the
185 <code class="directive">Allow</code> directive allows access to the server
186 to be controlled based on the existence of an <a href="../env.html">environment variable</a>. When <code>Allow from
187 env=<var>env-variable</var></code> is specified, then the request is
188 allowed access if the environment variable <var>env-variable</var>
189 exists. When <code>Allow from env=!<var>env-variable</var></code> is
190 specified, then the request is allowed access if the environment
191 variable <var>env-variable</var> doesn't exist.
192 The server provides the ability to set environment
193 variables in a flexible way based on characteristics of the client
194 request using the directives provided by
195 <code class="module"><a href="../mod/mod_setenvif.html">mod_setenvif</a></code>. Therefore, this directive can be
196 used to allow access based on such factors as the clients
197 <code>User-Agent</code> (browser type), <code>Referer</code>, or
198 other HTTP request header fields.</p>
200 <pre class="prettyprint lang-config">SetEnvIf User-Agent ^KnockKnock/2\.0 let_me_in
201 <Directory /docroot>
204 Allow from env=let_me_in
205 </Directory></pre>
208 <p>In this case, browsers with a user-agent string beginning
209 with <code>KnockKnock/2.0</code> will be allowed access, and all
210 others will be denied.</p>
212 <div class="note"> <h3>Merging of configuration sections</h3>
213 <p>When any directive provided by this module is used in a new
214 configuration section, no directives provided by this module are
215 inherited from previous configuration sections.</p>
220 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
221 <div class="directive-section"><h2><a name="Deny" id="Deny">Deny</a> <a name="deny" id="deny">Directive</a></h2>
222 <table class="directive">
223 <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Controls which hosts are denied access to the
225 <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code> Deny from all|<var>host</var>|env=[!]<var>env-variable</var>
226 [<var>host</var>|env=[!]<var>env-variable</var>] ...</code></td></tr>
227 <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>directory, .htaccess</td></tr>
228 <tr><th><a href="directive-dict.html#Override">Override:</a></th><td>Limit</td></tr>
229 <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
230 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_access_compat</td></tr>
232 <p>This directive allows access to the server to be restricted
233 based on hostname, IP address, or environment variables. The
234 arguments for the <code class="directive">Deny</code> directive are
235 identical to the arguments for the <code class="directive"><a href="#allow">Allow</a></code> directive.</p>
238 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
239 <div class="directive-section"><h2><a name="Order" id="Order">Order</a> <a name="order" id="order">Directive</a></h2>
240 <table class="directive">
241 <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Controls the default access state and the order in which
242 <code class="directive">Allow</code> and <code class="directive">Deny</code> are
244 <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code> Order <var>ordering</var></code></td></tr>
245 <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>Order Deny,Allow</code></td></tr>
246 <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>directory, .htaccess</td></tr>
247 <tr><th><a href="directive-dict.html#Override">Override:</a></th><td>Limit</td></tr>
248 <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
249 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_access_compat</td></tr>
252 <p>The <code class="directive">Order</code> directive, along with the
253 <code class="directive"><a href="#allow">Allow</a></code> and
254 <code class="directive"><a href="#deny">Deny</a></code> directives,
255 controls a three-pass access control system. The first pass
256 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
257 by the <code class="directive"><a href="#order">Order</a></code>
258 directive. The second pass parses the rest of the directives
259 (<code class="directive"><a href="#deny">Deny</a></code> or
260 <code class="directive"><a href="#allow">Allow</a></code>). The third
261 pass applies to all requests which do not match either of the first
264 <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
265 processed, unlike a typical firewall, where only the first match is
266 used. The last match is effective (also unlike a typical firewall).
267 Additionally, the order in which lines appear in the configuration
268 files is not significant -- all <code class="directive"><a href="#allow">Allow</a></code> lines are processed as
269 one group, all <code class="directive"><a href="#deny">Deny</a></code> lines are considered as
270 another, and the default state is considered by itself.</p>
272 <p><em>Ordering</em> is one of:</p>
275 <dt><code>Allow,Deny</code></dt>
277 <dd>First, all <code class="directive"><a href="#allow">Allow</a></code> directives are
278 evaluated; at least one must match, or the request is rejected.
279 Next, all <code class="directive"><a href="#deny">Deny</a></code>
280 directives are evaluated. If any matches, the request is rejected.
281 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
284 <dt><code>Deny,Allow</code></dt>
286 <dd>First, all <code class="directive"><a href="#deny">Deny</a></code> directives are
287 evaluated; if any match, the request is denied
288 <strong>unless</strong> it also matches an <code class="directive"><a href="#allow">Allow</a></code> directive. Any
289 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
292 <dt><code>Mutual-failure</code></dt>
294 <dd>This order has the same effect as <code>Order
295 Allow,Deny</code> and is deprecated in its favor.</dd>
298 <p>Keywords may only be separated by a comma; <em>no whitespace</em>
299 is allowed between them.</p>
301 <table class="bordered">
304 <th>Allow,Deny result</th>
305 <th>Deny,Allow result</th>
307 <th>Match Allow only</th>
308 <td>Request allowed</td>
309 <td>Request allowed</td>
311 <th>Match Deny only</th>
312 <td>Request denied</td>
313 <td>Request denied</td>
316 <td>Default to second directive: Denied</td>
317 <td>Default to second directive: Allowed</td>
319 <th>Match both Allow & Deny</th>
320 <td>Final match controls: Denied</td>
321 <td>Final match controls: Allowed</td>
325 <p>In the following example, all hosts in the example.org domain
326 are allowed access; all other hosts are denied access.</p>
328 <pre class="prettyprint lang-config">Order Deny,Allow
330 Allow from example.org</pre>
333 <p>In the next example, all hosts in the example.org domain are
334 allowed access, except for the hosts which are in the
335 foo.example.org subdomain, who are denied access. All hosts not
336 in the example.org domain are denied access because the default
337 state is to <code class="directive"><a href="#deny">Deny</a></code>
338 access to the server.</p>
340 <pre class="prettyprint lang-config">Order Allow,Deny
341 Allow from example.org
342 Deny from foo.example.org</pre>
345 <p>On the other hand, if the <code class="directive">Order</code> in the
346 last example is changed to <code>Deny,Allow</code>, all hosts will
347 be allowed access. This happens because, regardless of the actual
348 ordering of the directives in the configuration file, the
349 <code>Allow from example.org</code> will be evaluated last and will
350 override the <code>Deny from foo.example.org</code>. All hosts not in
351 the <code>example.org</code> domain will also be allowed access
352 because the default state is <code class="directive"><a href="#allow">Allow</a></code>.</p>
354 <p>The presence of an <code class="directive">Order</code> directive can
355 affect access to a part of the server even in the absence of
356 accompanying <code class="directive"><a href="#allow">Allow</a></code>
357 and <code class="directive"><a href="#deny">Deny</a></code>
358 directives because of its effect on the default access state. For
361 <pre class="prettyprint lang-config"><Directory /www>
363 </Directory></pre>
366 <p>will Deny all access to the <code>/www</code> directory
367 because the default access state is set to
368 <code class="directive"><a href="#deny">Deny</a></code>.</p>
370 <p>The <code class="directive">Order</code> directive controls the order of access
371 directive processing only within each phase of the server's
372 configuration processing. This implies, for example, that an
373 <code class="directive"><a href="#allow">Allow</a></code> or <code class="directive"><a href="#deny">Deny</a></code> directive occurring in a
374 <code class="directive"><a href="../mod/core.html#location"><Location></a></code> section will
375 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
376 <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> section or
377 <code>.htaccess</code> file, regardless of the setting of the
378 <code class="directive">Order</code> directive. For details on the merging
379 of configuration sections, see the documentation on <a href="../sections.html">How Directory, Location and Files sections
382 <div class="note"> <h3>Merging of configuration sections</h3>
383 <p>When any directive provided by this module is used in a new
384 configuration section, no directives provided by this module are
385 inherited from previous configuration sections.</p>
390 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
391 <div class="directive-section"><h2><a name="Satisfy" id="Satisfy">Satisfy</a> <a name="satisfy" id="satisfy">Directive</a></h2>
392 <table class="directive">
393 <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Interaction between host-level access control and
394 user authentication</td></tr>
395 <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>Satisfy Any|All</code></td></tr>
396 <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>Satisfy All</code></td></tr>
397 <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>directory, .htaccess</td></tr>
398 <tr><th><a href="directive-dict.html#Override">Override:</a></th><td>AuthConfig</td></tr>
399 <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
400 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_access_compat</td></tr>
402 <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
403 either <code>All</code> or <code>Any</code>. This directive is only
404 useful if access to a particular area is being restricted by both
405 username/password <em>and</em> client host address. In this case
406 the default behavior (<code>All</code>) is to require that the client
407 passes the address access restriction <em>and</em> enters a valid
408 username and password. With the <code>Any</code> option the client will be
409 granted access if they either pass the host restriction or enter a
410 valid username and password. This can be used to password restrict
411 an area, but to let clients from particular addresses in without
412 prompting for a password.</p>
414 <p>For example, if you wanted to let people on your network have
415 unrestricted access to a portion of your website, but require that
416 people outside of your network provide a password, you could use a
417 configuration similar to the following:</p>
419 <pre class="prettyprint lang-config">Require valid-user
425 Another frequent use of the <code class="directive">Satisfy</code> directive
426 is to relax access restrictions for a subdirectory:
429 <pre class="prettyprint lang-config"><Directory /var/www/private>
433 <Directory /var/www/private/public>
436 </Directory></pre>
439 <p>In the above example, authentication will be required for the
440 <code>/var/www/private</code> directory, but will not be required
441 for the <code>/var/www/private/public</code> directory.</p>
443 <p>Since version 2.0.51 <code class="directive">Satisfy</code> directives can
444 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>
446 <div class="note"> <h3>Merging of configuration sections</h3>
447 <p>When any directive provided by this module is used in a new
448 configuration section, no directives provided by this module are
449 inherited from previous configuration sections.</p>
455 <li><code class="directive"><a href="#allow">Allow</a></code></li>
456 <li><code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code></li>
461 <div class="bottomlang">
462 <p><span>Available Languages: </span><a href="../en/mod/mod_access_compat.html" title="English"> en </a> |
463 <a href="../fr/mod/mod_access_compat.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
464 <a href="../ja/mod/mod_access_compat.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a></p>
465 </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>
466 <script type="text/javascript"><!--//--><![CDATA[//><!--
467 var comments_shortname = 'httpd';
468 var comments_identifier = 'http://httpd.apache.org/docs/trunk/mod/mod_access_compat.html';
470 if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
471 d.write('<div id="comments_thread"><\/div>');
472 var s = d.createElement('script');
473 s.type = 'text/javascript';
475 s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
476 (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
479 d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
481 })(window, document);
482 //--><!]]></script></div><div id="footer">
483 <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>
484 <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[//><!--
485 if (typeof(prettyPrint) !== 'undefined') {