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 7 --> 8<title>mod_access_compat - Apache HTTP Server</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"> 13</script> 14 15<link href="/images/favicon.ico" rel="shortcut icon" /></head> 16<body> 17<div id="page-header"> 18<p class="menu"><a href="/mod/">Modules</a> | <a href="/mod/directives.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.4</p> 20<img alt="" src="/images/feather.gif" /></div> 21<div class="up"><a href="./"><img title="<-" alt="<-" src="/images/left.gif" /></a></div> 22<div id="path"> 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.4</a> > <a href="./">Modules</a></div> 24<div id="page-content"> 25<div id="preamble"><h1>Apache Module mod_access_compat</h1> 26<div class="toplang"> 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> 30</div> 31<table class="module"><tr><th><a href="module-dict.html#Description">Description:</a></th><td>Group authorizations based on host (name or IP 32address)</td></tr> 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 37previous versions of Apache httpd 2.x. The directives provided by this module 38have 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> 40<h3>Summary</h3> 41 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 54 other.</p> 55 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> 60 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> 65 </div> 66 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> 73 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> 78 </div> 79 80</div> 81<div id="quickview"><h3 class="directives">Directives</h3> 82<ul id="toc"> 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> 87</ul> 88<h3>See also</h3> 89<ul class="seealso"> 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 95<div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div> 96<div class="directive-section"><h2><a name="Allow" id="Allow">Allow</a> <a name="allow" id="allow">Directive</a></h2> 97<table class="directive"> 98<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Controls which hosts can access an area of the 99server</td></tr> 100<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code> Allow from all|<var>host</var>|env=[!]<var>env-variable</var> 101[<var>host</var>|env=[!]<var>env-variable</var>] ...</code></td></tr> 102<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>directory, .htaccess</td></tr> 103<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>Limit</td></tr> 104<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr> 105<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_access_compat</td></tr> 106</table> 107 <p>The <code class="directive">Allow</code> directive affects which hosts can 108 access an area of the server. Access can be controlled by 109 hostname, IP address, IP address range, or by other 110 characteristics of the client request captured in environment 111 variables.</p> 112 113 <p>The first argument to this directive is always 114 <code>from</code>. The subsequent arguments can take three 115 different forms. If <code>Allow from all</code> is specified, then 116 all hosts are allowed access, subject to the configuration of the 117 <code class="directive"><a href="#deny">Deny</a></code> and <code class="directive"><a href="#order">Order</a></code> directives as discussed 118 below. To allow only particular hosts or groups of hosts to access 119 the server, the <em>host</em> can be specified in any of the 120 following formats:</p> 121 122 <dl> 123 <dt>A (partial) domain-name</dt> 124 125 <dd> 126 <pre class="prettyprint lang-config">Allow from example.org 127Allow from .net example.edu</pre> 128 129 <p>Hosts whose names match, or end in, this string are allowed 130 access. Only complete components are matched, so the above 131 example will match <code>foo.example.org</code> but it will not 132 match <code>fooexample.org</code>. This configuration will cause 133 Apache httpd to perform a double DNS lookup on the client IP 134 address, regardless of the setting of the <code class="directive"><a href="/mod/core.html#hostnamelookups">HostnameLookups</a></code> directive. It will do 135 a reverse DNS lookup on the IP address to find the associated 136 hostname, and then do a forward lookup on the hostname to assure 137 that it matches the original IP address. Only if the forward 138 and reverse DNS are consistent and the hostname matches will 139 access be allowed.</p></dd> 140 141 <dt>A full IP address</dt> 142 143 <dd> 144 <pre class="prettyprint lang-config">Allow from 10.1.2.3 145Allow from 192.168.1.104 192.168.1.205</pre> 146 147 <p>An IP address of a host allowed access</p></dd> 148 149 <dt>A partial IP address</dt> 150 151 <dd> 152 <pre class="prettyprint lang-config">Allow from 10.1 153Allow from 10 172.20 192.168.2</pre> 154 155 <p>The first 1 to 3 bytes of an IP address, for subnet 156 restriction.</p></dd> 157 158 <dt>A network/netmask pair</dt> 159 160 <dd> 161 <pre class="prettyprint lang-config">Allow from 10.1.0.0/255.255.0.0</pre> 162 163 <p>A network a.b.c.d, and a netmask w.x.y.z. For more 164 fine-grained subnet restriction.</p></dd> 165 166 <dt>A network/nnn CIDR specification</dt> 167 168 <dd> 169 <pre class="prettyprint lang-config">Allow from 10.1.0.0/16</pre> 170 171 <p>Similar to the previous case, except the netmask consists of 172 nnn high-order 1 bits.</p></dd> 173 </dl> 174 175 <p>Note that the last three examples above match exactly the 176 same set of hosts.</p> 177 178 <p>IPv6 addresses and IPv6 subnets can be specified as shown 179 below:</p> 180 181 <pre class="prettyprint lang-config">Allow from 2001:db8::a00:20ff:fea7:ccea 182Allow from 2001:db8::a00:20ff:fea7:ccea/10</pre> 183 184 185 <p>The third format of the arguments to the 186 <code class="directive">Allow</code> directive allows access to the server 187 to be controlled based on the existence of an <a href="/env.html">environment variable</a>. When <code>Allow from 188 env=<var>env-variable</var></code> is specified, then the request is 189 allowed access if the environment variable <var>env-variable</var> 190 exists. When <code>Allow from env=!<var>env-variable</var></code> is 191 specified, then the request is allowed access if the environment 192 variable <var>env-variable</var> doesn't exist. 193 The server provides the ability to set environment 194 variables in a flexible way based on characteristics of the client 195 request using the directives provided by 196 <code class="module"><a href="/mod/mod_setenvif.html">mod_setenvif</a></code>. Therefore, this directive can be 197 used to allow access based on such factors as the clients 198 <code>User-Agent</code> (browser type), <code>Referer</code>, or 199 other HTTP request header fields.</p> 200 201 <pre class="prettyprint lang-config">SetEnvIf User-Agent ^KnockKnock/2\.0 let_me_in 202<Directory /docroot> 203 Order Deny,Allow 204 Deny from all 205 Allow from env=let_me_in 206</Directory></pre> 207 208 209 <p>In this case, browsers with a user-agent string beginning 210 with <code>KnockKnock/2.0</code> will be allowed access, and all 211 others will be denied.</p> 212 213 <div class="note"> <h3>Merging of configuration sections</h3> 214 <p>When any directive provided by this module is used in a new 215 configuration section, no directives provided by this module are 216 inherited from previous configuration sections.</p> 217 </div> 218 219 220</div> 221<div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div> 222<div class="directive-section"><h2><a name="Deny" id="Deny">Deny</a> <a name="deny" id="deny">Directive</a></h2> 223<table class="directive"> 224<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Controls which hosts are denied access to the 225server</td></tr> 226<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code> Deny from all|<var>host</var>|env=[!]<var>env-variable</var> 227[<var>host</var>|env=[!]<var>env-variable</var>] ...</code></td></tr> 228<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>directory, .htaccess</td></tr> 229<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>Limit</td></tr> 230<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr> 231<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_access_compat</td></tr> 232</table> 233 <p>This directive allows access to the server to be restricted 234 based on hostname, IP address, or environment variables. The 235 arguments for the <code class="directive">Deny</code> directive are 236 identical to the arguments for the <code class="directive"><a href="#allow">Allow</a></code> directive.</p> 237 238</div> 239<div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div> 240<div class="directive-section"><h2><a name="Order" id="Order">Order</a> <a name="order" id="order">Directive</a></h2> 241<table class="directive"> 242<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Controls the default access state and the order in which 243<code class="directive">Allow</code> and <code class="directive">Deny</code> are 244evaluated.</td></tr> 245<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code> Order <var>ordering</var></code></td></tr> 246<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>Order Deny,Allow</code></td></tr> 247<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>directory, .htaccess</td></tr> 248<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>Limit</td></tr> 249<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr> 250<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_access_compat</td></tr> 251</table> 252 253 <p>The <code class="directive">Order</code> directive, along with the 254 <code class="directive"><a href="#allow">Allow</a></code> and 255 <code class="directive"><a href="#deny">Deny</a></code> directives, 256 controls a three-pass access control system. The first pass 257 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 258 by the <code class="directive"><a href="#order">Order</a></code> 259 directive. The second pass parses the rest of the directives 260 (<code class="directive"><a href="#deny">Deny</a></code> or 261 <code class="directive"><a href="#allow">Allow</a></code>). The third 262 pass applies to all requests which do not match either of the first 263 two.</p> 264 265 <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 266 processed, unlike a typical firewall, where only the first match is 267 used. The last match is effective (also unlike a typical firewall). 268 Additionally, the order in which lines appear in the configuration 269 files is not significant -- all <code class="directive"><a href="#allow">Allow</a></code> lines are processed as 270 one group, all <code class="directive"><a href="#deny">Deny</a></code> lines are considered as 271 another, and the default state is considered by itself.</p> 272 273 <p><em>Ordering</em> is one of:</p> 274 275 <dl> 276 <dt><code>Allow,Deny</code></dt> 277 278 <dd>First, all <code class="directive"><a href="#allow">Allow</a></code> directives are 279 evaluated; at least one must match, or the request is rejected. 280 Next, all <code class="directive"><a href="#deny">Deny</a></code> 281 directives are evaluated. If any matches, the request is rejected. 282 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 283 by default.</dd> 284 285 <dt><code>Deny,Allow</code></dt> 286 287 <dd>First, all <code class="directive"><a href="#deny">Deny</a></code> directives are 288 evaluated; if any match, the request is denied 289 <strong>unless</strong> it also matches an <code class="directive"><a href="#allow">Allow</a></code> directive. Any 290 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 291 permitted.</dd> 292 293 <dt><code>Mutual-failure</code></dt> 294 295 <dd>This order has the same effect as <code>Order 296 Allow,Deny</code> and is deprecated in its favor.</dd> 297 </dl> 298 299 <p>Keywords may only be separated by a comma; <em>no whitespace</em> 300 is allowed between them.</p> 301 302 <table class="bordered"> 303 <tr> 304 <th>Match</th> 305 <th>Allow,Deny result</th> 306 <th>Deny,Allow result</th> 307 </tr><tr> 308 <th>Match Allow only</th> 309 <td>Request allowed</td> 310 <td>Request allowed</td> 311 </tr><tr> 312 <th>Match Deny only</th> 313 <td>Request denied</td> 314 <td>Request denied</td> 315 </tr><tr> 316 <th>No match</th> 317 <td>Default to second directive: Denied</td> 318 <td>Default to second directive: Allowed</td> 319 </tr><tr> 320 <th>Match both Allow & Deny</th> 321 <td>Final match controls: Denied</td> 322 <td>Final match controls: Allowed</td> 323 </tr> 324 </table> 325 326 <p>In the following example, all hosts in the example.org domain 327 are allowed access; all other hosts are denied access.</p> 328 329 <pre class="prettyprint lang-config">Order Deny,Allow 330Deny from all 331Allow from example.org</pre> 332 333 334 <p>In the next example, all hosts in the example.org domain are 335 allowed access, except for the hosts which are in the 336 foo.example.org subdomain, who are denied access. All hosts not 337 in the example.org domain are denied access because the default 338 state is to <code class="directive"><a href="#deny">Deny</a></code> 339 access to the server.</p> 340 341 <pre class="prettyprint lang-config">Order Allow,Deny 342Allow from example.org 343Deny from foo.example.org</pre> 344 345 346 <p>On the other hand, if the <code class="directive">Order</code> in the 347 last example is changed to <code>Deny,Allow</code>, all hosts will 348 be allowed access. This happens because, regardless of the actual 349 ordering of the directives in the configuration file, the 350 <code>Allow from example.org</code> will be evaluated last and will 351 override the <code>Deny from foo.example.org</code>. All hosts not in 352 the <code>example.org</code> domain will also be allowed access 353 because the default state is <code class="directive"><a href="#allow">Allow</a></code>.</p> 354 355 <p>The presence of an <code class="directive">Order</code> directive can 356 affect access to a part of the server even in the absence of 357 accompanying <code class="directive"><a href="#allow">Allow</a></code> 358 and <code class="directive"><a href="#deny">Deny</a></code> 359 directives because of its effect on the default access state. For 360 example,</p> 361 362 <pre class="prettyprint lang-config"><Directory /www> 363 Order Allow,Deny 364</Directory></pre> 365 366 367 <p>will Deny all access to the <code>/www</code> directory 368 because the default access state is set to 369 <code class="directive"><a href="#deny">Deny</a></code>.</p> 370 371 <p>The <code class="directive">Order</code> directive controls the order of access 372 directive processing only within each phase of the server's 373 configuration processing. This implies, for example, that an 374 <code class="directive"><a href="#allow">Allow</a></code> or <code class="directive"><a href="#deny">Deny</a></code> directive occurring in a 375 <code class="directive"><a href="/mod/core.html#location"><Location></a></code> section will 376 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 377 <code class="directive"><a href="/mod/core.html#directory"><Directory></a></code> section or 378 <code>.htaccess</code> file, regardless of the setting of the 379 <code class="directive">Order</code> directive. For details on the merging 380 of configuration sections, see the documentation on <a href="/sections.html">How Directory, Location and Files sections 381 work</a>.</p> 382 383 <div class="note"> <h3>Merging of configuration sections</h3> 384 <p>When any directive provided by this module is used in a new 385 configuration section, no directives provided by this module are 386 inherited from previous configuration sections.</p> 387 </div> 388 389 390</div> 391<div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div> 392<div class="directive-section"><h2><a name="Satisfy" id="Satisfy">Satisfy</a> <a name="satisfy" id="satisfy">Directive</a></h2> 393<table class="directive"> 394<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Interaction between host-level access control and 395user authentication</td></tr> 396<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>Satisfy Any|All</code></td></tr> 397<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>Satisfy All</code></td></tr> 398<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>directory, .htaccess</td></tr> 399<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>AuthConfig</td></tr> 400<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr> 401<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_access_compat</td></tr> 402<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Influenced 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> in version 2.0.51 and 403later</td></tr> 404</table> 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> 416 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> 421 422 <pre class="prettyprint lang-config">Require valid-user 423Allow from 192.168.1 424Satisfy Any</pre> 425 426 427 <p> 428 Another frequent use of the <code class="directive">Satisfy</code> directive 429 is to relax access restrictions for a subdirectory: 430 </p> 431 432 <pre class="prettyprint lang-config"><Directory /var/www/private> 433 Require valid-user 434</Directory> 435 436<Directory /var/www/private/public> 437 Allow from all 438 Satisfy Any 439</Directory></pre> 440 441 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> 445 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> 448 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> 453 </div> 454 455 456<h3>See also</h3> 457<ul> 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> 460</ul> 461</div> 462</div> 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[//><!-- 469var comments_shortname = 'httpd'; 470var comments_identifier = 'http://httpd.apache.org/docs/2.4/mod/mod_access_compat.html'; 471(function(w, d) { 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'; 476 s.async = true; 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); 479 } 480 else { 481 d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>'); 482 } 483})(window, document); 484//--><!]]></script></div><div id="footer"> 485<p class="apache">Copyright 2014 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/directives.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[//><!-- 487if (typeof(prettyPrint) !== 'undefined') { 488 prettyPrint(); 489} 490//--><!]]></script> 491</body></html>
