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="../es/howto/htaccess.html" hreflang="es" rel="alternate" title="Español"> es </a> |
28 <a href="../fr/howto/htaccess.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
29 <a href="../ja/howto/htaccess.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
30 <a href="../ko/howto/htaccess.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> |
31 <a href="../pt-br/howto/htaccess.html" hreflang="pt-br" rel="alternate" title="Português (Brasil)"> pt-br </a></p>
34 <p><code>.htaccess</code> files provide a way to make configuration
35 changes on a per-directory basis.</p>
37 <div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#related">.htaccess files</a></li>
38 <li><img alt="" src="../images/down.gif" /> <a href="#what">What they are/How to use them</a></li>
39 <li><img alt="" src="../images/down.gif" /> <a href="#when">When (not) to use .htaccess files</a></li>
40 <li><img alt="" src="../images/down.gif" /> <a href="#how">How directives are applied</a></li>
41 <li><img alt="" src="../images/down.gif" /> <a href="#auth">Authentication example</a></li>
42 <li><img alt="" src="../images/down.gif" /> <a href="#ssi">Server Side Includes example</a></li>
43 <li><img alt="" src="../images/down.gif" /> <a href="#rewrite">Rewrite Rules in .htaccess files</a></li>
44 <li><img alt="" src="../images/down.gif" /> <a href="#cgi">CGI example</a></li>
45 <li><img alt="" src="../images/down.gif" /> <a href="#troubleshoot">Troubleshooting</a></li>
46 </ul><h3>See also</h3><ul class="seealso"><li><a href="#comments_section">Comments</a></li></ul></div>
47 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
49 <h2><a name="related" id="related">.htaccess files</a></h2>
50 <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>
52 <div class="note">You should avoid using <code>.htaccess</code> files completely if you have access to
53 httpd main server config file. Using <code>.htaccess</code> files slows down your Apache http server.
54 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>
55 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
57 <h2><a name="what" id="what">What they are/How to use them</a></h2>
60 <p><code>.htaccess</code> files (or "distributed configuration files")
61 provide a way to make configuration changes on a per-directory basis. A
62 file, containing one or more configuration directives, is placed in a
63 particular document directory, and the directives apply to that
64 directory, and all subdirectories thereof.</p>
66 <div class="note"><h3>Note:</h3>
67 <p>If you want to call your <code>.htaccess</code> file something
68 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,
69 if you would rather call the file <code>.config</code> then you
70 can put the following in your server configuration file:</p>
72 <pre class="prettyprint lang-config">AccessFileName ".config"</pre>
76 <p>In general, <code>.htaccess</code> files use the same syntax as
77 the <a href="../configuring.html#syntax">main configuration
78 files</a>. What you can put in these files is determined by the
79 <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> directive. This
80 directive specifies, in categories, what directives will be
81 honored if they are found in a <code>.htaccess</code> file. If a
82 directive is permitted in a <code>.htaccess</code> file, the
83 documentation for that directive will contain an Override section,
84 specifying what value must be in <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> in order for that
85 directive to be permitted.</p>
87 <p>For example, if you look at the documentation for the <code class="directive"><a href="../mod/core.html#adddefaultcharset">AddDefaultCharset</a></code>
88 directive, you will find that it is permitted in <code>.htaccess</code>
89 files. (See the Context line in the directive summary.) The <a href="../mod/directive-dict.html#Context">Override</a> line reads
90 <code>FileInfo</code>. Thus, you must have at least
91 <code>AllowOverride FileInfo</code> in order for this directive to be
92 honored in <code>.htaccess</code> files.</p>
94 <div class="example"><h3>Example:</h3><table>
96 <td><a href="../mod/directive-dict.html#Context">Context:</a></td>
97 <td>server config, virtual host, directory, .htaccess</td>
101 <td><a href="../mod/directive-dict.html#Override">Override:</a></td>
106 <p>If you are unsure whether a particular directive is permitted in a
107 <code>.htaccess</code> file, look at the documentation for that
108 directive, and check the Context line for ".htaccess".</p>
109 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
110 <div class="section">
111 <h2><a name="when" id="when">When (not) to use .htaccess files</a></h2>
113 <p>In general, you should only use <code>.htaccess</code> files when
114 you don't have access to the main server configuration file. There is,
115 for example, a common misconception that user authentication should
116 always be done in <code>.htaccess</code> files, and, in more recent years,
117 another misconception that <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> directives
118 must go in <code>.htaccess</code> files. This is simply not the
119 case. You can put user authentication configurations in the main server
120 configuration, and this is, in fact, the preferred way to do
121 things. Likewise, <code>mod_rewrite</code> directives work better,
122 in many respects, in the main server configuration.</p>
124 <p><code>.htaccess</code> files should be used in a case where the
125 content providers need to make configuration changes to the server on a
126 per-directory basis, but do not have root access on the server system.
127 In the event that the server administrator is not willing to make
128 frequent configuration changes, it might be desirable to permit
129 individual users to make these changes in <code>.htaccess</code> files
130 for themselves. This is particularly true, for example, in cases where
131 ISPs are hosting multiple user sites on a single machine, and want
132 their users to be able to alter their configuration.</p>
134 <p>However, in general, use of <code>.htaccess</code> files should be
135 avoided when possible. Any configuration that you would consider
136 putting in a <code>.htaccess</code> file, can just as effectively be
137 made in a <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> section in your main server
138 configuration file.</p>
140 <p>There are two main reasons to avoid the use of
141 <code>.htaccess</code> files.</p>
143 <p>The first of these is performance. When <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
144 is set to allow the use of <code>.htaccess</code> files, httpd will
145 look in every directory for <code>.htaccess</code> files. Thus,
146 permitting <code>.htaccess</code> files causes a performance hit,
147 whether or not you actually even use them! Also, the
148 <code>.htaccess</code> file is loaded every time a document is
151 <p>Further note that httpd must look for <code>.htaccess</code> files
152 in all higher-level directories, in order to have a full complement of
153 directives that it must apply. (See section on <a href="#how">how
154 directives are applied</a>.) Thus, if a file is requested out of a
155 directory <code>/www/htdocs/example</code>, httpd must look for the
158 <div class="example"><p><code>
161 /www/htdocs/.htaccess<br />
162 /www/htdocs/example/.htaccess
165 <p>And so, for each file access out of that directory, there are 4
166 additional file-system accesses, even if none of those files are
167 present. (Note that this would only be the case if
168 <code>.htaccess</code> files were enabled for <code>/</code>, which
169 is not usually the case.)</p>
171 <p>In the case of <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> directives, in
172 <code>.htaccess</code> context these regular expressions must be
173 re-compiled with every request to the directory, whereas in main
174 server configuration context they are compiled once and cached.
175 Additionally, the rules themselves are more complicated, as one must
176 work around the restrictions that come with per-directory context
177 and <code>mod_rewrite</code>. Consult the <a href="../rewrite/intro.html#htaccess">Rewrite Guide</a> for more
178 detail on this subject.</p>
180 <p>The second consideration is one of security. You are permitting
181 users to modify server configuration, which may result in changes over
182 which you have no control. Carefully consider whether you want to give
183 your users this privilege. Note also that giving users less
184 privileges than they need will lead to additional technical support
185 requests. Make sure you clearly tell your users what level of
186 privileges you have given them. Specifying exactly what you have set
187 <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> to, and pointing them
188 to the relevant documentation, will save yourself a lot of confusion
191 <p>Note that it is completely equivalent to put a <code>.htaccess</code>
192 file in a directory <code>/www/htdocs/example</code> containing a
193 directive, and to put that same directive in a Directory section
194 <code><Directory "/www/htdocs/example"></code> in your main server
197 <p><code>.htaccess</code> file in <code>/www/htdocs/example</code>:</p>
199 <div class="example"><h3>Contents of .htaccess file in
200 <code>/www/htdocs/example</code></h3><pre class="prettyprint lang-config">AddType text/example ".exm"</pre>
203 <div class="example"><h3>Section from your <code>httpd.conf</code>
204 file</h3><pre class="prettyprint lang-config"><Directory "/www/htdocs/example">
205 AddType text/example ".exm"
206 </Directory></pre>
209 <p>However, putting this configuration in your server configuration
210 file will result in less of a performance hit, as the configuration is
211 loaded once when httpd starts, rather than every time a file is
214 <p>The use of <code>.htaccess</code> files can be disabled completely
215 by setting the <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
216 directive to <code>none</code>:</p>
218 <pre class="prettyprint lang-config">AllowOverride None</pre>
220 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
221 <div class="section">
222 <h2><a name="how" id="how">How directives are applied</a></h2>
224 <p>The configuration directives found in a <code>.htaccess</code> file
225 are applied to the directory in which the <code>.htaccess</code> file
226 is found, and to all subdirectories thereof. However, it is important
227 to also remember that there may have been <code>.htaccess</code> files
228 in directories higher up. Directives are applied in the order that they
229 are found. Therefore, a <code>.htaccess</code> file in a particular
230 directory may override directives found in <code>.htaccess</code> files
231 found higher up in the directory tree. And those, in turn, may have
232 overridden directives found yet higher up, or in the main server
233 configuration file itself.</p>
237 <p>In the directory <code>/www/htdocs/example1</code> we have a
238 <code>.htaccess</code> file containing the following:</p>
240 <pre class="prettyprint lang-config">Options +ExecCGI</pre>
243 <p>(Note: you must have "<code>AllowOverride Options</code>" in effect
244 to permit the use of the "<code class="directive"><a href="../mod/core.html#options">Options</a></code>" directive in
245 <code>.htaccess</code> files.)</p>
247 <p>In the directory <code>/www/htdocs/example1/example2</code> we have
248 a <code>.htaccess</code> file containing:</p>
250 <pre class="prettyprint lang-config">Options Includes</pre>
253 <p>Because of this second <code>.htaccess</code> file, in the directory
254 <code>/www/htdocs/example1/example2</code>, CGI execution is not
255 permitted, as only <code>Options Includes</code> is in effect, which
256 completely overrides any earlier setting that may have been in
259 <h3><a name="merge" id="merge">Merging of .htaccess with the main
260 configuration files</a></h3>
262 <p>As discussed in the documentation on <a href="../sections.html">Configuration Sections</a>,
263 <code>.htaccess</code> files can override the <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> sections for
264 the corresponding directory, but will be overridden by other types
265 of configuration sections from the main configuration files. This
266 fact can be used to enforce certain configurations, even in the
267 presence of a liberal <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> setting. For example, to
268 prevent script execution while allowing anything else to be set in
269 <code>.htaccess</code> you can use:</p>
271 <pre class="prettyprint lang-config"><Directory "/www/htdocs">
276 Options +IncludesNoExec -ExecCGI
277 </Location></pre>
280 <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>
283 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
284 <div class="section">
285 <h2><a name="auth" id="auth">Authentication example</a></h2>
287 <p>If you jumped directly to this part of the document to find out how
288 to do authentication, it is important to note one thing. There is a
289 common misconception that you are required to use
290 <code>.htaccess</code> files in order to implement password
291 authentication. This is not the case. Putting authentication directives
292 in a <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code>
293 section, in your main server configuration file, is the preferred way
294 to implement this, and <code>.htaccess</code> files should be used only
295 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
296 not use <code>.htaccess</code> files.</p>
298 <p>Having said that, if you still think you need to use a
299 <code>.htaccess</code> file, you may find that a configuration such as
300 what follows may work for you.</p>
302 <p><code>.htaccess</code> file contents:</p>
304 <pre class="prettyprint lang-config">AuthType Basic
305 AuthName "Password Required"
306 AuthUserFile "/www/passwords/password.file"
307 AuthGroupFile "/www/passwords/group.file"
308 Require group admins</pre>
311 <p>Note that <code>AllowOverride AuthConfig</code> must be in effect
312 for these directives to have any effect.</p>
314 <p>Please see the <a href="auth.html">authentication tutorial</a> for a
315 more complete discussion of authentication and authorization.</p>
316 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
317 <div class="section">
318 <h2><a name="ssi" id="ssi">Server Side Includes example</a></h2>
320 <p>Another common use of <code>.htaccess</code> files is to enable
321 Server Side Includes for a particular directory. This may be done with
322 the following configuration directives, placed in a
323 <code>.htaccess</code> file in the desired directory:</p>
325 <pre class="prettyprint lang-config">Options +Includes
326 AddType text/html "shtml"
327 AddHandler server-parsed shtml</pre>
330 <p>Note that <code>AllowOverride Options</code> and <code>AllowOverride
331 FileInfo</code> must both be in effect for these directives to have any
334 <p>Please see the <a href="ssi.html">SSI tutorial</a> for a more
335 complete discussion of server-side includes.</p>
336 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
337 <div class="section">
338 <h2><a name="rewrite" id="rewrite">Rewrite Rules in .htaccess files</a></h2>
339 <p>When using <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> in
340 <code>.htaccess</code> files, be aware that the per-directory context
341 changes things a bit. In particular, rules are taken to be relative to
342 the current directory, rather than being the original requested URI.
343 Consider the following examples:</p>
345 <pre class="prettyprint lang-config"># In httpd.conf
346 RewriteRule "^/images/(.+)\.jpg" "/images/$1.png"
348 # In .htaccess in root dir
349 RewriteRule "^images/(.+)\.jpg" "images/$1.png"
351 # In .htaccess in images/
352 RewriteRule "^(.+)\.jpg" "$1.png"</pre>
355 <p>In a <code>.htaccess</code> in your document directory, the leading
356 slash is removed from the value supplied to <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code>, and in the
357 <code>images</code> subdirectory, <code>/images/</code> is removed from
358 it. Thus, your regular expression needs to omit that portion as
361 <p>Consult the <a href="../rewrite/">mod_rewrite documentation</a> for
362 further details on using <code>mod_rewrite</code>.</p>
364 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
365 <div class="section">
366 <h2><a name="cgi" id="cgi">CGI example</a></h2>
368 <p>Finally, you may wish to use a <code>.htaccess</code> file to permit
369 the execution of CGI programs in a particular directory. This may be
370 implemented with the following configuration:</p>
372 <pre class="prettyprint lang-config">Options +ExecCGI
373 AddHandler cgi-script "cgi" "pl"</pre>
376 <p>Alternately, if you wish to have all files in the given directory be
377 considered to be CGI programs, this may be done with the following
380 <pre class="prettyprint lang-config">Options +ExecCGI
381 SetHandler cgi-script</pre>
384 <p>Note that <code>AllowOverride Options</code> and <code>AllowOverride
385 FileInfo</code> must both be in effect for these directives to have any
388 <p>Please see the <a href="cgi.html">CGI tutorial</a> for a more
389 complete discussion of CGI programming and configuration.</p>
391 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
392 <div class="section">
393 <h2><a name="troubleshoot" id="troubleshoot">Troubleshooting</a></h2>
395 <p>When you put configuration directives in a <code>.htaccess</code>
396 file, and you don't get the desired effect, there are a number of
397 things that may be going wrong.</p>
399 <p>Most commonly, the problem is that <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> is not
400 set such that your configuration directives are being honored. Make
401 sure that you don't have a <code>AllowOverride None</code> in effect
402 for the file scope in question. A good test for this is to put garbage
403 in your <code>.htaccess</code> file and reload the page. If a server error is
404 not generated, then you almost certainly have <code>AllowOverride
405 None</code> in effect.</p>
407 <p>If, on the other hand, you are getting server errors when trying to
408 access documents, check your httpd error log. It will likely tell you
409 that the directive used in your <code>.htaccess</code> file is not
412 <div class="example"><p><code>
413 [Fri Sep 17 18:43:16 2010] [alert] [client 192.168.200.51] /var/www/html/.htaccess: DirectoryIndex not allowed here
416 <p>This will indicate either that you've used a directive that is
417 never permitted in <code>.htaccess</code> files, or that you simply
418 don't have <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> set to
419 a level sufficient for the directive you've used. Consult the
420 documentation for that particular directive to determine which is
423 <p>Alternately, it may tell you that you had a syntax error in your
424 usage of the directive itself.</p>
426 <div class="example"><p><code>
427 [Sat Aug 09 16:22:34 2008] [alert] [client 192.168.200.51] /var/www/html/.htaccess: RewriteCond: bad flag delimiters
430 <p>In this case, the error message should be specific to the
431 particular syntax error that you have committed.</p>
434 <div class="bottomlang">
435 <p><span>Available Languages: </span><a href="../en/howto/htaccess.html" title="English"> en </a> |
436 <a href="../es/howto/htaccess.html" hreflang="es" rel="alternate" title="Español"> es </a> |
437 <a href="../fr/howto/htaccess.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
438 <a href="../ja/howto/htaccess.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
439 <a href="../ko/howto/htaccess.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> |
440 <a href="../pt-br/howto/htaccess.html" hreflang="pt-br" rel="alternate" title="Português (Brasil)"> pt-br </a></p>
441 </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>
442 <script type="text/javascript"><!--//--><![CDATA[//><!--
443 var comments_shortname = 'httpd';
444 var comments_identifier = 'http://httpd.apache.org/docs/trunk/howto/htaccess.html';
446 if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
447 d.write('<div id="comments_thread"><\/div>');
448 var s = d.createElement('script');
449 s.type = 'text/javascript';
451 s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
452 (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
455 d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
457 })(window, document);
458 //--><!]]></script></div><div id="footer">
459 <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>
460 <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[//><!--
461 if (typeof(prettyPrint) !== 'undefined') {