</div>
- <p>This document covers compilation and installation of Apache
+ <p>This document covers compilation and installation of the Apache HTTP Server
on Unix and Unix-like systems only. For compiling and
- installation on Windows, see <a href="platform/windows.html">Using Apache with Microsoft
+ installation on Windows, see <a href="platform/windows.html">Using Apache HTTP Server with Microsoft
Windows</a>. For other platforms, see the <a href="platform/">platform</a> documentation.</p>
<p>Apache httpd uses <code>libtool</code> and <code>autoconf</code>
<li><img alt="" src="./images/down.gif" /> <a href="#customize">Customize</a></li>
<li><img alt="" src="./images/down.gif" /> <a href="#test">Test</a></li>
<li><img alt="" src="./images/down.gif" /> <a href="#upgrading">Upgrading</a></li>
-</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</a></li><li><a href="stopping.html">Stopping and Restarting</a></li></ul></div>
+</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></div>
<div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
<div class="section">
<h2><a name="overview" id="overview">Overview for the
<div class="section">
<h2><a name="requirements" id="requirements">Requirements</a></h2>
- <p>The following requirements exist for building Apache:</p>
+ <p>The following requirements exist for building Apache httpd:</p>
<dl>
<dt>Disk Space</dt>
<dd>Make sure you have at least 50 MB of temporary free disk
- space available. After installation Apache occupies
+ space available. After installation the server occupies
approximately 10 MB of disk space. The actual disk space
requirements will vary considerably based on your chosen
configuration options and any third-party modules.</dd>
<summary>
- <p>This document covers compilation and installation of Apache
+ <p>This document covers compilation and installation of the Apache HTTP Server
on Unix and Unix-like systems only. For compiling and
installation on Windows, see <a
- href="platform/windows.html">Using Apache with Microsoft
+ href="platform/windows.html">Using Apache HTTP Server with Microsoft
Windows</a>. For other platforms, see the <a
href="platform/">platform</a> documentation.</p>
</summary>
<seealso><a href="programs/configure.html">Configure the source tree</a></seealso>
-<seealso><a href="invoking.html">Starting Apache</a></seealso>
+<seealso><a href="invoking.html">Starting Apache httpd</a></seealso>
<seealso><a href="stopping.html">Stopping and Restarting</a></seealso>
<section id="overview"><title>Overview for the
<section id="requirements"><title>Requirements</title>
- <p>The following requirements exist for building Apache:</p>
+ <p>The following requirements exist for building Apache httpd:</p>
<dl>
<dt>Disk Space</dt>
<dd>Make sure you have at least 50 MB of temporary free disk
- space available. After installation Apache occupies
+ space available. After installation the server occupies
approximately 10 MB of disk space. The actual disk space
requirements will vary considerably based on your chosen
configuration options and any third-party modules.</dd>
<p>In order to effectively manage a web server, it is necessary
to get feedback about the activity and performance of the
- server as well as any problems that may be occurring. The Apache
- HTTP Server provides very comprehensive and flexible logging
+ server as well as any problems that may be occurring. The Apache HTTP Server
+ provides very comprehensive and flexible logging
capabilities. This document describes how to configure its
logging capabilities, and how to understand what the logs
contain.</p>
<h2><a name="security" id="security">Security Warning</a></h2>
- <p>Anyone who can write to the directory where Apache is
+ <p>Anyone who can write to the directory where Apache httpd is
writing a log file can almost certainly gain access to the uid
that the server is started as, which is normally root. Do
<em>NOT</em> give people write access to the directory the logs
log file typically grows 1 MB or more per 10,000 requests. It
will consequently be necessary to periodically rotate the log
files by moving or deleting the existing logs. This cannot be
- done while the server is running, because Apache will continue
+ done while the server is running, because Apache httpd will continue
writing to the old log file as long as it holds the file open.
Instead, the server must be <a href="stopping.html">restarted</a> after the log files are
moved or deleted so that it will open new log files.</p>
In order to write logs to a pipe, simply replace the filename
with the pipe character "<code>|</code>", followed by the name
of the executable which should accept log entries on its
- standard input. Apache will start the piped-log process when
+ standard input. The server will start the piped-log process when
the server starts, and will restart it if it crashes while the
server is running. (This last feature is why we can refer to
this technique as "reliable piped logging".)</p>
<summary>
<p>In order to effectively manage a web server, it is necessary
to get feedback about the activity and performance of the
- server as well as any problems that may be occurring. The Apache
- HTTP Server provides very comprehensive and flexible logging
+ server as well as any problems that may be occurring. The Apache HTTP Server
+ provides very comprehensive and flexible logging
capabilities. This document describes how to configure its
logging capabilities, and how to understand what the logs
contain.</p>
<section id="security">
<title>Security Warning</title>
- <p>Anyone who can write to the directory where Apache is
+ <p>Anyone who can write to the directory where Apache httpd is
writing a log file can almost certainly gain access to the uid
that the server is started as, which is normally root. Do
<em>NOT</em> give people write access to the directory the logs
log file typically grows 1 MB or more per 10,000 requests. It
will consequently be necessary to periodically rotate the log
files by moving or deleting the existing logs. This cannot be
- done while the server is running, because Apache will continue
+ done while the server is running, because Apache httpd will continue
writing to the old log file as long as it holds the file open.
Instead, the server must be <a
href="stopping.html">restarted</a> after the log files are
In order to write logs to a pipe, simply replace the filename
with the pipe character "<code>|</code>", followed by the name
of the executable which should accept log entries on its
- standard input. Apache will start the piped-log process when
+ standard input. The server will start the piped-log process when
the server starts, and will restart it if it crashes while the
server is running. (This last feature is why we can refer to
this technique as "reliable piped logging".)</p>
platforms in a range of different environments. Different
platforms and different environments often require different
features, or may have different ways of implementing the same
- feature most efficiently. Apache has always accommodated a wide
+ feature most efficiently. Apache httpd has always accommodated a wide
variety of environments through its modular design. This design
allows the webmaster to choose which features will be included
in the server by selecting which modules to load either at
compile-time or at run-time.</p>
- <p>Apache 2.0 extends this modular design to the most basic
+ <p>Apache HTTP Server 2.0 extends this modular design to the most basic
functions of a web server. The server ships with a selection of
Multi-Processing Modules (MPMs) which are responsible for
binding to network ports on the machine, accepting requests,
allows two important benefits:</p>
<ul>
- <li>Apache can more cleanly and efficiently support a wide
+ <li>Apache httpd can more cleanly and efficiently support a wide
variety of operating systems. In particular, the Windows
- version of Apache is now much more efficient, since
+ version of the server is now much more efficient, since
<code class="module"><a href="./mod/mpm_winnt.html">mpm_winnt</a></code> can use native
networking features in place of the POSIX layer used in
- Apache 1.3. This benefit also extends to other operating
+ Apache httpd 1.3. This benefit also extends to other operating
systems that implement specialized MPMs.</li>
<li>The server can be better customized for the needs of the
<code class="module"><a href="./mod/prefork.html">prefork</a></code>.</li>
</ul>
- <p>At the user level, MPMs appear much like other Apache
+ <p>At the user level, MPMs appear much like other Apache httpd
modules. The main difference is that one and only one MPM must
be loaded into the server at any time. The list of available
MPMs appears on the <a href="mod/">module index page</a>.</p>
platforms in a range of different environments. Different
platforms and different environments often require different
features, or may have different ways of implementing the same
- feature most efficiently. Apache has always accommodated a wide
+ feature most efficiently. Apache httpd has always accommodated a wide
variety of environments through its modular design. This design
allows the webmaster to choose which features will be included
in the server by selecting which modules to load either at
compile-time or at run-time.</p>
- <p>Apache 2.0 extends this modular design to the most basic
+ <p>Apache HTTP Server 2.0 extends this modular design to the most basic
functions of a web server. The server ships with a selection of
Multi-Processing Modules (MPMs) which are responsible for
binding to network ports on the machine, accepting requests,
allows two important benefits:</p>
<ul>
- <li>Apache can more cleanly and efficiently support a wide
+ <li>Apache httpd can more cleanly and efficiently support a wide
variety of operating systems. In particular, the Windows
- version of Apache is now much more efficient, since
+ version of the server is now much more efficient, since
<module>mpm_winnt</module> can use native
networking features in place of the POSIX layer used in
- Apache 1.3. This benefit also extends to other operating
+ Apache httpd 1.3. This benefit also extends to other operating
systems that implement specialized MPMs.</li>
<li>The server can be better customized for the needs of the
<module>prefork</module>.</li>
</ul>
- <p>At the user level, MPMs appear much like other Apache
+ <p>At the user level, MPMs appear much like other Apache httpd
modules. The main difference is that one and only one MPM must
be loaded into the server at any time. The list of available
MPMs appears on the <a href="mod/">module index page</a>.</p>
projects / apache / commitdiff