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>Compiling and Installing - 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>Compiling and Installing</h1> 23<div class="toplang"> 24<p><span>Available Languages: </span><a href="/de/install.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | 25<a href="/en/install.html" title="English"> en </a> | 26<a href="/es/install.html" hreflang="es" rel="alternate" title="Espa�ol"> es </a> | 27<a href="/fr/install.html" hreflang="fr" rel="alternate" title="Fran�ais"> fr </a> | 28<a href="/ja/install.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | 29<a href="/ko/install.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | 30<a href="/tr/install.html" hreflang="tr" rel="alternate" title="T�rk�e"> tr </a></p> 31</div> 32 33 34 <p>This document covers compilation and installation of the Apache HTTP Server 35 on Unix and Unix-like systems only. For compiling and 36 installation on Windows, see <a href="platform/windows.html">Using Apache HTTP Server with Microsoft 37 Windows</a> and <a href="platform/win_compiling.html">Compiling Apache for Microsoft Windows</a>. 38 For other platforms, see the <a href="platform/">platform</a> documentation.</p> 39 40 <p>Apache httpd uses <code>libtool</code> and <code>autoconf</code> 41 to create a build environment that looks like many other Open Source 42 projects.</p> 43 44 <p>If you are upgrading from one minor version to the next (for 45 example, 2.2.50 to 2.2.51), please skip down to the <a href="#upgrading">upgrading</a> section.</p> 46 47</div> 48<div id="quickview"><ul id="toc"><li><img alt="" src="/images/down.gif" /> <a href="#overview">Overview for the 49 impatient</a></li> 50<li><img alt="" src="/images/down.gif" /> <a href="#requirements">Requirements</a></li> 51<li><img alt="" src="/images/down.gif" /> <a href="#download">Download</a></li> 52<li><img alt="" src="/images/down.gif" /> <a href="#extract">Extract</a></li> 53<li><img alt="" src="/images/down.gif" /> <a href="#configure">Configuring the source tree</a></li> 54<li><img alt="" src="/images/down.gif" /> <a href="#compile">Build</a></li> 55<li><img alt="" src="/images/down.gif" /> <a href="#install">Install</a></li> 56<li><img alt="" src="/images/down.gif" /> <a href="#customize">Customize</a></li> 57<li><img alt="" src="/images/down.gif" /> <a href="#test">Test</a></li> 58<li><img alt="" src="/images/down.gif" /> <a href="#upgrading">Upgrading</a></li> 59<li><img alt="" src="/images/down.gif" /> <a href="#thirdp">Third-party packages</a></li> 60</ul><h3>See also</h3><ul class="seealso"><li><a href="programs/configure.html">Configure the source tree</a></li><li><a href="invoking.html">Starting Apache httpd</a></li><li><a href="stopping.html">Stopping and Restarting</a></li></ul><ul class="seealso"><li><a href="#comments_section">Comments</a></li></ul></div> 61<div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div> 62<div class="section"> 63<h2><a name="overview" id="overview">Overview for the 64 impatient</a></h2> 65 66 <table> 67 68 <tr> 69 <td><a href="#download">Download</a></td> 70 71 <td><code>$ lynx http://httpd.apache.org/download.cgi</code> 72 </td> 73 </tr> 74 75 <tr> 76 <td><a href="#extract">Extract</a></td> 77 78 <td><code>$ gzip -d httpd-<em>NN</em>.tar.gz<br /> 79 $ tar xvf httpd-<em>NN</em>.tar<br /> 80 $ cd httpd-<em>NN</em></code></td> 81 </tr> 82 83 <tr> 84 <td><a href="#configure">Configure</a></td> 85 86 <td><code>$ /configure --prefix=<em>PREFIX</em></code> 87 </td> 88 </tr> 89 90 <tr> 91 <td><a href="#compile">Compile</a></td> 92 93 <td><code>$ make</code> </td> 94 </tr> 95 96 <tr> 97 <td><a href="#install">Install</a></td> 98 99 <td><code>$ make install</code> </td> 100 </tr> 101 102 <tr> 103 <td><a href="#customize">Customize</a></td> 104 105 <td><code>$ vi <em>PREFIX</em>/conf/httpd.conf</code> </td> 106 </tr> 107 108 <tr> 109 <td><a href="#test">Test</a></td> 110 111 <td><code>$ <em>PREFIX</em>/bin/apachectl -k start</code> 112 </td> 113 </tr> 114 </table> 115 116 <p><em>NN</em> must be replaced with the current version 117 number, and <em>PREFIX</em> must be replaced with the 118 filesystem path under which the server should be installed. If 119 <em>PREFIX</em> is not specified, it defaults to 120 <code>/usr/local/apache2</code>.</p> 121 122 <p>Each section of the compilation and installation process is 123 described in more detail below, beginning with the requirements 124 for compiling and installing Apache httpd.</p> 125</div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div> 126<div class="section"> 127<h2><a name="requirements" id="requirements">Requirements</a></h2> 128 129 <p>The following requirements exist for building Apache httpd:</p> 130 131 <dl> 132 <dt>APR and APR-Util</dt> 133 <dd>Make sure you have APR and APR-Util already installed on 134 your system. If you don't, or prefer to not use the system-provided 135 versions, download the latest versions of both APR and APR-Util 136 from <a href="http://apr.apache.org/">Apache APR</a>, unpack 137 them into <code>/srclib/apr</code> and <code>/srclib/apr-util</code> 138 (be sure the directory names do not have version numbers; for example, 139 the APR distribution must be under /srclib/apr/) and use 140 <code>/configure</code>'s <code>--with-included-apr</code> 141 option. On some platforms, you may have to install the 142 corresponding <code>-dev</code> packages to allow httpd to build 143 against your installed copy of APR and APR-Util.</dd> 144 145 <dt>Perl-Compatible Regular Expressions Library (PCRE)</dt> 146 <dd>This library is required but not longer bundled with httpd. 147 Download the source code from <a href="http://www.pcre.org/">http://www.pcre.org</a>, 148 or install a Port or Package. If your build system can't find 149 the pcre-config script installed by the PCRE build, point to it 150 using the <code>--with-pcre</code> parameter. On some platforms, 151 you may have to install the corresponding <code>-dev</code> 152 package to allow httpd to build against your installed copy 153 of PCRE.</dd> 154 155 <dt>Disk Space</dt> 156 <dd>Make sure you have at least 50 MB of temporary free disk 157 space available. After installation the server occupies 158 approximately 10 MB of disk space. The actual disk space 159 requirements will vary considerably based on your chosen 160 configuration options, any third-party modules, and, of course, 161 the size of the web site or sites that you have on the server.</dd> 162 163 <dt>ANSI-C Compiler and Build System</dt> 164 <dd>Make sure you have an ANSI-C compiler installed. The <a href="http://gcc.gnu.org/">GNU C 165 compiler (GCC)</a> from the <a href="http://www.gnu.org/">Free Software Foundation (FSF)</a> 166 is recommended. If you don't have GCC 167 then at least make sure your vendor's compiler is ANSI 168 compliant. In addition, your <code>PATH</code> must contain 169 basic build tools such as <code>make</code>.</dd> 170 171 <dt>Accurate time keeping</dt> 172 <dd>Elements of the HTTP protocol are expressed as the time of 173 day. So, it's time to investigate setting some time 174 synchronization facility on your system. Usually the 175 <code>ntpdate</code> or <code>xntpd</code> programs are used for 176 this purpose which are based on the Network Time Protocol (NTP). 177 See the <a href="http://www.ntp.org">NTP 178 homepage</a> for more details about NTP software and public 179 time servers.</dd> 180 181 <dt><a href="http://www.perl.org/">Perl 5</a> 182 [OPTIONAL]</dt> 183 <dd>For some of the support scripts like <code class="program"><a href="/programs/apxs.html">apxs</a></code> or <code class="program"><a href="/programs/dbmmanage.html">dbmmanage</a></code> (which are 184 written in Perl) the Perl 5 interpreter is required (versions 185 5.003 or newer are sufficient). If you have multiple Perl 186 interpreters (for example, a systemwide install of Perl 4, and 187 your own install of Perl 5), you are advised to use the 188 <code>--with-perl</code> option (see below) to make sure the 189 correct one is used by <code class="program"><a href="/programs/configure.html">configure</a></code>. 190 If no Perl 5 interpreter is found by the 191 <code class="program"><a href="/programs/configure.html">configure</a></code> script, you will not be able to use 192 the affected support scripts. Of course, you will still be able to 193 build and use Apache httpd.</dd> 194 </dl> 195</div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div> 196<div class="section"> 197<h2><a name="download" id="download">Download</a></h2> 198 199 <p>The Apache HTTP Server can be downloaded from the <a href="http://httpd.apache.org/download.cgi">Apache HTTP Server 200 download site</a>, which lists several mirrors. Most users of 201 Apache on unix-like systems will be better off downloading and 202 compiling a source version. The build process (described below) is 203 easy, and it allows you to customize your server to suit your needs. 204 In addition, binary releases are often not up to date with the latest 205 source releases. If you do download a binary, follow the instructions 206 in the <code>INSTALL.bindist</code> file inside the distribution.</p> 207 208 <p>After downloading, it is important to verify that you have a 209 complete and unmodified version of the Apache HTTP Server. This 210 can be accomplished by testing the downloaded tarball against the 211 PGP signature. Details on how to do this are available on the <a href="http://httpd.apache.org/download.cgi#verify">download 212 page</a> and an extended example is available describing the <a href="http://httpd.apache.org/dev/verification.html">use of 213 PGP</a>.</p> 214 215</div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div> 216<div class="section"> 217<h2><a name="extract" id="extract">Extract</a></h2> 218 219 <p>Extracting the source from the Apache HTTP Server tarball is a 220 simple matter of uncompressing, and then untarring:</p> 221 222<div class="example"><p><code> 223$ gzip -d httpd-<em>NN</em>.tar.gz<br /> 224$ tar xvf httpd-<em>NN</em>.tar 225</code></p></div> 226 227 <p>This will create a new directory under the current directory 228 containing the source code for the distribution. You should 229 <code>cd</code> into that directory before proceeding with 230 compiling the server.</p> 231</div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div> 232<div class="section"> 233<h2><a name="configure" id="configure">Configuring the source tree</a></h2> 234 235 <p>The next step is to configure the Apache source tree for your 236 particular platform and personal requirements. This is done using 237 the script <code class="program"><a href="/programs/configure.html">configure</a></code> included in 238 the root directory of the distribution. (Developers downloading 239 an unreleased version of the Apache source tree will need to have 240 <code>autoconf</code> and <code>libtool</code> installed and will 241 need to run <code>buildconf</code> before proceeding with the next 242 steps. This is not necessary for official releases.)</p> 243 244 <p>To configure the source tree using all the default options, 245 simply type <code>/configure</code>. To change the default 246 options, <code class="program"><a href="/programs/configure.html">configure</a></code> accepts a variety of variables 247 and command line options.</p> 248 249 <p>The most important option is the location <code>--prefix</code> 250 where Apache is to be installed later, because Apache has to be 251 configured for this location to work correctly. More fine-tuned 252 control of the location of files is possible with additional <a href="programs/configure.html#installationdirectories">configure 253 options</a>.</p> 254 255 <p>Also at this point, you can specify which <a href="programs/configure.html#optionalfeatures">features</a> you 256 want included in Apache by enabling and disabling <a href="mod/">modules</a>. Apache comes with a wide range of modules 257 included by default. They will be compiled as 258 <a href="dso.html">shared objects (DSOs)</a> which can be loaded 259 or unloaded at runtime. 260 You can also choose to compile modules statically by using the option 261 <code>--enable-<var>module</var>=static</code>.</p> 262 263 <p>Additional modules are enabled using the 264 <code>--enable-<var>module</var></code> option, where 265 <var>module</var> is the name of the module with the 266 <code>mod_</code> string removed and with any underscore converted 267 to a dash. Similarly, you can disable modules with the 268 <code>--disable-<var>module</var></code> option. Be careful when 269 using these options, since <code class="program"><a href="/programs/configure.html">configure</a></code> cannot warn you 270 if the module you specify does not exist; it will simply ignore the 271 option.</p> 272 273 <p>In addition, it is sometimes necessary to provide the 274 <code class="program"><a href="/programs/configure.html">configure</a></code> script with extra information about the 275 location of your compiler, libraries, or header files. This is 276 done by passing either environment variables or command line 277 options to <code class="program"><a href="/programs/configure.html">configure</a></code>. For more information, see the 278 <code class="program"><a href="/programs/configure.html">configure</a></code> manual page. Or invoke 279 <code class="program"><a href="/programs/configure.html">configure</a></code> using the <code>--help</code> option.</p> 280 281 <p>For a short impression of what possibilities you have, here 282 is a typical example which compiles Apache for the installation 283 tree <code>/sw/pkg/apache</code> with a particular compiler and flags 284 plus the two additional modules <code class="module"><a href="/mod/mod_ldap.html">mod_ldap</a></code> and 285 <code class="module"><a href="/mod/mod_lua.html">mod_lua</a></code>:</p> 286 287<div class="example"><p><code> 288 $ CC="pgcc" CFLAGS="-O2" \<br /> 289 /configure --prefix=/sw/pkg/apache \<br /> 290 --enable-ldap=shared \<br /> 291 --enable-lua=shared 292</code></p></div> 293 294 <p>When <code class="program"><a href="/programs/configure.html">configure</a></code> is run it will take several minutes to 295 test for the availability of features on your system and build 296 Makefiles which will later be used to compile the server.</p> 297 298 <p>Details on all the different <code class="program"><a href="/programs/configure.html">configure</a></code> options are 299 available on the <code class="program"><a href="/programs/configure.html">configure</a></code> manual page.</p> 300</div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div> 301<div class="section"> 302<h2><a name="compile" id="compile">Build</a></h2> 303 304 <p>Now you can build the various parts which form the Apache 305 package by simply running the command:</p> 306 307<div class="example"><p><code>$ make</code></p></div> 308 309 <p>Please be patient here, since a base configuration takes 310 several minutes to compile and the time will vary widely 311 depending on your hardware and the number of modules that you 312 have enabled.</p> 313</div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div> 314<div class="section"> 315<h2><a name="install" id="install">Install</a></h2> 316 317 <p>Now it's time to install the package under the configured 318 installation <em>PREFIX</em> (see <code>--prefix</code> option 319 above) by running:</p> 320 321<div class="example"><p><code>$ make install</code></p></div> 322 323 <p>This step will typically require root privileges, since 324 <em>PREFIX</em> is usually a directory with restricted write 325 permissions.</p> 326 327 <p>If you are upgrading, the installation will not overwrite 328 your configuration files or documents.</p> 329</div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div> 330<div class="section"> 331<h2><a name="customize" id="customize">Customize</a></h2> 332 333 <p>Next, you can customize your Apache HTTP server by editing 334 the <a href="configuring.html">configuration files</a> under 335 <code><em>PREFIX</em>/conf/</code>.</p> 336 337<div class="example"><p><code>$ vi <em>PREFIX</em>/conf/httpd.conf</code></p></div> 338 339 <p>Have a look at the Apache manual under 340 <code><em>PREFIX</em>/docs/manual/</code> or consult <a href="http://httpd.apache.org/docs/2.4/">http://httpd.apache.org/docs/2.4/</a> for the most recent 341 version of this manual and a complete reference of available <a href="mod/directives.html">configuration directives</a>.</p> 342</div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div> 343<div class="section"> 344<h2><a name="test" id="test">Test</a></h2> 345 346 <p>Now you can <a href="invoking.html">start</a> your Apache 347 HTTP server by immediately running:</p> 348 349<div class="example"><p><code>$ <em>PREFIX</em>/bin/apachectl -k start</code></p></div> 350 351 <p>You should then be able to request your first document 352 via the URL <code>http://localhost/</code>. The web page you see is located 353 under the <code class="directive"><a href="/mod/core.html#documentroot">DocumentRoot</a></code>, 354 which will usually be <code><em>PREFIX</em>/htdocs/</code>. 355 Then <a href="stopping.html">stop</a> the server again by 356 running:</p> 357 358<div class="example"><p><code>$ <em>PREFIX</em>/bin/apachectl -k stop</code></p></div> 359</div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div> 360<div class="section"> 361<h2><a name="upgrading" id="upgrading">Upgrading</a></h2> 362 363 <p>The first step in upgrading is to read the release announcement 364 and the file <code>CHANGES</code> in the source distribution to 365 find any changes that may affect your site. When changing between 366 major releases (for example, from 2.0 to 2.2 or from 2.2 to 2.4), 367 there will likely be major differences in the compile-time and 368 run-time configuration that will require manual adjustments. All 369 modules will also need to be upgraded to accommodate changes in the 370 module API.</p> 371 372 <p>Upgrading from one minor version to the next (for example, from 373 2.2.55 to 2.2.57) is easier. The <code>make install</code> 374 process will not overwrite any of your existing documents, log 375 files, or configuration files. In addition, the developers make 376 every effort to avoid incompatible changes in the 377 <code class="program"><a href="/programs/configure.html">configure</a></code> options, run-time configuration, or the 378 module API between minor versions. In most cases you should be able to 379 use an identical <code class="program"><a href="/programs/configure.html">configure</a></code> command line, an identical 380 configuration file, and all of your modules should continue to 381 work.</p> 382 383 <p>To upgrade across minor versions, start by finding the file 384 <code>config.nice</code> in the <code>build</code> directory of 385 your installed server or at the root of the source tree for your 386 old install. This will contain the exact 387 <code class="program"><a href="/programs/configure.html">configure</a></code> command line that you used to 388 configure the source tree. Then to upgrade from one version to 389 the next, you need only copy the <code>config.nice</code> file to 390 the source tree of the new version, edit it to make any desired 391 changes, and then run:</p> 392 393 <div class="example"><p><code> 394 $ /config.nice<br /> 395 $ make<br /> 396 $ make install<br /> 397 $ <em>PREFIX</em>/bin/apachectl -k graceful-stop<br /> 398 $ <em>PREFIX</em>/bin/apachectl -k start<br /> 399 </code></p></div> 400 401 <div class="warning">You should always test any new version in your 402 environment before putting it into production. For example, you 403 can install and run the new version along side the old one by 404 using a different <code>--prefix</code> and a 405 different port (by adjusting the <code class="directive"><a href="/mod/mpm_common.html#listen">Listen</a></code> directive) to test for any 406 incompatibilities before doing the final upgrade.</div> 407 408 <p>You can pass additional arguments to <code>config.nice</code>, 409 which will be appended to your original <code class="program"><a href="/programs/configure.html">configure</a></code> 410 options:</p> 411 412 <div class="example"><p><code> 413 $ /config.nice --prefix=/home/test/apache --with-port=90 414 </code></p></div> 415</div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div> 416<div class="section"> 417<h2><a name="thirdp" id="thirdp">Third-party packages</a></h2> 418 419 <p>A large number of third parties provide their own packaged 420 distributions of the Apache HTTP Server for installation on 421 particular platforms. This includes the various Linux distributions, 422 various third-party Windows packages, Mac OS X, Solaris, and many 423 more.</p> 424 425 <p>Our software license not only permits, but encourages, this kind 426 of redistribution. However, it does result in a situation where the 427 configuration layout and defaults on your installation of the server 428 may differ from what is stated in the documentation. While 429 unfortunate, this situation is not likely to change any time 430 soon.</p> 431 432 <p>A <a href="http://wiki.apache.org/httpd/DistrosDefaultLayout">description 433 of these third-party distrubutions</a> is maintained in the HTTP 434 Server wiki, and should reflect the current state of these 435 third-party distributions. However, you will need to familiarize 436 yourself with your particular platform's package management and 437 installation procedures.</p> 438 439</div></div> 440<div class="bottomlang"> 441<p><span>Available Languages: </span><a href="/de/install.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | 442<a href="/en/install.html" title="English"> en </a> | 443<a href="/es/install.html" hreflang="es" rel="alternate" title="Espa�ol"> es </a> | 444<a href="/fr/install.html" hreflang="fr" rel="alternate" title="Fran�ais"> fr </a> | 445<a href="/ja/install.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | 446<a href="/ko/install.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | 447<a href="/tr/install.html" hreflang="tr" rel="alternate" title="T�rk�e"> tr </a></p> 448</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> 449<script type="text/javascript"><!--//--><![CDATA[//><!-- 450var comments_shortname = 'httpd'; 451var comments_identifier = 'http://httpd.apache.org/docs/2.4/install.html'; 452(function(w, d) { 453 if (w.location.hostname.toLowerCase() == "httpd.apache.org") { 454 d.write('<div id="comments_thread"><\/div>'); 455 var s = d.createElement('script'); 456 s.type = 'text/javascript'; 457 s.async = true; 458 s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier; 459 (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s); 460 } 461 else { 462 d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>'); 463 } 464})(window, document); 465//--><!]]></script></div><div id="footer"> 466<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> 467<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[//><!-- 468if (typeof(prettyPrint) !== 'undefined') { 469 prettyPrint(); 470} 471//--><!]]></script> 472</body></html>
