coar 97/07/06 07:54:50
Modified: htdocs/manual man-template.html new_features_1_1.html new_features_1_2.html new_features_1_3.html vhosts-in-depth.html htdocs/manual/misc API.html FAQ.html known_bugs.html htdocs/manual/mod core.html Log: Numerous HTML cleanups, largely courtesy of weblint (thanx, Marc!). Also brought core.html into some H2 naming consistency, and cleaned up man-template.html. Much, much more to come.. Revision Changes Path 1.7 +65 -53 apache/htdocs/manual/man-template.html Index: man-template.html =================================================================== RCS file: /export/home/cvs/apache/htdocs/manual/man-template.html,v retrieving revision 1.6 retrieving revision 1.7 diff -C3 -r1.6 -r1.7 *** man-template.html 1997/06/04 11:07:50 1.6 --- man-template.html 1997/07/06 14:54:44 1.7 *************** *** 1,69 **** <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <HTML> ! <HEAD> ! <TITLE>Apache module mod_foobar</TITLE> ! </HEAD> ! <!-- read and delete all blockquotes, and this comment --> - <!-- Background white, links blue (unvisited), navy (visited), red (active) --> ! <BODY ! BGCOLOR="#FFFFFF" ! TEXT="#000000" ! LINK="#0000FF" ! VLINK="#000080" ! ALINK="#FF0000" ! > <!--#include virtual="header.html" --> ! <H1 ALIGN="CENTER">Module mod_foobar</h1> ! ! <blockquote><em>Add this file as a link in modules.html</em></blockquote> ! ! This module is contained in the <code>mod_foobar.c</code> file, and ! <strong>is/is not</strong> compiled in by default. It provides for ! <strong>the foobar feature</strong>. Any document with the mime type ! <code>foo/bar</code> will be processed by this module. ! ! <blockquote><em>Add the magic mime type to the list in ! magic_types.html</em></blockquote> ! ! <h2>Summary</h2> ! General module documentation here. ! <h2>Directives</h2> ! <ul> ! <li><A HREF="#adirective">ADirective</A> ! </ul> ! <blockquote><em>Add these directives to the list in ! directives.html</em></blockquote> ! <hr> ! <h2><A name="adirective">ADirective</A></h2> ! <strong>Syntax:</strong> ADirective <em>some args</em><br> ! <strong>Default:</strong> <code>ADirective default value</code><br> ! <strong>Context:</strong> context-list<br> ! <blockquote><em>context-list is where this directive can appear; ! allowed: server config, virtual host, directory, .htaccess</em></blockquote> ! ! <strong>Override:</strong> override<br> ! ! <blockquote><em>required if the directive is allowed in .htaccess files; ! the AllowOverride option that allows the directive.</em></blockquote> ! ! <strong>Status:</strong> status<br> ! ! <blockquote><em>Core if in core apache, Base if in one of the standard modules, Extension if in an extension module (not compiled in by default) ! or Experimental</em></blockquote> ! <strong>Module:</strong> mod_foobar<p> ! The ADirective directive does something. <!--#include virtual="footer.html" --> ! </BODY> </HTML> - --- 1,81 ---- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <HTML> ! <HEAD> ! <TITLE>Apache module mod_foobar</TITLE> ! </HEAD> <!-- read and delete all blockquotes, and this comment --> <!-- Background white, links blue (unvisited), navy (visited), red (active) --> ! <BODY ! BGCOLOR="#FFFFFF" ! TEXT="#000000" ! LINK="#0000FF" ! VLINK="#000080" ! ALINK="#FF0000" ! > <!--#include virtual="header.html" --> ! <H1 ALIGN="CENTER">Module mod_foobar</h1> ! <BLOCKQUOTE><EM>Add this file as a link in modules.html</EM></BLOCKQUOTE> ! <P> ! This module is contained in the <code>mod_foobar.c</code> file, and ! <STRONG>is/is not</STRONG> compiled in by default. It provides for ! <STRONG>the foobar feature</STRONG>. Any document with the mime type ! <SAMP>foo/bar</SAMP> will be processed by this module. ! </P> ! ! <BLOCKQUOTE><EM>Add the magic mime type to the list in ! magic_types.html</EM></BLOCKQUOTE> ! ! <H2>Summary</H2> ! <P> ! <EM>General module documentation here.</EM> ! </P> ! ! <H2>Directives</H2> ! <UL> ! <LI><A HREF="#adirective">ADirective</A> ! </LI> ! </UL> ! ! <BLOCKQUOTE><EM>Add these directives to the list in ! directives.html</EM></BLOCKQUOTE> ! ! <HR> ! ! <H2><A NAME="adirective">ADirective directive</A></H2> ! <P> ! <STRONG>Syntax:</STRONG> ADirective <EM>some args</EM> ! <BR> ! <STRONG>Default:</STRONG> <SAMP>ADirective default value</SAMP> ! <BR> ! <STRONG>Context:</STRONG> context-list ! <BR> ! ! <BLOCKQUOTE><EM>context-list is where this directive can appear; ! allowed: server config, virtual host, directory, .htaccess</EM></BLOCKQUOTE> ! ! <STRONG>Override:</STRONG> override ! <BR> ! <BLOCKQUOTE><EM>required if the directive is allowed in .htaccess files; ! the AllowOverride option that allows the directive.</EM></BLOCKQUOTE> ! <STRONG>Status:</STRONG> status ! <BR> ! <BLOCKQUOTE><EM>Core if in core apache, Base if in one of the standard modules, Extension if in an extension module (not compiled in by default) ! or Experimental</EM></BLOCKQUOTE> ! <STRONG>Module:</STRONG> mod_foobar ! </P> ! <P> ! The ADirective directive does something. ! </P> ! <HR> <!--#include virtual="footer.html" --> ! </BODY> </HTML> 1.8 +1 -1 apache/htdocs/manual/new_features_1_1.html Index: new_features_1_1.html =================================================================== RCS file: /export/home/cvs/apache/htdocs/manual/new_features_1_1.html,v retrieving revision 1.7 retrieving revision 1.8 diff -C3 -r1.7 -r1.8 *** new_features_1_1.html 1997/06/04 11:07:50 1.7 --- new_features_1_1.html 1997/07/06 14:54:44 1.8 *************** *** 68,74 **** <A HREF="http://www.apache.org/status">the status of the www.apache.org server</A>. ! <li><b><a href="mod/mod_info.html">Server Information Module</a></b></br> This module gives a plethora of information about the other modules installed, their directives, and their configurations. It is extremely helpful in debugging configuration problems. For an --- 68,74 ---- <A HREF="http://www.apache.org/status">the status of the www.apache.org server</A>. ! <li><b><a href="mod/mod_info.html">Server Information Module</a></b> This module gives a plethora of information about the other modules installed, their directives, and their configurations. It is extremely helpful in debugging configuration problems. For an 1.31 +2 -2 apache/htdocs/manual/new_features_1_2.html Index: new_features_1_2.html =================================================================== RCS file: /export/home/cvs/apache/htdocs/manual/new_features_1_2.html,v retrieving revision 1.30 retrieving revision 1.31 diff -C3 -r1.30 -r1.31 *** new_features_1_2.html 1997/06/24 18:39:31 1.30 --- new_features_1_2.html 1997/07/06 14:54:44 1.31 *************** *** 45,51 **** <ul> ! <li><b><xa href="http11.html">HTTP/1.1 Compliance</a></b> [Documentation to be written]<br> Aside from the optional proxy module (which operates as HTTP/1.0), Apache is conditionally compliant with the HTTP/1.1 proposed standard, --- 45,51 ---- <ul> ! <li><b><a href="http11.html">HTTP/1.1 Compliance</a></b> [Documentation to be written]<br> Aside from the optional proxy module (which operates as HTTP/1.0), Apache is conditionally compliant with the HTTP/1.1 proposed standard, *************** *** 162,168 **** A new <code><IfModule></code> section allows directives to be enabled only if a given module is loaded into the server. ! <li><b><xa href="ncsa_auth.html">Authorization Directives Now Use NCSA-style Syntax</a></b><br> The <a href="mod/mod_auth.html#authuserfile">AuthUserFile</a>, <a --- 162,168 ---- A new <code><IfModule></code> section allows directives to be enabled only if a given module is loaded into the server. ! <li><b><a href="ncsa_auth.html">Authorization Directives Now Use NCSA-style Syntax</a></b><br> The <a href="mod/mod_auth.html#authuserfile">AuthUserFile</a>, <a 1.2 +3 -3 apache/htdocs/manual/new_features_1_3.html Index: new_features_1_3.html =================================================================== RCS file: /export/home/cvs/apache/htdocs/manual/new_features_1_3.html,v retrieving revision 1.1 retrieving revision 1.2 diff -C3 -r1.1 -r1.2 *** new_features_1_3.html 1997/06/23 07:06:59 1.1 --- new_features_1_3.html 1997/07/06 14:54:45 1.2 *************** *** 19,26 **** functionality. Because the core code has changed so significantly, there are certain liberties that earlier versions of Apache (and the NCSA daemon) took that recent Apache versions are ! pickier about - please check the <a ! href="misc/compat_notes.html">compatibility notes</a> if you have any problems.</p> <hr> --- 19,26 ---- functionality. Because the core code has changed so significantly, there are certain liberties that earlier versions of Apache (and the NCSA daemon) took that recent Apache versions are ! pickier about - please check the ! <a href="misc/compat_notes.html">compatibility notes</a> if you have any problems.</p> <hr> *************** *** 30,36 **** <ul> ! <li><b><xa href="nt.html">Support for Windows NT/95</a></b> [Documentation to be written]<br> Apache now supports the Windows NT and Windows 95 operating systems, --- 30,36 ---- <ul> ! <li><b><a href="nt.html">Support for Windows NT/95</a></b> [Documentation to be written]<br> Apache now supports the Windows NT and Windows 95 operating systems, 1.11 +22 -16 apache/htdocs/manual/vhosts-in-depth.html Index: vhosts-in-depth.html =================================================================== RCS file: /export/home/cvs/apache/htdocs/manual/vhosts-in-depth.html,v retrieving revision 1.10 retrieving revision 1.11 diff -C3 -r1.10 -r1.11 *** vhosts-in-depth.html 1997/07/02 18:07:16 1.10 --- vhosts-in-depth.html 1997/07/06 14:54:45 1.11 *************** *** 273,278 **** --- 273,279 ---- "main IP address". You essentially have to create a bogus <code>ServerName</code> for the main_server that does not match the machine's IPs. + <P> <li>During the scans in both <code>check_hostalias</code> and <code>check_serverpath</code> no check is made that the vhost being *************** *** 281,288 **** because the scan starts in the vhost list at the first vhost that matched the local IP address of the connection, not all IP-based vhosts can be matched. ! ! <p>Consider the config file above with three vhosts A, B, C. Suppose that B is a named-based vhost, and A and C are IP-based vhosts. If a request comes in on B or C's address containing a header "<SAMP>Host: A</SAMP>" then --- 282,289 ---- because the scan starts in the vhost list at the first vhost that matched the local IP address of the connection, not all IP-based vhosts can be matched. ! <p> ! Consider the config file above with three vhosts A, B, C. Suppose that B is a named-based vhost, and A and C are IP-based vhosts. If a request comes in on B or C's address containing a header "<SAMP>Host: A</SAMP>" then *************** *** 296,303 **** vhosts. During the <code>find_virtual_server</code> phase above no named-based vhost will be matched, so the main_server will remain the connection vhost. Then scans will cover all vhosts in the vhost list. ! ! <p>If you do have a <SAMP>_default_</SAMP> vhost, then you cannot place named-based vhosts after it in the config. This is because on any connection to the main server IPs the connection vhost will always be the <SAMP>_default_</SAMP> vhost since none of the name-based are --- 297,304 ---- vhosts. During the <code>find_virtual_server</code> phase above no named-based vhost will be matched, so the main_server will remain the connection vhost. Then scans will cover all vhosts in the vhost list. ! <p> ! If you do have a <SAMP>_default_</SAMP> vhost, then you cannot place named-based vhosts after it in the config. This is because on any connection to the main server IPs the connection vhost will always be the <SAMP>_default_</SAMP> vhost since none of the name-based are *************** *** 308,329 **** directives because it will force your server to rely on DNS to boot. Furthermore it poses a security threat if you do not control the DNS for all the domains listed. ! <a href="dns-caveats.html"> ! There's more information ! available on this and the next two topics</a>.</p> <li><code>ServerName</code> should always be set for each vhost. Otherwise ! A DNS lookup is required for each vhost.</p> <li>A DNS lookup is always required for the main_server's <code>ServerName</code> (or to generate that if it isn't specified ! in the config).</p> <li>If a <code>ServerPath</code> directive exists which is a prefix of another <code>ServerPath</code> directive that appears later in the configuration file, then the former will always be matched and the latter will never be matched. (That is assuming that no ! Host header was available to disambiguate the two.)</p> <li>If a vhost that would otherwise be a name-vhost includes a <code>Port</code> statement that doesn't match the main_server --- 309,333 ---- directives because it will force your server to rely on DNS to boot. Furthermore it poses a security threat if you do not control the DNS for all the domains listed. ! <a href="dns-caveats.html">There's more information ! available on this and the next two topics</a>. ! <p> <li><code>ServerName</code> should always be set for each vhost. Otherwise ! A DNS lookup is required for each vhost. ! <p> <li>A DNS lookup is always required for the main_server's <code>ServerName</code> (or to generate that if it isn't specified ! in the config). ! <p> <li>If a <code>ServerPath</code> directive exists which is a prefix of another <code>ServerPath</code> directive that appears later in the configuration file, then the former will always be matched and the latter will never be matched. (That is assuming that no ! Host header was available to disambiguate the two.) ! <p> <li>If a vhost that would otherwise be a name-vhost includes a <code>Port</code> statement that doesn't match the main_server *************** *** 333,349 **** to the port of the main_server) as the connection vhost. Then <code>check_hostalias</code> will refuse to check any other name-based vhost because of the port mismatch. The result is that the vhost ! will steal all hits going to the main_server address.</p> <li>If two IP-based vhosts have an address in common, the vhost appearing later in the file is always matched. Such a thing might happen inadvertently. If the config has name-based vhosts and for some reason the main_server <code>ServerName</code> resolves to the wrong address then all the name-based vhosts will be parsed as ip-based vhosts. ! Then the last of them will steal all the hits.</P> <li>The last name-based vhost in the config is always matched for any hit ! which doesn't match one of the other name-based vhosts.</p> </ul> --- 337,355 ---- to the port of the main_server) as the connection vhost. Then <code>check_hostalias</code> will refuse to check any other name-based vhost because of the port mismatch. The result is that the vhost ! will steal all hits going to the main_server address. ! <p> <li>If two IP-based vhosts have an address in common, the vhost appearing later in the file is always matched. Such a thing might happen inadvertently. If the config has name-based vhosts and for some reason the main_server <code>ServerName</code> resolves to the wrong address then all the name-based vhosts will be parsed as ip-based vhosts. ! Then the last of them will steal all the hits. ! <P> <li>The last name-based vhost in the config is always matched for any hit ! which doesn't match one of the other name-based vhosts. </ul> *************** *** 373,382 **** "ServerPath /abcdef"). <p> ! <li>Do not use <i>port-based</i> vhosts in the same server as name-based vhosts. A loose definition for port-based is a vhost which ! is determined by the port on the server (<em>i.e.</em> one server with ! ports 8000, 8080, and 80 all of which have different configurations). <p> </ul> --- 379,388 ---- "ServerPath /abcdef"). <p> ! <li>Do not use <EM>port-based</EM> vhosts in the same server as name-based vhosts. A loose definition for port-based is a vhost which ! is determined by the port on the server (<em>i.e.</em>, one server with ! ports 8000, 8080, and 80 - all of which have different configurations). <p> </ul> 1.9 +12 -12 apache/htdocs/manual/misc/API.html Index: API.html =================================================================== RCS file: /export/home/cvs/apache/htdocs/manual/misc/API.html,v retrieving revision 1.8 retrieving revision 1.9 diff -C3 -r1.8 -r1.9 *** API.html 1997/06/04 11:42:55 1.8 --- API.html 1997/07/06 14:54:47 1.9 *************** *** 561,567 **** struct my_structure *foo; ... ! foo = (foo *)palloc (r->pool, sizeof(my_structure)); } </pre> --- 561,567 ---- struct my_structure *foo; ... ! foo = (foo *)palloc (r->pool, sizeof(my_structure)); } </pre> *************** *** 598,604 **** of the strings, as a unit; for instance: <pre> ! pstrcat (r->pool, "foo", "/", "bar", NULL); </pre> returns a pointer to 8 bytes worth of memory, initialized to --- 598,604 ---- of the strings, as a unit; for instance: <pre> ! pstrcat (r->pool, "foo", "/", "bar", NULL); </pre> returns a pointer to 8 bytes worth of memory, initialized to *************** *** 614,620 **** <pre> ... ! FILE *f = pfopen (r->pool, r->filename, "r"); if (f == NULL) { ... } else { ... } </pre> --- 614,620 ---- <pre> ... ! FILE *f = pfopen (r->pool, r->filename, "r"); if (f == NULL) { ... } else { ... } </pre> *************** *** 933,954 **** int find_ct(request_rec *r) { int i; ! char *fn = pstrdup (r->pool, r->filename); mime_dir_config *conf = (mime_dir_config *) ! get_module_config(r->per_dir_config, &mime_module); char *type; ! if (S_ISDIR(r->finfo.st_mode)) { ! r->content_type = DIR_MAGIC_TYPE; return OK; } if((i=rind(fn,'.')) < 0) return DECLINED; ++i; ! if ((type = table_get (conf->encoding_types, &fn[i]))) { ! r->content_encoding = type; /* go back to previous extension to try to use it as a type */ --- 933,954 ---- int find_ct(request_rec *r) { int i; ! char *fn = pstrdup (r->pool, r->filename); mime_dir_config *conf = (mime_dir_config *) ! get_module_config(r->per_dir_config, &mime_module); char *type; ! if (S_ISDIR(r->finfo.st_mode)) { ! r->content_type = DIR_MAGIC_TYPE; return OK; } if((i=rind(fn,'.')) < 0) return DECLINED; ++i; ! if ((type = table_get (conf->encoding_types, &fn[i]))) { ! r->content_encoding = type; /* go back to previous extension to try to use it as a type */ *************** *** 957,965 **** ++i; } ! if ((type = table_get (conf->forced_types, &fn[i]))) { ! r->content_type = type; } return OK; --- 957,965 ---- ++i; } ! if ((type = table_get (conf->forced_types, &fn[i]))) { ! r->content_type = type; } return OK; *************** *** 989,995 **** <pre> char *add_redirect(cmd_parms *cmd, void *dummy, char *f, char *url) { ! server_rec *s = cmd->server; alias_server_conf *conf = (alias_server_conf *) get_module_config(s->module_config,&alias_module); alias_entry *new = push_array (conf->redirects); --- 989,995 ---- <pre> char *add_redirect(cmd_parms *cmd, void *dummy, char *f, char *url) { ! server_rec *s = cmd->server; alias_server_conf *conf = (alias_server_conf *) get_module_config(s->module_config,&alias_module); alias_entry *new = push_array (conf->redirects); 1.81 +1 -3 apache/htdocs/manual/misc/FAQ.html Index: FAQ.html =================================================================== RCS file: /export/home/cvs/apache/htdocs/manual/misc/FAQ.html,v retrieving revision 1.80 retrieving revision 1.81 diff -C3 -r1.80 -r1.81 *** FAQ.html 1997/07/05 17:33:34 1.80 --- FAQ.html 1997/07/06 14:54:47 1.81 *************** *** 15,21 **** <!--#include virtual="header.html" --> <H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1> <P> ! $Revision: 1.80 $ ($Date: 1997/07/05 17:33:34 $) </P> <P> The latest version of this FAQ is always available from the main --- 15,21 ---- <!--#include virtual="header.html" --> <H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1> <P> ! $Revision: 1.81 $ ($Date: 1997/07/06 14:54:47 $) </P> <P> The latest version of this FAQ is always available from the main *************** *** 227,234 **** <HR> <H2>The Answers</H2> - <P> - </P> <H3> Background </H3> --- 227,232 ---- 1.22 +4 -4 apache/htdocs/manual/misc/known_bugs.html Index: known_bugs.html =================================================================== RCS file: /export/home/cvs/apache/htdocs/manual/misc/known_bugs.html,v retrieving revision 1.21 retrieving revision 1.22 diff -C3 -r1.21 -r1.22 *** known_bugs.html 1997/06/30 21:42:27 1.21 --- known_bugs.html 1997/07/06 14:54:48 1.22 *************** *** 27,34 **** <H2>Apache 1.2 Bugs</H2> ! <OL><a name="listenbug"></a> ! <LI>On some architectures if your configuration uses multiple <a href="../mod/core.html#listen">Listen</a> directives then it is possible that the server will starve one of the sockets while serving hits on another. The work-around is to add --- 27,35 ---- <H2>Apache 1.2 Bugs</H2> ! <OL> ! <LI><a name="listenbug">On some architectures</A> ! if your configuration uses multiple <a href="../mod/core.html#listen">Listen</a> directives then it is possible that the server will starve one of the sockets while serving hits on another. The work-around is to add *************** *** 43,51 **** <a href="http://www.apache.org/bugdb.cgi/full/467">PR#467</a>. <P></LI> - <a name="cnegbug"></a> <LI><b>Fixed in 1.2.1.</b> ! Apache's <A HREF="../content-negotiation.html">Content Negotiation</A> should pick the smallest variant if there are several that are equally acceptable. A bug in 1.2 means it no longer does this unless all the variants have character sets. --- 44,51 ---- <a href="http://www.apache.org/bugdb.cgi/full/467">PR#467</a>. <P></LI> <LI><b>Fixed in 1.2.1.</b> ! <a name="cnegbug">Apache's</A> <A HREF="../content-negotiation.html">Content Negotiation</A> should pick the smallest variant if there are several that are equally acceptable. A bug in 1.2 means it no longer does this unless all the variants have character sets. 1.61 +54 -55 apache/htdocs/manual/mod/core.html Index: core.html =================================================================== RCS file: /export/home/cvs/apache/htdocs/manual/mod/core.html,v retrieving revision 1.60 retrieving revision 1.61 diff -C3 -r1.60 -r1.61 *** core.html 1997/06/29 01:14:15 1.60 --- core.html 1997/07/06 14:54:49 1.61 *************** *** 15,25 **** <!--#include virtual="header.html" --> <H1 ALIGN="CENTER">Apache Core Features</h1> ! These configuration parameters control the core Apache features, and are always available. ! ! <ul> <li><A HREF="#accessconfig">AccessConfig</A> <li><A HREF="#accessfilename">AccessFileName</A> --- 15,25 ---- <!--#include virtual="header.html" --> <H1 ALIGN="CENTER">Apache Core Features</h1> ! <P> These configuration parameters control the core Apache features, and are always available. ! </P> ! <H2>Directives</H2> <ul> <li><A HREF="#accessconfig">AccessConfig</A> <li><A HREF="#accessfilename">AccessFileName</A> *************** *** 75,81 **** </ul> <hr> ! <A name="accessconfig"><h2>AccessConfig directive</h2></A> <!--%plaintext <?INDEX {\tt AccessConfig} directive> --> <strong>Syntax:</strong> AccessConfig <em>filename</em><br> <strong>Default:</strong> <code>AccessConfig conf/access.conf</code><br> --- 75,81 ---- </ul> <hr> ! <h2><A name="accessconfig">AccessConfig directive</A></h2> <!--%plaintext <?INDEX {\tt AccessConfig} directive> --> <strong>Syntax:</strong> AccessConfig <em>filename</em><br> <strong>Default:</strong> <code>AccessConfig conf/access.conf</code><br> *************** *** 92,98 **** contain any server directive allowed in the <em>server config</em> context. <p><hr> ! <A name="accessfilename"><h2>AccessFileName directive</h2></A> <!--%plaintext <?INDEX {\tt AccessFileName} directive> --> <strong>Syntax:</strong> AccessFileName <em>filename</em><br> <strong>Default:</strong> <code>AccessFileName .htaccess</code><br> --- 92,98 ---- contain any server directive allowed in the <em>server config</em> context. <p><hr> ! <h2><A name="accessfilename">AccessFileName directive</A></h2> <!--%plaintext <?INDEX {\tt AccessFileName} directive> --> <strong>Syntax:</strong> AccessFileName <em>filename</em><br> <strong>Default:</strong> <code>AccessFileName .htaccess</code><br> *************** *** 113,119 **** AllowOverride None<br> </Directory></code></blockquote><p><hr> ! <A name="addmodule"><h2>AddModule directive</h2></A> <!--%plaintext <?INDEX {\tt AddModule} directive> --> <strong>Syntax:</strong> AddModule <em>module module ...</em><br> <strong>Context:</strong> server config <br> --- 113,119 ---- AllowOverride None<br> </Directory></code></blockquote><p><hr> ! <h2><A name="addmodule">AddModule directive</A></h2> <!--%plaintext <?INDEX {\tt AddModule} directive> --> <strong>Syntax:</strong> AddModule <em>module module ...</em><br> <strong>Context:</strong> server config <br> *************** *** 126,132 **** be cleared with the <A HREF="#clearmodulelist">ClearModuleList</A> directive.<p><hr> ! <A name="allowoverride"><h2>AllowOverride directive</h2></A> <!--%plaintext <?INDEX {\tt AllowOverride} directive> --> <strong>Syntax:</strong> AllowOverride <em>override override ...</em><br> <strong>Default:</strong> <code>AllowOverride All</code><br> --- 126,132 ---- be cleared with the <A HREF="#clearmodulelist">ClearModuleList</A> directive.<p><hr> ! <h2><A name="allowoverride">AllowOverride directive</A></h2> <!--%plaintext <?INDEX {\tt AllowOverride} directive> --> <strong>Syntax:</strong> AllowOverride <em>override override ...</em><br> <strong>Default:</strong> <code>AllowOverride All</code><br> *************** *** 188,194 **** <A HREF="mod_include.html#xbithack">XBitHack</A>). </dl><p><hr> ! <A name="authname"><h2>AuthName directive</h2></A> <!--%plaintext <?INDEX {\tt AuthName} directive> --> <strong>Syntax:</strong> AuthName <em>auth-domain</em><br> <strong>Context:</strong> directory, .htaccess<br> --- 188,194 ---- <A HREF="mod_include.html#xbithack">XBitHack</A>). </dl><p><hr> ! <h2><A name="authname">AuthName directive</A></h2> <!--%plaintext <?INDEX {\tt AuthName} directive> --> <strong>Syntax:</strong> AuthName <em>auth-domain</em><br> <strong>Context:</strong> directory, .htaccess<br> *************** *** 203,209 **** <A HREF="mod_auth.html#authuserfile">AuthUserFile</A> and <A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> to work.<p><hr> ! <A name="authtype"><h2>AuthType directive</h2></A> <!--%plaintext <?INDEX {\tt AuthType} directive> --> <strong>Syntax:</strong> AuthType <em>type</em><br> <strong>Context:</strong> directory, .htaccess<br> --- 203,209 ---- <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> <!--%plaintext <?INDEX {\tt AuthType} directive> --> <strong>Syntax:</strong> AuthType <em>type</em><br> <strong>Context:</strong> directory, .htaccess<br> *************** *** 218,224 **** <A HREF="mod_auth.html#authuserfile">AuthUserFile</A> and <A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> to work.<p><hr> ! <A name="bindaddress"><h2>BindAddress directive</h2></A> <!--%plaintext <?INDEX {\tt BindAddress} directive> --> <strong>Syntax:</strong> BindAddress <em>saddr</em><br> <strong>Default:</strong> <code>BindAddress *</code><br> --- 218,224 ---- <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> <!--%plaintext <?INDEX {\tt BindAddress} directive> --> <strong>Syntax:</strong> BindAddress <em>saddr</em><br> <strong>Default:</strong> <code>BindAddress *</code><br> *************** *** 249,255 **** <hr> ! <A name="clearmodulelist"><h2>ClearModuleList directive</h2></A> <!--%plaintext <?INDEX {\tt ClearModuleList} directive> --> <strong>Syntax:</strong> ClearModuleList<br> <strong>Context:</strong> server config<br> --- 249,255 ---- <hr> ! <h2><A name="clearmodulelist">ClearModuleList directive</A></h2> <!--%plaintext <?INDEX {\tt ClearModuleList} directive> --> <strong>Syntax:</strong> ClearModuleList<br> <strong>Context:</strong> server config<br> *************** *** 260,266 **** 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> ! <A name="defaulttype"><h2>DefaultType directive</h2></A> <!--%plaintext <?INDEX {\tt DefaultType} directive> --> <strong>Syntax:</strong> DefaultType <em>mime-type</em><br> <strong>Default:</strong> <code>DefaultType text/html</code><br> --- 260,266 ---- 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="defaulttype">DefaultType directive</A></h2> <!--%plaintext <?INDEX {\tt DefaultType} directive> --> <strong>Syntax:</strong> DefaultType <em>mime-type</em><br> <strong>Default:</strong> <code>DefaultType text/html</code><br> *************** *** 278,284 **** would be appropriate for a directory which contained many gif images with filenames missing the .gif extension.<p><hr> ! <A name="directory"><h2><Directory> directive</h2></A> <!--%plaintext <?INDEX {\tt Directory} section directive> --> <strong>Syntax:</strong> <Directory <em>directory</em>> ... </Directory> <br> <strong>Context:</strong> server config, virtual host<br> --- 278,284 ---- 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> <!--%plaintext <?INDEX {\tt Directory} section directive> --> <strong>Syntax:</strong> <Directory <em>directory</em>> ... </Directory> <br> <strong>Context:</strong> server config, virtual host<br> *************** *** 356,362 **** nest, and cannot appear in a <A HREF="#limit"><Limit></A> section. <p><hr> ! <A NAME="documentroot"><h2>DocumentRoot directive</h2></A> <!--%plaintext <?INDEX {\tt DocumentRoot} directive> --> <strong>Syntax:</strong> DocumentRoot <em>directory-filename</em><br> <strong>Default:</strong> <code>DocumentRoot --- 356,362 ---- nest, and cannot appear in a <A HREF="#limit"><Limit></A> section. <p><hr> ! <h2><A NAME="documentroot">DocumentRoot directive</A></h2> <!--%plaintext <?INDEX {\tt DocumentRoot} directive> --> <strong>Syntax:</strong> DocumentRoot <em>directory-filename</em><br> <strong>Default:</strong> <code>DocumentRoot *************** *** 378,384 **** <p><hr> ! <A name="errordocument"><h2>ErrorDocument directive</h2></A> <!--%plaintext <?INDEX {\tt ErrorDocument} directive> --> <strong>Syntax:</strong> ErrorDocument <em>error-code document</em><br> <strong>Context</strong> server config, virtual host, directory, .htaccess<br> --- 378,384 ---- <p><hr> ! <h2><A name="errordocument">ErrorDocument directive</A></h2> <!--%plaintext <?INDEX {\tt ErrorDocument} directive> --> <strong>Syntax:</strong> ErrorDocument <em>error-code document</em><br> <strong>Context</strong> server config, virtual host, directory, .htaccess<br> *************** *** 427,433 **** <P>See Also: <A HREF="../custom-error.html">documentation of customizable responses.</A><p><hr> ! <A name="errorlog"><h2>ErrorLog directive</h2></A> <!--%plaintext <?INDEX {\tt ErrorLog} directive> --> <strong>Syntax:</strong> ErrorLog <em>filename</em><br> <strong>Default:</strong> <code>ErrorLog logs/error_log</code><br> --- 427,433 ---- <P>See Also: <A HREF="../custom-error.html">documentation of customizable responses.</A><p><hr> ! <h2><A name="errorlog">ErrorLog directive</A></h2> <!--%plaintext <?INDEX {\tt ErrorLog} directive> --> <strong>Syntax:</strong> ErrorLog <em>filename</em><br> <strong>Default:</strong> <code>ErrorLog logs/error_log</code><br> *************** *** 448,454 **** <p><hr> ! <A name="files"><h2><Files></h2></A> <strong>Syntax:</strong> <Files <em>filename</em>> ... </Files><br> <strong>Context:</strong> server config, virtual host, htaccess<br> --- 448,454 ---- <p><hr> ! <h2><A name="files"><Files> directive</A></h2> <strong>Syntax:</strong> <Files <em>filename</em>> ... </Files><br> <strong>Context:</strong> server config, virtual host, htaccess<br> *************** *** 489,495 **** <p> <hr> ! <A name="group"><h2>Group directive</h2></A> <!--%plaintext <?INDEX {\tt Group} directive> --> <strong>Syntax:</strong> Group <em>unix-group</em><br> <strong>Default:</strong> <code>Group #-1</code><br> --- 489,495 ---- <p> <hr> ! <h2><A name="group">Group directive</A></h2> <!--%plaintext <?INDEX {\tt Group} directive> --> <strong>Syntax:</strong> Group <em>unix-group</em><br> <strong>Default:</strong> <code>Group #-1</code><br> *************** *** 523,529 **** SECURITY: See <A HREF="#user">User</A> for a discussion of the security considerations.<p><hr> ! <A name="hostnamelookups"><h2>HostNameLookups directive</h2></A> <!--%plaintext <?INDEX {\tt HostNameLookups} directive> --> <strong>Syntax:</strong> HostNameLookups <em>boolean</em><br> <strong>Default:</strong> <code>HostNameLookups on</code><br> --- 523,529 ---- SECURITY: See <A HREF="#user">User</A> for a discussion of the security considerations.<p><hr> ! <h2><A name="hostnamelookups">HostNameLookups directive</A></h2> <!--%plaintext <?INDEX {\tt HostNameLookups} directive> --> <strong>Syntax:</strong> HostNameLookups <em>boolean</em><br> <strong>Default:</strong> <code>HostNameLookups on</code><br> *************** *** 539,545 **** provided in the <i>/support</i> directory, can be used to look up host names from logged IP addresses offline.<p><hr> ! <A name="identitycheck"><h2>IdentityCheck directive</h2></A> <!--%plaintext <?INDEX {\tt IdentityCheck} directive> --> <strong>Syntax:</strong> IdentityCheck <em>boolean</em><br> <strong>Default:</strong> <code>IdentityCheck off</code><br> --- 539,545 ---- provided in the <i>/support</i> directory, can be used to look up host names from logged IP addresses offline.<p><hr> ! <h2><A name="identitycheck">IdentityCheck directive</A></h2> <!--%plaintext <?INDEX {\tt IdentityCheck} directive> --> <strong>Syntax:</strong> IdentityCheck <em>boolean</em><br> <strong>Default:</strong> <code>IdentityCheck off</code><br> *************** *** 561,567 **** servers accessible from the Internet. <p><hr> ! <A NAME="ifmodule"><H2><IfModule></H2></A> <b>Syntax:</b> <IfModule [!]<i>module-name</i>> <i>...</i> </IfModule><br> <b>Default:</b> None<br> --- 561,567 ---- servers accessible from the Internet. <p><hr> ! <H2><A NAME="ifmodule"><IfModule> directive</A></H2> <b>Syntax:</b> <IfModule [!]<i>module-name</i>> <i>...</i> </IfModule><br> <b>Default:</b> None<br> *************** *** 601,607 **** <P> <hr> ! <h2><a name="keepalive">KeepAlive</a></h2> <strong>Syntax: (Apache 1.1)</strong> KeepAlive <em>max-requests</em><br> <strong>Default: (Apache 1.1)</strong> <code>KeepAlive 5</code><br> <strong>Syntax: (Apache 1.2)</strong> KeepAlive <em>on/off</em><br> --- 601,607 ---- <P> <hr> ! <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> *************** *** 624,630 **** persistent connections, "Off" to disable. See also the <a href="#maxkeepaliverequests">MaxKeepAliveRequests</a> directive.</p> ! <h2><a name="keepalivetimeout">KeepAliveTimeout</a></h2> <strong>Syntax:</strong> KeepAliveTimeout <em>seconds</em><br> <strong>Default:</strong> <code>KeepAliveTimeout 15</code><br> <strong>Context:</strong> server config<br> --- 624,630 ---- persistent connections, "Off" to disable. See also the <a href="#maxkeepaliverequests">MaxKeepAliveRequests</a> directive.</p> ! <h2><a name="keepalivetimeout">KeepAliveTimeout directive</a></h2> <strong>Syntax:</strong> KeepAliveTimeout <em>seconds</em><br> <strong>Default:</strong> <code>KeepAliveTimeout 15</code><br> <strong>Context:</strong> server config<br> *************** *** 639,645 **** applies. <hr> ! <A name="listen"><h2>Listen</h2></A> <strong>Syntax:</strong> Listen [<em>IP address</em>:]<em>port number</em><br> <strong>Context:</strong> server config<br> --- 639,645 ---- applies. <hr> ! <h2><A name="listen">Listen directive</A></h2> <strong>Syntax:</strong> Listen [<em>IP address</em>:]<em>port number</em><br> <strong>Context:</strong> server config<br> *************** *** 660,666 **** <a href="../misc/known_bugs.html#listenbug">Known Bugs</a></p> <hr> ! <A NAME="listenbacklog"><H2>ListenBacklog</H2></A> <strong>Syntax:</strong> ListenBacklog <em>backlog</em><br> <strong>Default:</strong> <code>ListenBacklog 511</code><br> <strong>Context:</strong> server config<br> --- 660,666 ---- <a href="../misc/known_bugs.html#listenbug">Known Bugs</a></p> <hr> ! <H2><A NAME="listenbacklog">ListenBacklog directive</A></H2> <strong>Syntax:</strong> ListenBacklog <em>backlog</em><br> <strong>Default:</strong> <code>ListenBacklog 511</code><br> <strong>Context:</strong> server config<br> *************** *** 673,679 **** to increase this when under a TCP SYN flood attack. See the backlog parameter to the <code>listen(2)</code> system call. ! <A name="limit"><h2><Limit> directive</h2></A> <!--%plaintext <?INDEX {\tt Limit} section directive> --> <strong>Syntax:</strong> <Limit <em>method method</em> ... > ... </Limit><br> --- 673,679 ---- to increase this when under a TCP SYN flood attack. See the backlog parameter to the <code>listen(2)</code> system call. ! <h2><A name="limit"><Limit> directive</A></h2> <!--%plaintext <?INDEX {\tt Limit} section directive> --> <strong>Syntax:</strong> <Limit <em>method method</em> ... > ... </Limit><br> *************** *** 693,699 **** If an access control directive appears outside a <Limit> directive, then it applies to all access methods.<p><hr> ! <h2><a name="location"><Location></a></h2> <strong>Syntax:</strong> <Location <em>URL</em>> ... </Location><br> --- 693,699 ---- If an access control directive appears outside a <Limit> directive, then it applies to all access methods.<p><hr> ! <h2><a name="location"><Location> directive</a></h2> <strong>Syntax:</strong> <Location <em>URL</em>> ... </Location><br> *************** *** 747,753 **** </pre> <hr> ! <A NAME="lockfile"><H2>LockFile</H2></A> <strong>Syntax:</strong> LockFile <em>filename</em><BR> <strong>Default:</strong> <code>LockFile logs/accept.lock</code><BR> <strong>Context:</strong> server config<BR> --- 747,753 ---- </pre> <hr> ! <H2><A NAME="lockfile">LockFile directive</A></H2> <strong>Syntax:</strong> LockFile <em>filename</em><BR> <strong>Default:</strong> <code>LockFile logs/accept.lock</code><BR> <strong>Context:</strong> server config<BR> *************** *** 763,769 **** <P><HR> ! <A name="maxclients"><h2>MaxClients</h2></A> <!--%plaintext <?INDEX {\tt MaxClients} directive> --> <strong>Syntax:</strong> MaxClients <em>number</em><br> <strong>Default:</strong> <code>MaxClients 256</code><br> --- 763,769 ---- <P><HR> ! <h2><A name="maxclients">MaxClients directive</A></h2> <!--%plaintext <?INDEX {\tt MaxClients} directive> --> <strong>Syntax:</strong> MaxClients <em>number</em><br> <strong>Default:</strong> <code>MaxClients 256</code><br> *************** *** 774,780 **** requests that can be supported; not more than this number of child server processes will be created.<p><hr> ! <A name="maxkeepaliverequests"><h2>MaxKeepAliveRequests</h2></A> <strong>Syntax:</strong> MaxKeepAliveRequests <em>number</em><br> <strong>Default:</strong> <code>MaxKeepAliveRequests 100</code><br> <strong>Context:</strong> server config<br> --- 774,780 ---- 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> <strong>Syntax:</strong> MaxKeepAliveRequests <em>number</em><br> <strong>Default:</strong> <code>MaxKeepAliveRequests 100</code><br> <strong>Context:</strong> server config<br> *************** *** 788,794 **** allowed. We recommend that this setting be kept to a high value for maximum server performance. ! <A name="maxrequestsperchild"><h2>MaxRequestsPerChild directive</h2></A> <!--%plaintext <?INDEX {\tt MaxRequestsPerChild} directive> --> <strong>Syntax:</strong> MaxRequestsPerChild <em>number</em><br> <strong>Default:</strong> <code>MaxRequestsPerChild 0</code><br> --- 788,794 ---- allowed. We recommend that this setting be kept to a high value for maximum server performance. ! <h2><A name="maxrequestsperchild">MaxRequestsPerChild directive</A></h2> <!--%plaintext <?INDEX {\tt MaxRequestsPerChild} directive> --> <strong>Syntax:</strong> MaxRequestsPerChild <em>number</em><br> <strong>Default:</strong> <code>MaxRequestsPerChild 0</code><br> *************** *** 808,814 **** number of processes when the server load reduces. </ul><p><hr> ! <A name="maxspareservers"><h2>MaxSpareServers directive</h2></A> <!--%plaintext <?INDEX {\tt MaxSpareServers} directive> --> <strong>Syntax:</strong> MaxSpareServers <em>number</em><br> <strong>Default:</strong> <code>MaxSpareServers 10</code><br> --- 808,814 ---- number of processes when the server load reduces. </ul><p><hr> ! <h2><A name="maxspareservers">MaxSpareServers directive</A></h2> <!--%plaintext <?INDEX {\tt MaxSpareServers} directive> --> <strong>Syntax:</strong> MaxSpareServers <em>number</em><br> <strong>Default:</strong> <code>MaxSpareServers 10</code><br> *************** *** 826,832 **** See also <A HREF="#minspareservers">MinSpareServers</A> and <A HREF="#startservers">StartServers</A>.<p><hr> ! <A name="minspareservers"><h2>MinSpareServers directive</h2></A> <!--%plaintext <?INDEX {\tt MinSpareServers} directive> --> <strong>Syntax:</strong> MinSpareServers <em>number</em><br> <strong>Default:</strong> <code>MinSpareServers 5</code><br> --- 826,832 ---- See also <A HREF="#minspareservers">MinSpareServers</A> and <A HREF="#startservers">StartServers</A>.<p><hr> ! <h2><A name="minspareservers">MinSpareServers directive</A></h2> <!--%plaintext <?INDEX {\tt MinSpareServers} directive> --> <strong>Syntax:</strong> MinSpareServers <em>number</em><br> <strong>Default:</strong> <code>MinSpareServers 5</code><br> *************** *** 844,850 **** See also <A HREF="#maxspareservers">MaxSpareServers</A> and <A HREF="#startservers">StartServers</A>.<p><hr> ! <A name="options"><h2>Options directive</h2></A> <!--%plaintext <?INDEX {\tt Options} directive> --> <strong>Syntax:</strong> Options <em>[+|-]option [+|-]option ...</em><br> <strong>Context:</strong> server config, virtual host, directory, .htaccess<br> --- 844,850 ---- See also <A HREF="#maxspareservers">MaxSpareServers</A> and <A HREF="#startservers">StartServers</A>.<p><hr> ! <h2><A name="options">Options directive</A></h2> <!--%plaintext <?INDEX {\tt Options} directive> --> <strong>Syntax:</strong> Options <em>[+|-]option [+|-]option ...</em><br> <strong>Context:</strong> server config, virtual host, directory, .htaccess<br> *************** *** 931,937 **** are set for the /web/docs/spec directory. <hr> ! <A name="pidfile"><h2>PidFile directive</h2></A> <!--%plaintext <?INDEX {\tt PidFile} directive> --> <strong>Syntax:</strong> PidFile <em>filename</em><br> <strong>Default:</strong> <code>PidFile logs/httpd.pid</code><br> --- 931,937 ---- are set for the /web/docs/spec directory. <hr> ! <h2><A name="pidfile">PidFile directive</A></h2> <!--%plaintext <?INDEX {\tt PidFile} directive> --> <strong>Syntax:</strong> PidFile <em>filename</em><br> <strong>Default:</strong> <code>PidFile logs/httpd.pid</code><br> *************** *** 953,959 **** <p><hr> ! <A name="port"><h2>Port directive</h2></A> <!--%plaintext <?INDEX {\tt Port} directive> --> <strong>Syntax:</strong> Port <em>number</em><br> <strong>Default:</strong> <code>Port 80</code><br> --- 953,959 ---- <p><hr> ! <h2><A name="port">Port directive</A></h2> <!--%plaintext <?INDEX {\tt Port} directive> --> <strong>Syntax:</strong> Port <em>number</em><br> <strong>Default:</strong> <code>Port 80</code><br> *************** *** 1009,1015 **** root whilst handling connections, your site may be open to a major security attack.<p><hr> ! <A name="require"><h2>require directive</h2></A> <!--%plaintext <?INDEX {\tt require} directive> --> <strong>Syntax:</strong> require <em>entity-name entity entity...</em><br> <strong>Context:</strong> directory, .htaccess<br> --- 1009,1015 ---- root whilst handling connections, your site may be open to a major security attack.<p><hr> ! <h2><A name="require">require directive</A></h2> <!--%plaintext <?INDEX {\tt require} directive> --> <strong>Syntax:</strong> require <em>entity-name entity entity...</em><br> <strong>Context:</strong> directory, .htaccess<br> *************** *** 1046,1052 **** <A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> (to define users and groups) in order to work correctly.<p><hr> ! <A name="resourceconfig"><h2>ResourceConfig directive</h2></A> <!--%plaintext <?INDEX {\tt ResourceConfig} directive> --> <strong>Syntax:</strong> ResourceConfig <em>filename</em><br> <strong>Default:</strong> <code>ResourceConfig conf/srm.conf</code><br> --- 1046,1052 ---- <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> <!--%plaintext <?INDEX {\tt ResourceConfig} directive> --> <strong>Syntax:</strong> ResourceConfig <em>filename</em><br> <strong>Default:</strong> <code>ResourceConfig conf/srm.conf</code><br> *************** *** 1065,1072 **** See also <A HREF="#accessconfig">AccessConfig</A>.<p><hr> ! <A name="rlimit"> </A> ! <A name="rlimitcpu"><h2>RLimitCPU directive</h2></A> <!--%plaintext <?INDEX {\tt RLimitCPU} directive> --> <strong>Syntax:</strong> RLimitCPU <em># or 'max'</em> <em>[# or 'max']</em><br> <strong>Default:</strong> <code>Unset uses operating system defaults</code><br> --- 1065,1071 ---- See also <A HREF="#accessconfig">AccessConfig</A>.<p><hr> ! <H2><A name="rlimit">RLimitCPU</A> <A NAME="rlimit">directive</A></H2> <!--%plaintext <?INDEX {\tt RLimitCPU} directive> --> <strong>Syntax:</strong> RLimitCPU <em># or 'max'</em> <em>[# or 'max']</em><br> <strong>Default:</strong> <code>Unset uses operating system defaults</code><br> *************** *** 1085,1091 **** See also <A HREF="#rlimitmem">RLimitMEM</A> or <A HREF="#rlimitnproc">RLimitNPROC</A>.<p><hr> ! <A name="rlimitmem"><h2>RLimitMEM directive</h2></A> <!--%plaintext <?INDEX {\tt RLimitMEM} directive> --> <strong>Syntax:</strong> RLimitMEM <em># or 'max'</em> <em>[# or 'max']</em><br> <strong>Default:</strong> <code>Unset uses operating system defaults</code><br> --- 1084,1090 ---- See also <A HREF="#rlimitmem">RLimitMEM</A> or <A HREF="#rlimitnproc">RLimitNPROC</A>.<p><hr> ! <h2><A name="rlimitmem">RLimitMEM directive</A></h2> <!--%plaintext <?INDEX {\tt RLimitMEM} directive> --> <strong>Syntax:</strong> RLimitMEM <em># or 'max'</em> <em>[# or 'max']</em><br> <strong>Default:</strong> <code>Unset uses operating system defaults</code><br> *************** *** 1104,1110 **** See also <A HREF="#rlimitcpu">RLimitCPU</A> or <A HREF="#rlimitnproc">RLimitNPROC</A>.<p><hr> ! <A name="rlimitnproc"><h2>RLimitNPROC directive</h2></A> <!--%plaintext <?INDEX {\tt RLimitNPROC} directive> --> <strong>Syntax:</strong> RLimitNPROC <em># or 'max'</em> <em>[# or 'max']</em><br> <strong>Default:</strong> <code>Unset uses operating system defaults</code><br> --- 1103,1109 ---- See also <A HREF="#rlimitcpu">RLimitCPU</A> or <A HREF="#rlimitnproc">RLimitNPROC</A>.<p><hr> ! <h2><A name="rlimitnproc">RLimitNPROC directive</A></h2> <!--%plaintext <?INDEX {\tt RLimitNPROC} directive> --> <strong>Syntax:</strong> RLimitNPROC <em># or 'max'</em> <em>[# or 'max']</em><br> <strong>Default:</strong> <code>Unset uses operating system defaults</code><br> *************** *** 1130,1136 **** <p><hr> ! <A name="satisfy"><h2>Satisfy</h2></A> <!--%plaintext <?INDEX {\tt Satisfy} directive> --> <strong>Syntax:</strong> Satisfy <em>'any' or 'all'</em><br> <strong>Default:</strong> Satisfy all<br> --- 1129,1135 ---- <p><hr> ! <h2><A name="satisfy">Satisfy directive</A></h2> <!--%plaintext <?INDEX {\tt Satisfy} directive> --> <strong>Syntax:</strong> Satisfy <em>'any' or 'all'</em><br> <strong>Default:</strong> Satisfy all<br> *************** *** 1152,1158 **** <p><hr> ! <A name="scoreboardfile"><h2>ScoreBoardFile directive</h2></A> <!--%plaintext <?INDEX {\tt ScoreBoardFile} directive> --> <strong>Syntax:</strong> ScoreBoardFile <em>filename</em><br> <strong>Default:</strong> <code>ScoreBoardFile logs/apache_status</code><br> --- 1151,1157 ---- <p><hr> ! <h2><A name="scoreboardfile">ScoreBoardFile directive</A></h2> <!--%plaintext <?INDEX {\tt ScoreBoardFile} directive> --> <strong>Syntax:</strong> ScoreBoardFile <em>filename</em><br> <strong>Default:</strong> <code>ScoreBoardFile logs/apache_status</code><br> *************** *** 1189,1195 **** <p><hr> ! <A name="sendbuffersize"><h2>SendBufferSize directive</h2></A> <!--%plaintext <?INDEX {\tt SendBufferSize} directive> --> <strong>Syntax:</strong> SendBufferSize <em>bytes</em><br> <strong>Context:</strong> server config<br> --- 1188,1194 ---- <p><hr> ! <h2><A name="sendbuffersize">SendBufferSize directive</A></h2> <!--%plaintext <?INDEX {\tt SendBufferSize} directive> --> <strong>Syntax:</strong> SendBufferSize <em>bytes</em><br> <strong>Context:</strong> server config<br> *************** *** 1201,1207 **** fast pipes) <p><hr> ! <A name="serveradmin"><h2>ServerAdmin directive</h2></A> <!--%plaintext <?INDEX {\tt ServerAdmin} directive> --> <strong>Syntax:</strong> ServerAdmin <em>email-address</em><br> <strong>Context:</strong> server config, virtual host<br> --- 1200,1206 ---- fast pipes) <p><hr> ! <h2><A name="serveradmin">ServerAdmin directive</A></h2> <!--%plaintext <?INDEX {\tt ServerAdmin} directive> --> <strong>Syntax:</strong> ServerAdmin <em>email-address</em><br> <strong>Context:</strong> server config, virtual host<br> *************** *** 1214,1220 **** <blockquote><code>ServerAdmin [EMAIL PROTECTED]</code></blockquote> as users do not always mention that they are talking about the server!<p><hr> ! <A name="serveralias"><h2>ServerAlias directive</h2></A> <strong>Syntax:</strong> ServerAlias <em>host1 host2 ...</em><br> <strong>Context:</strong> virtual host<br> --- 1213,1219 ---- <blockquote><code>ServerAdmin [EMAIL PROTECTED]</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> <strong>Syntax:</strong> ServerAlias <em>host1 host2 ...</em><br> <strong>Context:</strong> virtual host<br> *************** *** 1230,1236 **** <hr> ! <A name="servername"><h2>ServerName directive</h2></A> <!--%plaintext <?INDEX {\tt ServerName} directive> --> <strong>Syntax:</strong> ServerName <em>fully-qualified domain name</em><br> <strong>Context:</strong> server config, virtual host<br> --- 1229,1235 ---- <hr> ! <h2><A name="servername">ServerName directive</A></h2> <!--%plaintext <?INDEX {\tt ServerName} directive> --> <strong>Syntax:</strong> ServerName <em>fully-qualified domain name</em><br> <strong>Context:</strong> server config, virtual host<br> *************** *** 1247,1253 **** <a href="../dns-caveats.html">DNS Issues</a></p> <hr> ! <A name="serverpath"><h2>ServerPath directive</h2></A> <strong>Syntax:</strong> ServerPath <em>pathname</em><br> <strong>Context:</strong> virtual host<br> --- 1246,1252 ---- <a href="../dns-caveats.html">DNS Issues</a></p> <hr> ! <h2><A name="serverpath">ServerPath directive</A></h2> <strong>Syntax:</strong> ServerPath <em>pathname</em><br> <strong>Context:</strong> virtual host<br> *************** *** 1261,1267 **** <a href="../vhosts-in-depth.html">In-depth description of Virtual Host matching</a></p> <hr> ! <A name="serverroot"><h2>ServerRoot directive</h2></A> <!--%plaintext <?INDEX {\tt ServerRoot} directive> --> <strong>Syntax:</strong> ServerRoot <em>directory-filename</em><br> <strong>Default:</strong> <code>ServerRoot /usr/local/etc/httpd</code><br> --- 1260,1266 ---- <a href="../vhosts-in-depth.html">In-depth description of Virtual Host matching</a></p> <hr> ! <h2><A name="serverroot">ServerRoot directive</A></h2> <!--%plaintext <?INDEX {\tt ServerRoot} directive> --> <strong>Syntax:</strong> ServerRoot <em>directory-filename</em><br> <strong>Default:</strong> <code>ServerRoot /usr/local/etc/httpd</code><br> *************** *** 1274,1280 **** as relative to this directory.<br> See also <a href="../invoking.html">the <code>-d</code> option to httpd</a>.<p><hr> ! <A name="servertype"><h2>ServerType directive</h2></A> <!--%plaintext <?INDEX {\tt ServerType} directive> --> <strong>Syntax:</strong> ServerType <em>type</em><br> <strong>Default:</strong> <code>ServerType standalone</code><br> --- 1273,1279 ---- as relative to this directory.<br> See also <a href="../invoking.html">the <code>-d</code> option to httpd</a>.<p><hr> ! <h2><A name="servertype">ServerType directive</A></h2> <!--%plaintext <?INDEX {\tt ServerType} directive> --> <strong>Syntax:</strong> ServerType <em>type</em><br> <strong>Default:</strong> <code>ServerType standalone</code><br> *************** *** 1308,1314 **** cannot be guaranteed in either, but whilst most people are happy to use standalone, inetd is probably least prone to attack.<p><hr> ! <A name="startservers"><h2>StartServers directive</h2></A> <!--%plaintext <?INDEX {\tt StartServers} directive> --> <strong>Syntax:</strong> StartServers <em>number</em><br> <strong>Default:</strong> <code>StartServers 5</code><br> --- 1307,1313 ---- cannot be guaranteed in either, but whilst most people are happy to use standalone, inetd is probably least prone to attack.<p><hr> ! <h2><A name="startservers">StartServers directive</A></h2> <!--%plaintext <?INDEX {\tt StartServers} directive> --> <strong>Syntax:</strong> StartServers <em>number</em><br> <strong>Default:</strong> <code>StartServers 5</code><br> *************** *** 1322,1328 **** See also <A HREF="#minspareservers">MinSpareServers</A> and <A HREF="#maxspareservers">MaxSpareServers</A>.<p><hr> ! <A name="timeout"><h2>TimeOut directive</h2></A> <!--%plaintext <?INDEX {\tt TimeOut} directive> --> <strong>Syntax:</strong> TimeOut <em>number</em><br> <strong>Default:</strong> <code>TimeOut 300</code><br> --- 1321,1327 ---- See also <A HREF="#minspareservers">MinSpareServers</A> and <A HREF="#maxspareservers">MaxSpareServers</A>.<p><hr> ! <h2><A name="timeout">TimeOut directive</A></h2> <!--%plaintext <?INDEX {\tt TimeOut} directive> --> <strong>Syntax:</strong> TimeOut <em>number</em><br> <strong>Default:</strong> <code>TimeOut 300</code><br> *************** *** 1349,1355 **** <p><hr> ! <A name="user"><h2>User directive</h2></A> <!--%plaintext <?INDEX {\tt User} directive> --> <strong>Syntax:</strong> User <em>unix-userid</em><br> <strong>Default:</strong> <code>User #-1</code><br> --- 1348,1354 ---- <p><hr> ! <h2><A name="user">User directive</A></h2> <!--%plaintext <?INDEX {\tt User} directive> --> <strong>Syntax:</strong> User <em>unix-userid</em><br> <strong>Default:</strong> <code>User #-1</code><br> *************** *** 1388,1394 **** <code>root</code> unless you know exactly what you are doing, and what the dangers are.<p><hr> ! <A name="virtualhost"><h2><VirtualHost> directive</h2></A> <!--%plaintext <?INDEX {\tt VirtualHost} section directive> --> <strong>Syntax:</strong> <VirtualHost <em>addr</em>[:<em>port</em>] ...> ... </VirtualHost> <br> --- 1387,1393 ---- <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> <!--%plaintext <?INDEX {\tt VirtualHost} section directive> --> <strong>Syntax:</strong> <VirtualHost <em>addr</em>[:<em>port</em>] ...> ... </VirtualHost> <br>