</UL>
<HR>
-<H2><A name="accessconfig">AccessConfig directive</A></H2>
+<H2><A NAME="accessconfig">AccessConfig directive</A></H2>
<!--%plaintext <?INDEX {\tt AccessConfig} directive> -->
<A
HREF="directive-dict.html#Syntax"
contain any server directive allowed in the <EM>server config</EM> context.
<P><HR>
-<H2><A name="accessfilename">AccessFileName directive</A></H2>
+<H2><A NAME="accessfilename">AccessFileName directive</A></H2>
<!--%plaintext <?INDEX {\tt AccessFileName} directive> -->
<A
HREF="directive-dict.html#Syntax"
<A
HREF="directive-dict.html#Compatibility"
REL="Help"
-><STRONG>Compatibility:</STRONG></A> AccessFileName can accept more than one filename only in Apache 1.3 and later<P>
+><STRONG>Compatibility:</STRONG></A> AccessFileName can accept more than
+one filename only in Apache 1.3 and later<P>
When returning a document to the client the server looks for the first existing
access control file from this list of names in every directory of the path to
AllowOverride None<BR>
</Directory></CODE></BLOCKQUOTE><P><HR>
-<H2><A name="addmodule">AddModule directive</A></H2>
+<H2><A NAME="addmodule">AddModule directive</A></H2>
<!--%plaintext <?INDEX {\tt AddModule} directive> -->
<A
HREF="directive-dict.html#Syntax"
<A
HREF="directive-dict.html#Compatibility"
REL="Help"
-><STRONG>Compatibility:</STRONG></A> AddModule is only available in Apache 1.2 and later<P>
+><STRONG>Compatibility:</STRONG></A> AddModule is only available in
+Apache 1.2 and later<P>
The server can have modules compiled in which are not actively in use.
This directive can be used to enable the use of those modules. The
be cleared with the <A HREF="#clearmodulelist">ClearModuleList</A>
directive.<P><HR>
-<H2><A name="allowoverride">AllowOverride directive</A></H2>
+<H2><A NAME="allowoverride">AllowOverride directive</A></H2>
<!--%plaintext <?INDEX {\tt AllowOverride} directive> -->
<A
HREF="directive-dict.html#Syntax"
<A HREF="mod_include.html#xbithack">XBitHack</A>).
</DL><P><HR>
-<H2><A name="authname">AuthName directive</A></H2>
+<H2><A NAME="authname">AuthName directive</A></H2>
<!--%plaintext <?INDEX {\tt AuthName} directive> -->
<A
HREF="directive-dict.html#Syntax"
<A HREF="mod_auth.html#authuserfile">AuthUserFile</A> and
<A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> to work.<P><HR>
-<H2><A name="authtype">AuthType directive</A></H2>
+<H2><A NAME="authtype">AuthType directive</A></H2>
<!--%plaintext <?INDEX {\tt AuthType} directive> -->
<A
HREF="directive-dict.html#Syntax"
<A HREF="mod_auth.html#authuserfile">AuthUserFile</A> and
<A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> to work.<P><HR>
-<H2><A name="bindaddress">BindAddress directive</A></H2>
+<H2><A NAME="bindaddress">BindAddress directive</A></H2>
<!--%plaintext <?INDEX {\tt BindAddress} directive> -->
<A
HREF="directive-dict.html#Syntax"
<HR>
-<H2><A name="bs2000authfile">BS2000AuthFile directive</A></H2>
+<H2><A NAME="bs2000authfile">BS2000AuthFile directive</A></H2>
<!--%plaintext <?INDEX {\tt BS2000AuthFile} directive> -->
<A
HREF="directive-dict.html#Syntax"
<A
HREF="directive-dict.html#Compatibility"
REL="Help"
-><STRONG>Compatibility:</STRONG></A> BS2000AuthFile is only available for BS2000 machines, as of Apache 1.3 and later.<P>
+><STRONG>Compatibility:</STRONG></A> BS2000AuthFile is only available for
+BS2000 machines, as of Apache 1.3 and later.<P>
The <CODE>BS2000AuthFile</CODE> directive is available for BS2000 hosts
only. It must be used to define the password file which is used to
<HR>
-<H2><A name="clearmodulelist">ClearModuleList directive</A></H2>
+<H2><A NAME="clearmodulelist">ClearModuleList directive</A></H2>
<!--%plaintext <?INDEX {\tt ClearModuleList} directive> -->
<A
HREF="directive-dict.html#Syntax"
<A
HREF="directive-dict.html#Compatibility"
REL="Help"
-><STRONG>Compatibility:</STRONG></A> ClearModuleList is only available in Apache 1.2 and later<P>
+><STRONG>Compatibility:</STRONG></A> ClearModuleList is only available in
+Apache 1.2 and later<P>
The server comes with a built-in list of active modules. This
directive clears the list. It is assumed that the list will then be
re-populated using the <A HREF="#addmodule">AddModule</A> directive.<P><HR>
-<H2><A name="contentdigest">ContentDigest directive</A></H2>
+<H2><A NAME="contentdigest">ContentDigest directive</A></H2>
<!--%plaintext <?INDEX {\tt ContentDigest} directive> -->
<A
HREF="directive-dict.html#Syntax"
<A
HREF="directive-dict.html#Context"
REL="Help"
-><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess<BR>
+><STRONG>Context:</STRONG></A> server config, virtual host, directory,
+.htaccess<BR>
<A
HREF="directive-dict.html#Override"
REL="Help"
<A
HREF="directive-dict.html#Compatibility"
REL="Help"
-><STRONG>Compatibility:</STRONG></A> ContentDigest is only available in Apache 1.1 and later<P>
+><STRONG>Compatibility:</STRONG></A> ContentDigest is only available in
+Apache 1.1 and later<P>
This directive enables the generation of <CODE>Content-MD5</CODE> headers
as defined in RFC1864 respectively RFC2068.<P>
<HR>
-<H2><A name="coredumpdirectory">CoreDumpDirectory directive</A></H2>
+<H2><A NAME="coredumpdirectory">CoreDumpDirectory directive</A></H2>
<!--%plaintext <?INDEX {\tt CoreDumpDirectory} directive> -->
<A
HREF="directive-dict.html#Syntax"
want a core dump for debugging, you can use this directive to place
it in a different location.<P><HR>
-<H2><A name="defaulttype">DefaultType directive</A></H2>
+<H2><A NAME="defaulttype">DefaultType directive</A></H2>
<!--%plaintext <?INDEX {\tt DefaultType} directive> -->
<A
HREF="directive-dict.html#Syntax"
<A
HREF="directive-dict.html#Context"
REL="Help"
-><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess<BR>
+><STRONG>Context:</STRONG></A> server config, virtual host, directory,
+.htaccess<BR>
<A
HREF="directive-dict.html#Override"
REL="Help"
would be appropriate for a directory which contained many gif images
with filenames missing the .gif extension.<P><HR>
-<H2><A name="directory"><Directory> directive</A></H2>
+<H2><A NAME="directory"><Directory> directive</A></H2>
<!--%plaintext <?INDEX {\tt Directory} section directive> -->
<A
HREF="directive-dict.html#Syntax"
REL="Help"
-><STRONG>Syntax:</STRONG></A> <Directory <EM>directory</EM>> ... </Directory> <BR>
+><STRONG>Syntax:</STRONG></A> <Directory <EM>directory</EM>>
+ ... </Directory> <BR>
<A
HREF="directive-dict.html#Context"
REL="Help"
<HR>
-<H2><A name="directorymatch"><DirectoryMatch></A></H2>
+<H2><A NAME="directorymatch"><DirectoryMatch></A></H2>
<A
HREF="directive-dict.html#Syntax"
REL="Help"
-><STRONG>Syntax:</STRONG></A> <DirectoryMatch <EM>regex</EM>> ... </DirectoryMatch> <BR>
+><STRONG>Syntax:</STRONG></A> <DirectoryMatch <EM>regex</EM>>
+ ... </DirectoryMatch> <BR>
<A
HREF="directive-dict.html#Context"
REL="Help"
REL="Help"
><STRONG>Compatibility:</STRONG></A> Available in Apache 1.3 and later
-<P><DirectoryMatch> and </DirectoryMatch> are used to enclose a group of
+<P><DirectoryMatch> and </DirectoryMatch> are used to enclose a
+group of
directives which will apply only to the named directory and sub-directories
of that directory, the same as <A
HREF="#directory"><Directory></A>. However, it takes as an
<P><HR>
-<H2><A name="errordocument">ErrorDocument directive</A></H2>
+<H2><A NAME="errordocument">ErrorDocument directive</A></H2>
<!--%plaintext <?INDEX {\tt ErrorDocument} directive> -->
<A
HREF="directive-dict.html#Syntax"
<A
HREF="directive-dict.html#Context"
REL="Help"
-><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess<BR>
+><STRONG>Context:</STRONG></A> server config, virtual host, directory,
+.htaccess<BR>
<A
HREF="directive-dict.html#Status"
REL="Help"
<P>See Also: <A HREF="../custom-error.html">documentation of customizable
responses.</A><P><HR>
-<H2><A name="errorlog">ErrorLog directive</A></H2>
+<H2><A NAME="errorlog">ErrorLog directive</A></H2>
<!--%plaintext <?INDEX {\tt ErrorLog} directive> -->
<A
HREF="directive-dict.html#Syntax"
REL="Help"
-><STRONG>Syntax:</STRONG></A> ErrorLog <EM>filename</EM>|<CODE>syslog</CODE><BR>
+><STRONG>Syntax:</STRONG></A> ErrorLog <EM>filename</EM>|<CODE>syslog</CODE>
+<BR>
<A
HREF="directive-dict.html#Default"
REL="Help"
if the system supports it.
<P>
-SECURITY: See the <A HREF="../misc/security_tips.html#serverroot">security tips</A>
+SECURITY: See the
+<A HREF="../misc/security_tips.html#serverroot">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="#loglevel">LogLevel</A>
<P><HR>
-<H2><A name="files"><Files> directive</A></H2>
+<H2><A NAME="files"><Files> directive</A></H2>
<A
HREF="directive-dict.html#Syntax"
REL="Help"
<HR>
-<H2><A name="filesmatch"><FilesMatch></A></H2>
+<H2><A NAME="filesmatch"><FilesMatch></A></H2>
<A
HREF="directive-dict.html#Syntax"
REL="Help"
<HR>
-<H2><A name="group">Group directive</A></H2>
+<H2><A NAME="group">Group directive</A></H2>
<!--%plaintext <?INDEX {\tt Group} directive> -->
<A
HREF="directive-dict.html#Syntax"
SECURITY: See <A HREF="#user">User</A> for a discussion of the security
considerations.<P><HR>
-<H2><A name="hostnamelookups">HostNameLookups directive</A></H2>
+<H2><A NAME="hostnamelookups">HostNameLookups directive</A></H2>
<!--%plaintext <?INDEX {\tt HostNameLookups} directive> -->
<A
HREF="directive-dict.html#Syntax"
<A
HREF="directive-dict.html#Context"
REL="Help"
-><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess<BR>
+><STRONG>Context:</STRONG></A> server config, virtual host, directory,
+.htaccess<BR>
<A
HREF="directive-dict.html#Status"
REL="Help"
<A
HREF="directive-dict.html#Compatibility"
REL="Help"
-><STRONG>Compatibility:</STRONG></A> <CODE>double</CODE> available only in Apache
+><STRONG>Compatibility:</STRONG></A> <CODE>double</CODE> available only in
+Apache
1.3 and above.<BR>
<A
HREF="directive-dict.html#Compatibility"
REL="Help"
-><STRONG>Compatibility:</STRONG></A> Default was <CODE>on</CODE> prior to Apache
-1.3.<P>
+><STRONG>Compatibility:</STRONG></A> Default was <CODE>on</CODE> prior to
This directive enables DNS lookups so that host names can be logged (and
passed to CGIs/SSIs in <CODE>REMOTE_HOST</CODE>).
provided in the <EM>/support</EM> directory, can be used to look up host names
from logged IP addresses offline.<P><HR>
-<H2><A name="identitycheck">IdentityCheck directive</A></H2>
+<H2><A NAME="identitycheck">IdentityCheck directive</A></H2>
<!--%plaintext <?INDEX {\tt IdentityCheck} directive> -->
<A
HREF="directive-dict.html#Syntax"
<A
HREF="directive-dict.html#Syntax"
REL="Help"
-><STRONG>Syntax:</STRONG></A> <IfModule [!]<EM>module-name</EM>> <EM>...</EM>
+><STRONG>Syntax:</STRONG></A> <IfModule [!]<EM>module-name</EM>>
+ <EM>...</EM>
</IfModule><BR>
<A
HREF="directive-dict.html#Default"
<P> <HR>
-<H2><A name="include">Include directive</A></H2>
+<H2><A NAME="include">Include directive</A></H2>
<STRONG>Syntax: (Apache 1.2)</STRONG> Include <EM>filename</EM><BR>
<A
HREF="directive-dict.html#Context"
<A
HREF="directive-dict.html#Compatibility"
REL="Help"
-><STRONG>Compatibility:</STRONG></A> Include is only available in Apache 1.3 and later.
+><STRONG>Compatibility:</STRONG></A> Include is only available in Apache 1.3
+and later.
<P>
-This directive allows inclusion of other configuration files from within the server configuration files.
+This directive allows inclusion of other configuration files from within the
+server configuration files.
<P> <HR>
-<H2><A name="keepalive">KeepAlive directive</A></H2>
+<H2><A NAME="keepalive">KeepAlive directive</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>
persistent connections, "Off" to disable. See also the <A
HREF="#maxkeepaliverequests">MaxKeepAliveRequests</A> directive.</P><HR>
-<H2><A name="keepalivetimeout">KeepAliveTimeout directive</A></H2>
+<H2><A NAME="keepalivetimeout">KeepAliveTimeout directive</A></H2>
<A
HREF="directive-dict.html#Syntax"
REL="Help"
<A
HREF="directive-dict.html#Compatibility"
REL="Help"
-><STRONG>Compatibility:</STRONG></A> KeepAliveTimeout is only available in Apache
-1.1 and later.<P>
+><STRONG>Compatibility:</STRONG></A> 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
applies.
<HR>
-<H2><A name="limit"><Limit> directive</A></H2>
+<H2><A NAME="limit"><Limit> directive</A></H2>
<!--%plaintext <?INDEX {\tt Limit} section directive> -->
<A
HREF="directive-dict.html#Syntax"
<STRONG>If you wish to limit all methods, do not include any
<Limit> directive at all.</STRONG> <P><HR>
-<H2><A name="listen">Listen directive</A></H2>
+<H2><A NAME="listen">Listen directive</A></H2>
<A
HREF="directive-dict.html#Syntax"
REL="Help"
<STRONG>See Also:</STRONG>
<A HREF="../bind.html">Setting which addresses and ports Apache uses</A><BR>
<STRONG>See Also:</STRONG>
-<A HREF="http//www.apache.org/info/known_bugs.html#listenbug">Known Bugs</A></P>
+<A HREF="http://www.apache.org/info/known_bugs.html#listenbug">Known Bugs</A>
+</P>
<HR>
<H2><A NAME="listenbacklog">ListenBacklog directive</A></H2>
to increase this when under a TCP SYN flood attack. See
the backlog parameter to the <CODE>listen(2)</CODE> system call.</P><HR>
-<H2><A name="location"><Location> directive</A></H2>
+<H2><A NAME="location"><Location> directive</A></H2>
<A
HREF="directive-dict.html#Syntax"
<Directory> sections and <CODE>.htaccess</CODE> files are
read, and after the <Files> sections.</P>
-<p>Note that URLs do not have to line up with the filesystem at all,
+<P>Note that URLs do not have to line up with the filesystem at all,
it should be emphasized that <Location> operates completely outside
the filesystem.
-<p>For all origin (non-proxy) requests, the URL to be matched is
-of the form <code>/path/</code>, and you should not include any
-<code>http://servername</code> prefix. For proxy requests, the URL
-to be matched is of the form <code>scheme://servername/path</code>,
+<P>For all origin (non-proxy) requests, the URL to be matched is
+of the form <CODE>/path/</CODE>, and you should not include any
+<CODE>http://servername</CODE> prefix. For proxy requests, the URL
+to be matched is of the form <CODE>scheme://servername/path</CODE>,
and you must include the prefix.
-<p>The URL may use wildcards In a wild-card string, `?' matches any
+<P>The URL may use wildcards In a wild-card string, `?' matches any
single character, and `*' matches any sequences of characters.
<P><STRONG>Apache 1.2 and above:</STRONG>
"/special/data". In Apache 1.3 and above, a new directive
<A HREF="#locationmatch"><LocationMatch></A> exists which
behaves identical to the regex version of
-<code><Location></code>.
+<CODE><Location></CODE>.
<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
+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>
</Location>
</PRE>
-<p><strong>Apache 1.3 and above note about / (slash)</strong>: The slash character has special
+<P><STRONG>Apache 1.3 and above note about / (slash)</STRONG>: The slash
+character has special
meaning depending on where in a URL it appears. People may be used
to its behaviour in the filesystem where multiple adjacent slashes are
-frequently collapsed to a single slash (i.e. <code>/home///foo</code>
-is the same as <code>/home/foo</code>). In URL-space this is not
-necessarily true. The <code><LocationMatch></code> directive
-and the regex version of <code><Location></code> require you
+frequently collapsed to a single slash (i.e. <CODE>/home///foo</CODE>
+is the same as <CODE>/home/foo</CODE>). In URL-space this is not
+necessarily true. The <CODE><LocationMatch></CODE> directive
+and the regex version of <CODE><Location></CODE> require you
to explicitly specify multiple slashes if that is your intention.
-For example, <code><LocationMatch ^/abc></code> would match the
-request URL <code>/abc</code> but not the request URL <code>//abc</code>.
-The (non-regex) <code><Location></code> directive behaves
+For example, <CODE><LocationMatch ^/abc></CODE> would match the
+request URL <CODE>/abc</CODE> but not the request URL <CODE>//abc</CODE>.
+The (non-regex) <CODE><Location></CODE> directive behaves
similarly when used for proxy requests. But when (non-regex)
-<code><Location></code> is used for non-proxy requests it will
+<CODE><Location></CODE> is used for non-proxy requests it will
implicitly match multiple slashes with a single slash. For example,
-if you specify <code><Location /abc/def></code> and the request
-is to <code>/abc//def</code> then it will match.
+if you specify <CODE><Location /abc/def></CODE> and the request
+is to <CODE>/abc//def</CODE> then it will match.
<P>
<STRONG>See also</STRONG>: <A HREF="../sections.html">How Directory,
<HR>
-<H2><A name="locationmatch"><LocationMatch></A></H2>
+<H2><A NAME="locationmatch"><LocationMatch></A></H2>
<A
HREF="directive-dict.html#Syntax"
<A
HREF="directive-dict.html#Compatibility"
REL="Help"
-><STRONG>Compatibility:</STRONG></A> LogLevel is only available in 1.3 or later.
+><STRONG>Compatibility:</STRONG></A> LogLevel is only available in 1.3 or
+later.
<P>LogLevel adjusts the verbosity of the messages recorded in the
error logs (see <A HREF="#errorlog">ErrorLog</A> directive).
<TR><TD><TD>"httpd: caught SIGBUS, attempting to dump core in ..."
<TR><TD><CODE>info</CODE>
<TD>Informational.
- <TR><TD><TD>"Server seems busy, (you may need to increase StartServers, or Min/MaxSpareServers)..."
+ <TR><TD><TD>"Server seems busy, (you may need to increase StartServers, or
+ Min/MaxSpareServers)..."
<TR><TD><CODE>debug</CODE>
<TD>Debug-level messages
<TR><TD><TD>"Opening config file ..."
Using a level of at least <CODE>crit</CODE> is recommended.
<P><HR>
-<H2><A name="maxclients">MaxClients directive</A></H2>
+<H2><A NAME="maxclients">MaxClients directive</A></H2>
<!--%plaintext <?INDEX {\tt MaxClients} directive> -->
<A
HREF="directive-dict.html#Syntax"
processes will be created. To configure more than 256 clients, you must
edit the HARD_SERVER_LIMIT entry in httpd.h and recompile.<P><HR>
-<H2><A name="maxkeepaliverequests">MaxKeepAliveRequests directive</A></H2>
+<H2><A NAME="maxkeepaliverequests">MaxKeepAliveRequests directive</A></H2>
<A
HREF="directive-dict.html#Syntax"
REL="Help"
allowed. We recommend that this setting be kept to a high value for
maximum server performance.</P><HR>
-<H2><A name="maxrequestsperchild">MaxRequestsPerChild directive</A></H2>
+<H2><A NAME="maxrequestsperchild">MaxRequestsPerChild directive</A></H2>
<!--%plaintext <?INDEX {\tt MaxRequestsPerChild} directive> -->
<A
HREF="directive-dict.html#Syntax"
number of processes when the server load reduces.
</UL><P><HR>
-<H2><A name="maxspareservers">MaxSpareServers directive</A></H2>
+<H2><A NAME="maxspareservers">MaxSpareServers directive</A></H2>
<!--%plaintext <?INDEX {\tt MaxSpareServers} directive> -->
<A
HREF="directive-dict.html#Syntax"
See also <A HREF="#minspareservers">MinSpareServers</A> and
<A HREF="#startservers">StartServers</A>.<P><HR>
-<H2><A name="minspareservers">MinSpareServers directive</A></H2>
+<H2><A NAME="minspareservers">MinSpareServers directive</A></H2>
<!--%plaintext <?INDEX {\tt MinSpareServers} directive> -->
<A
HREF="directive-dict.html#Syntax"
See also <A HREF="#maxspareservers">MaxSpareServers</A> and
<A HREF="#startservers">StartServers</A>.<P><HR>
-<H2><A name="namevirtualhost">NameVirtualHost directive</A></H2>
+<H2><A NAME="namevirtualhost">NameVirtualHost directive</A></H2>
<!--%plaintext <?INDEX {\tt NameVirtualHost} directive> -->
<A
HREF="directive-dict.html#Syntax"
<A
HREF="directive-dict.html#Compatibility"
REL="Help"
-><STRONG>Compatibility:</STRONG></A> NameVirtualHost is only available in Apache 1.3 and later<P>
+><STRONG>Compatibility:</STRONG></A> NameVirtualHost is only available in
+Apache 1.3 and later<P>
The NameVirtualHost directive is a required directive if you want to configure
<A HREF="../vhosts/index.html">name-based virtual hosts</A>.<P>
name-based virtual host names resolve. If you have multiple name-based
hosts on multiple addresses, repeat the directive for each address.<P>
-Note: the "main server" and any _default_ servers will <b>never</b>
+Note: the "main server" and any _default_ servers will <STRONG>never</STRONG>
be served for a request to a NameVirtualHost IP Address (unless for some
reason you specify NameVirtualHost but then don't define any VirtualHosts
-for that address).<p>
+for that address).<P>
Optionally you can specify a port number on which the name-based
virtual hosts should be used, e.g.
<STRONG>See also:</STRONG>
<A HREF="../vhosts/index.html">Apache Virtual Host documentation</A>
-<H2><A name="options">Options directive</A></H2>
+<H2><A NAME="options">Options directive</A></H2>
<!--%plaintext <?INDEX {\tt Options} directive> -->
<A
HREF="directive-dict.html#Syntax"
<A
HREF="directive-dict.html#Context"
REL="Help"
-><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess<BR>
+><STRONG>Context:</STRONG></A> server config, virtual host, directory,
+.htaccess<BR>
<A
HREF="directive-dict.html#Override"
REL="Help"
<DD>
<!--%plaintext <?INDEX {\tt FollowSymLinks} option> -->
The server will follow symbolic links in this directory.
-<STRONG>Note</STRONG>: even though the server follows the symlink it does <EM>not</EM>
+<STRONG>Note</STRONG>: even though the server follows the symlink it
+does <EM>not</EM>
change the pathname used to match against <CODE><Directory></CODE>
sections.
<DT>Includes
then the options <CODE>FollowSymLinks</CODE> and <CODE>Includes</CODE>
are set for the /web/docs/spec directory.<P>
-<STRONG>Note:</STRONG> Using <CODE>-IncludesNOEXEC</CODE> or <CODE>-Includes</CODE>
+<STRONG>Note:</STRONG> Using <CODE>-IncludesNOEXEC</CODE> or
+<CODE>-Includes</CODE>
disables server-side includes completely regardless of the previous setting.<P>
The default in the absence of any other settings is <CODE>All</CODE>.<P>
<HR>
-<H2><A name="pidfile">PidFile directive</A></H2>
+<H2><A NAME="pidfile">PidFile directive</A></H2>
<!--%plaintext <?INDEX {\tt PidFile} directive> -->
<A
HREF="directive-dict.html#Syntax"
<P><HR>
-<H2><A name="port">Port directive</A></H2>
+<H2><A NAME="port">Port directive</A></H2>
<!--%plaintext <?INDEX {\tt Port} directive> -->
<A
HREF="directive-dict.html#Syntax"
REL="Help"
><STRONG>Status:</STRONG></A> core<P>
-<EM>Number</EM> is a number from 0 to 65535; some port numbers (especially below
+<EM>Number</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>
root whilst handling connections, your site may be open to a major security
attack.<P><HR>
-<H2><A name="require">require directive</A></H2>
+<H2><A NAME="require">require directive</A></H2>
<!--%plaintext <?INDEX {\tt require} directive> -->
<A
HREF="directive-dict.html#Syntax"
<A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> (to define users and
groups) in order to work correctly.<P><HR>
-<H2><A name="resourceconfig">ResourceConfig directive</A></H2>
+<H2><A NAME="resourceconfig">ResourceConfig directive</A></H2>
<!--%plaintext <?INDEX {\tt ResourceConfig} directive> -->
<A
HREF="directive-dict.html#Syntax"
See also <A HREF="#accessconfig">AccessConfig</A>.<P><HR>
-<H2><A
name="rlimit">RLimitCPU</A> <A NAME="rlimitcpu">directive</A></H2>
+<H2><A
NAME="rlimit">RLimitCPU</A> <A NAME="rlimitcpu">directive</A></H2>
<!--%plaintext <?INDEX {\tt RLimitCPU} directive> -->
<A
HREF="directive-dict.html#Syntax"
REL="Help"
-><STRONG>Syntax:</STRONG></A> RLimitCPU <EM># or 'max'</EM> <EM>[# or 'max']</EM><BR>
+><STRONG>Syntax:</STRONG></A> RLimitCPU <EM># or 'max'</EM>
+ <EM>[# or 'max']</EM>
+<BR>
<A
HREF="directive-dict.html#Default"
REL="Help"
-><STRONG>Default:</STRONG></A> <EM>Unset; uses operating system defaults</EM><BR>
+><STRONG>Default:</STRONG></A> <EM>Unset; uses operating system defaults</EM>
+<BR>
<A
HREF="directive-dict.html#Context"
REL="Help"
<A
HREF="directive-dict.html#Compatibility"
REL="Help"
-><STRONG>Compatibility:</STRONG></A> RLimitCPU is only available in Apache 1.2 and later<P>
+><STRONG>Compatibility:</STRONG></A> 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>
+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>
+See also <A HREF="#rlimitmem">RLimitMEM</A> or
+<A HREF="#rlimitnproc">RLimitNPROC</A>.<P><HR>
-<H2><A name="rlimitmem">RLimitMEM directive</A></H2>
+<H2><A NAME="rlimitmem">RLimitMEM directive</A></H2>
<!--%plaintext <?INDEX {\tt RLimitMEM} directive> -->
<A
HREF="directive-dict.html#Syntax"
REL="Help"
-><STRONG>Syntax:</STRONG></A> RLimitMEM <EM># or 'max'</EM> <EM>[# or 'max']</EM><BR>
+><STRONG>Syntax:</STRONG></A> RLimitMEM <EM># or 'max'</EM>
+ <EM>[# or 'max']</EM><BR>
<A
HREF="directive-dict.html#Default"
REL="Help"
-><STRONG>Default:</STRONG></A> <EM>Unset; uses operating system defaults</EM><BR>
+><STRONG>Default:</STRONG></A> <EM>Unset; uses operating system defaults</EM>
+<BR>
<A
HREF="directive-dict.html#Context"
REL="Help"
<A
HREF="directive-dict.html#Compatibility"
REL="Help"
-><STRONG>Compatibility:</STRONG></A> RLimitMEM is only available in Apache 1.2 and later<P>
+><STRONG>Compatibility:</STRONG></A> 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>
+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
+s
erver 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>
+See also <A HREF="#rlimitcpu">RLimitCPU</A> or
+<A HREF="#rlimitnproc">RLimitNPROC</A>.<P><HR>
-<H2><A name="rlimitnproc">RLimitNPROC directive</A></H2>
+<H2><A NAME="rlimitnproc">RLimitNPROC directive</A></H2>
<!--%plaintext <?INDEX {\tt RLimitNPROC} directive> -->
<A
HREF="directive-dict.html#Syntax"
REL="Help"
-><STRONG>Syntax:</STRONG></A> RLimitNPROC <EM># or 'max'</EM> <EM>[# or 'max']</EM><BR>
+><STRONG>Syntax:</STRONG></A> RLimitNPROC <EM># or 'max'</EM>
+ <EM>[# or 'max']</EM><BR>
<A
HREF="directive-dict.html#Default"
REL="Help"
-><STRONG>Default:</STRONG></A> <EM>Unset; uses operating system defaults</EM><BR>
+><STRONG>Default:</STRONG></A> <EM>Unset; uses operating system defaults</EM>
+<BR>
<A
HREF="directive-dict.html#Context"
REL="Help"
<A
HREF="directive-dict.html#Compatibility"
REL="Help"
-><STRONG>Compatibility:</STRONG></A> RLimitNPROC is only available in Apache 1.2 and later<P>
+><STRONG>Compatibility:</STRONG></A> 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>
+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 <STRONG>not</STRONG> running under userids other than the
+Note: If CGI processes are <STRONG>not</STRONG> 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
<STRONG><EM>cannot fork</EM></STRONG> messages in the error_log.<P>
-See also <A HREF="#rlimitmem">RLimitMEM</A> or <A HREF="#rlimitcpu">RLimitCPU</A>.
+See also <A HREF="#rlimitmem">RLimitMEM</A> or
+<A HREF="#rlimitcpu">RLimitCPU</A>.
<P><HR>
-<H2><A name="satisfy">Satisfy directive</A></H2>
+<H2><A NAME="satisfy">Satisfy directive</A></H2>
<!--%plaintext <?INDEX {\tt Satisfy} directive> -->
<A
HREF="directive-dict.html#Syntax"
<A
HREF="directive-dict.html#Compatibility"
REL="Help"
-><STRONG>Compatibility:</STRONG></A> Satisfy is only available in Apache 1.2 and later<P>
+><STRONG>Compatibility:</STRONG></A> 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
<P><HR>
-<H2><A name="scoreboardfile">ScoreBoardFile directive</A></H2>
+<H2><A NAME="scoreboardfile">ScoreBoardFile directive</A></H2>
<!--%plaintext <?INDEX {\tt ScoreBoardFile} directive> -->
<A
HREF="directive-dict.html#Syntax"
<A
HREF="directive-dict.html#Default"
REL="Help"
-><STRONG>Default:</STRONG></A> <CODE>ScoreBoardFile logs/apache_status</CODE><BR>
+><STRONG>Default:</STRONG></A> <CODE>ScoreBoardFile logs/apache_status</CODE>
+<BR>
<A
HREF="directive-dict.html#Context"
REL="Help"
<P><HR>
-<H2><A name="sendbuffersize">SendBufferSize directive</A></H2>
+<H2><A NAME="sendbuffersize">SendBufferSize directive</A></H2>
<!--%plaintext <?INDEX {\tt SendBufferSize} directive> -->
<A
HREF="directive-dict.html#Syntax"
fast pipes)
<P><HR>
-<H2><A name="serveradmin">ServerAdmin directive</A></H2>
+<H2><A NAME="serveradmin">ServerAdmin directive</A></H2>
<!--%plaintext <?INDEX {\tt ServerAdmin} directive> -->
<A
HREF="directive-dict.html#Syntax"
<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>
-<H2><A name="serveralias">ServerAlias directive</A></H2>
+<H2><A NAME="serveralias">ServerAlias directive</A></H2>
<A
HREF="directive-dict.html#Syntax"
<HR>
-<H2><A name="servername">ServerName directive</A></H2>
+<H2><A NAME="servername">ServerName directive</A></H2>
<!--%plaintext <?INDEX {\tt ServerName} directive> -->
<A
HREF="directive-dict.html#Syntax"
REL="Help"
-><STRONG>Syntax:</STRONG></A> ServerName <EM>fully-qualified domain name</EM><BR>
+><STRONG>Syntax:</STRONG></A> ServerName <EM>fully-qualified domain name</EM>
+<BR>
<A
HREF="directive-dict.html#Context"
REL="Help"
</P>
<HR>
-<H2><A name="serverpath">ServerPath directive</A></H2>
+<H2><A NAME="serverpath">ServerPath directive</A></H2>
<A
HREF="directive-dict.html#Syntax"
<HR>
-<H2><A name="serverroot">ServerRoot directive</A></H2>
+<H2><A NAME="serverroot">ServerRoot directive</A></H2>
<!--%plaintext <?INDEX {\tt ServerRoot} directive> -->
<A
HREF="directive-dict.html#Syntax"
<A
HREF="directive-dict.html#Context"
REL="Help"
-><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess<BR>
+><STRONG>Context:</STRONG></A> server config, virtual host, directory,
+.htaccess<BR>
<A
HREF="directive-dict.html#Status"
REL="Help"
<A
HREF="directive-dict.html#Compatibility"
REL="Help"
-><STRONG>Compatibility:</STRONG></A> ServerSignature is only available in Apache
+><STRONG>Compatibility:</STRONG></A> ServerSignature is only available in
+Apache
1.3 and later.<P>
The ServerSignature directive allows the configuration of a trailing
<HR>
-<H2><A name="servertokens">ServerTokens directive</A></H2>
+<H2><A NAME="servertokens">ServerTokens directive</A></H2>
<!--%plaintext <?INDEX {\tt ServerTokens} directive> -->
<A
HREF="directive-dict.html#Syntax"
</DD>
<DT><CODE>ServerTokens Full</CODE> (or not specified)
</DT>
- <DD>Server sends (e.g.): <SAMP>Server: Apache/1.3.0 (UNIX) PHP/3.0 MyMod/1.2</SAMP>
+ <DD>Server sends (e.g.): <SAMP>Server: Apache/1.3.0 (UNIX) PHP/3.0
+ MyMod/1.2</SAMP>
</DD>
</DL>
<P>
<HR>
-<H2><A name="servertype">ServerType directive</A></H2>
+<H2><A NAME="servertype">ServerType directive</A></H2>
<!--%plaintext <?INDEX {\tt ServerType} directive> -->
<A
HREF="directive-dict.html#Syntax"
subsequent connections. If you intend running Apache to serve a busy site,
standalone will probably be your only option.<P>
-<H2><A name="startservers">StartServers directive</A></H2>
+<H2><A NAME="startservers">StartServers directive</A></H2>
<!--%plaintext <?INDEX {\tt StartServers} directive> -->
<A
HREF="directive-dict.html#Syntax"
See also <A HREF="#minspareservers">MinSpareServers</A> and
<A HREF="#maxspareservers">MaxSpareServers</A>.<P><HR>
-<H2><A name="threadsperchild">ThreadsPerChild</A></H2>
+<H2><A NAME="threadsperchild">ThreadsPerChild</A></H2>
<A
HREF="directive-dict.html#Syntax"
REL="Help"
<HR>
-<H2><A name="timeout">TimeOut directive</A></H2>
+<H2><A NAME="timeout">TimeOut directive</A></H2>
<!--%plaintext <?INDEX {\tt TimeOut} directive> -->
<A
HREF="directive-dict.html#Syntax"
<P><HR>
-<H2><A name="usecanonicalname">UseCanonicalName directive</A></H2>
+<H2><A NAME="usecanonicalname">UseCanonicalName directive</A></H2>
<!--%plaintext <?INDEX {\tt UseCanonicalName} directive> -->
<A HREF="directive-dict.html#Syntax" REL="Help">
<STRONG>Syntax:</STRONG></A> UseCanonicalName <EM>on|off</EM><BR>
<A HREF="directive-dict.html#Default" REL="Help">
<STRONG>Default:</STRONG></A> <CODE>UseCanonicalName on</CODE><BR>
<A HREF="directive-dict.html#Context" REL="Help">
-<STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess<BR>
+<STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess
+<BR>
<A HREF="directive-dict.html#Override" REL="Help">
<STRONG>Override:</STRONG></A> AuthConfig<BR>
<A HREF="directive-dict.html#Compatibility" REL="Help">
-<STRONG>Compatibility:</STRONG></A> UseCanonicalName is only available in Apache 1.3 and later<P>
+<STRONG>Compatibility:</STRONG></A> UseCanonicalName is only available in
+Apache 1.3 and later<P>
In many situations Apache has to construct a <EM>self-referential</EM>
URL. That is, a URL which refers back to the same server.
<P><HR>
-<H2><A name="user">User directive</A></H2>
+<H2><A NAME="user">User directive</A></H2>
<!--%plaintext <?INDEX {\tt User} directive> -->
<A
HREF="directive-dict.html#Syntax"
<CODE>root</CODE> unless you know exactly what you are doing, and what the
dangers are.<P><HR>
-<H2><A name="virtualhost"><VirtualHost> directive</A></H2>
+<H2><A NAME="virtualhost"><VirtualHost> directive</A></H2>
<!--%plaintext <?INDEX {\tt VirtualHost} section directive> -->
<A
HREF="directive-dict.html#Syntax"
REL="Help"
-><STRONG>Syntax:</STRONG></A> <VirtualHost <EM>addr</EM>[:<EM>port</EM>] ...> ...
+><STRONG>Syntax:</STRONG></A> <VirtualHost <EM>addr</EM>[:<EM>port</EM>]
+ ...> ...
</VirtualHost> <BR>
<A
HREF="directive-dict.html#Context"
</VirtualHost>
</CODE></BLOCKQUOTE>
-Each VirtualHost must correspond to a different IP address, different port number or a
+Each VirtualHost must correspond to a different IP address, different port
+number 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,
projects / apache / commitdiff