Loading docs/manual/mod/core.html +65 −65 Changes for docs/manual/mod/core.html: 65 added lines, 65 removed lines. Original line number Diff line number Diff line Loading @@ -84,7 +84,7 @@ always available. </UL> <HR> <h2><A name="accessconfig">AccessConfig directive</A></h2> <H2><A name="accessconfig">AccessConfig directive</A></H2> <!--%plaintext <?INDEX {\tt AccessConfig} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -113,7 +113,7 @@ Historically, this file only contained contain any server directive allowed in the <EM>server config</EM> context. <P><HR> <h2><A name="accessfilename">AccessFileName directive</A></h2> <H2><A name="accessfilename">AccessFileName directive</A></H2> <!--%plaintext <?INDEX {\tt AccessFileName} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -150,7 +150,7 @@ for directives, unless they have been disabled with AllowOverride None<BR> </Directory></CODE></BLOCKQUOTE><P><HR> <h2><A name="addmodule">AddModule directive</A></h2> <H2><A name="addmodule">AddModule directive</A></H2> <!--%plaintext <?INDEX {\tt AddModule} directive> --> <A HREF="directive-dict.html#Syntax" Loading @@ -175,7 +175,7 @@ server comes with a pre-loaded list of active modules; this list can be cleared with the <A HREF="#clearmodulelist">ClearModuleList</A> directive.<P><HR> <h2><A name="allowoverride">AllowOverride directive</A></h2> <H2><A name="allowoverride">AllowOverride directive</A></H2> <!--%plaintext <?INDEX {\tt AllowOverride} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -249,7 +249,7 @@ Allow use of the directives controlling specific directory features <A HREF="mod_include.html#xbithack">XBitHack</A>). </DL><P><HR> <h2><A name="authname">AuthName directive</A></h2> <H2><A name="authname">AuthName directive</A></H2> <!--%plaintext <?INDEX {\tt AuthName} directive> --> <A HREF="directive-dict.html#Syntax" Loading @@ -276,7 +276,7 @@ It must be accompanied by <A HREF="#authtype">AuthType</A> and <A HREF="mod_auth.html#authuserfile">AuthUserFile</A> and <A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> to work.<P><HR> <h2><A name="authtype">AuthType directive</A></h2> <H2><A name="authtype">AuthType directive</A></H2> <!--%plaintext <?INDEX {\tt AuthType} directive> --> <A HREF="directive-dict.html#Syntax" Loading @@ -303,7 +303,7 @@ It must be accompanied by <A HREF="#authname">AuthName</A> and <A HREF="mod_auth.html#authuserfile">AuthUserFile</A> and <A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> to work.<P><HR> <h2><A name="bindaddress">BindAddress directive</A></h2> <H2><A name="bindaddress">BindAddress directive</A></H2> <!--%plaintext <?INDEX {\tt BindAddress} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -352,7 +352,7 @@ HREF="#virtualhost"><VirtualHost></A></CODE> sections. <HR> <h2><A name="clearmodulelist">ClearModuleList directive</A></h2> <H2><A name="clearmodulelist">ClearModuleList directive</A></H2> <!--%plaintext <?INDEX {\tt ClearModuleList} directive> --> <A HREF="directive-dict.html#Syntax" Loading @@ -375,7 +375,7 @@ The server comes with a built-in list of active modules. This directive clears the list. It is assumed that the list will then be re-populated using the <A HREF="#addmodule">AddModule</A> directive.<P><HR> <h2><A name="contentdigest">ContentDigest directive</A></h2> <H2><A name="contentdigest">ContentDigest directive</A></H2> <!--%plaintext <?INDEX {\tt ContentDigest} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -427,7 +427,7 @@ CGI scripts, and byte range responses do not have this header. <HR> <h2><A name="coredumpdirectory">CoreDumpDirectory directive</A></h2> <H2><A name="coredumpdirectory">CoreDumpDirectory directive</A></H2> <!--%plaintext <?INDEX {\tt CoreDumpDirectory} directive> --> <A HREF="directive-dict.html#Syntax" Loading @@ -453,7 +453,7 @@ the server runs as, core dumps won't normally get written. If you want a core dump for debugging, you can use this directive to place it in a different location.<P><HR> <h2><A name="defaulttype">DefaultType directive</A></h2> <H2><A name="defaulttype">DefaultType directive</A></H2> <!--%plaintext <?INDEX {\tt DefaultType} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -486,7 +486,7 @@ example: would be appropriate for a directory which contained many gif images with filenames missing the .gif extension.<P><HR> <h2><A name="directory"><Directory> directive</A></h2> <H2><A name="directory"><Directory> directive</A></H2> <!--%plaintext <?INDEX {\tt Directory} section directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -611,7 +611,7 @@ different sections are combined when a request is received <HR> <h2><A name="directorymatch"><DirectoryMatch></A></h2> <H2><A name="directorymatch"><DirectoryMatch></A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" Loading Loading @@ -651,7 +651,7 @@ different sections are combined when a request is received <HR> <h2><A NAME="documentroot">DocumentRoot directive</A></h2> <H2><A NAME="documentroot">DocumentRoot directive</A></H2> <!--%plaintext <?INDEX {\tt DocumentRoot} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -685,7 +685,7 @@ please avoid that. <P><HR> <h2><A name="errordocument">ErrorDocument directive</A></h2> <H2><A name="errordocument">ErrorDocument directive</A></H2> <!--%plaintext <?INDEX {\tt ErrorDocument} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -749,7 +749,7 @@ from the nature of the HTTP basic authentication scheme. <P>See Also: <A HREF="../custom-error.html">documentation of customizable responses.</A><P><HR> <h2><A name="errorlog">ErrorLog directive</A></h2> <H2><A name="errorlog">ErrorLog directive</A></H2> <!--%plaintext <?INDEX {\tt ErrorLog} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -782,7 +782,7 @@ than the user that starts the server. <P><HR> <h2><A name="files"><Files> directive</A></h2> <H2><A name="files"><Files> directive</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" Loading Loading @@ -844,7 +844,7 @@ different sections are combined when a request is received <HR> <h2><A name="filesmatch"><FilesMatch></A></h2> <H2><A name="filesmatch"><FilesMatch></A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" Loading Loading @@ -880,7 +880,7 @@ different sections are combined when a request is received <HR> <h2><A name="group">Group directive</A></h2> <H2><A name="group">Group directive</A></H2> <!--%plaintext <?INDEX {\tt Group} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -926,7 +926,7 @@ as the group specified in the main Group directive.<P> SECURITY: See <A HREF="#user">User</A> for a discussion of the security considerations.<P><HR> <h2><A name="hostnamelookups">HostNameLookups directive</A></h2> <H2><A name="hostnamelookups">HostNameLookups directive</A></H2> <!--%plaintext <?INDEX {\tt HostNameLookups} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -984,7 +984,7 @@ lookups can take considerable amounts of time. The utility <EM>logresolve</EM>, provided in the <EM>/support</EM> directory, can be used to look up host names from logged IP addresses offline.<P><HR> <h2><A name="identitycheck">IdentityCheck directive</A></h2> <H2><A name="identitycheck">IdentityCheck directive</A></H2> <!--%plaintext <?INDEX {\tt IdentityCheck} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1073,7 +1073,7 @@ simple multiple-module tests. <P> <HR> <h2><A name="include">Include directive</A></h2> <H2><A name="include">Include directive</A></H2> <STRONG>Syntax: (Apache 1.2)</STRONG> Include <EM>filename</EM><BR> <A HREF="directive-dict.html#Context" Loading @@ -1092,7 +1092,7 @@ This directive allows inclusion of other configuration files from within the ser <P> <HR> <h2><A name="keepalive">KeepAlive directive</A></h2> <H2><A name="keepalive">KeepAlive directive</A></H2> <STRONG>Syntax: (Apache 1.1)</STRONG> KeepAlive <EM>max-requests</EM><BR> <STRONG>Default: (Apache 1.1)</STRONG> <CODE>KeepAlive 5</CODE><BR> <STRONG>Syntax: (Apache 1.2)</STRONG> KeepAlive <EM>on/off</EM><BR> Loading Loading @@ -1124,7 +1124,7 @@ server resources. Set this to <CODE>0</CODE> to disable support. persistent connections, "Off" to disable. See also the <A HREF="#maxkeepaliverequests">MaxKeepAliveRequests</A> directive.</P><HR> <h2><A name="keepalivetimeout">KeepAliveTimeout directive</A></h2> <H2><A name="keepalivetimeout">KeepAliveTimeout directive</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" Loading Loading @@ -1154,7 +1154,7 @@ HREF="#timeout"><CODE>Timeout</CODE></A> directive applies. <HR> <h2><A name="limit"><Limit> directive</A></h2> <H2><A name="limit"><Limit> directive</A></H2> <!--%plaintext <?INDEX {\tt Limit} section directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1188,7 +1188,7 @@ OPTIONS. If GET is used it will also restrict HEAD requests. <STRONG>If you wish to limit all methods, do not include any <Limit> directive at all.</STRONG> <P><HR> <h2><A name="listen">Listen directive</A></h2> <H2><A name="listen">Listen directive</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" Loading Loading @@ -1282,7 +1282,7 @@ tuning is needed or desired, however on some systems it is desirable to increase this when under a TCP SYN flood attack. See the backlog parameter to the <CODE>listen(2)</CODE> system call.</P><HR> <h2><A name="location"><Location> directive</A></h2> <H2><A name="location"><Location> directive</A></H2> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1355,7 +1355,7 @@ different sections are combined when a request is received <HR> <h2><A name="locationmatch"><LocationMatch></A></h2> <H2><A name="locationmatch"><LocationMatch></A></H2> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1428,7 +1428,7 @@ server will try to create.<P> <P><HR> <h2><A name="maxclients">MaxClients directive</A></h2> <H2><A name="maxclients">MaxClients directive</A></H2> <!--%plaintext <?INDEX {\tt MaxClients} directive> --> <A HREF="directive-dict.html#Syntax" Loading @@ -1451,7 +1451,7 @@ The MaxClients directive sets the limit on the number of simultaneous requests that can be supported; not more than this number of child server processes will be created.<P><HR> <h2><A name="maxkeepaliverequests">MaxKeepAliveRequests directive</A></h2> <H2><A name="maxkeepaliverequests">MaxKeepAliveRequests directive</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" Loading Loading @@ -1480,7 +1480,7 @@ on. If it is set to "<CODE>0</CODE>", unlimited requests will be allowed. We recommend that this setting be kept to a high value for maximum server performance.</P><HR> <h2><A name="maxrequestsperchild">MaxRequestsPerChild directive</A></h2> <H2><A name="maxrequestsperchild">MaxRequestsPerChild directive</A></H2> <!--%plaintext <?INDEX {\tt MaxRequestsPerChild} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1512,7 +1512,7 @@ memory leakage; number of processes when the server load reduces. </UL><P><HR> <h2><A name="maxspareservers">MaxSpareServers directive</A></h2> <H2><A name="maxspareservers">MaxSpareServers directive</A></H2> <!--%plaintext <?INDEX {\tt MaxSpareServers} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1542,7 +1542,7 @@ Setting this parameter to a large number is almost always a bad idea.<P> See also <A HREF="#minspareservers">MinSpareServers</A> and <A HREF="#startservers">StartServers</A>.<P><HR> <h2><A name="minspareservers">MinSpareServers directive</A></h2> <H2><A name="minspareservers">MinSpareServers directive</A></H2> <!--%plaintext <?INDEX {\tt MinSpareServers} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1572,7 +1572,7 @@ Setting this parameter to a large number is almost always a bad idea.<P> See also <A HREF="#maxspareservers">MaxSpareServers</A> and <A HREF="#startservers">StartServers</A>.<P><HR> <h2><A name="namevirtualhost">NameVirtualHost directive</A></h2> <H2><A name="namevirtualhost">NameVirtualHost directive</A></H2> <!--%plaintext <?INDEX {\tt NameVirtualHost} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1612,7 +1612,7 @@ virtual hosts should be used, e.g. <STRONG>See also:</STRONG> <A HREF="../vhosts/index.html">Apache Virtual Host documentation</A> <h2><A name="options">Options directive</A></h2> <H2><A name="options">Options directive</A></H2> <!--%plaintext <?INDEX {\tt Options} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1711,7 +1711,7 @@ then the options <CODE>FollowSymLinks</CODE> and <CODE>Includes</CODE> are set for the /web/docs/spec directory. <HR> <h2><A name="pidfile">PidFile directive</A></h2> <H2><A name="pidfile">PidFile directive</A></H2> <!--%plaintext <?INDEX {\tt PidFile} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1745,7 +1745,7 @@ The PidFile is subject to the same warnings about log file placement and <P><HR> <h2><A name="port">Port directive</A></h2> <H2><A name="port">Port directive</A></H2> <!--%plaintext <?INDEX {\tt Port} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1815,7 +1815,7 @@ not to set <A HREF="#user">User</A> to root. If you run the server as root whilst handling connections, your site may be open to a major security attack.<P><HR> <h2><A name="require">require directive</A></h2> <H2><A name="require">require directive</A></H2> <!--%plaintext <?INDEX {\tt require} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1864,7 +1864,7 @@ Require must be accompanied by <A HREF="#authname">AuthName</A> and <A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> (to define users and groups) in order to work correctly.<P><HR> <h2><A name="resourceconfig">ResourceConfig directive</A></h2> <H2><A name="resourceconfig">ResourceConfig directive</A></H2> <!--%plaintext <?INDEX {\tt ResourceConfig} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1929,7 +1929,7 @@ CPU resource limits are expressed in seconds per process.<P> See also <A HREF="#rlimitmem">RLimitMEM</A> or <A HREF="#rlimitnproc">RLimitNPROC</A>.<P><HR> <h2><A name="rlimitmem">RLimitMEM directive</A></h2> <H2><A name="rlimitmem">RLimitMEM directive</A></H2> <!--%plaintext <?INDEX {\tt RLimitMEM} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1963,7 +1963,7 @@ Memory resource limits are expressed in bytes per process.<P> See also <A HREF="#rlimitcpu">RLimitCPU</A> or <A HREF="#rlimitnproc">RLimitNPROC</A>.<P><HR> <h2><A name="rlimitnproc">RLimitNPROC directive</A></h2> <H2><A name="rlimitnproc">RLimitNPROC directive</A></H2> <!--%plaintext <?INDEX {\tt RLimitNPROC} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2004,7 +2004,7 @@ See also <A HREF="#rlimitmem">RLimitMEM</A> or <A HREF="#rlimitcpu">RLimitCPU</A <P><HR> <h2><A name="satisfy">Satisfy directive</A></h2> <H2><A name="satisfy">Satisfy directive</A></H2> <!--%plaintext <?INDEX {\tt Satisfy} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2041,7 +2041,7 @@ clients from particular addresses in without prompting for a password. <P><HR> <h2><A name="scoreboardfile">ScoreBoardFile directive</A></h2> <H2><A name="scoreboardfile">ScoreBoardFile directive</A></H2> <!--%plaintext <?INDEX {\tt ScoreBoardFile} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2092,7 +2092,7 @@ release. (Prior to 1.3b4, <CODE>HAVE_SHMGET</CODE> would have sufficed.)<P> <P><HR> <h2><A name="sendbuffersize">SendBufferSize directive</A></h2> <H2><A name="sendbuffersize">SendBufferSize directive</A></H2> <!--%plaintext <?INDEX {\tt SendBufferSize} directive> --> <A HREF="directive-dict.html#Syntax" Loading @@ -2113,7 +2113,7 @@ speed high latency (i.e. 100ms or so, such as transcontinental fast pipes) <P><HR> <h2><A name="serveradmin">ServerAdmin directive</A></h2> <H2><A name="serveradmin">ServerAdmin directive</A></H2> <!--%plaintext <?INDEX {\tt ServerAdmin} directive> --> <A HREF="directive-dict.html#Syntax" Loading @@ -2135,7 +2135,7 @@ It may be worth setting up a dedicated address for this, e.g. <BLOCKQUOTE><CODE>ServerAdmin www-admin@foo.bar.com</CODE></BLOCKQUOTE> as users do not always mention that they are talking about the server!<P><HR> <h2><A name="serveralias">ServerAlias directive</A></h2> <H2><A name="serveralias">ServerAlias directive</A></H2> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2164,7 +2164,7 @@ with <HR> <h2><A name="servername">ServerName directive</A></h2> <H2><A name="servername">ServerName directive</A></H2> <!--%plaintext <?INDEX {\tt ServerName} directive> --> <A HREF="directive-dict.html#Syntax" Loading @@ -2190,7 +2190,7 @@ were <CODE>monster.wibble.com</CODE>.<P> <A HREF="../dns-caveats.html">DNS Issues</A></P> <HR> <h2><A name="serverpath">ServerPath directive</A></h2> <H2><A name="serverpath">ServerPath directive</A></H2> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2218,7 +2218,7 @@ use with <A HREF="../vhosts/index.html">name-based virtual hosts</A>. <HR> <h2><A name="serverroot">ServerRoot directive</A></h2> <H2><A name="serverroot">ServerRoot directive</A></H2> <!--%plaintext <?INDEX {\tt ServerRoot} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2248,48 +2248,48 @@ for information on how to properly set permissions on the ServerRoot.<P> <HR> <H2><A name="serversignature">ServerSignature directive</A></h2> <H2><A NAME="serversignature">ServerSignature directive</A></H2> <!--%plaintext <?INDEX {\tt ServerSignature} directive> --> <A HREF="directive-dict.html#Syntax" REL="Help" ><STRONG>Syntax:</STRONG></A> ServerSignature <em>Off | On | EMail</em><br> ><STRONG>Syntax:</STRONG></A> ServerSignature <EM>Off | On | EMail</EM><BR> <A HREF="directive-dict.html#Default" REL="Help" ><STRONG>Default:</STRONG></A> <code>ServerSignature Off</code><br> ><STRONG>Default:</STRONG></A> <CODE>ServerSignature Off</CODE><BR> <A HREF="directive-dict.html#Context" REL="Help" ><STRONG>Context:</STRONG></A> directory, .htaccess<br> ><STRONG>Context:</STRONG></A> directory, .htaccess<BR> <A HREF="directive-dict.html#Status" REL="Help" ><STRONG>Status:</STRONG></A> core<p> ><STRONG>Status:</STRONG></A> core<BR> <A HREF="directive-dict.html#Compatibility" REL="Help" ><STRONG>Compatibility:</STRONG></A> ServerSignature is only available in Apache 1.3 and later.<p> 1.3 and later.<P> The ServerSignature directive allows the configuration of a trailing footer line under server-generated documents (error messages, mod_proxy ftp directory listings, mod_info output, ...). The reason why you would want to enable such a footer line is that in a chain of proxies, the user often has no possibility to tell which of the chained servers actually produced a returned error message.<br> The <samp>Off</samp> setting, which is the default, suppresses the chained servers actually produced a returned error message.<BR> The <SAMP>Off</SAMP> setting, which is the default, suppresses the error line (and is therefore compatible with the behavior of Apache-1.2 and below). The <samp>On</samp> setting simply adds a Apache-1.2 and below). The <SAMP>On</SAMP> setting simply adds a line with the server version number and <A HREF="#servername">ServerName</A> of the serving virtual host, and the <samp>EMail</samp> setting additionally creates a "mailto:" the <SAMP>EMail</SAMP> setting additionally creates a "mailto:" reference to the <A HREF="#serveradmin">ServerAdmin</A> of the referenced document. <HR> <h2><A name="servertype">ServerType directive</A></h2> <H2><A name="servertype">ServerType directive</A></H2> <!--%plaintext <?INDEX {\tt ServerType} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2333,7 +2333,7 @@ it is far more efficient. The server is started once, and services all subsequent connections. If you intend running Apache to serve a busy site, standalone will probably be your only option.<P> <h2><A name="startservers">StartServers directive</A></h2> <H2><A name="startservers">StartServers directive</A></H2> <!--%plaintext <?INDEX {\tt StartServers} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2364,7 +2364,7 @@ on the load, there is usually little reason to adjust this parameter.<P> See also <A HREF="#minspareservers">MinSpareServers</A> and <A HREF="#maxspareservers">MaxSpareServers</A>.<P><HR> <h2><A name="threadsperchild">ThreadsPerChild</A></h2> <H2><A name="threadsperchild">ThreadsPerChild</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" Loading Loading @@ -2394,7 +2394,7 @@ with Windows <HR> <h2><A name="timeout">TimeOut directive</A></h2> <H2><A name="timeout">TimeOut directive</A></H2> <!--%plaintext <?INDEX {\tt TimeOut} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2433,7 +2433,7 @@ a packet is sent. <P><HR> <h2><A name="user">User directive</A></h2> <H2><A name="user">User directive</A></H2> <!--%plaintext <?INDEX {\tt User} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2484,7 +2484,7 @@ SECURITY: Don't set User (or <A HREF="#group">Group</A>) to <CODE>root</CODE> unless you know exactly what you are doing, and what the dangers are.<P><HR> <h2><A name="virtualhost"><VirtualHost> directive</A></h2> <H2><A name="virtualhost"><VirtualHost> directive</A></H2> <!--%plaintext <?INDEX {\tt VirtualHost} section directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading
docs/manual/mod/core.html +65 −65 Changes for docs/manual/mod/core.html: 65 added lines, 65 removed lines. Original line number Diff line number Diff line Loading @@ -84,7 +84,7 @@ always available. </UL> <HR> <h2><A name="accessconfig">AccessConfig directive</A></h2> <H2><A name="accessconfig">AccessConfig directive</A></H2> <!--%plaintext <?INDEX {\tt AccessConfig} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -113,7 +113,7 @@ Historically, this file only contained contain any server directive allowed in the <EM>server config</EM> context. <P><HR> <h2><A name="accessfilename">AccessFileName directive</A></h2> <H2><A name="accessfilename">AccessFileName directive</A></H2> <!--%plaintext <?INDEX {\tt AccessFileName} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -150,7 +150,7 @@ for directives, unless they have been disabled with AllowOverride None<BR> </Directory></CODE></BLOCKQUOTE><P><HR> <h2><A name="addmodule">AddModule directive</A></h2> <H2><A name="addmodule">AddModule directive</A></H2> <!--%plaintext <?INDEX {\tt AddModule} directive> --> <A HREF="directive-dict.html#Syntax" Loading @@ -175,7 +175,7 @@ server comes with a pre-loaded list of active modules; this list can be cleared with the <A HREF="#clearmodulelist">ClearModuleList</A> directive.<P><HR> <h2><A name="allowoverride">AllowOverride directive</A></h2> <H2><A name="allowoverride">AllowOverride directive</A></H2> <!--%plaintext <?INDEX {\tt AllowOverride} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -249,7 +249,7 @@ Allow use of the directives controlling specific directory features <A HREF="mod_include.html#xbithack">XBitHack</A>). </DL><P><HR> <h2><A name="authname">AuthName directive</A></h2> <H2><A name="authname">AuthName directive</A></H2> <!--%plaintext <?INDEX {\tt AuthName} directive> --> <A HREF="directive-dict.html#Syntax" Loading @@ -276,7 +276,7 @@ It must be accompanied by <A HREF="#authtype">AuthType</A> and <A HREF="mod_auth.html#authuserfile">AuthUserFile</A> and <A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> to work.<P><HR> <h2><A name="authtype">AuthType directive</A></h2> <H2><A name="authtype">AuthType directive</A></H2> <!--%plaintext <?INDEX {\tt AuthType} directive> --> <A HREF="directive-dict.html#Syntax" Loading @@ -303,7 +303,7 @@ It must be accompanied by <A HREF="#authname">AuthName</A> and <A HREF="mod_auth.html#authuserfile">AuthUserFile</A> and <A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> to work.<P><HR> <h2><A name="bindaddress">BindAddress directive</A></h2> <H2><A name="bindaddress">BindAddress directive</A></H2> <!--%plaintext <?INDEX {\tt BindAddress} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -352,7 +352,7 @@ HREF="#virtualhost"><VirtualHost></A></CODE> sections. <HR> <h2><A name="clearmodulelist">ClearModuleList directive</A></h2> <H2><A name="clearmodulelist">ClearModuleList directive</A></H2> <!--%plaintext <?INDEX {\tt ClearModuleList} directive> --> <A HREF="directive-dict.html#Syntax" Loading @@ -375,7 +375,7 @@ The server comes with a built-in list of active modules. This directive clears the list. It is assumed that the list will then be re-populated using the <A HREF="#addmodule">AddModule</A> directive.<P><HR> <h2><A name="contentdigest">ContentDigest directive</A></h2> <H2><A name="contentdigest">ContentDigest directive</A></H2> <!--%plaintext <?INDEX {\tt ContentDigest} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -427,7 +427,7 @@ CGI scripts, and byte range responses do not have this header. <HR> <h2><A name="coredumpdirectory">CoreDumpDirectory directive</A></h2> <H2><A name="coredumpdirectory">CoreDumpDirectory directive</A></H2> <!--%plaintext <?INDEX {\tt CoreDumpDirectory} directive> --> <A HREF="directive-dict.html#Syntax" Loading @@ -453,7 +453,7 @@ the server runs as, core dumps won't normally get written. If you want a core dump for debugging, you can use this directive to place it in a different location.<P><HR> <h2><A name="defaulttype">DefaultType directive</A></h2> <H2><A name="defaulttype">DefaultType directive</A></H2> <!--%plaintext <?INDEX {\tt DefaultType} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -486,7 +486,7 @@ example: would be appropriate for a directory which contained many gif images with filenames missing the .gif extension.<P><HR> <h2><A name="directory"><Directory> directive</A></h2> <H2><A name="directory"><Directory> directive</A></H2> <!--%plaintext <?INDEX {\tt Directory} section directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -611,7 +611,7 @@ different sections are combined when a request is received <HR> <h2><A name="directorymatch"><DirectoryMatch></A></h2> <H2><A name="directorymatch"><DirectoryMatch></A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" Loading Loading @@ -651,7 +651,7 @@ different sections are combined when a request is received <HR> <h2><A NAME="documentroot">DocumentRoot directive</A></h2> <H2><A NAME="documentroot">DocumentRoot directive</A></H2> <!--%plaintext <?INDEX {\tt DocumentRoot} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -685,7 +685,7 @@ please avoid that. <P><HR> <h2><A name="errordocument">ErrorDocument directive</A></h2> <H2><A name="errordocument">ErrorDocument directive</A></H2> <!--%plaintext <?INDEX {\tt ErrorDocument} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -749,7 +749,7 @@ from the nature of the HTTP basic authentication scheme. <P>See Also: <A HREF="../custom-error.html">documentation of customizable responses.</A><P><HR> <h2><A name="errorlog">ErrorLog directive</A></h2> <H2><A name="errorlog">ErrorLog directive</A></H2> <!--%plaintext <?INDEX {\tt ErrorLog} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -782,7 +782,7 @@ than the user that starts the server. <P><HR> <h2><A name="files"><Files> directive</A></h2> <H2><A name="files"><Files> directive</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" Loading Loading @@ -844,7 +844,7 @@ different sections are combined when a request is received <HR> <h2><A name="filesmatch"><FilesMatch></A></h2> <H2><A name="filesmatch"><FilesMatch></A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" Loading Loading @@ -880,7 +880,7 @@ different sections are combined when a request is received <HR> <h2><A name="group">Group directive</A></h2> <H2><A name="group">Group directive</A></H2> <!--%plaintext <?INDEX {\tt Group} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -926,7 +926,7 @@ as the group specified in the main Group directive.<P> SECURITY: See <A HREF="#user">User</A> for a discussion of the security considerations.<P><HR> <h2><A name="hostnamelookups">HostNameLookups directive</A></h2> <H2><A name="hostnamelookups">HostNameLookups directive</A></H2> <!--%plaintext <?INDEX {\tt HostNameLookups} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -984,7 +984,7 @@ lookups can take considerable amounts of time. The utility <EM>logresolve</EM>, provided in the <EM>/support</EM> directory, can be used to look up host names from logged IP addresses offline.<P><HR> <h2><A name="identitycheck">IdentityCheck directive</A></h2> <H2><A name="identitycheck">IdentityCheck directive</A></H2> <!--%plaintext <?INDEX {\tt IdentityCheck} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1073,7 +1073,7 @@ simple multiple-module tests. <P> <HR> <h2><A name="include">Include directive</A></h2> <H2><A name="include">Include directive</A></H2> <STRONG>Syntax: (Apache 1.2)</STRONG> Include <EM>filename</EM><BR> <A HREF="directive-dict.html#Context" Loading @@ -1092,7 +1092,7 @@ This directive allows inclusion of other configuration files from within the ser <P> <HR> <h2><A name="keepalive">KeepAlive directive</A></h2> <H2><A name="keepalive">KeepAlive directive</A></H2> <STRONG>Syntax: (Apache 1.1)</STRONG> KeepAlive <EM>max-requests</EM><BR> <STRONG>Default: (Apache 1.1)</STRONG> <CODE>KeepAlive 5</CODE><BR> <STRONG>Syntax: (Apache 1.2)</STRONG> KeepAlive <EM>on/off</EM><BR> Loading Loading @@ -1124,7 +1124,7 @@ server resources. Set this to <CODE>0</CODE> to disable support. persistent connections, "Off" to disable. See also the <A HREF="#maxkeepaliverequests">MaxKeepAliveRequests</A> directive.</P><HR> <h2><A name="keepalivetimeout">KeepAliveTimeout directive</A></h2> <H2><A name="keepalivetimeout">KeepAliveTimeout directive</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" Loading Loading @@ -1154,7 +1154,7 @@ HREF="#timeout"><CODE>Timeout</CODE></A> directive applies. <HR> <h2><A name="limit"><Limit> directive</A></h2> <H2><A name="limit"><Limit> directive</A></H2> <!--%plaintext <?INDEX {\tt Limit} section directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1188,7 +1188,7 @@ OPTIONS. If GET is used it will also restrict HEAD requests. <STRONG>If you wish to limit all methods, do not include any <Limit> directive at all.</STRONG> <P><HR> <h2><A name="listen">Listen directive</A></h2> <H2><A name="listen">Listen directive</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" Loading Loading @@ -1282,7 +1282,7 @@ tuning is needed or desired, however on some systems it is desirable to increase this when under a TCP SYN flood attack. See the backlog parameter to the <CODE>listen(2)</CODE> system call.</P><HR> <h2><A name="location"><Location> directive</A></h2> <H2><A name="location"><Location> directive</A></H2> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1355,7 +1355,7 @@ different sections are combined when a request is received <HR> <h2><A name="locationmatch"><LocationMatch></A></h2> <H2><A name="locationmatch"><LocationMatch></A></H2> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1428,7 +1428,7 @@ server will try to create.<P> <P><HR> <h2><A name="maxclients">MaxClients directive</A></h2> <H2><A name="maxclients">MaxClients directive</A></H2> <!--%plaintext <?INDEX {\tt MaxClients} directive> --> <A HREF="directive-dict.html#Syntax" Loading @@ -1451,7 +1451,7 @@ The MaxClients directive sets the limit on the number of simultaneous requests that can be supported; not more than this number of child server processes will be created.<P><HR> <h2><A name="maxkeepaliverequests">MaxKeepAliveRequests directive</A></h2> <H2><A name="maxkeepaliverequests">MaxKeepAliveRequests directive</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" Loading Loading @@ -1480,7 +1480,7 @@ on. If it is set to "<CODE>0</CODE>", unlimited requests will be allowed. We recommend that this setting be kept to a high value for maximum server performance.</P><HR> <h2><A name="maxrequestsperchild">MaxRequestsPerChild directive</A></h2> <H2><A name="maxrequestsperchild">MaxRequestsPerChild directive</A></H2> <!--%plaintext <?INDEX {\tt MaxRequestsPerChild} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1512,7 +1512,7 @@ memory leakage; number of processes when the server load reduces. </UL><P><HR> <h2><A name="maxspareservers">MaxSpareServers directive</A></h2> <H2><A name="maxspareservers">MaxSpareServers directive</A></H2> <!--%plaintext <?INDEX {\tt MaxSpareServers} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1542,7 +1542,7 @@ Setting this parameter to a large number is almost always a bad idea.<P> See also <A HREF="#minspareservers">MinSpareServers</A> and <A HREF="#startservers">StartServers</A>.<P><HR> <h2><A name="minspareservers">MinSpareServers directive</A></h2> <H2><A name="minspareservers">MinSpareServers directive</A></H2> <!--%plaintext <?INDEX {\tt MinSpareServers} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1572,7 +1572,7 @@ Setting this parameter to a large number is almost always a bad idea.<P> See also <A HREF="#maxspareservers">MaxSpareServers</A> and <A HREF="#startservers">StartServers</A>.<P><HR> <h2><A name="namevirtualhost">NameVirtualHost directive</A></h2> <H2><A name="namevirtualhost">NameVirtualHost directive</A></H2> <!--%plaintext <?INDEX {\tt NameVirtualHost} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1612,7 +1612,7 @@ virtual hosts should be used, e.g. <STRONG>See also:</STRONG> <A HREF="../vhosts/index.html">Apache Virtual Host documentation</A> <h2><A name="options">Options directive</A></h2> <H2><A name="options">Options directive</A></H2> <!--%plaintext <?INDEX {\tt Options} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1711,7 +1711,7 @@ then the options <CODE>FollowSymLinks</CODE> and <CODE>Includes</CODE> are set for the /web/docs/spec directory. <HR> <h2><A name="pidfile">PidFile directive</A></h2> <H2><A name="pidfile">PidFile directive</A></H2> <!--%plaintext <?INDEX {\tt PidFile} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1745,7 +1745,7 @@ The PidFile is subject to the same warnings about log file placement and <P><HR> <h2><A name="port">Port directive</A></h2> <H2><A name="port">Port directive</A></H2> <!--%plaintext <?INDEX {\tt Port} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1815,7 +1815,7 @@ not to set <A HREF="#user">User</A> to root. If you run the server as root whilst handling connections, your site may be open to a major security attack.<P><HR> <h2><A name="require">require directive</A></h2> <H2><A name="require">require directive</A></H2> <!--%plaintext <?INDEX {\tt require} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1864,7 +1864,7 @@ Require must be accompanied by <A HREF="#authname">AuthName</A> and <A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> (to define users and groups) in order to work correctly.<P><HR> <h2><A name="resourceconfig">ResourceConfig directive</A></h2> <H2><A name="resourceconfig">ResourceConfig directive</A></H2> <!--%plaintext <?INDEX {\tt ResourceConfig} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1929,7 +1929,7 @@ CPU resource limits are expressed in seconds per process.<P> See also <A HREF="#rlimitmem">RLimitMEM</A> or <A HREF="#rlimitnproc">RLimitNPROC</A>.<P><HR> <h2><A name="rlimitmem">RLimitMEM directive</A></h2> <H2><A name="rlimitmem">RLimitMEM directive</A></H2> <!--%plaintext <?INDEX {\tt RLimitMEM} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -1963,7 +1963,7 @@ Memory resource limits are expressed in bytes per process.<P> See also <A HREF="#rlimitcpu">RLimitCPU</A> or <A HREF="#rlimitnproc">RLimitNPROC</A>.<P><HR> <h2><A name="rlimitnproc">RLimitNPROC directive</A></h2> <H2><A name="rlimitnproc">RLimitNPROC directive</A></H2> <!--%plaintext <?INDEX {\tt RLimitNPROC} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2004,7 +2004,7 @@ See also <A HREF="#rlimitmem">RLimitMEM</A> or <A HREF="#rlimitcpu">RLimitCPU</A <P><HR> <h2><A name="satisfy">Satisfy directive</A></h2> <H2><A name="satisfy">Satisfy directive</A></H2> <!--%plaintext <?INDEX {\tt Satisfy} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2041,7 +2041,7 @@ clients from particular addresses in without prompting for a password. <P><HR> <h2><A name="scoreboardfile">ScoreBoardFile directive</A></h2> <H2><A name="scoreboardfile">ScoreBoardFile directive</A></H2> <!--%plaintext <?INDEX {\tt ScoreBoardFile} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2092,7 +2092,7 @@ release. (Prior to 1.3b4, <CODE>HAVE_SHMGET</CODE> would have sufficed.)<P> <P><HR> <h2><A name="sendbuffersize">SendBufferSize directive</A></h2> <H2><A name="sendbuffersize">SendBufferSize directive</A></H2> <!--%plaintext <?INDEX {\tt SendBufferSize} directive> --> <A HREF="directive-dict.html#Syntax" Loading @@ -2113,7 +2113,7 @@ speed high latency (i.e. 100ms or so, such as transcontinental fast pipes) <P><HR> <h2><A name="serveradmin">ServerAdmin directive</A></h2> <H2><A name="serveradmin">ServerAdmin directive</A></H2> <!--%plaintext <?INDEX {\tt ServerAdmin} directive> --> <A HREF="directive-dict.html#Syntax" Loading @@ -2135,7 +2135,7 @@ It may be worth setting up a dedicated address for this, e.g. <BLOCKQUOTE><CODE>ServerAdmin www-admin@foo.bar.com</CODE></BLOCKQUOTE> as users do not always mention that they are talking about the server!<P><HR> <h2><A name="serveralias">ServerAlias directive</A></h2> <H2><A name="serveralias">ServerAlias directive</A></H2> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2164,7 +2164,7 @@ with <HR> <h2><A name="servername">ServerName directive</A></h2> <H2><A name="servername">ServerName directive</A></H2> <!--%plaintext <?INDEX {\tt ServerName} directive> --> <A HREF="directive-dict.html#Syntax" Loading @@ -2190,7 +2190,7 @@ were <CODE>monster.wibble.com</CODE>.<P> <A HREF="../dns-caveats.html">DNS Issues</A></P> <HR> <h2><A name="serverpath">ServerPath directive</A></h2> <H2><A name="serverpath">ServerPath directive</A></H2> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2218,7 +2218,7 @@ use with <A HREF="../vhosts/index.html">name-based virtual hosts</A>. <HR> <h2><A name="serverroot">ServerRoot directive</A></h2> <H2><A name="serverroot">ServerRoot directive</A></H2> <!--%plaintext <?INDEX {\tt ServerRoot} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2248,48 +2248,48 @@ for information on how to properly set permissions on the ServerRoot.<P> <HR> <H2><A name="serversignature">ServerSignature directive</A></h2> <H2><A NAME="serversignature">ServerSignature directive</A></H2> <!--%plaintext <?INDEX {\tt ServerSignature} directive> --> <A HREF="directive-dict.html#Syntax" REL="Help" ><STRONG>Syntax:</STRONG></A> ServerSignature <em>Off | On | EMail</em><br> ><STRONG>Syntax:</STRONG></A> ServerSignature <EM>Off | On | EMail</EM><BR> <A HREF="directive-dict.html#Default" REL="Help" ><STRONG>Default:</STRONG></A> <code>ServerSignature Off</code><br> ><STRONG>Default:</STRONG></A> <CODE>ServerSignature Off</CODE><BR> <A HREF="directive-dict.html#Context" REL="Help" ><STRONG>Context:</STRONG></A> directory, .htaccess<br> ><STRONG>Context:</STRONG></A> directory, .htaccess<BR> <A HREF="directive-dict.html#Status" REL="Help" ><STRONG>Status:</STRONG></A> core<p> ><STRONG>Status:</STRONG></A> core<BR> <A HREF="directive-dict.html#Compatibility" REL="Help" ><STRONG>Compatibility:</STRONG></A> ServerSignature is only available in Apache 1.3 and later.<p> 1.3 and later.<P> The ServerSignature directive allows the configuration of a trailing footer line under server-generated documents (error messages, mod_proxy ftp directory listings, mod_info output, ...). The reason why you would want to enable such a footer line is that in a chain of proxies, the user often has no possibility to tell which of the chained servers actually produced a returned error message.<br> The <samp>Off</samp> setting, which is the default, suppresses the chained servers actually produced a returned error message.<BR> The <SAMP>Off</SAMP> setting, which is the default, suppresses the error line (and is therefore compatible with the behavior of Apache-1.2 and below). The <samp>On</samp> setting simply adds a Apache-1.2 and below). The <SAMP>On</SAMP> setting simply adds a line with the server version number and <A HREF="#servername">ServerName</A> of the serving virtual host, and the <samp>EMail</samp> setting additionally creates a "mailto:" the <SAMP>EMail</SAMP> setting additionally creates a "mailto:" reference to the <A HREF="#serveradmin">ServerAdmin</A> of the referenced document. <HR> <h2><A name="servertype">ServerType directive</A></h2> <H2><A name="servertype">ServerType directive</A></H2> <!--%plaintext <?INDEX {\tt ServerType} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2333,7 +2333,7 @@ it is far more efficient. The server is started once, and services all subsequent connections. If you intend running Apache to serve a busy site, standalone will probably be your only option.<P> <h2><A name="startservers">StartServers directive</A></h2> <H2><A name="startservers">StartServers directive</A></H2> <!--%plaintext <?INDEX {\tt StartServers} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2364,7 +2364,7 @@ on the load, there is usually little reason to adjust this parameter.<P> See also <A HREF="#minspareservers">MinSpareServers</A> and <A HREF="#maxspareservers">MaxSpareServers</A>.<P><HR> <h2><A name="threadsperchild">ThreadsPerChild</A></h2> <H2><A name="threadsperchild">ThreadsPerChild</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" Loading Loading @@ -2394,7 +2394,7 @@ with Windows <HR> <h2><A name="timeout">TimeOut directive</A></h2> <H2><A name="timeout">TimeOut directive</A></H2> <!--%plaintext <?INDEX {\tt TimeOut} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2433,7 +2433,7 @@ a packet is sent. <P><HR> <h2><A name="user">User directive</A></h2> <H2><A name="user">User directive</A></H2> <!--%plaintext <?INDEX {\tt User} directive> --> <A HREF="directive-dict.html#Syntax" Loading Loading @@ -2484,7 +2484,7 @@ SECURITY: Don't set User (or <A HREF="#group">Group</A>) to <CODE>root</CODE> unless you know exactly what you are doing, and what the dangers are.<P><HR> <h2><A name="virtualhost"><VirtualHost> directive</A></h2> <H2><A name="virtualhost"><VirtualHost> directive</A></H2> <!--%plaintext <?INDEX {\tt VirtualHost} section directive> --> <A HREF="directive-dict.html#Syntax" Loading