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>Mapping URLs to Filesystem Locations - 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></div><div id="page-content"><div id="preamble"><h1>Mapping URLs to Filesystem Locations</h1>
26 <p><span>Available Languages: </span><a href="./en/urlmapping.html" title="English"> en </a> |
27 <a href="./fr/urlmapping.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
28 <a href="./ja/urlmapping.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
29 <a href="./ko/urlmapping.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> |
30 <a href="./tr/urlmapping.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p>
33 <p>This document explains how the Apache HTTP Server uses the URL of a request
34 to determine the filesystem location from which to serve a
37 <div id="quickview"><ul id="toc"><li><img alt="" src="./images/down.gif" /> <a href="#related">Related Modules and Directives</a></li>
38 <li><img alt="" src="./images/down.gif" /> <a href="#documentroot">DocumentRoot</a></li>
39 <li><img alt="" src="./images/down.gif" /> <a href="#outside">Files Outside the DocumentRoot</a></li>
40 <li><img alt="" src="./images/down.gif" /> <a href="#user">User Directories</a></li>
41 <li><img alt="" src="./images/down.gif" /> <a href="#redirect">URL Redirection</a></li>
42 <li><img alt="" src="./images/down.gif" /> <a href="#proxy">Reverse Proxy</a></li>
43 <li><img alt="" src="./images/down.gif" /> <a href="#rewrite">Rewriting Engine</a></li>
44 <li><img alt="" src="./images/down.gif" /> <a href="#notfound">File Not Found</a></li>
45 <li><img alt="" src="./images/down.gif" /> <a href="#other">Other URL Mapping Modules</a></li>
46 </ul><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">Related Modules and Directives</a></h2>
51 <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="./mod/mod_actions.html">mod_actions</a></code></li><li><code class="module"><a href="./mod/mod_alias.html">mod_alias</a></code></li><li><code class="module"><a href="./mod/mod_autoindex.html">mod_autoindex</a></code></li><li><code class="module"><a href="./mod/mod_dir.html">mod_dir</a></code></li><li><code class="module"><a href="./mod/mod_imagemap.html">mod_imagemap</a></code></li><li><code class="module"><a href="./mod/mod_negotiation.html">mod_negotiation</a></code></li><li><code class="module"><a href="./mod/mod_proxy.html">mod_proxy</a></code></li><li><code class="module"><a href="./mod/mod_rewrite.html">mod_rewrite</a></code></li><li><code class="module"><a href="./mod/mod_speling.html">mod_speling</a></code></li><li><code class="module"><a href="./mod/mod_userdir.html">mod_userdir</a></code></li><li><code class="module"><a href="./mod/mod_vhost_alias.html">mod_vhost_alias</a></code></li></ul></td><td><ul><li><code class="directive"><a href="./mod/mod_alias.html#alias">Alias</a></code></li><li><code class="directive"><a href="./mod/mod_alias.html#aliasmatch">AliasMatch</a></code></li><li><code class="directive"><a href="./mod/mod_speling.html#checkspelling">CheckSpelling</a></code></li><li><code class="directive"><a href="./mod/mod_dir.html#directoryindex">DirectoryIndex</a></code></li><li><code class="directive"><a href="./mod/core.html#documentroot">DocumentRoot</a></code></li><li><code class="directive"><a href="./mod/core.html#errordocument">ErrorDocument</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_proxy.html#proxypass">ProxyPass</a></code></li><li><code class="directive"><a href="./mod/mod_proxy.html#proxypassreverse">ProxyPassReverse</a></code></li><li><code class="directive"><a href="./mod/mod_proxy.html#proxypassreversecookiedomain">ProxyPassReverseCookieDomain</a></code></li><li><code class="directive"><a href="./mod/mod_proxy.html#proxypassreversecookiepath">ProxyPassReverseCookiePath</a></code></li><li><code class="directive"><a href="./mod/mod_alias.html#redirect">Redirect</a></code></li><li><code class="directive"><a href="./mod/mod_alias.html#redirectmatch">RedirectMatch</a></code></li><li><code class="directive"><a href="./mod/mod_rewrite.html#rewritecond">RewriteCond</a></code></li><li><code class="directive"><a href="./mod/mod_rewrite.html#rewriterule">RewriteRule</a></code></li><li><code class="directive"><a href="./mod/mod_alias.html#scriptalias">ScriptAlias</a></code></li><li><code class="directive"><a href="./mod/mod_alias.html#scriptaliasmatch">ScriptAliasMatch</a></code></li><li><code class="directive"><a href="./mod/mod_userdir.html#userdir">UserDir</a></code></li></ul></td></tr></table>
52 </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
54 <h2><a name="documentroot" id="documentroot">DocumentRoot</a></h2>
56 <p>In deciding what file to serve for a given request, httpd's
57 default behavior is to take the URL-Path for the request (the part
58 of the URL following the hostname and port) and add it to the end
59 of the <code class="directive"><a href="./mod/core.html#documentroot">DocumentRoot</a></code> specified
60 in your configuration files. Therefore, the files and directories
61 underneath the <code class="directive"><a href="./mod/core.html#documentroot">DocumentRoot</a></code>
62 make up the basic document tree which will be visible from the
65 <p>For example, if <code class="directive"><a href="./mod/core.html#documentroot">DocumentRoot</a></code>
66 were set to <code>/var/www/html</code> then a request for
67 <code>http://www.example.com/fish/guppies.html</code> would result
68 in the file <code>/var/www/html/fish/guppies.html</code> being
69 served to the requesting client.</p>
71 <p>If a directory is requested (i.e. a path ending with
72 <code>/</code>), the file served from that directory is defined by
73 the <code class="directive"><a href="./mod/mod_dir.html#directoryindex">DirectoryIndex</a></code> directive.
74 For example, if <code>DocumentRoot</code> were set as above, and
77 <div class="example"><p><code>DirectoryIndex index.html index.php</code></p></div>
79 <p>Then a request for <code>http://www.example.com/fish/</code> will
80 cause httpd to attempt to serve the file
81 <code>/var/www/html/fish/index.html</code>. In the event that
82 that file does not exist, it will next attempt to serve the file
83 <code>/var/www/html/fish/index.php</code>.</p>
85 <p>If neither of these files existed, the next step is to
86 attempt to provide a directory index, if
87 <code class="module"><a href="./mod/mod_autoindex.html">mod_autoindex</a></code> is loaded and configured to permit
90 <p>httpd is also capable of <a href="vhosts/">Virtual
91 Hosting</a>, where the server receives requests for more than one
92 host. In this case, a different <code class="directive"><a href="./mod/core.html#documentroot">DocumentRoot</a></code> can be specified for each
93 virtual host, or alternatively, the directives provided by the
94 module <code class="module"><a href="./mod/mod_vhost_alias.html">mod_vhost_alias</a></code> can
95 be used to dynamically determine the appropriate place from which
96 to serve content based on the requested IP address or
99 <p>The <code class="directive"><a href="./mod/core.html#documentroot">DocumentRoot</a></code> directive
100 is set in your main server configuration file
101 (<code>httpd.conf</code>) and, possibly, once per additional <a href="vhosts/">Virtual Host</a> you create.</p>
102 </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
103 <div class="section">
104 <h2><a name="outside" id="outside">Files Outside the DocumentRoot</a></h2>
106 <p>There are frequently circumstances where it is necessary to
107 allow web access to parts of the filesystem that are not strictly
108 underneath the <code class="directive"><a href="./mod/core.html#documentroot">DocumentRoot</a></code>. httpd offers several
109 different ways to accomplish this. On Unix systems, symbolic links
110 can bring other parts of the filesystem under the <code class="directive"><a href="./mod/core.html#documentroot">DocumentRoot</a></code>. For security reasons,
111 httpd will follow symbolic links only if the <code class="directive"><a href="./mod/core.html#options">Options</a></code> setting for the relevant
112 directory includes <code>FollowSymLinks</code> or
113 <code>SymLinksIfOwnerMatch</code>.</p>
115 <p>Alternatively, the <code class="directive"><a href="./mod/mod_alias.html#alias">Alias</a></code> directive will map any part
116 of the filesystem into the web space. For example, with</p>
118 <pre class="prettyprint lang-config">Alias "/docs" "/var/web"</pre>
121 <p>the URL <code>http://www.example.com/docs/dir/file.html</code>
122 will be served from <code>/var/web/dir/file.html</code>. The
123 <code class="directive"><a href="./mod/mod_alias.html#scriptalias">ScriptAlias</a></code> directive
124 works the same way, with the additional effect that all content
125 located at the target path is treated as <a class="glossarylink" href="./glossary.html#cgi" title="see glossary">CGI</a> scripts.</p>
127 <p>For situations where you require additional flexibility, you
128 can use the <code class="directive"><a href="./mod/mod_alias.html#aliasmatch">AliasMatch</a></code>
129 and <code class="directive"><a href="./mod/mod_alias.html#scriptaliasmatch">ScriptAliasMatch</a></code>
130 directives to do powerful <a class="glossarylink" href="./glossary.html#regex" title="see glossary">regular
131 expression</a> based matching and substitution. For
134 <pre class="prettyprint lang-config">ScriptAliasMatch "^/~([a-zA-Z0-9]+)/cgi-bin/(.+)" "/home/$1/cgi-bin/$2"</pre>
137 <p>will map a request to
138 <code>http://example.com/~user/cgi-bin/script.cgi</code> to the
139 path <code>/home/user/cgi-bin/script.cgi</code> and will treat
140 the resulting file as a CGI script.</p>
141 </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
142 <div class="section">
143 <h2><a name="user" id="user">User Directories</a></h2>
145 <p>Traditionally on Unix systems, the home directory of a
146 particular <em>user</em> can be referred to as
147 <code>~user/</code>. The module <code class="module"><a href="./mod/mod_userdir.html">mod_userdir</a></code>
148 extends this idea to the web by allowing files under each user's
149 home directory to be accessed using URLs such as the
152 <div class="example"><p><code>http://www.example.com/~user/file.html</code></p></div>
154 <p>For security reasons, it is inappropriate to give direct
155 access to a user's home directory from the web. Therefore, the
156 <code class="directive"><a href="./mod/mod_userdir.html#userdir">UserDir</a></code> directive
157 specifies a directory underneath the user's home directory
158 where web files are located. Using the default setting of
159 <code>Userdir public_html</code>, the above URL maps to a file
161 <code>/home/user/public_html/file.html</code> where
162 <code>/home/user/</code> is the user's home directory as
163 specified in <code>/etc/passwd</code>.</p>
165 <p>There are also several other forms of the
166 <code>Userdir</code> directive which you can use on systems
167 where <code>/etc/passwd</code> does not contain the location of
168 the home directory.</p>
170 <p>Some people find the "~" symbol (which is often encoded on the
171 web as <code>%7e</code>) to be awkward and prefer to use an
172 alternate string to represent user directories. This functionality
173 is not supported by mod_userdir. However, if users' home
174 directories are structured in a regular way, then it is possible
175 to use the <code class="directive"><a href="./mod/mod_alias.html#aliasmatch">AliasMatch</a></code>
176 directive to achieve the desired effect. For example, to make
177 <code>http://www.example.com/upages/user/file.html</code> map to
178 <code>/home/user/public_html/file.html</code>, use the following
179 <code>AliasMatch</code> directive:</p>
181 <pre class="prettyprint lang-config">AliasMatch "^/upages/([a-zA-Z0-9]+)(/(.*))?$" "/home/$1/public_html/$3"</pre>
183 </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
184 <div class="section">
185 <h2><a name="redirect" id="redirect">URL Redirection</a></h2>
187 <p>The configuration directives discussed in the above sections
188 tell httpd to get content from a specific place in the filesystem
189 and return it to the client. Sometimes, it is desirable instead to
190 inform the client that the requested content is located at a
191 different URL, and instruct the client to make a new request with
192 the new URL. This is called <em>redirection</em> and is
193 implemented by the <code class="directive"><a href="./mod/mod_alias.html#redirect">Redirect</a></code> directive. For example, if
194 the contents of the directory <code>/foo/</code> under the
195 <code class="directive"><a href="./mod/core.html#documentroot">DocumentRoot</a></code> are moved
196 to the new directory <code>/bar/</code>, you can instruct clients
197 to request the content at the new location as follows:</p>
199 <pre class="prettyprint lang-config">Redirect permanent "/foo/" "http://www.example.com/bar/"</pre>
202 <p>This will redirect any URL-Path starting in
203 <code>/foo/</code> to the same URL path on the
204 <code>www.example.com</code> server with <code>/bar/</code>
205 substituted for <code>/foo/</code>. You can redirect clients to
206 any server, not only the origin server.</p>
208 <p>httpd also provides a <code class="directive"><a href="./mod/mod_alias.html#redirectmatch">RedirectMatch</a></code> directive for more
209 complicated rewriting problems. For example, to redirect requests
210 for the site home page to a different site, but leave all other
211 requests alone, use the following configuration:</p>
213 <pre class="prettyprint lang-config">RedirectMatch permanent "^/$" "http://www.example.com/startpage.html"</pre>
216 <p>Alternatively, to temporarily redirect all pages on one site
217 to a particular page on another site, use the following:</p>
219 <pre class="prettyprint lang-config">RedirectMatch temp ".*" "http://othersite.example.com/startpage.html"</pre>
221 </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
222 <div class="section">
223 <h2><a name="proxy" id="proxy">Reverse Proxy</a></h2>
225 <p>httpd also allows you to bring remote documents into the URL space
226 of the local server. This technique is called <em>reverse
227 proxying</em> because the web server acts like a proxy server by
228 fetching the documents from a remote server and returning them to the
229 client. It is different from normal (forward) proxying because, to the client,
230 it appears the documents originate at the reverse proxy server.</p>
232 <p>In the following example, when clients request documents under the
233 <code>/foo/</code> directory, the server fetches those documents from
234 the <code>/bar/</code> directory on <code>internal.example.com</code>
235 and returns them to the client as if they were from the local
238 <pre class="prettyprint lang-config">ProxyPass "/foo/" "http://internal.example.com/bar/"<br />
239 ProxyPassReverse "/foo/" "http://internal.example.com/bar/"<br />
240 ProxyPassReverseCookieDomain internal.example.com public.example.com<br />
241 ProxyPassReverseCookiePath "/foo/" "/bar/"</pre>
244 <p>The <code class="directive"><a href="./mod/mod_proxy.html#proxypass">ProxyPass</a></code> configures
245 the server to fetch the appropriate documents, while the
246 <code class="directive"><a href="./mod/mod_proxy.html#proxypassreverse">ProxyPassReverse</a></code>
247 directive rewrites redirects originating at
248 <code>internal.example.com</code> so that they target the appropriate
249 directory on the local server. Similarly, the
250 <code class="directive"><a href="./mod/mod_proxy.html#proxypassreversecookiedomain">ProxyPassReverseCookieDomain</a></code>
251 and <code class="directive"><a href="./mod/mod_proxy.html#proxypassreversecookiepath">ProxyPassReverseCookiePath</a></code>
252 rewrite cookies set by the backend server.</p>
253 <p>It is important to note, however, that
254 links inside the documents will not be rewritten. So any absolute
255 links on <code>internal.example.com</code> will result in the client
256 breaking out of the proxy server and requesting directly from
257 <code>internal.example.com</code>. You can modify these links (and other
258 content) in a page as it is being served to the client using
259 <code class="module"><a href="./mod/mod_substitute.html">mod_substitute</a></code>.</p>
261 <pre class="prettyprint lang-config">Substitute s/internal\.example\.com/www.example.com/i</pre>
264 <p>For more sophisticated rewriting of links in HTML and XHTML, the
265 <code class="module"><a href="./mod/mod_proxy_html.html">mod_proxy_html</a></code> module is also available. It allows you
266 to create maps of URLs that need to be rewritten, so that complex
267 proxying scenarios can be handled.</p>
268 </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
269 <div class="section">
270 <h2><a name="rewrite" id="rewrite">Rewriting Engine</a></h2>
272 <p>When even more powerful substitution is required, the rewriting
273 engine provided by <code class="module"><a href="./mod/mod_rewrite.html">mod_rewrite</a></code>
274 can be useful. The directives provided by this module can use
275 characteristics of the request such as browser type or source IP
276 address in deciding from where to serve content. In addition,
277 mod_rewrite can use external database files or programs to
278 determine how to handle a request. The rewriting engine is capable
279 of performing all three types of mappings discussed above:
280 internal redirects (aliases), external redirects, and proxying.
281 Many practical examples employing mod_rewrite are discussed in the
282 <a href="rewrite/">detailed mod_rewrite documentation</a>.</p>
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="notfound" id="notfound">File Not Found</a></h2>
287 <p>Inevitably, URLs will be requested for which no matching
288 file can be found in the filesystem. This can happen for
289 several reasons. In some cases, it can be a result of moving
290 documents from one location to another. In this case, it is
291 best to use <a href="#redirect">URL redirection</a> to inform
292 clients of the new location of the resource. In this way, you
293 can assure that old bookmarks and links will continue to work,
294 even though the resource is at a new location.</p>
296 <p>Another common cause of "File Not Found" errors is
297 accidental mistyping of URLs, either directly in the browser,
298 or in HTML links. httpd provides the module
299 <code class="module"><a href="./mod/mod_speling.html">mod_speling</a></code> (sic) to help with
300 this problem. When this module is activated, it will intercept
301 "File Not Found" errors and look for a resource with a similar
302 filename. If one such file is found, mod_speling will send an
303 HTTP redirect to the client informing it of the correct
304 location. If several "close" files are found, a list of
305 available alternatives will be presented to the client.</p>
307 <p>An especially useful feature of mod_speling, is that it will
308 compare filenames without respect to case. This can help
309 systems where users are unaware of the case-sensitive nature of
310 URLs and the unix filesystem. But using mod_speling for
311 anything more than the occasional URL correction can place
312 additional load on the server, since each "incorrect" request
313 is followed by a URL redirection and a new request from the
316 <p><code class="module"><a href="./mod/mod_dir.html">mod_dir</a></code> provides <code class="directive"><a href="./mod/mod_dir.html#fallbackresource">FallbackResource</a></code>, which can be used to map virtual
317 URIs to a real resource, which then serves them. This is a very
318 useful replacement to <code class="module"><a href="./mod/mod_rewrite.html">mod_rewrite</a></code> when implementing
319 a 'front controller'</p>
321 <p>If all attempts to locate the content fail, httpd returns
322 an error page with HTTP status code 404 (file not found). The
323 appearance of this page is controlled with the
324 <code class="directive"><a href="./mod/core.html#errordocument">ErrorDocument</a></code> directive
325 and can be customized in a flexible manner as discussed in the
326 <a href="custom-error.html">Custom error responses</a>
328 </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
329 <div class="section">
330 <h2><a name="other" id="other">Other URL Mapping Modules</a></h2>
334 <p>Other modules available for URL mapping include:</p>
337 <li><code class="module"><a href="./mod/mod_actions.html">mod_actions</a></code> - Maps a request to a CGI script
338 based on the request method, or resource MIME type.</li>
339 <li><code class="module"><a href="./mod/mod_dir.html">mod_dir</a></code> - Provides basic mapping of a trailing
340 slash into an index file such as <code>index.html</code>.</li>
341 <li><code class="module"><a href="./mod/mod_imagemap.html">mod_imagemap</a></code> - Maps a request to a URL based
342 on where a user clicks on an image embedded in a HTML document.</li>
343 <li><code class="module"><a href="./mod/mod_negotiation.html">mod_negotiation</a></code> - Selects an appropriate
344 document based on client preferences such as language or content
349 <div class="bottomlang">
350 <p><span>Available Languages: </span><a href="./en/urlmapping.html" title="English"> en </a> |
351 <a href="./fr/urlmapping.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
352 <a href="./ja/urlmapping.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
353 <a href="./ko/urlmapping.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> |
354 <a href="./tr/urlmapping.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p>
355 </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>
356 <script type="text/javascript"><!--//--><![CDATA[//><!--
357 var comments_shortname = 'httpd';
358 var comments_identifier = 'http://httpd.apache.org/docs/trunk/urlmapping.html';
360 if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
361 d.write('<div id="comments_thread"><\/div>');
362 var s = d.createElement('script');
363 s.type = 'text/javascript';
365 s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
366 (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
369 d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
371 })(window, document);
372 //--><!]]></script></div><div id="footer">
373 <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>
374 <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[//><!--
375 if (typeof(prettyPrint) !== 'undefined') {