core.html revision 61a8652e827e9682430e985d4bf51c991de3e39f
bcb4e51a409d94ae670de96afb8483a4f7855294Stephan Bosch<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<HTML>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<HEAD>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<TITLE>Apache Core Features</TITLE>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen</HEAD>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<BODY>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<!--#include virtual="header.html" -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<H1>Apache Core Features</h1>
12f0c4396d2d9c02b7d5e070aaf64fed5853e9bfAki Tuomi
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenThese configuration parameters control the core Apache features, and are
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenalways available.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<ul>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#accessconfig">AccessConfig</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#accessfilename">AccessFileName</A>
efe78d3ba24fc866af1c79b9223dc0809ba26cadStephan Bosch<li><A HREF="#addmodule">AddModule</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#allowoverride">AllowOverride</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#authname">AuthName</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#authtype">AuthType</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#bindaddress">BindAddress</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#clearmodulelist">ClearModuleList</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#defaulttype">DefaultType</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#directory">&lt;Directory&gt;</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#documentroot">DocumentRoot</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#errordocument">ErrorDocument</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#errorlog">ErrorLog</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#files">&lt;Files&gt;</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#group">Group</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#hostnamelookups">HostNameLookups</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#identitycheck">IdentityCheck</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#ifmodule">&lt;IfModule&gt;</A>
45b0d8d0b97be14d10e3a3c12c169e4b352b2aacTimo Sirainen<li><A HREF="#keepalive">KeepAlive</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#keepalivetimeout">KeepAliveTimeout</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#limit">&lt;Limit&gt;</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#listen">Listen</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#location">&lt;Location&gt;</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#maxclients">MaxClients</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#maxkeepaliverequests">MaxKeepAliveRequests</a>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#maxrequestsperchild">MaxRequestsPerChild</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#maxspareservers">MaxSpareServers</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#minspareservers">MinSpareServers</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#options">Options</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#pidfile">PidFile</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#port">Port</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#require">require</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#resourceconfig">ResourceConfig</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#rlimitcpu">RLimitCPU</A>
12f0c4396d2d9c02b7d5e070aaf64fed5853e9bfAki Tuomi<li><A HREF="#rlimitmem">RLimitMEM</A>
12f0c4396d2d9c02b7d5e070aaf64fed5853e9bfAki Tuomi<li><A HREF="#rlimitnproc">RLimitNPROC</A>
12f0c4396d2d9c02b7d5e070aaf64fed5853e9bfAki Tuomi<li><A HREF="#satisfy">Satisfy</A>
12f0c4396d2d9c02b7d5e070aaf64fed5853e9bfAki Tuomi<li><A HREF="#scoreboardfile">ScoreBoardFile</A>
12f0c4396d2d9c02b7d5e070aaf64fed5853e9bfAki Tuomi<li><A HREF="#sendbuffersize">SendBufferSize</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#serveradmin">ServerAdmin</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#serveralias">ServerAlias</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#servername">ServerName</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#serverpath">ServerPath</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#serverroot">ServerRoot</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#servertype">ServerType</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#startservers">StartServers</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#timeout">TimeOut</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#user">User</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li><A HREF="#virtualhost">&lt;VirtualHost&gt;</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen</ul>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<hr>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A name="accessconfig"><h2>AccessConfig directive</h2></A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<!--%plaintext &lt;?INDEX {\tt AccessConfig} directive&gt; -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Syntax:</strong> AccessConfig <em>filename</em><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Default:</strong> <code>AccessConfig conf/access.conf</code><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Context:</strong> server config, virtual host<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Status:</strong> core<p>
45b0d8d0b97be14d10e3a3c12c169e4b352b2aacTimo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenThe server will read this file for more directives after reading the
45b0d8d0b97be14d10e3a3c12c169e4b352b2aacTimo Sirainen<A HREF="#resourceconfig">ResourceConfig</A> file. <em>Filename</em> is
45b0d8d0b97be14d10e3a3c12c169e4b352b2aacTimo Sirainenrelative to the <A HREF="#serverroot">ServerRoot</A>.
9644b7914445f0fb1098038218bfcb7d135a8698Timo SirainenThis feature can be disabled using:
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<blockquote><code>AccessConfig /dev/null</code></blockquote>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenHistorically, this file only contained
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="#directory">&lt;Directory&gt;</A> sections; in fact it can now
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainencontain any server directive allowed in the <em>server config</em> context.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<p><hr>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A name="accessfilename"><h2>AccessFileName directive</h2></A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<!--%plaintext &lt;?INDEX {\tt AccessFileName} directive&gt; -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Syntax:</strong> AccessFileName <em>filename</em><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Default:</strong> <code>AccessFileName .htaccess</code><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Context:</strong> server config, virtual host<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Status:</strong> core<p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenWhen returning a document to the client the server looks for an
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenaccess control file with this name in every directory of the path to
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenthe document, if access control files are enabled for that directory.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenFor example:
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<blockquote><code>AccessFileName .acl</code></blockquote>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenbefore returning the document /usr/local/web/index.html, the
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenserver will read /.acl, /usr/.acl, /usr/local/.acl and /usr/local/web/.acl
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenfor directives, unless they have been disabled with
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<blockquote><code>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen&lt;Directory /&gt;<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenAllowOverride None<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen&lt;/Directory&gt;</code></blockquote><p><hr>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A name="addmodule"><h2>AddModule directive</h2></A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<!--%plaintext &lt;?INDEX {\tt AddModule} directive&gt; -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Syntax:</strong> AddModule <em>module module ...</em><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Context:</strong> server config <br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Status:</strong> core<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Compatibility:</strong> AddModule is only available in Apache 1.2 and later<p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenThe server can have modules compiled in which are not actively in use.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenThis directive can be used to enable the use of those modules. The
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenserver comes with a pre-loaded list of active modules; this list can
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenbe cleared with the <A HREF="#clearmodulelist">ClearModuleList</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainendirective.<p><hr>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A name="allowoverride"><h2>AllowOverride directive</h2></A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<!--%plaintext &lt;?INDEX {\tt AllowOverride} directive&gt; -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Syntax:</strong> AllowOverride <em>override override ...</em><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Default:</strong> <code>AllowOverride All</code><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Context:</strong> directory<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Status:</strong> core<p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenWhen the server finds an .htaccess file (as specified by
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="#accessfilename">AccessFileName</A>) it needs to know which
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainendirectives declared in that file can override earlier access information.<p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<em>Override</em> can be set to <code>None</code>, in which case the server
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenwill not read the file, <code>All</code> in which case the server will
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenallow all the directives, or one or more of the following:
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<dl>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<dt>AuthConfig
1d738cce754bc64bbc66d3355ebdaf3f6eac55f1Timo Sirainen<dd>
45b0d8d0b97be14d10e3a3c12c169e4b352b2aacTimo Sirainen<!--%plaintext &lt;?INDEX {\tt AuthConfig} override&gt; -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenAllow use of the authorization directives
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen(<A HREF="mod_auth_dbm.html#authdbmgroupfile">AuthDBMGroupFile</A>,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="mod_auth_dbm.html#authdbmuserfile">AuthDBMUserFile</A>,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A>,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="#authname">AuthName</A>, <A HREF="#authtype">AuthType</A>,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="mod_auth.html#authuserfile">AuthUserFile</A>,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="#require">require</A>, etc.).
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<dt>FileInfo
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<dd>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<!--%plaintext &lt;?INDEX {\tt FileInfo} override&gt; -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenAllow use of the directives controlling document types
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen(<A HREF="mod_mime.html#addencoding">AddEncoding</A>,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="mod_mime.html#addlanguage">AddLanguage</A>,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="mod_mime.html#addtype">AddType</A>,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="#defaulttype">DefaultType</A>,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="#errordocument">ErrorDocument</A>,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="mod_negotiation.html#languagepriority">LanguagePriority</A>, etc.).
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<dt>Indexes
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<dd>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<!--%plaintext &lt;?INDEX {\tt Indexes} override&gt; -->
45b0d8d0b97be14d10e3a3c12c169e4b352b2aacTimo SirainenAllow use of the directives controlling directory indexing
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen(<A HREF="mod_dir.html#adddescription">AddDescription</A>,
45b0d8d0b97be14d10e3a3c12c169e4b352b2aacTimo Sirainen<A HREF="mod_dir.html#addicon">AddIcon</A>,
45b0d8d0b97be14d10e3a3c12c169e4b352b2aacTimo Sirainen<A HREF="mod_dir.html#addiconbyencoding">AddIconByEncoding</A>,
9644b7914445f0fb1098038218bfcb7d135a8698Timo Sirainen<A HREF="mod_dir.html#addiconbytype">AddIconByType</A>,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="mod_dir.html#defaulticon">DefaultIcon</A>,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="mod_dir.html#directoryindex">DirectoryIndex</A>,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="mod_dir.html#fancyindexing">FancyIndexing</A>,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="mod_dir.html#headername">HeaderName</A>,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="mod_dir.html#indexignore">IndexIgnore</A>,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="mod_dir.html#indexoptions">IndexOptions</A>,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="mod_dir.html#readmename">ReadmeName</A>, etc.).
f6d5c9fbdac9af5c4d3f467f828dc6f056309d5eTimo Sirainen<dt>Limit
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<dd>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<!--%plaintext &lt;?INDEX {\tt Limit} override&gt; -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenAllow use of the directives controlling host access (allow, deny and order).
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<dt>Options
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<dd>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<!--%plaintext &lt;?INDEX {\tt Options} override&gt; -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenAllow use of the directives controlling specific directory features
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen(<A HREF="#options">Options</A> and
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="mod_include.html#xbithack">XBitHack</A>).
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen</dl><p><hr>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A name="authname"><h2>AuthName directive</h2></A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<!--%plaintext &lt;?INDEX {\tt AuthName} directive&gt; -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Syntax:</strong> AuthName <em>auth-domain</em><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Context:</strong> directory, .htaccess<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Override:</strong> AuthConfig<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Status:</strong> core<p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenThis directive sets the name of the authorization realm for a directory.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenThis realm is given to the client so that the user knows which username and
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenpassword to send.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenIt must be accompanied by <A HREF="#authtype">AuthType</A> and
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="#require">require</A> directives, and directives such as
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="mod_auth.html#authuserfile">AuthUserFile</A> and
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> to work.<p><hr>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A name="authtype"><h2>AuthType directive</h2></A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<!--%plaintext &lt;?INDEX {\tt AuthType} directive&gt; -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Syntax:</strong> AuthType <em>type</em><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Context:</strong> directory, .htaccess<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Override:</strong> AuthConfig<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Status:</strong> core<p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenThis directive selects the type of user authentication for a directory.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenOnly <code>Basic</code> is currently implemented.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<!--%plaintext &lt;?INDEX {\tt Basic} authentication scheme&gt; -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenIt must be accompanied by <A HREF="#authname">AuthName</A> and
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="#require">require</A> directives, and directives such as
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="mod_auth.html#authuserfile">AuthUserFile</A> and
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> to work.<p><hr>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A name="bindaddress"><h2>BindAddress directive</h2></A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<!--%plaintext &lt;?INDEX {\tt BindAddress} directive&gt; -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Syntax:</strong> BindAddress <em>saddr</em><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Default:</strong> <code>BindAddress *</code><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Context:</strong> server config<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Status:</strong> core<p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenA Unix&#174; http server can either listen for connections to every
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenIP address of the server machine, or just one IP address of the server
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenmachine. <em>Saddr</em> can be
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<menu>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li>*
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li>An IP address
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li>A fully-qualified internet domain name
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen</menu>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenIf the value is *, then the server will listen for connections on
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenevery IP address, otherwise it will only listen on the IP address
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenspecified. <p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenThis option can be used as an alternative method for supporting
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="/virtual-host.html">virtual hosts</A> instead of using
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="#virtualhost">&lt;VirtualHost&gt;</A> sections.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<p><strong>See Also:</strong>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<a href="/dns-caveats.html">DNS Issues</a><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>See Also:</strong>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<a href="/bind.html">Setting which addresses and ports Apache uses</a></p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<hr>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A name="clearmodulelist"><h2>ClearModuleList directive</h2></A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<!--%plaintext &lt;?INDEX {\tt ClearModuleList} directive&gt; -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Syntax:</strong> ClearModuleList<br>
1af0c5d8814c2304d09d8ca844a84f0b9b0c1f61Timo Sirainen<strong>Context:</strong> server config<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Status:</strong> core<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Compatibility:</strong> ClearModuleList is only available in Apache 1.2 and later<p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
b71e08759c02a49d02cdfb28343351ad28fc10b5Timo SirainenThe server comes with a built-in list of active modules. This
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainendirective clears the list. It is assumed that the list will then be
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenre-populated using the <A HREF="#addmodule">AddModule</A> directive.<p><hr>
e20e638805c4bd54e039891a3e92760b1dfa189aTimo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A name="defaulttype"><h2>DefaultType directive</h2></A>
e20e638805c4bd54e039891a3e92760b1dfa189aTimo Sirainen<!--%plaintext &lt;?INDEX {\tt DefaultType} directive&gt; -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Syntax:</strong> DefaultType <em>mime-type</em><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Default:</strong> <code>DefaultType text/html</code><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Context:</strong> server config, virtual host, directory, .htaccess<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Override:</strong> FileInfo<br>
e20e638805c4bd54e039891a3e92760b1dfa189aTimo Sirainen<strong>Status:</strong> core<p>
e20e638805c4bd54e039891a3e92760b1dfa189aTimo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenThere will be times when the server is asked to provide a document
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenwhose type cannot be determined by its MIME types mappings.<p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenThe server must inform the client of the content-type of the document, so in
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenthe event of an unknown type it uses the <CODE>DefaultType</CODE>. For
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenexample:
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<blockquote><code>DefaultType image/gif</code></blockquote>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenwould be appropriate for a directory which contained many gif images
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenwith filenames missing the .gif extension.<p><hr>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A name="directory"><h2>&lt;Directory&gt; directive</h2></A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<!--%plaintext &lt;?INDEX {\tt Directory} section directive&gt; -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Syntax:</strong> &lt;Directory <em>directory</em>&gt; ... &lt;/Directory&gt; <br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Context:</strong> server config, virtual host<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Status:</strong> Core. <p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen&lt;Directory&gt; and &lt;/Directory&gt; are used to enclose a group of
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainendirectives which will apply only to the named directory and sub-directories
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenof that directory. Any directive which is allowed in a directory
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainencontext may be used. <em>Directory</em> is either the full path to a directory,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenor a wild-card string. In a wild-card string, `?' matches any single character,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenand `*' matches any sequences of characters. Example:
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<pre>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen &lt;Directory /usr/local/httpd/htdocs&gt;
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen Options Indexes FollowSymLinks
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen &lt;/Directory&gt;
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen</pre>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<p><strong>Apache 1.2 and above:</strong>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenExtended regular expressions can also be used, with the addition of the
85da8c055280cd45553b6b335e9fb226d6e2801eTimo Sirainen<code>~</code> character. For example:</p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<pre>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen &lt;Directory ~ &quot;^/www/.*/[0-9]{3}&quot;&gt;
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen</pre>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenwould match directories in /www/ that consisted of three numbers.<p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<p>If multiple directory sections match the directory (or its parents) containing
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainena document, then the directives are applied in the order of shortest match
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenfirst, interspersed with the directives from the
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A HREF="#accessfilename">.htaccess</A> files. For example, with
6a4bfb2b0bb9f53fb1d4e705bf3948ef4d1ecccbTimo Sirainen<blockquote><code>
6a4bfb2b0bb9f53fb1d4e705bf3948ef4d1ecccbTimo Sirainen&lt;Directory /&gt;<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenAllowOverride None<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen&lt;/Directory&gt;<br><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen&lt;Directory /home/*&gt;<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenAllowOverride FileInfo<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen&lt;/Directory&gt;</code></blockquote>
45b0d8d0b97be14d10e3a3c12c169e4b352b2aacTimo Sirainenfor access to the document <code>/home/web/dir/doc.html</code> the
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainensteps are:
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<menu>
6a4bfb2b0bb9f53fb1d4e705bf3948ef4d1ecccbTimo Sirainen<li>Apply directive <code>AllowOverride None</code> (disabling
6a4bfb2b0bb9f53fb1d4e705bf3948ef4d1ecccbTimo Sirainen<code>.htaccess</code> files).
6a4bfb2b0bb9f53fb1d4e705bf3948ef4d1ecccbTimo Sirainen<li>Apply directive <code>AllowOverride FileInfo</code> (for directory
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<code>/home/web</code>).
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<li>Apply any FileInfo directives in <code>/home/web/.htaccess</code>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen</menu>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<P>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<STRONG>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenNote that the default Apache access for &lt;Directory /&gt; is
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<SAMP>Allow from All</SAMP>. This means that Apache will serve any file
48325adac125d7ff275ec69b05b7a92be9637630Timo Sirainenmapped from an URL. It is recommended that you change this with a block
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainensuch as
66ecc94150cbce23aad3240135e0782e0a74d479Timo Sirainen</STRONG>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<PRE>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen &lt;Directory /&gt;
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen Order Deny,Allow
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen Deny from All
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen &lt;/Directory&gt;
85da8c055280cd45553b6b335e9fb226d6e2801eTimo Sirainen</PRE>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<P>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<STRONG>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenand then override this for directories you <EM>want</EM> accessible.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenSee the
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen HREF="/misc/security_tips.html"
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen>Security Tips</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenpage for more details.
66ecc94150cbce23aad3240135e0782e0a74d479Timo Sirainen</STRONG>
66ecc94150cbce23aad3240135e0782e0a74d479Timo Sirainen</P>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenThe directory sections typically occur in the access.conf file, but they
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenmay appear in any configuration file. &lt;Directory&gt; directives cannot
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainennest, and cannot appear in a <A HREF="#limit">&lt;Limit&gt;</A> section.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<p><hr>
b71e08759c02a49d02cdfb28343351ad28fc10b5Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A NAME="documentroot"><h2>DocumentRoot directive</h2></A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<!--%plaintext &lt;?INDEX {\tt DocumentRoot} directive&gt; -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Syntax:</strong> DocumentRoot <em>directory-filename</em><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Default:</strong> <code>DocumentRoot
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen/usr/local/etc/httpd/htdocs</code><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Context:</strong> server config, virtual host<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Status:</strong> core<p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
45b0d8d0b97be14d10e3a3c12c169e4b352b2aacTimo SirainenThis directive sets the directory from which httpd will serve files.
45b0d8d0b97be14d10e3a3c12c169e4b352b2aacTimo SirainenUnless matched by a directive like Alias, the server appends the path
45b0d8d0b97be14d10e3a3c12c169e4b352b2aacTimo Sirainenfrom the requested URL to the document root to make the path to the
45b0d8d0b97be14d10e3a3c12c169e4b352b2aacTimo Sirainendocument. Example:
45b0d8d0b97be14d10e3a3c12c169e4b352b2aacTimo Sirainen<blockquote><code>DocumentRoot /usr/web</code></blockquote>
45b0d8d0b97be14d10e3a3c12c169e4b352b2aacTimo Sirainenthen an access to <code>http://www.my.host.com/index.html</code> refers
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainento <code>/usr/web/index.html</code>.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<P>There appears to be a bug in mod_dir which causes problems when the
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenDocumentRoot has a trailing slash (i.e. "DocumentRoot /usr/web/") so
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenplease avoid that.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<p><hr>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
6a4bfb2b0bb9f53fb1d4e705bf3948ef4d1ecccbTimo Sirainen<A name="errordocument"><h2>ErrorDocument directive</h2></A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<!--%plaintext &lt;?INDEX {\tt ErrorDocument} directive&gt; -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Syntax:</strong> ErrorDocument <em>error-code document</em><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Context</strong> server config, virtual host, directory, .htaccess<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Status:</strong> core<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Override:</strong> FileInfo<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Compatibility:</strong> The directory and .htaccess contexts
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenare only available in Apache 1.1 and later.<p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenIn the event of a problem or error, Apache can be configured to do
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenone of four things,
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<OL>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<LI>output a simple hardcoded error message
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<LI>output a customized message
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<LI>redirect to a local URL to handle the problem/error
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<LI>redirect to an external URL to handle the problem/error
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen</OL>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<P>The first option is the default, while options 2-4 are configured
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenusing the <CODE>ErrorDocument</CODE> directive, which is followed by
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenthe HTTP response code and a message or URL.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<P><em>Messages</em> in this context begin with a single quote
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen(<code>"</code>), which does not form part of the message itself.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenApache will sometimes offer additional information regarding the
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenproblem/error.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<P>URLs can begin with a slash (/) for local URLs, or be a full
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenURL which the client can resolve. Examples:
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<blockquote><code>
6a4bfb2b0bb9f53fb1d4e705bf3948ef4d1ecccbTimo SirainenErrorDocument 500 http://foo.example.com/cgi-bin/tester<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenErrorDocument 404 /cgi-bin/bad_urls.pl<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenErrorDocument 401 /subscription_info.html<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenErrorDocument 403 "Sorry can't allow you access today
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen</code></blockquote>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<P>Note that when you specify an <CODE>ErrorDocument</CODE> that
6a4bfb2b0bb9f53fb1d4e705bf3948ef4d1ecccbTimo Sirainenpoints to a remote URL (ie. anything with a method such as "http" in
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenfront of it) Apache will send a redirect to the client to tell it
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenwhere to find the document, even if the document ends up being
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenon the same server.. This has several implications, the
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenmost important being that <STRONG>if you use an "ErrorDocument 401"
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainendirective then it must refer to a local document.</STRONG> This results
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenfrom the nature of the HTTP basic authentication scheme.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<P>See Also: <A HREF="/custom-error.html">documentation of customizable
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenresponses.</A><p><hr>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A name="errorlog"><h2>ErrorLog directive</h2></A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<!--%plaintext &lt;?INDEX {\tt ErrorLog} directive&gt; -->
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Syntax:</strong> ErrorLog <em>filename</em><br>
6a4bfb2b0bb9f53fb1d4e705bf3948ef4d1ecccbTimo Sirainen<strong>Default:</strong> <code>ErrorLog logs/error_log</code><br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Context:</strong> server config, virtual host<br>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<strong>Status:</strong> core<p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenThe error log directive sets the name of the file to which the server will log
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenany errors it encounters. If the filename does not begin with a slash (/)
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenthen it is assumed to be relative to the <A HREF="#serverroot">ServerRoot</A>.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenExample:
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<blockquote><code>ErrorLog /dev/null</code></blockquote>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo SirainenThis effectively turns off error logging.<p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
6a4bfb2b0bb9f53fb1d4e705bf3948ef4d1ecccbTimo SirainenSECURITY: See the <A HREF="/misc/security_tips.html">security tips</A>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainendocument for details on why your security could be compromised if
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenthe directory where logfiles are stored is writable by anyone other
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenthan the user that starts the server.
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<p><hr>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<A name="files"><h2>&lt;Files&gt;</h2></A>
6a4bfb2b0bb9f53fb1d4e705bf3948ef4d1ecccbTimo Sirainen<strong>Syntax:</strong> &lt;Files <em>filename</em>&gt;
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen... &lt;/Files&gt;<br>
ca2f3260811c4ccd0afb774d7e13a5bd64d0cc34Timo Sirainen<strong>Context:</strong> server config, virtual host, htaccess<br>
ca2f3260811c4ccd0afb774d7e13a5bd64d0cc34Timo Sirainen<strong>Status:</strong> core<br>
ca2f3260811c4ccd0afb774d7e13a5bd64d0cc34Timo Sirainen<strong>Compatibility:</strong> only available in Apache
ca2f3260811c4ccd0afb774d7e13a5bd64d0cc34Timo Sirainen1.2 and above.<p>
ca2f3260811c4ccd0afb774d7e13a5bd64d0cc34Timo Sirainen
ca2f3260811c4ccd0afb774d7e13a5bd64d0cc34Timo Sirainen<p>The &lt;Files&gt; directive provides for access control by
ca2f3260811c4ccd0afb774d7e13a5bd64d0cc34Timo Sirainenfilename. It is comparable to the <a
ca2f3260811c4ccd0afb774d7e13a5bd64d0cc34Timo Sirainenhref="#directory">&lt;Directory&gt;</a> directive and
c734f70a462bb01a1b8b902375b5b3c7f78d9857Timo Sirainen<a href="#location">&lt;Location&gt;</a> directives. It
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenshould be matched with a &lt;/Files&gt; directive. Directives that
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenapply to the filename given should be listed
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenwithin. <code>&lt;Files&gt;</code> sections are processed in the
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenorder they appear in the configuration file, after the
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen&lt;Directory&gt; sections and <code>.htaccess</code> files are
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenread, but before &lt;Location&gt; sections.</p>
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainen<p>The <em>filename</em> argument should include a filename, or a
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenwild-card string, where `?' matches any single character, and `*' matches any
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainensequences of characters. Extended regular expressions can also be used, with the addition of
7a896d960824c93e2f04ac21e8eae0f892bf8d20Timo Sirainenthe <code>~</code> character. For example:</p>
<pre>
&lt;Files ~ &quot;\.(gif|jpe?g|png)$&quot;&gt;
</pre>
would match most common Internet graphics formats.
<p>Note that unlike <a
href="#directory"><code>&lt;Directory&gt;</code></a> and <a
href="#location"><code>&lt;Location&gt;</code></a> sections,
<code>&lt;Files&gt;</code> sections can be used inside .htaccess
files. This allows users to control access to their own files, at a
file-by-file level. When used in an .htaccess file, if the
<em>filename</em> does not begin with a <code>/</code> character,
the directory being applied will be prefixed automatically.
<p> <hr>
<A name="group"><h2>Group directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt Group} directive&gt; -->
<strong>Syntax:</strong> Group <em>unix-group</em><br>
<strong>Default:</strong> <code>Group #-1</code><br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> core<p>
The Group directive sets the group under which the server will answer requests.
In order to use this directive, the stand-alone server must be run initially
as root. <em>Unix-group</em> is one of:
<dl>
<dt>A group name
<dd>Refers to the given group by name.
<dt># followed by a group number.
<dd>Refers to a group by its number.
</dl>
It is recommended that you set up a new group specifically for running the
server. Some admins use user <code>nobody</code>, but this is not always
possible or desirable.<p>
Note: if you start the server as a non-root user, it will fail to change
to the specified group, and will instead continue to run as the group of the
original user. <p>
Special note: Use of this directive in &lt;VirtualHost&gt; requires a
properly configured <A HREF="/suexec.html">suEXEC wrapper</A>.
When used inside a &lt;VirtualHost&gt; in this manner, only the group
that CGIs are run as is affected. Non-CGI requests are still processed
as the group specified in the main Group directive.<p>
SECURITY: See <A HREF="#user">User</A> for a discussion of the security
considerations.<p><hr>
<A name="hostnamelookups"><h2>HostNameLookups directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt HostNameLookups} directive&gt; -->
<strong>Syntax:</strong> HostNameLookups <em>boolean</em><br>
<strong>Default:</strong> <code>HostNameLookups on</code><br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> core<p>
This directive enables DNS lookups so that host names can be logged.
Having this directive set <code>on</code> also enables the use of names
in &lt;Limit&gt; blocks for access control.<p>
Heavily loaded sites should set this directive <code>off</code>, since DNS
lookups can take considerable amounts of time. The utility <i>logresolve</i>,
provided in the <i>/support</i> directory, can be used to look up host names
from logged IP addresses offline.<p><hr>
<A name="identitycheck"><h2>IdentityCheck directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt IdentityCheck} directive&gt; -->
<strong>Syntax:</strong> IdentityCheck <em>boolean</em><br>
<strong>Default:</strong> <code>IdentityCheck off</code><br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> core<p>
This directive enables RFC1413-compliant logging of the remote user name
for each connection, where the client machine runs identd or something similar.
This information is logged in the access log. <em>Boolean</em> is either
<code>on</code> or <code>off</code>.<p>
The information should not be trusted in any way except for rudimentary usage
tracking.<p>
Note that this can cause serious latency problems accessing your server
since every request requires one of these lookups to be performed. When
firewalls are involved each lookup might possibly fail and add 30 seconds
of latency to each hit. So in general this is not very useful on public
servers accessible from the internet.
<p><hr>
<A NAME="ifmodule"><H2>&lt;IfModule&gt;</H2></A>
<b>Syntax:</b> &lt;IfModule [!]<i>module-name</i>&gt; <i>...</i>
&lt;/IfModule&gt;<br>
<b>Default:</b> None<br>
<b>Context:</b> all<br>
<b>Status:</b> Core
<strong>Compatibility:</strong> ScriptLog is only available in 1.2 and
later.<P>
<p>
The &lt;IfModule <i>test</i>&gt;...&lt;/IfModule&gt;
section is used to mark directives that are conditional. The
directives within an IfModule section are only
processed if the <i>test</i> is true. If <i>test</i>
is false, everything between the start and end markers
is ignored.<p>
The <i>test</i> in the &lt;IfModule&gt; section directive
can be one of two forms:
<ul>
<li><i>module name</i>
<li>!<i>module name</i>
</ul>
<p>In the former case, the directives between the start and end markers
are only processed if the module named <i>module name</i> is compiled
in to Apache. The second format reverses the test, and only processes
the directives if <i>module name</i> is <b>not</b> compiled in.
<p>The <i>module name</i> argument is a module name as given as the file
name of the module, at the time it was compiled. For example,
<code>mod_rewrite.c</code>.
<p>&lt;IfModule&gt; sections are nest-able, which can be used to implement
simple multiple-module tests.
<P> <hr>
<h2><a name="keepalive">KeepAlive</a></h2>
<strong>Syntax: (Apache 1.1)</strong> KeepAlive <em>max-requests</em><br>
<strong>Default: (Apache 1.1)</strong> <code>KeepAlive 5</code><br>
<strong>Syntax: (Apache 1.2)</strong> KeepAlive <em>on/off</em><br>
<strong>Default: (Apache 1.2)</strong> <code>KeepAlive On</code><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> Core<br>
<strong>Compatibility:</strong> KeepAlive is only available in Apache
1.1 and later.<p>
This directive enables
<a href="/keepalive.html">Keep-Alive</a>
support.
<p><strong>Apache 1.1</strong>: Set <em>max-requests</em>
to the maximum number of requests you want Apache to entertain per
request. A limit is imposed to prevent a client from hogging your
server resources. Set this to <code>0</code> to disable support.
<p><strong>Apache 1.2 and later</strong>: Set to "On" to enable
persistent connections, "Off" to disable. See also the <a
href="#maxkeepaliverequests">MaxKeepAliveRequests</a> directive.</p>
<h2><a name="keepalivetimeout">KeepAliveTimeout</a></h2>
<strong>Syntax:</strong> KeepAliveTimeout <em>seconds</em><br>
<strong>Default:</strong> <code>KeepAliveTimeout 15</code><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> Core<br>
<strong>Compatibility:</strong> KeepAliveTimeout is only available in Apache
1.1 and later.<p>
The number of seconds Apache will wait for a subsequent request before
closing the connection. Once a request has been received, the timeout
value specified by the <a
href="#timeout"><code>Timeout</code></a> directive
applies.
<hr>
<A name="listen"><h2>Listen</h2></A>
<strong>Syntax:</strong>
Listen [<em>IP address</em>:]<em>port number</em><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> core<br>
<strong>Compatibility:</strong> Listen is only available in Apache
1.1 and later.<p>
<p>The Listen directive instructs Apache to listen to more than one IP
address or port; by default it responds to requests on all IP
interfaces, but only on the port given by the <a href="#port">Port</a>
directive.</p>
<p><strong>See Also:</strong>
<a href="/dns-caveats.html">DNS Issues</a><br>
<strong>See Also:</strong>
<a href="/bind.html">Setting which addresses and ports Apache uses</a><br>
<strong>See Also:</strong>
<a href="/misc/known_bugs.html#listenbug">Known Bugs</a></p>
<hr>
<A name="limit"><h2>&lt;Limit&gt; directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt Limit} section directive&gt; -->
<strong>Syntax:</strong>
&lt;Limit <em>method method</em> ... &gt; ... &lt;/Limit&gt;<br>
<strong>Context:</strong> any<br>
<strong>Status:</strong> core<p>
&lt;Limit&gt; and &lt;/Limit&gt; are used to enclose a group of
access control directives which will then apply only to the specified
access methods, where <em>method</em> is any valid HTTP method.
Any directive except another &lt;Limit&gt; or
<A HREF="#directory">&lt;Directory&gt;</A> may be used; the majority will be
unaffected by the &lt;Limit&gt;. Example:
<blockquote><code>
&lt;Limit GET POST&gt;<br>
require valid-user<br>
&lt;/Limit&gt;</code></blockquote>
If an access control directive appears outside a &lt;Limit&gt; directive,
then it applies to all access methods.<p><hr>
<h2><a name="location">&lt;Location&gt;</a></h2>
<strong>Syntax:</strong> &lt;Location <em>URL</em>&gt;
... &lt;/Location&gt;<br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> core<br>
<strong>Compatibility:</strong> Location is only available in Apache
1.1 and later.<p>
<p>The &lt;Location&gt; directive provides for access control by
URL. It is comparable to the <a
href="#directory">&lt;Directory&gt;</a> directive, and
should be matched with a &lt;/Location&gt; directive. Directives that
apply to the URL given should be listed
within. <code>&lt;Location&gt;</code> sections are processed in the
order they appear in the configuration file, after the
&lt;Directory&gt; sections and <code>.htaccess</code> files are
read.</p>
<p>Note that, due to the way HTTP functions, <em>URL prefix</em>
should, save for proxy requests, be of the form <code>/path/</code>,
and should not include the <code>http://servername</code>. It doesn't
necessarily have to protect a directory (it can be an individual
file, or a number of files), and can include wild-cards. In a wild-card
string, `?' matches any single character, and `*' matches any
sequences of characters.
<p><strong>Apache 1.2 and above:</strong>
Extended regular expressions can also be used, with the addition of
the
<code>~</code> character. For example:</p>
<pre>
&lt;Location ~ &quot;/(extra|special)/data&quot;&gt;
</pre>
would match URLs that contained the substring "/extra/data" or
"/special/data".</p>
<p>The <code>Location</code> functionality is especially useful when
combined with the <code><a
href="mod_mime.html#sethandler">SetHandler</a></code> directive. For example, to enable status requests, but allow them only
from browsers at foo.com, you might use:
<pre>
&lt;Location /status&gt;
SetHandler server-status
order deny,allow
deny from all
allow from .foo.com
&lt;/Location&gt;
</pre>
<hr>
<A name="maxclients"><h2>MaxClients directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt MaxClients} directive&gt; -->
<strong>Syntax:</strong> MaxClients <em>number</em><br>
<strong>Default:</strong> <code>MaxClients 256</code><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> core<p>
The MaxClients directive sets the limit on the number of simultaneous
requests that can be supported; not more than this number of child server
processes will be created.<p><hr>
<A name="maxkeepaliverequests"><h2>MaxKeepAliveRequests</h2></A>
<strong>Syntax:</strong> MaxKeepAliveRequests <em>number</em><br>
<strong>Default:</strong> <code>MaxKeepAliveRequests 100</code><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> core<br>
<strong>Compatibility:</strong> Only available in Apache
1.2 and later.
<p>The MaxKeepAliveRequests directive limits the number of requests
allowed per connection when <a href="#keepalive">KeepAlive</a> is
on. If it is set to "<code>0</code>", unlimited requests will be
allowed. We recommend that this setting be kept to a high value for
maximum server peformance.
<A name="maxrequestsperchild"><h2>MaxRequestsPerChild directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt MaxRequestsPerChild} directive&gt; -->
<strong>Syntax:</strong> MaxRequestsPerChild <em>number</em><br>
<strong>Default:</strong> <code>MaxRequestsPerChild 0</code><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> core<p>
The MaxRequestsPerChild directive sets the limit on the number of requests
that an individual child server process will handle. After MaxRequestsPerChild
requests, the child process will die. If MaxRequestsPerChild is 0, then
the process will never expire.<p>
Setting MaxRequestsPerChild to a non-zero limit has two beneficial effects:
<ul>
<li>it limits the amount of memory that process can consume by (accidental)
memory leakage;
<li> by giving processes a finite lifetime, it helps reduce the
number of processes when the server load reduces.
</ul><p><hr>
<A name="maxspareservers"><h2>MaxSpareServers directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt MaxSpareServers} directive&gt; -->
<strong>Syntax:</strong> MaxSpareServers <em>number</em><br>
<strong>Default:</strong> <code>MaxSpareServers 10</code><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> core<p>
The MaxSpareServers directive sets the desired maximum number of <em>idle</em>
child server processes. An idle process is one which is not handling
a request. If there are more than MaxSpareServers idle, then the parent
process will kill off the excess processes.<p>
Tuning of this parameter should only be necessary on very busy sites.
Setting this parameter to a large number is almost always a bad idea.<p>
See also <A HREF="#minspareservers">MinSpareServers</A> and
<A HREF="#startservers">StartServers</A>.<p><hr>
<A name="minspareservers"><h2>MinSpareServers directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt MinSpareServers} directive&gt; -->
<strong>Syntax:</strong> MinSpareServers <em>number</em><br>
<strong>Default:</strong> <code>MinSpareServers 5</code><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> core<p>
The MinSpareServers directive sets the desired minimum number of <em>idle</em>
child server processes. An idle process is one which is not handling
a request. If there are fewer than MinSpareServers idle, then the parent
process creates new children at a maximum rate of 1 per second.<p>
Tuning of this parameter should only be necessary on very busy sites.
Setting this parameter to a large number is almost always a bad idea.<p>
See also <A HREF="#maxspareservers">MaxSpareServers</A> and
<A HREF="#startservers">StartServers</A>.<p><hr>
<A name="options"><h2>Options directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt Options} directive&gt; -->
<strong>Syntax:</strong> Options <em>[+|-]option [+|-]option ...</em><br>
<strong>Context:</strong> server config, virtual host, directory, .htaccess<br>
<strong>Override:</strong> Options<br>
<strong>Status:</strong> core<p>
The Options directive controls which server features are available in
a particular directory.
<p>
<em>option</em> can be set to <code>None</code>, in which case none of
the extra features are enabled, or one or more of the following:
<dl>
<dt>All
<dd>All options except for MultiViews.
<dt>ExecCGI
<dd>
<!--%plaintext &lt;?INDEX {\tt ExecCGI} option&gt; -->
Execution of CGI scripts is permitted.
<dt>FollowSymLinks
<dd>
<!--%plaintext &lt;?INDEX {\tt FollowSymLinks} option&gt; -->
The server will follow symbolic links in this directory.
<dt>Includes
<dd>
<!--%plaintext &lt;?INDEX {\tt Includes} option&gt; -->
Server-side includes are permitted.
<dt>IncludesNOEXEC
<dd>
<!--%plaintext &lt;?INDEX {\tt IncludesNOEXEC} option&gt; -->
Server-side includes are permitted, but the #exec command and
#include of CGI scripts are disabled.
<dt>Indexes
<dd>
<!--%plaintext &lt;?INDEX {\tt Indexes} option&gt; -->
If a URL which maps to a directory is requested, and the there is no
DirectoryIndex (e.g. index.html) in that directory, then the server will
return a formatted listing of the directory.
<dt>MultiViews
<dd>
<!--%plaintext &lt;?INDEX {\tt MultiViews} option&gt; -->
<A HREF="/content-negotiation.html">Content negotiated</A> MultiViews are
allowed.
<dt>SymLinksIfOwnerMatch
<dd>
<!--%plaintext &lt;?INDEX {\tt SymLinksIfOwnerMatch} option&gt; -->
The server will only follow symbolic links for which the target
file or directory is owned by the same user id as the link.
</dl>
Normally, if multiple <code>Options</code> could apply to a directory,
then the most specific one is taken complete; the options are not
merged. However if <i>all</i> the options on the <code>Options</code>
directive are preceded by a + or - symbol, the options are
merged. Any options preceded by a + are added to the options
currently in force, and any options preceded by a - are removed from
the options currently in force. <P>
For example, without any + and - symbols:
<blockquote><code>
&lt;Directory /web/docs&gt; <br>
Options Indexes FollowSymLinks<br>
&lt;/Directory&gt;<br>
&lt;Directory /web/docs/spec&gt; <br>
Options Includes<br>
&lt;/Directory&gt;
</code></blockquote>
then only <code>Includes</code> will be set for the /web/docs/spec
directory. However if the second <code>Options</code> directive uses the +
and - symbols:<p>
<blockquote><code>
&lt;Directory /web/docs&gt; <br>
Options Indexes FollowSymLinks<br>
&lt;/Directory&gt;<br>
&lt;Directory /web/docs/spec&gt; <br>
Options +Includes -Indexes<br>
&lt;/Directory&gt;
</code></blockquote>
then the options <code>FollowSymLinks</code> and <code>Includes</code>
are set for the /web/docs/spec directory.
<hr>
<A name="pidfile"><h2>PidFile directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt PidFile} directive&gt; -->
<strong>Syntax:</strong> PidFile <em>filename</em><br>
<strong>Default:</strong> <code>PidFile logs/httpd.pid</code><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> core<p>
The PidFile directive sets the file to which the server records the
process id of the daemon. If the filename does not begin with a slash (/)
then it is assumed to be relative to the <A HREF="#serverroot">ServerRoot</A>.
The PidFile is only used in <A HREF="#servertype">standalone</A> mode.<p>
It is often useful to be able to send the server a signal, so that it closes
and then reopens its <A HREF="#errorlog">ErrorLog</A> and TransferLog, and
re-reads its configuration files. This is done by sending a SIGHUP (kill -1)
signal to the process id listed in the PidFile.<p>
The PidFile is subject to the same warnings about log file placement and
<a href="/misc/security_tips.html">security</a>.
<p><hr>
<A name="port"><h2>Port directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt Port} directive&gt; -->
<strong>Syntax:</strong> Port <em>number</em><br>
<strong>Default:</strong> <code>Port 80</code><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> core<p>
The Port directive sets the network port on which the server listens.
<em>Num</em> is a number from 0 to 65535; some port numbers (especially below
1024) are reserved for particular protocols. See <code>/etc/services</code>
for a list of some defined ports; the standard port for the http protocol
is 80.<p>
Port 80 is one of Unix's special ports. All ports numbered
below 1024 are reserved for system use, i.e. regular (non-root) users cannot
make use of them; instead they can only use higher port numbers.<p>
To use port 80, you must start the server from the root account.
After binding to the port and before accepting requests, Apache will change
to a low privileged user as set by the <A HREF="#user">User directive</A>.<p>
If you cannot use port 80, choose any other unused port. Non-root users
will have to choose a port number higher than 1023, such as 8000.<p>
SECURITY: if you do start the server as root, be sure
not to set <A HREF="#user">User</A> to root. If you run the server as
root whilst handling connections, your site may be open to a major security
attack.<p><hr>
<A name="require"><h2>require directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt require} directive&gt; -->
<strong>Syntax:</strong> require <em>entity-name entity entity...</em><br>
<strong>Context:</strong> directory, .htaccess<br>
<strong>Override:</strong> AuthConfig<br>
<strong>Status:</strong> core<p>
This directive selects which authenticated users can access a directory.
The allowed syntaxes are:
<ul>
<li>require user <em>userid userid ...</em><p>
Only the named users can access the directory.<p>
<li>require group <em>group-name group-name ...</em><p>
Only users in the named groups can access the directory.<p>
<li>require valid-user<p>
All valid users can access the directory.
</ul>
<p>
If <code>require</code> appears in a <A HREF="#limit">&lt;Limit&gt;</A>
section, then it restricts access to the named methods, otherwise
it restricts access for all methods. Example:
<blockquote><code>
AuthType Basic<br>
AuthName somedomain<br>
AuthUserFile /web/users<br>
AuthGroupFile /web/groups<br>
&lt;Limit GET POST&gt;<br>
require group admin<br>
&lt;/Limit&gt;
</code></blockquote>
Require must be accompanied by <A HREF="#authname">AuthName</A> and
<A HREF="#authtype">AuthType</A> directives, and directives such as
<A HREF="mod_auth.html#authuserfile">AuthUserFile</A> and
<A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> (to define users and
groups) in order to work correctly.<p><hr>
<A name="resourceconfig"><h2>ResourceConfig directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt ResourceConfig} directive&gt; -->
<strong>Syntax:</strong> ResourceConfig <em>filename</em><br>
<strong>Default:</strong> <code>ResourceConfig conf/srm.conf</code><br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> core<p>
The server will read this file for more directives after reading the
httpd.conf file. <em>Filename</em> is relative to the
<A HREF="#serverroot">ServerRoot</A>.
This feature can be disabled using:
<blockquote><code>ResourceConfig /dev/null</code></blockquote>
Historically, this file contained most directives except for server
configuration directives and <A HREF="#directory">&lt;Directory&gt;</A>
sections; in fact it can now contain any server directive allowed in the
<em>server config</em> context.<p>
See also <A HREF="#accessconfig">AccessConfig</A>.<p><hr>
<A name="rlimit">
<A name="rlimitcpu"><h2>RLimitCPU directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt RLimitCPU} directive&gt; -->
<strong>Syntax:</strong> RLimitCPU <em># or 'max'</em> <em>[# or 'max']</em><br>
<strong>Default:</strong> <code>Unset uses operating system defaults</code><br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> core<br>
<strong>Compatibility:</strong> RLimitCPU is only available in Apache 1.2 and later<p>
Takes 1 or 2 parameters. The first parameter sets the soft resource limit for all
processes and the second parameter sets the maximum resource limit. Either parameter
can be a number, or <em>max</em> to indicate to the server that the limit should
be set to the maximum allowed by the operating system configuration. Raising the
maximum resource limit requires that the server is running as root, or in the initial
startup phase.<p>
CPU resource limits are expressed in seconds per process.<p>
See also <A HREF="#rlimitmem">RLimitMEM</A> or <A HREF="#rlimitnproc">RLimitNPROC</A>.<p><hr>
<A name="rlimitmem"><h2>RLimitMEM directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt RLimitMEM} directive&gt; -->
<strong>Syntax:</strong> RLimitMEM <em># or 'max'</em> <em>[# or 'max']</em><br>
<strong>Default:</strong> <code>Unset uses operating system defaults</code><br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> core<br>
<strong>Compatibility:</strong> RLimitMEM is only available in Apache 1.2 and later<p>
Takes 1 or 2 parameters. The first parameter sets the soft resource limit for all
processes and the second parameter sets the maximum resource limit. Either parameter
can be a number, or <em>max</em> to indicate to the server that the limit should
be set to the maximum allowed by the operating system configuration. Raising the
maximum resource limit requires that the server is running as root, or in the initial
startup phase.<p>
Memory resource limits are expressed in bytes per process.<p>
See also <A HREF="#rlimitcpu">RLimitCPU</A> or <A HREF="#rlimitnproc">RLimitNPROC</A>.<p><hr>
<A name="rlimitnproc"><h2>RLimitNPROC directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt RLimitNPROC} directive&gt; -->
<strong>Syntax:</strong> RLimitNPROC <em># or 'max'</em> <em>[# or 'max']</em><br>
<strong>Default:</strong> <code>Unset uses operating system defaults</code><br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> core<br>
<strong>Compatibility:</strong> RLimitNPROC is only available in Apache 1.2 and later<p>
Takes 1 or 2 parameters. The first parameter sets the soft resource limit for all
processes and the second parameter sets the maximum resource limit. Either parameter
can be a number, or <em>max</em> to indicate to the server that the limit should
be set to the maximum allowed by the operating system configuration. Raising the
maximum resource limit requires that the server is running as root, or in the initial
startup phase.<p>
Process limits control the number of processes per user.<p>
Note: If CGI processes are <b>not</b> running under userids other than the
web server userid, this directive will limit the number of processes that the
server itself can create. Evidence of this situation will be indicated by
<b><em>cannot fork</em></b> messages in the error_log.<p>
See also <A HREF="#rlimitmem">RLimitMEM</A> or <A HREF="#rlimitcpu">RLimitCPU</A>.
<p><hr>
<A name="satisfy"><h2>Satisfy</h2></A>
<!--%plaintext &lt;?INDEX {\tt Satisfy} directive&gt; -->
<strong>Syntax:</strong> Satisfy <em>'any' or 'all'</em><br>
<strong>Default:</strong> Satisy all<br>
<strong>Context:</strong> directory, .htaccess<br>
<strong>Status:</strong> core<br>
<strong>Compatibility:</strong> Satisfy is only available in Apache 1.2 and later<p>
Access policy if both allow and require used. The parameter can be
either <em>'all'</em> or <em>'any'</em>. This directive is only useful
if access to a particular area is being restricted by both
username/password <i>and</i> client host address. In this case the
default behavior ("all") is to require that the client passes the
address access restriction <i>and</i> enters a valid username and
password. With the "any" option the client will be granted access if
they either pass the host restriction or enter a valid username and
password. This can be used to password restrict an area, but to let
clients from particular addresses in without prompting for a password.
<p><hr>
<A name="scoreboardfile"><h2>ScoreBoardFile directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt ScoreBoardFile} directive&gt; -->
<strong>Syntax:</strong> ScoreBoardFile <em>filename</em><br>
<strong>Default:</strong> <code>ScoreBoardFile logs/apache_status</code><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> core<p>
The ScoreBoardFile directive is required on some architectures to place
a file that the server will use to communicate between its children and
the parent. The easiest way to find out if your architecture requires
a scoreboard file is to run Apache and see if it creates the file named
by the directive. If your architecture requires it then you must ensure
that this file is not used at the same time by more than one invocation
of Apache.<p>
If you have to use a ScoreBoardFile then you may see improved speed by
placing it on a RAM disk. But be careful that you heed the same warnings
about log file placement and
<a href="/misc/security_tips.html">security</a>.<p>
Apache 1.2 and above:<p>
Linux 2.x users should consider defining <code>Rules LINUX_TWEAK=yes</code>
in the <code>Configuration</code> file which will cause the server to
use shared memory instead of a scoreboard file. This is known to cause
compilation problems with some distributions and kernels, so we have not
enabled it by default. (Patches to conditionally determine the ability
to set this option are quite welcome.)<p>
SVR4 users should consider adding <code>-DHAVE_SHMGET</code> to the
<code>EXTRA_CFLAGS</code> in your <code>Configuration</code>. This
is believed to work, but we were unable to test it in time for 1.2
release.<p>
<p><hr>
<A name="sendbuffersize"><h2>SendBufferSize directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt SendBufferSize} directive&gt; -->
<strong>Syntax:</strong> SendBufferSize <em>bytes</em><br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> core<p>
The server will set the TCP buffer size to the number of bytes
specified. Very useful to increase past standard OS defaults on high
speed high latency (i.e. 100ms or so, such as transcontinental
fast pipes)
<p><hr>
<A name="serveradmin"><h2>ServerAdmin directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt ServerAdmin} directive&gt; -->
<strong>Syntax:</strong> ServerAdmin <em>email-address</em><br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> core<p>
The ServerAdmin sets the e-mail address that the server includes in any
error messages it returns to the client.<p>
It may be worth setting up a dedicated address for this, e.g.
<blockquote><code>ServerAdmin www-admin@foo.bar.com</code></blockquote>
as users do not always mention that they are talking about the server!<p><hr>
<A name="serveralias"><h2>ServerAlias directive</h2></A>
<strong>Syntax:</strong> ServerAlias <em>host1 host2 ...</em><br>
<strong>Context:</strong> virtual host<br>
<strong>Status:</strong> core<br>
<strong>Compatibility:</strong> ServerAlias is only available in Apache
1.1 and later.<p>
The ServerAlias directive sets the alternate names for a host, for use
with
<a href="/host.html">Host-header based virtual hosts</a>.
<p><strong>See Also</strong>:
<a href="/vhosts-in-depth.html">In-depth description of Virtual Host matching</a></p>
<hr>
<A name="servername"><h2>ServerName directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt ServerName} directive&gt; -->
<strong>Syntax:</strong> ServerName <em>fully-qualified domain name</em><br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> core<p>
The ServerName directive sets the hostname of the server; this is only
used when creating redirection URLs. If it is not specified, then the
server attempts to deduce it from its own IP address; however this may
not work reliably, or may not return the preferred hostname. For example:
<blockquote><code>ServerName www.wibble.com</code></blockquote>
would be used if the canonical (main) name of the actual machine
were <code>monster.wibble.com</code>.<p>
<p><strong>See Also</strong>:
<a href="/dns-caveats.html">DNS Issues</a></p>
<hr>
<A name="serverpath"><h2>ServerPath directive</h2></A>
<strong>Syntax:</strong> ServerPath <em>pathname</em><br>
<strong>Context:</strong> virtual host<br>
<strong>Status:</strong> core<br>
<strong>Compatibility:</strong> ServerPath is only available in Apache
1.1 and later.<p>
The ServerPath directive sets the legacy URL pathname for a host, for
use with <a href="/host.html">Host-header based virtual hosts</a>.
<p><strong>See Also</strong>:
<a href="/vhosts-in-depth.html">In-depth description of Virtual Host matching</a></p>
<hr>
<A name="serverroot"><h2>ServerRoot directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt ServerRoot} directive&gt; -->
<strong>Syntax:</strong> ServerRoot <em>directory-filename</em><br>
<strong>Default:</strong> <code>ServerRoot /usr/local/etc/httpd</code><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> core<p>
The ServerRoot directive sets the directory in which the server lives.
Typically it will contain the subdirectories <code>conf/</code> and
<code>logs/</code>. Relative paths for other configuration files are taken
as relative to this directory.<br>
See also <a href="/invoking.html">the <code>-d</code> option to httpd</a>.<p><hr>
<A name="servertype"><h2>ServerType directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt ServerType} directive&gt; -->
<strong>Syntax:</strong> ServerType <em>type</em><br>
<strong>Default:</strong> <code>ServerType standalone</code><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> core<p>
The ServerType directive sets how the server is executed by the system.
<em>Type</em> is one of
<dl>
<dt>inetd
<dd>The server will be run from the system process inetd; the command to start
the server is added to <code>/etc/inetd.conf</code>
<dt>standalone
<dd>The server will run as a daemon process; the command to start the server
is added to the system startup scripts. (<code>/etc/rc.local</code> or
<code>/etc/rc3.d/...</code>.)
</dl>
Inetd is the lesser used of the two options. For each http
connection received, a new copy of the server is started from scratch;
after the connection is complete, this program exits. There is a high price to
pay per connection, but for security reasons, some admins prefer this option.
<p>
Standalone is the most common setting for ServerType since
it is far more efficient. The server is started once, and services all
subsequent connections. If you intend running Apache to serve a busy site,
standalone will probably be your only option.<p>
SECURITY: if you are paranoid about security, run in inetd mode. Security
cannot be guaranteed in either, but whilst most people are happy to use
standalone, inetd is probably least prone to attack.<p><hr>
<A name="startservers"><h2>StartServers directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt StartServers} directive&gt; -->
<strong>Syntax:</strong> StartServers <em>number</em><br>
<strong>Default:</strong> <code>StartServers 5</code><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> core<p>
The StartServers directive sets the number of child server processes created
on startup. As the number of processes is dynamically controlled depending
on the load, there is usually little reason to adjust this parameter.<p>
See also <A HREF="#minspareservers">MinSpareServers</A> and
<A HREF="#maxspareservers">MaxSpareServers</A>.<p><hr>
<A name="timeout"><h2>TimeOut directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt TimeOut} directive&gt; -->
<strong>Syntax:</strong> TimeOut <em>number</em><br>
<strong>Default:</strong> <code>TimeOut 300</code><br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> core<p>
The TimeOut directive currently defines the amount of time Apache will
wait for three things:
<OL>
<LI>The total amount of time it takes to receive a GET request.
<LI>The amount of time between receipt of TCP packets on a POST or
PUT request.
<LI>The amount of time between ACKs on transmissions of TCP packets
in responses.
</OL>
We plan on making these separately configurable at some point down the
road. The timer used to default to 1200 before 1.2, but has been
lowered to 300 which is still far more than necessary in most
situations. It is not set any lower by default because there may
still be odd places in the code where the timer is not reset when
a packet is sent.
<p><hr>
<A name="user"><h2>User directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt User} directive&gt; -->
<strong>Syntax:</strong> User <em>unix-userid</em><br>
<strong>Default:</strong> <code>User #-1</code><br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> core<p>
The User directive sets the userid as which the server will answer requests.
In order to use this directive, the standalone server must be run initially
as root. <em>Unix-userid</em> is one of:
<dl>
<dt>A username
<dd>Refers to the given user by name.
<dt># followed by a user number.
<dd>Refers to a user by their number.
</dl>
The user should have no privileges which result in it being able to access
files which are not intended to be visible to the outside world, and
similarly, the user should not be able to execute code which is not
meant for httpd requests. It is recommended that you set up a new user and
group specifically for running the server. Some admins use user
<code>nobody</code>, but this is not always possible or desirable.<p>
Notes: If you start the server as a non-root user, it will fail to change
to the lesser privileged user, and will instead continue to run as
that original user. If you do start the server as root, then it is normal
for the parent process to remain running as root.<p>
Special note: Use of this directive in &lt;VirtualHost&gt; requires a
properly configured <A HREF="/suexec.html">suEXEC wrapper</A>.
When used inside a &lt;VirtualHost&gt; in this manner, only the user
that CGIs are run as is affected. Non-CGI requests are still processed
with the user specified in the main User directive.<p>
SECURITY: Don't set User (or <A HREF="#group">Group</A>) to
<code>root</code> unless you know exactly what you are doing, and what the
dangers are.<p><hr>
<A name="virtualhost"><h2>&lt;VirtualHost&gt; directive</h2></A>
<!--%plaintext &lt;?INDEX {\tt VirtualHost} section directive&gt; -->
<strong>Syntax:</strong> &lt;VirtualHost <em>addr</em>[:<em>port</em>] ...&gt; ...
&lt;/VirtualHost&gt; <br>
<strong>Context:</strong> server config<br>
<strong>Status:</strong> Core.<br>
<strong>Compatibility:</strong> Non-IP address-based Virtual Hosting only
available in Apache 1.1 and later.<br>
<strong>Compatibility:</strong> Multiple address support only available in
Apache 1.2 and later.<p>
&lt;VirtualHost&gt; and &lt;/VirtualHost&gt; are used to enclose a group of
directives which will apply only to a particular virtual host.
Any directive which is allowed in a virtual host context may be used.
When the server receives a request for a document on a particular virtual
host, it uses the configuration directives enclosed in the &lt;VirtualHost&gt;
section. <em>Addr</em> can be
<menu>
<li>The IP address of the virtual host
<li>A fully qualified domain name for the IP address of the virtual host.
</menu> Example:
<blockquote>
<code>
&lt;VirtualHost host.foo.com&gt; <br>
ServerAdmin webmaster@host.foo.com <br>
DocumentRoot /www/docs/host.foo.com <br>
ServerName host.foo.com <br>
ErrorLog logs/host.foo.com-error_log <br>
TransferLog logs/host.foo.com-access_log <br>
&lt;/VirtualHost&gt;
</code></blockquote>
Each VirtualHost must correspond to a different IP address or a
different host name for the server, in the latter case the server
machine must be configured to accept IP packets for multiple
addresses. (If the machine does not have multiple network interfaces,
then this can be accomplished with the <code>ifconfig alias</code>
command (if your OS supports it), or with kernel patches like <A
HREF="/misc/vif-info.html">VIF</A> (for SunOS(TM) 4.1.x)).<p>
The special name <code>_default_</code> can be specified in which case
this virtual host will match any ip address that is not explicitly listed
in another virtual host. In the absence of any _default_ virtual host
the "main" server config, consisting of all those definitions outside
any VirtualHost section, is used when no match occurs.<p>
<strong>SECURITY</strong>: See the
<A HREF="/misc/security_tips.html">security tips</A>
document for details on why your security could be compromised if
the directory where logfiles are stored is writable by anyone other
than the user that starts the server.
<p><strong>See also:</strong>
<A HREF="/dns-caveats.html">Warnings about DNS and Apache</a><br>
<strong>See also:</strong>
<A HREF="/virtual-host.html">Information on Virtual Hosts.
(multihome)</A><br>
<strong>See also:</strong>
<a href="/host.html">Non-IP address-based Virtual Hosts</a><br>
<strong>See also:</strong>
<a href="/vhosts-in-depth.html">In-depth description of Virtual Host matching</a>
</p>
<!--#include virtual="footer.html" -->
</BODY>
</HTML>