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>Apache HTTP Server Tutorial: .htaccess files - 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>
18 <body id="manual-page"><div id="page-header">
19 <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>
20 <p class="apache">Apache HTTP Server Version 2.5</p>
21 <img alt="" src="../images/feather.png" /></div>
22 <div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div>
24 <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="./">How-To / Tutorials</a></div><div id="page-content"><div id="preamble"><h1>Apache HTTP Server Tutorial: .htaccess files</h1>
26 <p><span>Available Languages: </span><a href="../en/howto/htaccess.html" title="English"> en </a> |
27 <a href="../fr/howto/htaccess.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
28 <a href="../ja/howto/htaccess.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
29 <a href="../ko/howto/htaccess.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> |
30 <a href="../pt-br/howto/htaccess.html" hreflang="pt-br" rel="alternate" title="Português (Brasil)"> pt-br </a></p>
33 <p><code>.htaccess</code> files provide a way to make configuration
34 changes on a per-directory basis.</p>
36 <div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#related">.htaccess files</a></li>
37 <li><img alt="" src="../images/down.gif" /> <a href="#what">What they are/How to use them</a></li>
38 <li><img alt="" src="../images/down.gif" /> <a href="#when">When (not) to use .htaccess files</a></li>
39 <li><img alt="" src="../images/down.gif" /> <a href="#how">How directives are applied</a></li>
40 <li><img alt="" src="../images/down.gif" /> <a href="#auth">Authentication example</a></li>
41 <li><img alt="" src="../images/down.gif" /> <a href="#ssi">Server Side Includes example</a></li>
42 <li><img alt="" src="../images/down.gif" /> <a href="#rewrite">Rewrite Rules in .htaccess files</a></li>
43 <li><img alt="" src="../images/down.gif" /> <a href="#cgi">CGI example</a></li>
44 <li><img alt="" src="../images/down.gif" /> <a href="#troubleshoot">Troubleshooting</a></li>
45 </ul><h3>See also</h3><ul class="seealso"><li><a href="#comments_section">Comments</a></li></ul></div>
46 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
48 <h2><a name="related" id="related">.htaccess files</a></h2>
49 <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="../mod/core.html">core</a></code></li><li><code class="module"><a href="../mod/mod_authn_file.html">mod_authn_file</a></code></li><li><code class="module"><a href="../mod/mod_authz_groupfile.html">mod_authz_groupfile</a></code></li><li><code class="module"><a href="../mod/mod_cgi.html">mod_cgi</a></code></li><li><code class="module"><a href="../mod/mod_include.html">mod_include</a></code></li><li><code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#accessfilename">AccessFileName</a></code></li><li><code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code></li><li><code class="directive"><a href="../mod/core.html#options">Options</a></code></li><li><code class="directive"><a href="../mod/mod_mime.html#addhandler">AddHandler</a></code></li><li><code class="directive"><a href="../mod/core.html#sethandler">SetHandler</a></code></li><li><code class="directive"><a href="../mod/mod_authn_core.html#authtype">AuthType</a></code></li><li><code class="directive"><a href="../mod/mod_authn_core.html#authname">AuthName</a></code></li><li><code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code></li><li><code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code></li><li><code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code></li></ul></td></tr></table>
51 <div class="note">You should avoid using <code>.htaccess</code> files completely if you have access to
52 httpd main server config file. Using <code>.htaccess</code> files slows down your Apache http server.
53 Any directive that you can include in a <code>.htaccess</code> file is better set in a <code class="directive"><a href="../mod/core.html#directory">Directory</a></code> block, as it will have the same effect with better performance.</div>
54 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
56 <h2><a name="what" id="what">What they are/How to use them</a></h2>
59 <p><code>.htaccess</code> files (or "distributed configuration files")
60 provide a way to make configuration changes on a per-directory basis. A
61 file, containing one or more configuration directives, is placed in a
62 particular document directory, and the directives apply to that
63 directory, and all subdirectories thereof.</p>
65 <div class="note"><h3>Note:</h3>
66 <p>If you want to call your <code>.htaccess</code> file something
67 else, you can change the name of the file using the <code class="directive"><a href="../mod/core.html#accessfilename">AccessFileName</a></code> directive. For example,
68 if you would rather call the file <code>.config</code> then you
69 can put the following in your server configuration file:</p>
71 <pre class="prettyprint lang-config">AccessFileName ".config"</pre>
75 <p>In general, <code>.htaccess</code> files use the same syntax as
76 the <a href="../configuring.html#syntax">main configuration
77 files</a>. What you can put in these files is determined by the
78 <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> directive. This
79 directive specifies, in categories, what directives will be
80 honored if they are found in a <code>.htaccess</code> file. If a
81 directive is permitted in a <code>.htaccess</code> file, the
82 documentation for that directive will contain an Override section,
83 specifying what value must be in <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> in order for that
84 directive to be permitted.</p>
86 <p>For example, if you look at the documentation for the <code class="directive"><a href="../mod/core.html#adddefaultcharset">AddDefaultCharset</a></code>
87 directive, you will find that it is permitted in <code>.htaccess</code>
88 files. (See the Context line in the directive summary.) The <a href="../mod/directive-dict.html#Context">Override</a> line reads
89 <code>FileInfo</code>. Thus, you must have at least
90 <code>AllowOverride FileInfo</code> in order for this directive to be
91 honored in <code>.htaccess</code> files.</p>
93 <div class="example"><h3>Example:</h3><table>
95 <td><a href="../mod/directive-dict.html#Context">Context:</a></td>
96 <td>server config, virtual host, directory, .htaccess</td>
100 <td><a href="../mod/directive-dict.html#Override">Override:</a></td>
105 <p>If you are unsure whether a particular directive is permitted in a
106 <code>.htaccess</code> file, look at the documentation for that
107 directive, and check the Context line for ".htaccess".</p>
108 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
109 <div class="section">
110 <h2><a name="when" id="when">When (not) to use .htaccess files</a></h2>
112 <p>In general, you should only use <code>.htaccess</code> files when
113 you don't have access to the main server configuration file. There is,
114 for example, a common misconception that user authentication should
115 always be done in <code>.htaccess</code> files, and, in more recent years,
116 another misconception that <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> directives
117 must go in <code>.htaccess</code> files. This is simply not the
118 case. You can put user authentication configurations in the main server
119 configuration, and this is, in fact, the preferred way to do
120 things. Likewise, <code>mod_rewrite</code> directives work better,
121 in many respects, in the main server configuration.</p>
123 <p><code>.htaccess</code> files should be used in a case where the
124 content providers need to make configuration changes to the server on a
125 per-directory basis, but do not have root access on the server system.
126 In the event that the server administrator is not willing to make
127 frequent configuration changes, it might be desirable to permit
128 individual users to make these changes in <code>.htaccess</code> files
129 for themselves. This is particularly true, for example, in cases where
130 ISPs are hosting multiple user sites on a single machine, and want
131 their users to be able to alter their configuration.</p>
133 <p>However, in general, use of <code>.htaccess</code> files should be
134 avoided when possible. Any configuration that you would consider
135 putting in a <code>.htaccess</code> file, can just as effectively be
136 made in a <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> section in your main server
137 configuration file.</p>
139 <p>There are two main reasons to avoid the use of
140 <code>.htaccess</code> files.</p>
142 <p>The first of these is performance. When <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
143 is set to allow the use of <code>.htaccess</code> files, httpd will
144 look in every directory for <code>.htaccess</code> files. Thus,
145 permitting <code>.htaccess</code> files causes a performance hit,
146 whether or not you actually even use them! Also, the
147 <code>.htaccess</code> file is loaded every time a document is
150 <p>Further note that httpd must look for <code>.htaccess</code> files
151 in all higher-level directories, in order to have a full complement of
152 directives that it must apply. (See section on <a href="#how">how
153 directives are applied</a>.) Thus, if a file is requested out of a
154 directory <code>/www/htdocs/example</code>, httpd must look for the
157 <div class="example"><p><code>
160 /www/htdocs/.htaccess<br />
161 /www/htdocs/example/.htaccess
164 <p>And so, for each file access out of that directory, there are 4
165 additional file-system accesses, even if none of those files are
166 present. (Note that this would only be the case if
167 <code>.htaccess</code> files were enabled for <code>/</code>, which
168 is not usually the case.)</p>
170 <p>In the case of <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> directives, in
171 <code>.htaccess</code> context these regular expressions must be
172 re-compiled with every request to the directory, whereas in main
173 server configuration context they are compiled once and cached.
174 Additionally, the rules themselves are more complicated, as one must
175 work around the restrictions that come with per-directory context
176 and <code>mod_rewrite</code>. Consult the <a href="../rewrite/intro.html#htaccess">Rewrite Guide</a> for more
177 detail on this subject.</p>
179 <p>The second consideration is one of security. You are permitting
180 users to modify server configuration, which may result in changes over
181 which you have no control. Carefully consider whether you want to give
182 your users this privilege. Note also that giving users less
183 privileges than they need will lead to additional technical support
184 requests. Make sure you clearly tell your users what level of
185 privileges you have given them. Specifying exactly what you have set
186 <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> to, and pointing them
187 to the relevant documentation, will save yourself a lot of confusion
190 <p>Note that it is completely equivalent to put a <code>.htaccess</code>
191 file in a directory <code>/www/htdocs/example</code> containing a
192 directive, and to put that same directive in a Directory section
193 <code><Directory "/www/htdocs/example"></code> in your main server
196 <p><code>.htaccess</code> file in <code>/www/htdocs/example</code>:</p>
198 <div class="example"><h3>Contents of .htaccess file in
199 <code>/www/htdocs/example</code></h3><pre class="prettyprint lang-config">AddType text/example ".exm"</pre>
202 <div class="example"><h3>Section from your <code>httpd.conf</code>
203 file</h3><pre class="prettyprint lang-config"><Directory "/www/htdocs/example">
204 AddType text/example ".exm"
205 </Directory></pre>
208 <p>However, putting this configuration in your server configuration
209 file will result in less of a performance hit, as the configuration is
210 loaded once when httpd starts, rather than every time a file is
213 <p>The use of <code>.htaccess</code> files can be disabled completely
214 by setting the <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
215 directive to <code>none</code>:</p>
217 <pre class="prettyprint lang-config">AllowOverride None</pre>
219 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
220 <div class="section">
221 <h2><a name="how" id="how">How directives are applied</a></h2>
223 <p>The configuration directives found in a <code>.htaccess</code> file
224 are applied to the directory in which the <code>.htaccess</code> file
225 is found, and to all subdirectories thereof. However, it is important
226 to also remember that there may have been <code>.htaccess</code> files
227 in directories higher up. Directives are applied in the order that they
228 are found. Therefore, a <code>.htaccess</code> file in a particular
229 directory may override directives found in <code>.htaccess</code> files
230 found higher up in the directory tree. And those, in turn, may have
231 overridden directives found yet higher up, or in the main server
232 configuration file itself.</p>
236 <p>In the directory <code>/www/htdocs/example1</code> we have a
237 <code>.htaccess</code> file containing the following:</p>
239 <pre class="prettyprint lang-config">Options +ExecCGI</pre>
242 <p>(Note: you must have "<code>AllowOverride Options</code>" in effect
243 to permit the use of the "<code class="directive"><a href="../mod/core.html#options">Options</a></code>" directive in
244 <code>.htaccess</code> files.)</p>
246 <p>In the directory <code>/www/htdocs/example1/example2</code> we have
247 a <code>.htaccess</code> file containing:</p>
249 <pre class="prettyprint lang-config">Options Includes</pre>
252 <p>Because of this second <code>.htaccess</code> file, in the directory
253 <code>/www/htdocs/example1/example2</code>, CGI execution is not
254 permitted, as only <code>Options Includes</code> is in effect, which
255 completely overrides any earlier setting that may have been in
258 <h3><a name="merge" id="merge">Merging of .htaccess with the main
259 configuration files</a></h3>
261 <p>As discussed in the documentation on <a href="../sections.html">Configuration Sections</a>,
262 <code>.htaccess</code> files can override the <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> sections for
263 the corresponding directory, but will be overridden by other types
264 of configuration sections from the main configuration files. This
265 fact can be used to enforce certain configurations, even in the
266 presence of a liberal <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> setting. For example, to
267 prevent script execution while allowing anything else to be set in
268 <code>.htaccess</code> you can use:</p>
270 <pre class="prettyprint lang-config"><Directory "/www/htdocs">
275 Options +IncludesNoExec -ExecCGI<br />
276 </Location></pre>
279 <div class="note">This example assumes that your <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> is <code>/www/htdocs</code>.</div>
282 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
283 <div class="section">
284 <h2><a name="auth" id="auth">Authentication example</a></h2>
286 <p>If you jumped directly to this part of the document to find out how
287 to do authentication, it is important to note one thing. There is a
288 common misconception that you are required to use
289 <code>.htaccess</code> files in order to implement password
290 authentication. This is not the case. Putting authentication directives
291 in a <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code>
292 section, in your main server configuration file, is the preferred way
293 to implement this, and <code>.htaccess</code> files should be used only
294 if you don't have access to the main server configuration file. See <a href="#when">above</a> for a discussion of when you should and should
295 not use <code>.htaccess</code> files.</p>
297 <p>Having said that, if you still think you need to use a
298 <code>.htaccess</code> file, you may find that a configuration such as
299 what follows may work for you.</p>
301 <p><code>.htaccess</code> file contents:</p>
303 <pre class="prettyprint lang-config">AuthType Basic
304 AuthName "Password Required"
305 AuthUserFile "/www/passwords/password.file"
306 AuthGroupFile "/www/passwords/group.file"
307 Require group admins</pre>
310 <p>Note that <code>AllowOverride AuthConfig</code> must be in effect
311 for these directives to have any effect.</p>
313 <p>Please see the <a href="auth.html">authentication tutorial</a> for a
314 more complete discussion of authentication and authorization.</p>
315 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
316 <div class="section">
317 <h2><a name="ssi" id="ssi">Server Side Includes example</a></h2>
319 <p>Another common use of <code>.htaccess</code> files is to enable
320 Server Side Includes for a particular directory. This may be done with
321 the following configuration directives, placed in a
322 <code>.htaccess</code> file in the desired directory:</p>
324 <pre class="prettyprint lang-config">Options +Includes
325 AddType text/html "shtml"
326 AddHandler server-parsed shtml</pre>
329 <p>Note that <code>AllowOverride Options</code> and <code>AllowOverride
330 FileInfo</code> must both be in effect for these directives to have any
333 <p>Please see the <a href="ssi.html">SSI tutorial</a> for a more
334 complete discussion of server-side includes.</p>
335 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
336 <div class="section">
337 <h2><a name="rewrite" id="rewrite">Rewrite Rules in .htaccess files</a></h2>
338 <p>When using <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> in
339 <code>.htaccess</code> files, be aware that the per-directory context
340 changes things a bit. In particular, rules are taken to be relative to
341 the current directory, rather than being the original requested URI.
342 Consider the following examples:</p>
344 <pre class="prettyprint lang-config"># In httpd.conf
345 RewriteRule "^/images/(.+)\.jpg" "/images/$1.png"
347 # In .htaccess in root dir
348 RewriteRule "^images/(.+)\.jpg" "images/$1.png"
350 # In .htaccess in images/
351 RewriteRule "^(.+)\.jpg" "$1.png"</pre>
354 <p>In a <code>.htaccess</code> in your document directory, the leading
355 slash is removed from the value supplied to <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code>, and in the
356 <code>images</code> subdirectory, <code>/images/</code> is removed from
357 it. Thus, your regular expression needs to omit that portion as
360 <p>Consult the <a href="../rewrite/">mod_rewrite documentation</a> for
361 further details on using <code>mod_rewrite</code>.</p>
363 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
364 <div class="section">
365 <h2><a name="cgi" id="cgi">CGI example</a></h2>
367 <p>Finally, you may wish to use a <code>.htaccess</code> file to permit
368 the execution of CGI programs in a particular directory. This may be
369 implemented with the following configuration:</p>
371 <pre class="prettyprint lang-config">Options +ExecCGI
372 AddHandler cgi-script "cgi" "pl"</pre>
375 <p>Alternately, if you wish to have all files in the given directory be
376 considered to be CGI programs, this may be done with the following
379 <pre class="prettyprint lang-config">Options +ExecCGI
380 SetHandler cgi-script</pre>
383 <p>Note that <code>AllowOverride Options</code> and <code>AllowOverride
384 FileInfo</code> must both be in effect for these directives to have any
387 <p>Please see the <a href="cgi.html">CGI tutorial</a> for a more
388 complete discussion of CGI programming and configuration.</p>
390 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
391 <div class="section">
392 <h2><a name="troubleshoot" id="troubleshoot">Troubleshooting</a></h2>
394 <p>When you put configuration directives in a <code>.htaccess</code>
395 file, and you don't get the desired effect, there are a number of
396 things that may be going wrong.</p>
398 <p>Most commonly, the problem is that <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> is not
399 set such that your configuration directives are being honored. Make
400 sure that you don't have a <code>AllowOverride None</code> in effect
401 for the file scope in question. A good test for this is to put garbage
402 in your <code>.htaccess</code> file and reload the page. If a server error is
403 not generated, then you almost certainly have <code>AllowOverride
404 None</code> in effect.</p>
406 <p>If, on the other hand, you are getting server errors when trying to
407 access documents, check your httpd error log. It will likely tell you
408 that the directive used in your <code>.htaccess</code> file is not
411 <div class="example"><p><code>
412 [Fri Sep 17 18:43:16 2010] [alert] [client 192.168.200.51] /var/www/html/.htaccess: DirectoryIndex not allowed here
415 <p>This will indicate either that you've used a directive that is
416 never permitted in <code>.htaccess</code> files, or that you simply
417 don't have <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> set to
418 a level sufficient for the directive you've used. Consult the
419 documentation for that particular directive to determine which is
422 <p>Alternately, it may tell you that you had a syntax error in your
423 usage of the directive itself.</p>
425 <div class="example"><p><code>
426 [Sat Aug 09 16:22:34 2008] [alert] [client 192.168.200.51] /var/www/html/.htaccess: RewriteCond: bad flag delimiters
429 <p>In this case, the error message should be specific to the
430 particular syntax error that you have committed.</p>
433 <div class="bottomlang">
434 <p><span>Available Languages: </span><a href="../en/howto/htaccess.html" title="English"> en </a> |
435 <a href="../fr/howto/htaccess.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
436 <a href="../ja/howto/htaccess.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
437 <a href="../ko/howto/htaccess.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> |
438 <a href="../pt-br/howto/htaccess.html" hreflang="pt-br" rel="alternate" title="Português (Brasil)"> pt-br </a></p>
439 </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>
440 <script type="text/javascript"><!--//--><![CDATA[//><!--
441 var comments_shortname = 'httpd';
442 var comments_identifier = 'http://httpd.apache.org/docs/trunk/howto/htaccess.html';
444 if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
445 d.write('<div id="comments_thread"><\/div>');
446 var s = d.createElement('script');
447 s.type = 'text/javascript';
449 s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
450 (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
453 d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
455 })(window, document);
456 //--><!]]></script></div><div id="footer">
457 <p class="apache">Copyright 2016 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>
458 <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[//><!--
459 if (typeof(prettyPrint) !== 'undefined') {