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