core.html revision 7cc8575b89434b03a0b6e33047943f6562f50c55
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl BGCOLOR="#FFFFFF"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl TEXT="#000000"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl LINK="#0000FF"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl VLINK="#000080"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl ALINK="#FF0000"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--#include virtual="header.html" -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThese configuration parameters control the core Apache features, and are
25cf1a301a396c38e8adf52c15f537b80d2483f7jlalways available.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<LI><A HREF="#limitrequestfieldsize">LimitRequestFieldsize</A>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<LI><A HREF="#maxkeepaliverequests">MaxKeepAliveRequests</A>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<LI><A HREF="#maxrequestsperchild">MaxRequestsPerChild</A>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<LI><A HREF="#scriptinterpretersource">ScriptInterpreterSource</A>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="accessconfig">AccessConfig directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt AccessConfig} directive> -->
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah REL="Help"
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah><STRONG>Syntax:</STRONG></A> AccessConfig <EM>filename</EM><BR>
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah><STRONG>Default:</STRONG></A> <CODE>AccessConfig conf/access.conf</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Context:</STRONG></A> server config, virtual host<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe server will read this file for more directives after reading the
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<A HREF="#resourceconfig">ResourceConfig</A> file. <EM>Filename</EM> is
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThis feature can be disabled using:
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<BLOCKQUOTE><CODE>AccessConfig /dev/null</CODE></BLOCKQUOTE>
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuahHistorically, this file only contained
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah<A HREF="#directory"><Directory></A> sections; in fact it can now
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuahcontain any server directive allowed in the <EM>server config</EM> context.
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah<H2><A NAME="accessfilename">AccessFileName directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt AccessFileName} directive> -->
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah REL="Help"
febcc4a52c3ed7fe3a106da2c2ba52c56afd5111jimand><STRONG>Syntax:</STRONG></A> AccessFileName <EM>filename filename ...</EM><BR>
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah REL="Help"
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah><STRONG>Default:</STRONG></A> <CODE>AccessFileName .htaccess</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Context:</STRONG></A> server config, virtual host<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> AccessFileName can accept more than
25cf1a301a396c38e8adf52c15f537b80d2483f7jlone filename only in Apache 1.3 and later<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlWhen returning a document to the client the server looks for the first existing
25cf1a301a396c38e8adf52c15f537b80d2483f7jlaccess control file from this list of names in every directory of the path to
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthe document, if access control files are enabled for that directory.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlFor example:
25cf1a301a396c38e8adf52c15f537b80d2483f7jlbefore returning the document /usr/local/web/index.html, the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlserver will read /.acl, /usr/.acl, /usr/local/.acl and /usr/local/web/.acl
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfor directives, unless they have been disabled with
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<Directory /><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlAllowOverride None<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt AddModule} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> AddModule <EM>module module ...</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> AddModule is only available in
25cf1a301a396c38e8adf52c15f537b80d2483f7jlApache 1.2 and later<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe server can have modules compiled in which are not actively in use.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThis directive can be used to enable the use of those modules. The
25cf1a301a396c38e8adf52c15f537b80d2483f7jlserver comes with a pre-loaded list of active modules; this list can
25cf1a301a396c38e8adf52c15f537b80d2483f7jlbe cleared with the <A HREF="#clearmodulelist">ClearModuleList</A>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="allowoverride">AllowOverride directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt AllowOverride} directive> -->
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah REL="Help"
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah><STRONG>Syntax:</STRONG></A> AllowOverride <EM>override override ...</EM><BR>
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah HREF="directive-dict.html#Default"
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>AllowOverride All</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuahWhen the server finds an .htaccess file (as specified by
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah<A HREF="#accessfilename">AccessFileName</A>) it needs to know which
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuahdirectives declared in that file can override earlier access information.<P>
febcc4a52c3ed7fe3a106da2c2ba52c56afd5111jimand<EM>Override</EM> can be set to <CODE>None</CODE>, in which case the server
25cf1a301a396c38e8adf52c15f537b80d2483f7jlwill not read the file, <CODE>All</CODE> in which case the server will
25cf1a301a396c38e8adf52c15f537b80d2483f7jlallow all the directives, or one or more of the following:
febcc4a52c3ed7fe3a106da2c2ba52c56afd5111jimand<DT>AuthConfig
febcc4a52c3ed7fe3a106da2c2ba52c56afd5111jimand<!--%plaintext <?INDEX {\tt AuthConfig} override> -->
febcc4a52c3ed7fe3a106da2c2ba52c56afd5111jimandAllow use of the authorization directives
25cf1a301a396c38e8adf52c15f537b80d2483f7jl(<A HREF="mod_auth_dbm.html#authdbmgroupfile">AuthDBMGroupFile</A>,
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<A HREF="mod_auth_dbm.html#authdbmuserfile">AuthDBMUserFile</A>,
febcc4a52c3ed7fe3a106da2c2ba52c56afd5111jimand<A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A>,
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<A HREF="#authname">AuthName</A>, <A HREF="#authtype">AuthType</A>,
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<DT>FileInfo
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah<!--%plaintext <?INDEX {\tt FileInfo} override> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jlAllow use of the directives controlling document types
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<A HREF="mod_negotiation.html#languagepriority">LanguagePriority</A>, <EM>etc.</EM>).
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<DT>Indexes
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt Indexes} override> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jlAllow use of the directives controlling directory indexing
25cf1a301a396c38e8adf52c15f537b80d2483f7jl(<A HREF="mod_autoindex.html#adddescription">AddDescription</A>,
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<A HREF="mod_autoindex.html#addiconbyencoding">AddIconByEncoding</A>,
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah<A HREF="mod_autoindex.html#addiconbytype">AddIconByType</A>,
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<A HREF="mod_autoindex.html#fancyindexing">FancyIndexing</A>,
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<A HREF="mod_autoindex.html#indexoptions">IndexOptions</A>,
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<A HREF="mod_autoindex.html#readmename">ReadmeName</A>, <EM>etc.</EM>).
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah<!--%plaintext <?INDEX {\tt Limit} override> -->
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuahAllow use of the directives controlling host access (allow, deny and order).
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah<DT>Options
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah<!--%plaintext <?INDEX {\tt Options} override> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jlAllow use of the directives controlling specific directory features
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt AuthName} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> AuthName <EM>auth-domain</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah HREF="directive-dict.html#Override"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuahThis directive sets the name of the authorization realm for a directory.
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuahThis realm is given to the client so that the user knows which username and
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuahpassword to send. <SAMP>AuthName</SAMP> takes a single argument;
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuahif the realm name contains spaces, it must be enclosed in quotation marks.
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuahIt must be accompanied by <A HREF="#authtype">AuthType</A> and
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah<A HREF="#require">require</A> directives, and directives such as
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah<A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> to work.<P><HR>
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah<!--%plaintext <?INDEX {\tt AuthType} directive> -->
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah REL="Help"
febcc4a52c3ed7fe3a106da2c2ba52c56afd5111jimand><STRONG>Syntax:</STRONG></A> AuthType <EM>type</EM><BR>
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah REL="Help"
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah HREF="directive-dict.html#Override"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThis directive selects the type of user authentication for a directory.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlOnly <CODE>Basic</CODE> and <CODE>Digest</CODE> are currently implemented.
1e2e7a75ddb1eedcefa449ce98fd5862749b72eehuah<!--%plaintext <?INDEX {\tt Basic} authentication scheme> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jlIt must be accompanied by <A HREF="#authname">AuthName</A> and
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<A HREF="#require">require</A> directives, and directives such as
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> to work.<P><HR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt BindAddress} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> BindAddress <EM>saddr</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>BindAddress *</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jlA Unix® http server can either listen for connections to every
25cf1a301a396c38e8adf52c15f537b80d2483f7jlIP address of the server machine, or just one IP address of the server
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<LI>An IP address
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<LI>A fully-qualified Internet domain name
25cf1a301a396c38e8adf52c15f537b80d2483f7jlIf the value is *, then the server will listen for connections on
25cf1a301a396c38e8adf52c15f537b80d2483f7jlevery IP address, otherwise it will only listen on the IP address
25cf1a301a396c38e8adf52c15f537b80d2483f7jlspecified. <P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlOnly one <CODE>BindAddress</CODE> directive can be used. For more
25cf1a301a396c38e8adf52c15f537b80d2483f7jlcontrol over which address and ports Apache listens to, use the
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<CODE><A HREF="#listen">Listen</A></CODE> directive instead of
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<CODE>BindAddress</CODE> can be used as an alternative method for
25cf1a301a396c38e8adf52c15f537b80d2483f7jlsupporting <A HREF="/vhosts/index.html">virtual hosts</A> using
25cf1a301a396c38e8adf52c15f537b80d2483f7jlHREF="#virtualhost"><VirtualHost></A></CODE> sections.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<A HREF="/bind.html">Setting which addresses and ports Apache uses</A></P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="bs2000account">BS2000Account directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt BS2000Account} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> BS2000Account <EM>account</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> BS2000Account is only available for
25cf1a301a396c38e8adf52c15f537b80d2483f7jlBS2000 machines, as of Apache 1.3 and later.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe <CODE>BS2000Account</CODE> directive is available for BS2000 hosts
25cf1a301a396c38e8adf52c15f537b80d2483f7jlonly. It must be used to define the account number for the non-privileged
25cf1a301a396c38e8adf52c15f537b80d2483f7jlapache server user (which was configured using the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThis is required by the BS2000 POSIX subsystem (to change the underlying
25cf1a301a396c38e8adf52c15f537b80d2483f7jlBS2000 task environment by performing a sub-LOGON) to prevent CGI scripts
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfrom accessing resources of the privileged account which started the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlOnly one <CODE>BS2000Account</CODE> directive can be used. <P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="clearmodulelist">ClearModuleList directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt ClearModuleList} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> ClearModuleList is only available in
25cf1a301a396c38e8adf52c15f537b80d2483f7jlApache 1.2 and later<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe server comes with a built-in list of active modules. This
25cf1a301a396c38e8adf52c15f537b80d2483f7jldirective clears the list. It is assumed that the list will then be
25cf1a301a396c38e8adf52c15f537b80d2483f7jlre-populated using the <A HREF="#addmodule">AddModule</A> directive.<P><HR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="contentdigest">ContentDigest directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt ContentDigest} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> ContentDigest <EM>on|off</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>ContentDigest off</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Context:</STRONG></A> server config, virtual host, directory,
25cf1a301a396c38e8adf52c15f537b80d2483f7jl.htaccess<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Override"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> ContentDigest is only available in
25cf1a301a396c38e8adf52c15f537b80d2483f7jlApache 1.1 and later<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThis directive enables the generation of <CODE>Content-MD5</CODE> headers
25cf1a301a396c38e8adf52c15f537b80d2483f7jlas defined in RFC1864 respectively RFC2068.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlMD5 is an algorithm for computing a "message digest" (sometimes called
25cf1a301a396c38e8adf52c15f537b80d2483f7jl"fingerprint") of arbitrary-length data, with a high degree of confidence
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthat any alterations in the data will be reflected in alterations in the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlmessage digest.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe <CODE>Content-MD5</CODE> header provides an end-to-end message
25cf1a301a396c38e8adf52c15f537b80d2483f7jlintegrity check (MIC) of the entity-body. A proxy or client may check this
25cf1a301a396c38e8adf52c15f537b80d2483f7jlheader for detecting accidental modification of the entity-body
25cf1a301a396c38e8adf52c15f537b80d2483f7jlin transit.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlExample header:
25cf1a301a396c38e8adf52c15f537b80d2483f7jlNote that this can cause performance problems on your server
25cf1a301a396c38e8adf52c15f537b80d2483f7jlsince the message digest is computed on every request
25cf1a301a396c38e8adf52c15f537b80d2483f7jl(the values are not cached).<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<CODE>Content-MD5</CODE> is only sent for documents served by the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlcore, and not by any module. For example, SSI documents, output from
25cf1a301a396c38e8adf52c15f537b80d2483f7jlCGI scripts, and byte range responses do not have this header.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="coredumpdirectory">CoreDumpDirectory directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt CoreDumpDirectory} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> CoreDumpDirectory <EM>directory</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> the same location as ServerRoot<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThis controls the directory to which Apache attempts to switch before
25cf1a301a396c38e8adf52c15f537b80d2483f7jldumping core. The default is in the <A HREF="#serverroot">ServerRoot</A>
25cf1a301a396c38e8adf52c15f537b80d2483f7jldirectory, however since this should not be writable by the user
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthe server runs as, core dumps won't normally get written. If you
25cf1a301a396c38e8adf52c15f537b80d2483f7jlwant a core dump for debugging, you can use this directive to place
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt DefaultType} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> DefaultType <EM>MIME-type</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>DefaultType text/html</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Context:</STRONG></A> server config, virtual host, directory,
25cf1a301a396c38e8adf52c15f537b80d2483f7jl.htaccess<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Override"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThere will be times when the server is asked to provide a document
25cf1a301a396c38e8adf52c15f537b80d2483f7jlwhose type cannot be determined by its MIME types mappings.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe server must inform the client of the content-type of the document, so in
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthe event of an unknown type it uses the <CODE>DefaultType</CODE>. For
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<BLOCKQUOTE><CODE>DefaultType image/gif</CODE></BLOCKQUOTE>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlwould be appropriate for a directory which contained many gif images
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="directory"><Directory> directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt Directory} section directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> <Directory <EM>directory</EM>>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl ... </Directory> <BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Context:</STRONG></A> server config, virtual host<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<Directory> and </Directory> are used to enclose a group of
25cf1a301a396c38e8adf52c15f537b80d2483f7jldirectives which will apply only to the named directory and sub-directories
25cf1a301a396c38e8adf52c15f537b80d2483f7jlof that directory. Any directive which is allowed in a directory
25cf1a301a396c38e8adf52c15f537b80d2483f7jlcontext may be used. <EM>Directory</EM> is either the full path to a directory,
25cf1a301a396c38e8adf52c15f537b80d2483f7jlor a wild-card string. In a wild-card string, `?' matches any single character,
25cf1a301a396c38e8adf52c15f537b80d2483f7jland `*' matches any sequences of characters. As of Apache 1.3, you
25cf1a301a396c38e8adf52c15f537b80d2483f7jlmay also use `[]' character ranges like in the shell. Also as of Apache 1.3
25cf1a301a396c38e8adf52c15f537b80d2483f7jlnone of the wildcards match a `/' character, which more closely mimics the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlbehaviour of Unix shells.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl Options Indexes FollowSymLinks
25cf1a301a396c38e8adf52c15f537b80d2483f7jl </Directory>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlExtended regular expressions can also be used, with the addition of the
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <Directory ~ "^/www/.*/[0-9]{3}">
25cf1a301a396c38e8adf52c15f537b80d2483f7jlwould match directories in /www/ that consisted of three numbers.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>If multiple (non-regular expression) directory sections match the
25cf1a301a396c38e8adf52c15f537b80d2483f7jldirectory (or its parents) containing
25cf1a301a396c38e8adf52c15f537b80d2483f7jla document, then the directives are applied in the order of shortest match
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfirst, interspersed with the directives from the
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<A HREF="#accessfilename">.htaccess</A> files. For example, with
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<Directory /><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlAllowOverride None<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<Directory /home/*><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlAllowOverride FileInfo<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfor access to the document <CODE>/home/web/dir/doc.html</CODE> the
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<LI>Apply directive <CODE>AllowOverride None</CODE> (disabling
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<LI>Apply directive <CODE>AllowOverride FileInfo</CODE> (for directory
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<LI>Apply any FileInfo directives in <CODE>/home/web/.htaccess</CODE>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlRegular expression directory sections are handled slightly differently
25cf1a301a396c38e8adf52c15f537b80d2483f7jlby Apache 1.2 and 1.3. In Apache 1.2 they are interspersed with the normal
25cf1a301a396c38e8adf52c15f537b80d2483f7jldirectory sections and applied in the order they appear in the configuration
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfile. They are applied only once, and apply when the shortest match
25cf1a301a396c38e8adf52c15f537b80d2483f7jlpossible occurs. In Apache 1.3 regular expressions are not considered
25cf1a301a396c38e8adf52c15f537b80d2483f7jluntil after all of the normal sections have been applied. Then all of
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthe regular expressions are tested in the order they appeared in the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlconfiguration file. For example, with
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<Directory ~ abc$><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl... directives here ...<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl</Directory><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlSuppose that the filename being accessed is
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<CODE>/home/abc/public_html/abc/index.html</CODE>. The server
25cf1a301a396c38e8adf52c15f537b80d2483f7jlconsiders each of <CODE>/</CODE>, <CODE>/home</CODE>, <CODE>/home/abc</CODE>,
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<CODE>/home/abc/public_html</CODE>, and <CODE>/home/abc/public_html/abc</CODE>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlin that order. In Apache 1.2, when
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<CODE>/home/abc</CODE> is considered, the regular expression will match
25cf1a301a396c38e8adf52c15f537b80d2483f7jland be applied. In Apache 1.3 the regular expression isn't considered
25cf1a301a396c38e8adf52c15f537b80d2483f7jlat all at that point in the tree. It won't be considered until after
25cf1a301a396c38e8adf52c15f537b80d2483f7jlall normal <Directory>s and <CODE>.htaccess</CODE> files have
25cf1a301a396c38e8adf52c15f537b80d2483f7jlbeen applied. Then the regular expression will
25cf1a301a396c38e8adf52c15f537b80d2483f7jlmatch on <CODE>/home/abc/public_html/abc</CODE> and be applied.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlNote that the default Apache access for <Directory /> is
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<SAMP>Allow from All</SAMP>. This means that Apache will serve any file
25cf1a301a396c38e8adf52c15f537b80d2483f7jlmapped from an URL. It is recommended that you change this with a block
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <Directory />
25cf1a301a396c38e8adf52c15f537b80d2483f7jl Order Deny,Allow
25cf1a301a396c38e8adf52c15f537b80d2483f7jl Deny from All
25cf1a301a396c38e8adf52c15f537b80d2483f7jl </Directory>
25cf1a301a396c38e8adf52c15f537b80d2483f7jland then override this for directories you <EM>want</EM> accessible.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl>Security Tips</A>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlpage for more details.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe directory sections typically occur in the access.conf file, but they
25cf1a301a396c38e8adf52c15f537b80d2483f7jlmay appear in any configuration file. <Directory> directives cannot
25cf1a301a396c38e8adf52c15f537b80d2483f7jlnest, and cannot appear in a <A HREF="#limit"><Limit></A> or
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<STRONG>See also</STRONG>: <A HREF="/sections.html">How Directory,
25cf1a301a396c38e8adf52c15f537b80d2483f7jlLocation and Files sections work</A> for an explanation of how these
25cf1a301a396c38e8adf52c15f537b80d2483f7jldifferent sections are combined when a request is received
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="directorymatch"><DirectoryMatch></A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> <DirectoryMatch <EM>regex</EM>>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl ... </DirectoryMatch> <BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Context:</STRONG></A> server config, virtual host<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> Available in Apache 1.3 and later
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P><DirectoryMatch> and </DirectoryMatch> are used to enclose a
25cf1a301a396c38e8adf52c15f537b80d2483f7jldirectives which will apply only to the named directory and sub-directories
25cf1a301a396c38e8adf52c15f537b80d2483f7jlof that directory, the same as <A
25cf1a301a396c38e8adf52c15f537b80d2483f7jlHREF="#directory"><Directory></A>. However, it takes as an
25cf1a301a396c38e8adf52c15f537b80d2483f7jlargument a regular expression. For example:</P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <DirectoryMatch "^/www/.*/[0-9]{3}">
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>would match directories in /www/ that consisted of three numbers.</P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<A HREF="#directory"><Directory></A> for a description of how
25cf1a301a396c38e8adf52c15f537b80d2483f7jlregular expressions are mixed in with normal <Directory>s.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<STRONG>See also</STRONG>: <A HREF="/sections.html">How Directory,
25cf1a301a396c38e8adf52c15f537b80d2483f7jlLocation and Files sections work</A> for an explanation of how these
25cf1a301a396c38e8adf52c15f537b80d2483f7jldifferent sections are combined when a request is received
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="documentroot">DocumentRoot directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt DocumentRoot} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> DocumentRoot <EM>directory-filename</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Context:</STRONG></A> server config, virtual host<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThis directive sets the directory from which httpd will serve files.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlUnless matched by a directive like Alias, the server appends the path
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfrom the requested URL to the document root to make the path to the
25cf1a301a396c38e8adf52c15f537b80d2483f7jldocument. Example:
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<BLOCKQUOTE><CODE>DocumentRoot /usr/web</CODE></BLOCKQUOTE>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthen an access to <CODE>http://www.my.host.com/index.html</CODE> refers
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>There appears to be a bug in mod_dir which causes problems when the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlDocumentRoot has a trailing slash (<EM>i.e.</EM>, "DocumentRoot /usr/web/") so
25cf1a301a396c38e8adf52c15f537b80d2483f7jlplease avoid that.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="errordocument">ErrorDocument directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt ErrorDocument} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> ErrorDocument <EM>error-code document</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Context:</STRONG></A> server config, virtual host, directory,
25cf1a301a396c38e8adf52c15f537b80d2483f7jl.htaccess<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Override"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> The directory and .htaccess contexts
25cf1a301a396c38e8adf52c15f537b80d2483f7jlare only available in Apache 1.1 and later.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlIn the event of a problem or error, Apache can be configured to do
25cf1a301a396c38e8adf52c15f537b80d2483f7jlone of four things,
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<LI>output a simple hardcoded error message
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<LI>output a customized message
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<LI>redirect to an external URL to handle the problem/error
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>The first option is the default, while options 2-4 are configured
25cf1a301a396c38e8adf52c15f537b80d2483f7jlusing the <CODE>ErrorDocument</CODE> directive, which is followed by
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthe HTTP response code and a message or URL.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P><EM>Messages</EM> in this context begin with a single quote
25cf1a301a396c38e8adf52c15f537b80d2483f7jl(<CODE>"</CODE>), which does not form part of the message itself.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlApache will sometimes offer additional information regarding the
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>URLs can begin with a slash (/) for local URLs, or be a full
25cf1a301a396c38e8adf52c15f537b80d2483f7jlURL which the client can resolve. Examples:
25cf1a301a396c38e8adf52c15f537b80d2483f7jlErrorDocument 500 http://foo.example.com/cgi-bin/tester<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlErrorDocument 403 "Sorry can't allow you access today
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>Note that when you specify an <CODE>ErrorDocument</CODE> that
25cf1a301a396c38e8adf52c15f537b80d2483f7jlpoints to a remote URL (ie. anything with a method such as "http" in
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfront of it) Apache will send a redirect to the client to tell it
25cf1a301a396c38e8adf52c15f537b80d2483f7jlwhere to find the document, even if the document ends up being
25cf1a301a396c38e8adf52c15f537b80d2483f7jlon the same server.. This has several implications, the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlmost important being that <STRONG>if you use an "ErrorDocument 401"
25cf1a301a396c38e8adf52c15f537b80d2483f7jldirective then it must refer to a local document.</STRONG> This results
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfrom the nature of the HTTP basic authentication scheme.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>See Also: <A HREF="/custom-error.html">documentation of customizable
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt ErrorLog} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> ErrorLog <EM>filename</EM>|<CODE>syslog[:facility]</CODE>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>ErrorLog logs/error_log</CODE> (Unix)<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>ErrorLog logs/error.log</CODE>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl (Windows and OS/2)<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Context:</STRONG></A> server config, virtual host<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe error log directive sets the name of the file to which the server will log
25cf1a301a396c38e8adf52c15f537b80d2483f7jlany errors it encounters. If the filename does not begin with a slash (/)
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthen it is assumed to be relative to the <A HREF="#serverroot">ServerRoot</A>.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlIf the filename begins with a pipe (|) then it is assumed to be a command to
25cf1a301a396c38e8adf52c15f537b80d2483f7jlspawn to handle the error log.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlUsing <CODE>syslog</CODE> instead of a filename enables logging via syslogd(8)
25cf1a301a396c38e8adf52c15f537b80d2483f7jlif the system supports it. The default is to use syslog facility
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<CODE>local7</CODE>, but you can override this by using the
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<CODE>syslog:</CODE><EM>facility</EM> syntax where <EM>facility</EM> can be
25cf1a301a396c38e8adf52c15f537b80d2483f7jlone of the names usually documented in syslog(1).
25cf1a301a396c38e8adf52c15f537b80d2483f7jlSECURITY: See the
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<A HREF="/misc/security_tips.html#serverroot">security tips</A>
25cf1a301a396c38e8adf52c15f537b80d2483f7jldocument for details on why your security could be compromised if
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthe directory where logfiles are stored is writable by anyone other
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthan the user that starts the server.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P><STRONG>See also:</STRONG> <A HREF="#loglevel">LogLevel</A>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> <Files <EM>filename</EM>>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl... </Files><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Context:</STRONG></A> server config, virtual host, .htaccess<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> only available in Apache
25cf1a301a396c38e8adf52c15f537b80d2483f7jl1.2 and above.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>The <Files> directive provides for access control by
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfilename. It is comparable to the <A
25cf1a301a396c38e8adf52c15f537b80d2483f7jlshould be matched with a </Files> directive. The
25cf1a301a396c38e8adf52c15f537b80d2483f7jldirectives given within this section will be applied to any
25cf1a301a396c38e8adf52c15f537b80d2483f7jlobject with a basename (last component of filename) matching
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthe specified filename.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlorder they appear in the configuration file, after the
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<Directory> sections and <CODE>.htaccess</CODE> files are
25cf1a301a396c38e8adf52c15f537b80d2483f7jlread, but before <Location> sections. Note that
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<Files> can be nested inside <Directory>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlsections to restrict the portion of the filesystem they
25cf1a301a396c38e8adf52c15f537b80d2483f7jlapply to.</P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>The <EM>filename</EM> argument should include a filename, or a
25cf1a301a396c38e8adf52c15f537b80d2483f7jlwild-card string, where `?' matches any single character, and `*' matches any
25cf1a301a396c38e8adf52c15f537b80d2483f7jlsequences of characters. Extended regular expressions can also be used,
25cf1a301a396c38e8adf52c15f537b80d2483f7jlwith the addition of
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <Files ~ "\.(gif|jpe?g|png)$">
25cf1a301a396c38e8adf52c15f537b80d2483f7jlwould match most common Internet graphics formats. In Apache 1.3 and
25cf1a301a396c38e8adf52c15f537b80d2483f7jllater, <A HREF="#filesmatch"><FilesMatch></A> is preferred,
25cf1a301a396c38e8adf52c15f537b80d2483f7jlHREF="#directory"><CODE><Directory></CODE></A> and <A
25cf1a301a396c38e8adf52c15f537b80d2483f7jlHREF="#location"><CODE><Location></CODE></A> sections,
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<CODE><Files></CODE> sections can be used inside .htaccess
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfiles. This allows users to control access to their own files, at a
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfile-by-file level.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<STRONG>See also</STRONG>: <A HREF="/sections.html">How Directory,
25cf1a301a396c38e8adf52c15f537b80d2483f7jlLocation and Files sections work</A> for an explanation of how these
25cf1a301a396c38e8adf52c15f537b80d2483f7jldifferent sections are combined when a request is received
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> <FilesMatch <EM>regex</EM>>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl... </FilesMatch><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Context:</STRONG></A> server config, virtual host, .htaccess<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> only available in Apache
25cf1a301a396c38e8adf52c15f537b80d2483f7jl1.3 and above.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>The <FilesMatch> directive provides for access control by
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfilename, just as the <A HREF="#files"><Files></A> directive
25cf1a301a396c38e8adf52c15f537b80d2483f7jldoes. However, it accepts a regular expression. For example:</P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <FilesMatch "\.(gif|jpe?g|png)$">
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<STRONG>See also</STRONG>: <A HREF="/sections.html">How Directory,
25cf1a301a396c38e8adf52c15f537b80d2483f7jlLocation and Files sections work</A> for an explanation of how these
25cf1a301a396c38e8adf52c15f537b80d2483f7jldifferent sections are combined when a request is received
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt Group} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> Group <EM>unix-group</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Context:</STRONG></A> server config, virtual host<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe Group directive sets the group under which the server will answer requests.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlIn order to use this directive, the stand-alone server must be run initially
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<DT>A group name
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<DD>Refers to the given group by name.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<DT># followed by a group number.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<DD>Refers to a group by its number.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlIt is recommended that you set up a new group specifically for running the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlserver. Some admins use user <CODE>nobody</CODE>, but this is not always
25cf1a301a396c38e8adf52c15f537b80d2483f7jlpossible or desirable.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlNote: if you start the server as a non-root user, it will fail to change
f7832c8d6c8b1d0020951f2b254dca0a6a741824hywto the specified group, and will instead continue to run as the group of the
f7832c8d6c8b1d0020951f2b254dca0a6a741824hyworiginal user. <P>
3cbfd4cf9e3b91b2efed73184d8c6dc586fc1935jimandSpecial note: Use of this directive in <VirtualHost> requires a
3cbfd4cf9e3b91b2efed73184d8c6dc586fc1935jimandproperly configured <A HREF="/suexec.html">suEXEC wrapper</A>.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlWhen used inside a <VirtualHost> in this manner, only the group
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthat CGIs are run as is affected. Non-CGI requests are still processed
25cf1a301a396c38e8adf52c15f537b80d2483f7jlas the group specified in the main Group directive.<P>
3cbfd4cf9e3b91b2efed73184d8c6dc586fc1935jimandSECURITY: See <A HREF="#user">User</A> for a discussion of the security
3cbfd4cf9e3b91b2efed73184d8c6dc586fc1935jimand<H2><A NAME="hostnamelookups">HostNameLookups directive</A></H2>
3cbfd4cf9e3b91b2efed73184d8c6dc586fc1935jimand<!--%plaintext <?INDEX {\tt HostNameLookups} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> HostNameLookups <EM>on | off | double</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
f7832c8d6c8b1d0020951f2b254dca0a6a741824hyw><STRONG>Default:</STRONG></A> <CODE>HostNameLookups off</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Context:</STRONG></A> server config, virtual host, directory<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
e98fafb9956429b59c817d4fbd27720c73879203jl HREF="directive-dict.html#Compatibility"
e98fafb9956429b59c817d4fbd27720c73879203jl REL="Help"
e98fafb9956429b59c817d4fbd27720c73879203jl><STRONG>Compatibility:</STRONG></A> <CODE>double</CODE> available only in
e98fafb9956429b59c817d4fbd27720c73879203jl1.3 and above.<BR>
e98fafb9956429b59c817d4fbd27720c73879203jl HREF="directive-dict.html#Compatibility"
e98fafb9956429b59c817d4fbd27720c73879203jl REL="Help"
e98fafb9956429b59c817d4fbd27720c73879203jl><STRONG>Compatibility:</STRONG></A> Default was <CODE>on</CODE> prior to
e98fafb9956429b59c817d4fbd27720c73879203jlApache 1.3.<P>
e98fafb9956429b59c817d4fbd27720c73879203jlThis directive enables DNS lookups so that host names can be logged (and
e98fafb9956429b59c817d4fbd27720c73879203jlThe value <CODE>double</CODE> refers to doing double-reverse DNS.
e98fafb9956429b59c817d4fbd27720c73879203jlThat is, after a reverse lookup is performed, a forward lookup is then
e98fafb9956429b59c817d4fbd27720c73879203jlperformed on that result. At least one of the ip addresses in the forward
e98fafb9956429b59c817d4fbd27720c73879203jllookup must match the original address. (In "tcpwrappers" terminology
e98fafb9956429b59c817d4fbd27720c73879203jlRegardless of the setting, when <A HREF="mod_access.html">mod_access</A>
e98fafb9956429b59c817d4fbd27720c73879203jlis used for controlling access by hostname, a double reverse lookup
e98fafb9956429b59c817d4fbd27720c73879203jlwill be performed. This is necessary for security. Note that the
e98fafb9956429b59c817d4fbd27720c73879203jlresult of this double-reverse isn't generally available unless
e98fafb9956429b59c817d4fbd27720c73879203jlyou set <CODE>HostnameLookups double</CODE>. For example, if only
e98fafb9956429b59c817d4fbd27720c73879203jl<CODE>HostnameLookups on</CODE> and a request is made to an object that
e98fafb9956429b59c817d4fbd27720c73879203jlis protected by hostname restrictions, regardless of whether the
e98fafb9956429b59c817d4fbd27720c73879203jldouble-reverse fails or not, CGIs will still be passed the single-reverse
e98fafb9956429b59c817d4fbd27720c73879203jlThe default for this directive was previously <CODE>on</CODE> in
e98fafb9956429b59c817d4fbd27720c73879203jlversions of Apache prior to 1.3. It was changed to <CODE>off</CODE>
e98fafb9956429b59c817d4fbd27720c73879203jlin order to save the network traffic for those sites that don't truly
e98fafb9956429b59c817d4fbd27720c73879203jlneed the reverse lookups done. It is also better for the end users
e98fafb9956429b59c817d4fbd27720c73879203jlbecause they don't have to suffer the extra latency that a lookup
e98fafb9956429b59c817d4fbd27720c73879203jlHeavily loaded sites should leave this directive <CODE>off</CODE>, since DNS
e98fafb9956429b59c817d4fbd27720c73879203jllookups can take considerable amounts of time. The utility <EM>logresolve</EM>,
e98fafb9956429b59c817d4fbd27720c73879203jlprovided in the <EM>/support</EM> directory, can be used to look up host names
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="identitycheck">IdentityCheck directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt IdentityCheck} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> IdentityCheck <EM>boolean</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>IdentityCheck off</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Context:</STRONG></A> server config, virtual host, directory<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThis directive enables RFC1413-compliant logging of the remote user name
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfor each connection, where the client machine runs identd or something similar.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThis information is logged in the access log. <EM>Boolean</EM> is either
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe information should not be trusted in any way except for rudimentary usage
25cf1a301a396c38e8adf52c15f537b80d2483f7jltracking.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlNote that this can cause serious latency problems accessing your server
25cf1a301a396c38e8adf52c15f537b80d2483f7jlsince every request requires one of these lookups to be performed. When
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfirewalls are involved each lookup might possibly fail and add 30 seconds
25cf1a301a396c38e8adf52c15f537b80d2483f7jlof latency to each hit. So in general this is not very useful on public
25cf1a301a396c38e8adf52c15f537b80d2483f7jlservers accessible from the Internet.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="ifdefine"><IfDefine> directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> <IfDefine [!]<EM>parameter-name</EM>> <EM>...</EM>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl</IfDefine><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> <IfDefine> is only available in
25cf1a301a396c38e8adf52c15f537b80d2483f7jl1.3.1 and later.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlsection is used to mark directives that are conditional. The
25cf1a301a396c38e8adf52c15f537b80d2483f7jldirectives within an IfDefine section are only
25cf1a301a396c38e8adf52c15f537b80d2483f7jlis false, everything between the start and end markers
25cf1a301a396c38e8adf52c15f537b80d2483f7jlis ignored.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe <EM>test</EM> in the <IfDefine> section directive
25cf1a301a396c38e8adf52c15f537b80d2483f7jlcan be one of two forms:
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>In the former case, the directives between the start and end markers are
25cf1a301a396c38e8adf52c15f537b80d2483f7jlonly processed if the parameter named <EM>parameter-name</EM> is defined.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe second format reverses the test, and only processes the directives if
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>The <EM>parameter-name</EM> argument is a define as given on the
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<CODE>httpd</CODE> command line via <CODE>-D</CODE><EM>parameter-</EM>, at the
25cf1a301a396c38e8adf52c15f537b80d2483f7jltime the server was started.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P><IfDefine> sections are nest-able, which can be used to implement
25cf1a301a396c38e8adf52c15f537b80d2483f7jlsimple multiple-parameter tests.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl $ httpd -DReverseProxy ...
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <IfDefine ReverseProxy>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl </IfDefine>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="ifmodule"><IfModule> directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> <IfModule [!]<EM>module-name</EM>>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl</IfModule><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> IfModule is only available in 1.2 and
25cf1a301a396c38e8adf52c15f537b80d2483f7jlsection is used to mark directives that are conditional. The
25cf1a301a396c38e8adf52c15f537b80d2483f7jldirectives within an IfModule section are only
25cf1a301a396c38e8adf52c15f537b80d2483f7jlis false, everything between the start and end markers
25cf1a301a396c38e8adf52c15f537b80d2483f7jlis ignored.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe <EM>test</EM> in the <IfModule> section directive
25cf1a301a396c38e8adf52c15f537b80d2483f7jlcan be one of two forms:
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>In the former case, the directives between the start and end markers
25cf1a301a396c38e8adf52c15f537b80d2483f7jlare only processed if the module named <EM>module name</EM> is compiled
25cf1a301a396c38e8adf52c15f537b80d2483f7jlin to Apache. The second format reverses the test, and only processes
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthe directives if <EM>module name</EM> is <STRONG>not</STRONG> compiled in.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>The <EM>module name</EM> argument is a module name as given as the file
25cf1a301a396c38e8adf52c15f537b80d2483f7jlname of the module, at the time it was compiled. For example,
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P><IfModule> sections are nest-able, which can be used to implement
25cf1a301a396c38e8adf52c15f537b80d2483f7jlsimple multiple-module tests.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> Include is only available in Apache 1.3
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThis directive allows inclusion of other configuration files from within the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlserver configuration files.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<STRONG>Syntax: (Apache 1.1)</STRONG> KeepAlive <EM>max-requests</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<STRONG>Default: (Apache 1.1)</STRONG> <CODE>KeepAlive 5</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<STRONG>Syntax: (Apache 1.2)</STRONG> KeepAlive <EM>on/off</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<STRONG>Default: (Apache 1.2)</STRONG> <CODE>KeepAlive On</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> KeepAlive is only available in Apache
25cf1a301a396c38e8adf52c15f537b80d2483f7jl1.1 and later.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThis directive enables
25cf1a301a396c38e8adf52c15f537b80d2483f7jlto the maximum number of requests you want Apache to entertain per
25cf1a301a396c38e8adf52c15f537b80d2483f7jlrequest. A limit is imposed to prevent a client from hogging your
25cf1a301a396c38e8adf52c15f537b80d2483f7jlserver resources. Set this to <CODE>0</CODE> to disable support.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P><STRONG>Apache 1.2 and later</STRONG>: Set to "On" to enable
25cf1a301a396c38e8adf52c15f537b80d2483f7jlpersistent connections, "Off" to disable. See also the <A
25cf1a301a396c38e8adf52c15f537b80d2483f7jlHREF="#maxkeepaliverequests">MaxKeepAliveRequests</A> directive.</P><HR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="keepalivetimeout">KeepAliveTimeout directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> KeepAliveTimeout <EM>seconds</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>KeepAliveTimeout 15</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> KeepAliveTimeout is only available in
25cf1a301a396c38e8adf52c15f537b80d2483f7jlApache 1.1 and later.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe number of seconds Apache will wait for a subsequent request before
25cf1a301a396c38e8adf52c15f537b80d2483f7jlclosing the connection. Once a request has been received, the timeout
25cf1a301a396c38e8adf52c15f537b80d2483f7jlvalue specified by the <A
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt Limit} section directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <Limit <EM>method method</EM> ... > ... </Limit><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jlAccess controls are normally effective for <STRONG>all</STRONG> access
25cf1a301a396c38e8adf52c15f537b80d2483f7jlmethods, and this is the usual desired behaviour. <STRONG>In the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlgeneral case, access control directives should not be placed within a
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>The purpose of the <Limit> directive is to restrict the effect
25cf1a301a396c38e8adf52c15f537b80d2483f7jlof the access controls to the nominated HTTP methods. For all other
25cf1a301a396c38e8adf52c15f537b80d2483f7jlmethods, the access restrictions that are enclosed in the
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<Limit> bracket <STRONG>will have no effect</STRONG>. The
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfollowing example applies the access control only to the methods POST,
25cf1a301a396c38e8adf52c15f537b80d2483f7jlPUT, and DELETE, leaving all other methods unprotected:
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<Limit POST PUT DELETE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlrequire valid-user<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe method names listed can be one or more of: GET, POST, PUT, DELETE,
25cf1a301a396c38e8adf52c15f537b80d2483f7jlCONNECT, OPTIONS, TRACE, PATCH, PROPFIND, PROPPATCH, MKCOL, COPY,
25cf1a301a396c38e8adf52c15f537b80d2483f7jlMOVE, LOCK, and UNLOCK. <STRONG>The method name is
25cf1a301a396c38e8adf52c15f537b80d2483f7jlcase-sensitive.</STRONG> If GET is used it will also restrict HEAD
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="limitexcept"><LimitExcept> directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt LimitExcept} section directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <LimitExcept <EM>method method</EM> ... > ... </LimitExcept><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> Available in Apache 1.3.5 and later<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<LimitExcept> and </LimitExcept> are used to enclose a group of
25cf1a301a396c38e8adf52c15f537b80d2483f7jlaccess control directives which will then apply to any HTTP access method
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<STRONG>not</STRONG> listed in the arguments; i.e., it is the opposite of a
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<A HREF="#limit"><Limit></A> section and can be used to control both
25cf1a301a396c38e8adf52c15f537b80d2483f7jlstandard and nonstandard/unrecognized methods. See the documentation for
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="limitrequestbody">LimitRequestBody directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt LimitRequestBody} directive> -->
2dd3029adb4864ebca3dd9cd6dad5fc4d38abff6jimand><STRONG>Syntax:</STRONG></A> LimitRequestBody <EM>number</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>LimitRequestBody 0</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Context:</STRONG></A> server config, virtual host, directory,
25cf1a301a396c38e8adf52c15f537b80d2483f7jl.htaccess<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> LimitRequestBody is only available in
25cf1a301a396c38e8adf52c15f537b80d2483f7jlApache 1.3.2 and later.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<EM>Number</EM> is a long integer from 0 (meaning unlimited) to 2147483647
25cf1a301a396c38e8adf52c15f537b80d2483f7jl(2GB). The default value is defined by the compile-time constant
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<CODE>DEFAULT_LIMIT_REQUEST_BODY</CODE> (0 as distributed).
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe LimitRequestBody directive allows the user to set a
25cf1a301a396c38e8adf52c15f537b80d2483f7jllimit on the allowed size of an HTTP request message body within
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthe context in which the directive is given (server, per-directory,
25cf1a301a396c38e8adf52c15f537b80d2483f7jlper-file or per-location). If the client request exceeds that limit,
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthe server will return an error response instead of servicing the request.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe size of a normal request message body will vary greatly depending
25cf1a301a396c38e8adf52c15f537b80d2483f7jlon the nature of the resource and the methods allowed on that resource.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlCGI scripts typically use the message body for passing form information
25cf1a301a396c38e8adf52c15f537b80d2483f7jlto the server. Implementations of the PUT method will require a value
25cf1a301a396c38e8adf52c15f537b80d2483f7jlat least as large as any representation that the server wishes
25cf1a301a396c38e8adf52c15f537b80d2483f7jlto accept for that resource.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThis directive gives the server administrator greater control over abnormal
25cf1a301a396c38e8adf52c15f537b80d2483f7jlclient request behavior, which may be useful for avoiding some forms
25cf1a301a396c38e8adf52c15f537b80d2483f7jlof denial-of-service attacks.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="limitrequestfields">LimitRequestFields directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt LimitRequestFields} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> LimitRequestFields <EM>number</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>LimitRequestFields 100</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> LimitRequestFields is only available in
25cf1a301a396c38e8adf52c15f537b80d2483f7jlApache 1.3.2 and later.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<EM>Number</EM> is an integer from 0 (meaning unlimited) to 32767.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe default value is defined by the compile-time constant
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<CODE>DEFAULT_LIMIT_REQUEST_FIELDS</CODE> (100 as distributed).
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe LimitRequestFields directive allows the server administrator to modify
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthe limit on the number of request header fields allowed in an HTTP request.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlA server needs this value to be larger than the number of fields that a
25cf1a301a396c38e8adf52c15f537b80d2483f7jlnormal client request might include. The number of request header fields
25cf1a301a396c38e8adf52c15f537b80d2483f7jlused by a client rarely exceeds 20, but this may vary among different
25cf1a301a396c38e8adf52c15f537b80d2483f7jlclient implementations, often depending upon the extent to which a user
25cf1a301a396c38e8adf52c15f537b80d2483f7jlhas configured their browser to support detailed content negotiation.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlOptional HTTP extensions are often expressed using request header fields.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThis directive gives the server administrator greater control over abnormal
25cf1a301a396c38e8adf52c15f537b80d2483f7jlclient request behavior, which may be useful for avoiding some forms
25cf1a301a396c38e8adf52c15f537b80d2483f7jlof denial-of-service attacks. The value should be increased if normal
25cf1a301a396c38e8adf52c15f537b80d2483f7jlclients see an error response from the server that indicates too many
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfields were sent in the request.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="limitrequestfieldsize">LimitRequestFieldsize directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt LimitRequestFieldsize} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> LimitRequestFieldsize <EM>number</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>LimitRequestFieldsize 8190</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> LimitRequestFieldsize is only available in
25cf1a301a396c38e8adf52c15f537b80d2483f7jlApache 1.3.2 and later.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<EM>Number</EM> is an integer size in bytes from 0 to the value of the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlcompile-time constant <CODE>DEFAULT_LIMIT_REQUEST_FIELDSIZE</CODE>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl(8190 as distributed).
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe LimitRequestFieldsize directive allows the server administrator to reduce
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthe limit on the allowed size of an HTTP request header field below the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlnormal input buffer size compiled with the server. A server needs this
25cf1a301a396c38e8adf52c15f537b80d2483f7jlvalue to be large enough to hold any one header field from a normal client
25cf1a301a396c38e8adf52c15f537b80d2483f7jlrequest. The size of a normal request header field will vary greatly
25cf1a301a396c38e8adf52c15f537b80d2483f7jlamong different client implementations, often depending upon the extent
25cf1a301a396c38e8adf52c15f537b80d2483f7jlto which a user has configured their browser to support detailed
25cf1a301a396c38e8adf52c15f537b80d2483f7jlcontent negotiation.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThis directive gives the server administrator greater control over abnormal
25cf1a301a396c38e8adf52c15f537b80d2483f7jlclient request behavior, which may be useful for avoiding some forms
25cf1a301a396c38e8adf52c15f537b80d2483f7jlof denial-of-service attacks. Under normal conditions, the value should
25cf1a301a396c38e8adf52c15f537b80d2483f7jlnot be changed from the default.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="limitrequestline">LimitRequestLine directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt LimitRequestLine} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> LimitRequestLine <EM>number</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>LimitRequestLine 8190</CODE><BR>
e98fafb9956429b59c817d4fbd27720c73879203jl HREF="directive-dict.html#Context"
e98fafb9956429b59c817d4fbd27720c73879203jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> LimitRequestLine is only available in
25cf1a301a396c38e8adf52c15f537b80d2483f7jlApache 1.3.2 and later.
e98fafb9956429b59c817d4fbd27720c73879203jl<EM>Number</EM> is an integer size in bytes from 0 to the value of the
e98fafb9956429b59c817d4fbd27720c73879203jlcompile-time constant <CODE>DEFAULT_LIMIT_REQUEST_LINE</CODE>
e98fafb9956429b59c817d4fbd27720c73879203jl(8190 as distributed).
e98fafb9956429b59c817d4fbd27720c73879203jlThe LimitRequestLine directive allows the server administrator to reduce
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthe limit on the allowed size of a client's HTTP request-line below the
f7832c8d6c8b1d0020951f2b254dca0a6a741824hywnormal input buffer size compiled with the server. Since the request-line
f7832c8d6c8b1d0020951f2b254dca0a6a741824hywconsists of the HTTP method, URI, and protocol version, the
f7832c8d6c8b1d0020951f2b254dca0a6a741824hywLimitRequestLine directive places a restriction on the length of a
f7832c8d6c8b1d0020951f2b254dca0a6a741824hywrequest-URI allowed for a request on the server. A server needs this
f7832c8d6c8b1d0020951f2b254dca0a6a741824hywvalue to be large enough to hold any of its resource names, including
f7832c8d6c8b1d0020951f2b254dca0a6a741824hywany information that might be passed in the query part of a GET request.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThis directive gives the server administrator greater control over abnormal
25cf1a301a396c38e8adf52c15f537b80d2483f7jlclient request behavior, which may be useful for avoiding some forms
25cf1a301a396c38e8adf52c15f537b80d2483f7jlof denial-of-service attacks. Under normal conditions, the value should
25cf1a301a396c38e8adf52c15f537b80d2483f7jlnot be changed from the default.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> Listen is only available in Apache
25cf1a301a396c38e8adf52c15f537b80d2483f7jl1.1 and later.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>The Listen directive instructs Apache to listen to more than one IP
25cf1a301a396c38e8adf52c15f537b80d2483f7jladdress or port; by default it responds to requests on all IP
25cf1a301a396c38e8adf52c15f537b80d2483f7jlHREF="#bindaddress">BindAddress</A></TT> and <TT>Port</TT>. It tells
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthe server to accept incoming requests on the specified port or
25cf1a301a396c38e8adf52c15f537b80d2483f7jladdress-and-port combination. If the first format is used, with a port
25cf1a301a396c38e8adf52c15f537b80d2483f7jlnumber only, the server listens to the given port on all interfaces,
25cf1a301a396c38e8adf52c15f537b80d2483f7jlinstead of the port given by the <TT>Port</TT> directive. If an IP
25cf1a301a396c38e8adf52c15f537b80d2483f7jladdress is given as well as a port, the server will listen on the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlgiven port and interface. <P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlNote that you may still require a <TT>Port</TT> directive so
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthat URLs that Apache generates that point to your server still
25cf1a301a396c38e8adf52c15f537b80d2483f7jlMultiple Listen directives may be used
25cf1a301a396c38e8adf52c15f537b80d2483f7jlto specify a number of addresses and ports to listen to. The server
25cf1a301a396c38e8adf52c15f537b80d2483f7jlwill respond to requests from any of the listed addresses and
25cf1a301a396c38e8adf52c15f537b80d2483f7jlFor example, to make the server accept connections on both port
25cf1a301a396c38e8adf52c15f537b80d2483f7jl80 and port 8000, use:
25cf1a301a396c38e8adf52c15f537b80d2483f7jl Listen 8000
25cf1a301a396c38e8adf52c15f537b80d2483f7jlTo make the server accept connections on two specified
25cf1a301a396c38e8adf52c15f537b80d2483f7jlinterfaces and port numbers, use
25cf1a301a396c38e8adf52c15f537b80d2483f7jl Listen 192.170.2.1:80
25cf1a301a396c38e8adf52c15f537b80d2483f7jl Listen 192.170.2.5:8000
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<A HREF="/bind.html">Setting which addresses and ports Apache uses</A><BR>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<A HREF="http://www.apache.org/info/known_bugs.html#listenbug">Known Bugs</A>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<H2><A NAME="listenbacklog">ListenBacklog directive</A></H2>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb REL="Help"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb><STRONG>Syntax:</STRONG></A> ListenBacklog <EM>backlog</EM><BR>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb HREF="directive-dict.html#Default"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb REL="Help"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb><STRONG>Default:</STRONG></A> <CODE>ListenBacklog 511</CODE><BR>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb HREF="directive-dict.html#Context"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb REL="Help"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb REL="Help"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb HREF="directive-dict.html#Compatibility"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb REL="Help"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb><STRONG>Compatibility:</STRONG></A> ListenBacklog is only available in Apache
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbversions after 1.2.0.
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<P>The maximum length of the queue of pending connections. Generally no
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbtuning is needed or desired, however on some systems it is desirable
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbto increase this when under a TCP SYN flood attack. See
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbthe backlog parameter to the <CODE>listen(2)</CODE> system call.
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<P>This will often be limited to a smaller number by the operating
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbsystem. This varies from OS to OS. Also note that many OSes do not
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbuse exactly what is specified as the backlog, but use a number based on
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb(but normally larger than) what is set.
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<H2><A NAME="location"><Location> directive</A></H2>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb REL="Help"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb><STRONG>Syntax:</STRONG></A> <Location <EM>URL</EM>>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb... </Location><BR>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb HREF="directive-dict.html#Context"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb REL="Help"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb><STRONG>Context:</STRONG></A> server config, virtual host<BR>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb REL="Help"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb HREF="directive-dict.html#Compatibility"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb REL="Help"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb><STRONG>Compatibility:</STRONG></A> Location is only available in Apache
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb1.1 and later.<P>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<P>The <Location> directive provides for access control by
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbURL. It is similar to the <A
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbstarts a subsection which is terminated with a </Location>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbdirective. <CODE><Location></CODE> sections are processed in the
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmborder they appear in the configuration file, after the
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<Directory> sections and <CODE>.htaccess</CODE> files are
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbread, and after the <Files> sections.</P>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<P>Note that URLs do not have to line up with the filesystem at all,
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbit should be emphasized that <Location> operates completely outside
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbthe filesystem.
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<P>For all origin (non-proxy) requests, the URL to be matched is
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbof the form <CODE>/path/</CODE>, and you should not include any
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<CODE>http://servername</CODE> prefix. For proxy requests, the URL
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbto be matched is of the form <CODE>scheme://servername/path</CODE>,
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmband you must include the prefix.
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<P>The URL may use wildcards In a wild-card string, `?' matches any
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbsingle character, and `*' matches any sequences of characters.
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbExtended regular expressions can also be used, with the addition of
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbFor example:</P>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb <Location ~ "/(extra|special)/data">
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<P>would match URLs that contained the substring "/extra/data" or
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<A HREF="#locationmatch"><LocationMatch></A> exists which
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbbehaves identical to the regex version of
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<P>The <CODE>Location</CODE> functionality is especially useful when
25cf1a301a396c38e8adf52c15f537b80d2483f7jlHREF="mod_mime.html#sethandler">SetHandler</A></CODE> directive. For example,
25cf1a301a396c38e8adf52c15f537b80d2483f7jlto enable status requests, but allow them only
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfrom browsers at foo.com, you might use:
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <Location /status>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl SetHandler server-status
25cf1a301a396c38e8adf52c15f537b80d2483f7jl order deny,allow
25cf1a301a396c38e8adf52c15f537b80d2483f7jl deny from all
25cf1a301a396c38e8adf52c15f537b80d2483f7jl </Location>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P><STRONG>Apache 1.3 and above note about / (slash)</STRONG>: The slash
25cf1a301a396c38e8adf52c15f537b80d2483f7jlcharacter has special
25cf1a301a396c38e8adf52c15f537b80d2483f7jlmeaning depending on where in a URL it appears. People may be used
25cf1a301a396c38e8adf52c15f537b80d2483f7jlto its behaviour in the filesystem where multiple adjacent slashes are
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfrequently collapsed to a single slash (<EM>i.e.</EM>, <CODE>/home///foo</CODE>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlis the same as <CODE>/home/foo</CODE>). In URL-space this is not
25cf1a301a396c38e8adf52c15f537b80d2483f7jlnecessarily true. The <CODE><LocationMatch></CODE> directive
25cf1a301a396c38e8adf52c15f537b80d2483f7jland the regex version of <CODE><Location></CODE> require you
25cf1a301a396c38e8adf52c15f537b80d2483f7jlto explicitly specify multiple slashes if that is your intention.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlFor example, <CODE><LocationMatch ^/abc></CODE> would match the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlrequest URL <CODE>/abc</CODE> but not the request URL <CODE>//abc</CODE>.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe (non-regex) <CODE><Location></CODE> directive behaves
25cf1a301a396c38e8adf52c15f537b80d2483f7jlsimilarly when used for proxy requests. But when (non-regex)
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<CODE><Location></CODE> is used for non-proxy requests it will
25cf1a301a396c38e8adf52c15f537b80d2483f7jlimplicitly match multiple slashes with a single slash. For example,
25cf1a301a396c38e8adf52c15f537b80d2483f7jlif you specify <CODE><Location /abc/def></CODE> and the request
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<STRONG>See also</STRONG>: <A HREF="/sections.html">How Directory,
25cf1a301a396c38e8adf52c15f537b80d2483f7jlLocation and Files sections work</A> for an explanation of how these
25cf1a301a396c38e8adf52c15f537b80d2483f7jldifferent sections are combined when a request is received
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<H2><A NAME="locationmatch"><LocationMatch></A></H2>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb REL="Help"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb><STRONG>Syntax:</STRONG></A> <LocationMatch <EM>regex</EM>>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb... </LocationMatch><BR>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb HREF="directive-dict.html#Context"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb REL="Help"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb><STRONG>Context:</STRONG></A> server config, virtual host<BR>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb REL="Help"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb HREF="directive-dict.html#Compatibility"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb REL="Help"
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb><STRONG>Compatibility:</STRONG></A> LocationMatch is only available in
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbApache 1.3 and later.<P>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<P>The <LocationMatch> directive provides for access control by
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbURL, in an identical manner to <A
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbHREF="#location"><Location></A>. However, it takes a regular
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbexpression as an argument instead of a simple string. For example:</P>
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb <LocationMatch "/(extra|special)/data">
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<P>would match URLs that contained the substring "/extra/data" or
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmb<STRONG>See also</STRONG>: <A HREF="/sections.html">How Directory,
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbLocation and Files sections work</A> for an explanation of how these
50eff7691a80815571befbb7c9fe5f0bbf22dcbdmbdifferent sections are combined when a request is received
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> LockFile <EM>filename</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>LockFile logs/accept.lock</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe LockFile directive sets the path to the lockfile used when
25cf1a301a396c38e8adf52c15f537b80d2483f7jlApache is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or
25cf1a301a396c38e8adf52c15f537b80d2483f7jlUSE_FLOCK_SERIALIZED_ACCEPT. This directive should normally be
25cf1a301a396c38e8adf52c15f537b80d2483f7jlleft at its default value. The main reason for changing it is if
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthe <CODE>logs</CODE> directory is NFS mounted, since <STRONG>the lockfile
25cf1a301a396c38e8adf52c15f537b80d2483f7jlmust be stored on a local disk</STRONG>. The PID of the main
25cf1a301a396c38e8adf52c15f537b80d2483f7jlserver process is automatically appended to the filename. <P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<STRONG>SECURITY:</STRONG> It is best to avoid putting this file in a
25cf1a301a396c38e8adf52c15f537b80d2483f7jlworld writable directory such as <CODE>/var/tmp</CODE> because someone
25cf1a301a396c38e8adf52c15f537b80d2483f7jlcould create a denial of service attack and prevent the server from
25cf1a301a396c38e8adf52c15f537b80d2483f7jlstarting by creating a lockfile with the same name as the one the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlserver will try to create.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>LogLevel error</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Context:</STRONG></A> server config, virtual host<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> LogLevel is only available in 1.3 or
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>LogLevel adjusts the verbosity of the messages recorded in the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlerror logs (see <A HREF="#errorlog">ErrorLog</A> directive).
25cf1a301a396c38e8adf52c15f537b80d2483f7jldecreasing significance:
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <TD>Emergencies - system is unusable.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <TD>Action must be taken immediately.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <TR><TD><TD>"getpwuid: couldn't determine user name from uid"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <TD>Critical Conditions.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <TR><TD><TD>"socket: Failed to get a socket, exiting child"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <TD>Error conditions.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <TD>Warning conditions.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <TR><TD><TD>"child process 1234 did not exit, sending another SIGHUP"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <TD>Normal but significant condition.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <TR><TD><TD>"httpd: caught SIGBUS, attempting to dump core in ..."
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <TD>Informational.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <TR><TD><TD>"Server seems busy, (you may need to increase StartServers, or
25cf1a301a396c38e8adf52c15f537b80d2483f7jl <TD>Debug-level messages
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>When a particular level is specified, messages from all other levels
25cf1a301a396c38e8adf52c15f537b80d2483f7jlof higher significance will be reported as well. <EM>E.g.</EM>, when
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<CODE>LogLevel info</CODE> is specified, then messages with log levels of
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<CODE>notice</CODE> and <CODE>warn</CODE> will also be posted.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlUsing a level of at least <CODE>crit</CODE> is recommended.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt MaxClients} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> MaxClients <EM>number</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>MaxClients 256</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
f7832c8d6c8b1d0020951f2b254dca0a6a741824hyw REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>The MaxClients directive sets the limit on the number of simultaneous
25cf1a301a396c38e8adf52c15f537b80d2483f7jlrequests that can be supported; not more than this number of child server
25cf1a301a396c38e8adf52c15f537b80d2483f7jlprocesses will be created. To configure more than 256 clients, you must
25cf1a301a396c38e8adf52c15f537b80d2483f7jledit the HARD_SERVER_LIMIT entry in httpd.h and recompile.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>Any connection attempts over the MaxClients limit will normally
25cf1a301a396c38e8adf52c15f537b80d2483f7jlbe queued, up to a number based on the <A HREF="#listenbacklog">
25cf1a301a396c38e8adf52c15f537b80d2483f7jlListenBacklog</A> directive. Once a child process is freed at the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlend of a different request, the connection will then be serviced.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="maxkeepaliverequests">MaxKeepAliveRequests directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> MaxKeepAliveRequests <EM>number</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>MaxKeepAliveRequests 100</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> Only available in Apache
25cf1a301a396c38e8adf52c15f537b80d2483f7jl1.2 and later.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>The MaxKeepAliveRequests directive limits the number of requests
25cf1a301a396c38e8adf52c15f537b80d2483f7jlallowed per connection when <A HREF="#keepalive">KeepAlive</A> is
25cf1a301a396c38e8adf52c15f537b80d2483f7jlon. If it is set to "<CODE>0</CODE>", unlimited requests will be
25cf1a301a396c38e8adf52c15f537b80d2483f7jlallowed. We recommend that this setting be kept to a high value for
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="maxrequestsperchild">MaxRequestsPerChild directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt MaxRequestsPerChild} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> MaxRequestsPerChild <EM>number</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>MaxRequestsPerChild 0</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe MaxRequestsPerChild directive sets the limit on the number of requests
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthat an individual child server process will handle. After MaxRequestsPerChild
25cf1a301a396c38e8adf52c15f537b80d2483f7jlrequests, the child process will die. If MaxRequestsPerChild is 0, then
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthe process will never expire.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlSetting MaxRequestsPerChild to a non-zero limit has two beneficial effects:
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<LI>it limits the amount of memory that process can consume by (accidental)
25cf1a301a396c38e8adf52c15f537b80d2483f7jlmemory leakage;
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<LI> by giving processes a finite lifetime, it helps reduce the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlnumber of processes when the server load reduces.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P>This directive has no effect on Win32.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<P><STRONG>NOTE:</STRONG> For <EM>KeepAlive</EM> requests, only the first
25cf1a301a396c38e8adf52c15f537b80d2483f7jlrequest is counted towards this limit. In effect, it changes the
25cf1a301a396c38e8adf52c15f537b80d2483f7jlbehavior to limit the number of <EM>connections</EM> per child.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="maxspareservers">MaxSpareServers directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt MaxSpareServers} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> MaxSpareServers <EM>number</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>MaxSpareServers 10</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
c9d93b537520c235a6d4a0af53b9bf07cf3390e9James AndersonThe MaxSpareServers directive sets the desired maximum number of <EM>idle</EM>
c9d93b537520c235a6d4a0af53b9bf07cf3390e9James Andersonchild server processes. An idle process is one which is not handling
c9d93b537520c235a6d4a0af53b9bf07cf3390e9James Andersona request. If there are more than MaxSpareServers idle, then the parent
c9d93b537520c235a6d4a0af53b9bf07cf3390e9James Andersonprocess will kill off the excess processes.<P>
c9d93b537520c235a6d4a0af53b9bf07cf3390e9James AndersonTuning of this parameter should only be necessary on very busy sites.
c9d93b537520c235a6d4a0af53b9bf07cf3390e9James AndersonSetting this parameter to a large number is almost always a bad idea.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThis directive has no effect when used with the Apache Web server on a
25cf1a301a396c38e8adf52c15f537b80d2483f7jlMicrosoft Windows platform.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlSee also <A HREF="#minspareservers">MinSpareServers</A> and
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="minspareservers">MinSpareServers directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt MinSpareServers} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> MinSpareServers <EM>number</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Default"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Default:</STRONG></A> <CODE>MinSpareServers 5</CODE><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe MinSpareServers directive sets the desired minimum number of <EM>idle</EM>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlchild server processes. An idle process is one which is not handling
25cf1a301a396c38e8adf52c15f537b80d2483f7jla request. If there are fewer than MinSpareServers idle, then the parent
25cf1a301a396c38e8adf52c15f537b80d2483f7jlprocess creates new children at a maximum rate of 1 per second.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlTuning of this parameter should only be necessary on very busy sites.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlSetting this parameter to a large number is almost always a bad idea.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThis directive has no effect on Microsoft Windows.
25cf1a301a396c38e8adf52c15f537b80d2483f7jlSee also <A HREF="#maxspareservers">MaxSpareServers</A> and
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<H2><A NAME="namevirtualhost">NameVirtualHost directive</A></H2>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt NameVirtualHost} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> NameVirtualHost <EM>addr</EM>[:<EM>port</EM>]<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Compatibility"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Compatibility:</STRONG></A> NameVirtualHost is only available in
25cf1a301a396c38e8adf52c15f537b80d2483f7jlApache 1.3 and later<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe NameVirtualHost directive is a required directive if you want to configure
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<A HREF="/vhosts/index.html">name-based virtual hosts</A>.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlAlthough <EM>addr</EM> can be hostname it is recommended that you always use
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<BLOCKQUOTE><CODE>NameVirtualHost 111.22.33.44</CODE></BLOCKQUOTE>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlWith the NameVirtualHost directive you specify the address to which your
25cf1a301a396c38e8adf52c15f537b80d2483f7jlname-based virtual host names resolve. If you have multiple name-based
25cf1a301a396c38e8adf52c15f537b80d2483f7jlhosts on multiple addresses, repeat the directive for each address.<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlNote: the "main server" and any _default_ servers will <STRONG>never</STRONG>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlbe served for a request to a NameVirtualHost IP Address (unless for some
25cf1a301a396c38e8adf52c15f537b80d2483f7jlreason you specify NameVirtualHost but then don't define any VirtualHosts
25cf1a301a396c38e8adf52c15f537b80d2483f7jlfor that address).<P>
25cf1a301a396c38e8adf52c15f537b80d2483f7jlOptionally you can specify a port number on which the name-based
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<BLOCKQUOTE><CODE>NameVirtualHost 111.22.33.44:8080</CODE></BLOCKQUOTE>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<A HREF="/vhosts/index.html">Apache Virtual Host documentation</A>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<!--%plaintext <?INDEX {\tt Options} directive> -->
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Syntax:</STRONG></A> Options <EM>[+|-]option [+|-]option ...</EM><BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Context"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl><STRONG>Context:</STRONG></A> server config, virtual host, directory,
25cf1a301a396c38e8adf52c15f537b80d2483f7jl.htaccess<BR>
25cf1a301a396c38e8adf52c15f537b80d2483f7jl HREF="directive-dict.html#Override"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jl REL="Help"
25cf1a301a396c38e8adf52c15f537b80d2483f7jlThe Options directive controls which server features are available in
25cf1a301a396c38e8adf52c15f537b80d2483f7jla particular directory.
25cf1a301a396c38e8adf52c15f537b80d2483f7jl<EM>option</EM> can be set to <CODE>None</CODE>, in which case none of
25cf1a301a396c38e8adf52c15f537b80d2483f7jlthe extra features are enabled, or one or more of the following:
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Default"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Default"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Override"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Default"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Default"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Compatibility"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Default"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Compatibility"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Default"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Compatibility"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Default"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Compatibility"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Default"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
Linux 1.x users might be able to add
might work with some 1.x installations, but won't work with all of
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Default"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
Windows Registry to be searched using the script file extension (e.g., .pl) as a search key.
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Compatibility"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Compatibility"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Default"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Default"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Compatibility"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Default"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Compatibility"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Default"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Default"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Default"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Default"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Default"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Syntax"
HREF="directive-dict.html#Context"
HREF="directive-dict.html#Status"
HREF="directive-dict.html#Compatibility"
HREF="directive-dict.html#Compatibility"
<!--#include virtual="footer.html" -->