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