diff options
31 files changed, 391 insertions, 307 deletions
diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html index 00c40dcd2c..fbc9725e24 100644 --- a/docs/manual/mod/core.html +++ b/docs/manual/mod/core.html @@ -88,7 +88,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" @@ -117,7 +117,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" @@ -138,7 +138,8 @@ contain any server directive allowed in the <EM>server config</EM> context. <A HREF="directive-dict.html#Compatibility" REL="Help" -><STRONG>Compatibility:</STRONG></A> AccessFileName can accept more than one filename only in Apache 1.3 and later<P> +><STRONG>Compatibility:</STRONG></A> AccessFileName can accept more than +one filename only in Apache 1.3 and later<P> When returning a document to the client the server looks for the first existing access control file from this list of names in every directory of the path to @@ -154,7 +155,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" @@ -171,7 +172,8 @@ AllowOverride None<BR> <A HREF="directive-dict.html#Compatibility" REL="Help" -><STRONG>Compatibility:</STRONG></A> AddModule is only available in Apache 1.2 and later<P> +><STRONG>Compatibility:</STRONG></A> AddModule is only available in +Apache 1.2 and later<P> The server can have modules compiled in which are not actively in use. This directive can be used to enable the use of those modules. The @@ -179,7 +181,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" @@ -253,7 +255,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" @@ -280,7 +282,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" @@ -307,7 +309,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" @@ -356,7 +358,7 @@ HREF="#virtualhost"><VirtualHost></A></CODE> sections. <HR> -<H2><A name="bs2000authfile">BS2000AuthFile directive</A></H2> +<H2><A NAME="bs2000authfile">BS2000AuthFile directive</A></H2> <!--%plaintext <?INDEX {\tt BS2000AuthFile} directive> --> <A HREF="directive-dict.html#Syntax" @@ -377,7 +379,8 @@ HREF="#virtualhost"><VirtualHost></A></CODE> sections. <A HREF="directive-dict.html#Compatibility" REL="Help" -><STRONG>Compatibility:</STRONG></A> BS2000AuthFile is only available for BS2000 machines, as of Apache 1.3 and later.<P> +><STRONG>Compatibility:</STRONG></A> BS2000AuthFile is only available for +BS2000 machines, as of Apache 1.3 and later.<P> The <CODE>BS2000AuthFile</CODE> directive is available for BS2000 hosts only. It must be used to define the password file which is used to @@ -396,7 +399,7 @@ Only one <CODE>BS2000AuthFile</CODE> directive can be used. <P> <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" @@ -413,13 +416,14 @@ Only one <CODE>BS2000AuthFile</CODE> directive can be used. <P> <A HREF="directive-dict.html#Compatibility" REL="Help" -><STRONG>Compatibility:</STRONG></A> ClearModuleList is only available in Apache 1.2 and later<P> +><STRONG>Compatibility:</STRONG></A> ClearModuleList is only available in +Apache 1.2 and later<P> The server comes with a built-in list of active modules. This directive clears the list. It is assumed that the list will then be re-populated using the <A HREF="#addmodule">AddModule</A> directive.<P><HR> -<H2><A name="contentdigest">ContentDigest directive</A></H2> +<H2><A NAME="contentdigest">ContentDigest directive</A></H2> <!--%plaintext <?INDEX {\tt ContentDigest} directive> --> <A HREF="directive-dict.html#Syntax" @@ -432,7 +436,8 @@ re-populated using the <A HREF="#addmodule">AddModule</A> directive.<P><HR> <A HREF="directive-dict.html#Context" REL="Help" -><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess<BR> +><STRONG>Context:</STRONG></A> server config, virtual host, directory, +.htaccess<BR> <A HREF="directive-dict.html#Override" REL="Help" @@ -444,7 +449,8 @@ re-populated using the <A HREF="#addmodule">AddModule</A> directive.<P><HR> <A HREF="directive-dict.html#Compatibility" REL="Help" -><STRONG>Compatibility:</STRONG></A> ContentDigest is only available in Apache 1.1 and later<P> +><STRONG>Compatibility:</STRONG></A> ContentDigest is only available in +Apache 1.1 and later<P> This directive enables the generation of <CODE>Content-MD5</CODE> headers as defined in RFC1864 respectively RFC2068.<P> @@ -471,7 +477,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" @@ -497,7 +503,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" @@ -510,7 +516,8 @@ it in a different location.<P><HR> <A HREF="directive-dict.html#Context" REL="Help" -><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess<BR> +><STRONG>Context:</STRONG></A> server config, virtual host, directory, +.htaccess<BR> <A HREF="directive-dict.html#Override" REL="Help" @@ -530,12 +537,13 @@ 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" REL="Help" -><STRONG>Syntax:</STRONG></A> <Directory <EM>directory</EM>> ... </Directory> <BR> +><STRONG>Syntax:</STRONG></A> <Directory <EM>directory</EM>> + ... </Directory> <BR> <A HREF="directive-dict.html#Context" REL="Help" @@ -655,11 +663,12 @@ 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" -><STRONG>Syntax:</STRONG></A> <DirectoryMatch <EM>regex</EM>> ... </DirectoryMatch> <BR> +><STRONG>Syntax:</STRONG></A> <DirectoryMatch <EM>regex</EM>> + ... </DirectoryMatch> <BR> <A HREF="directive-dict.html#Context" REL="Help" @@ -673,7 +682,8 @@ different sections are combined when a request is received REL="Help" ><STRONG>Compatibility:</STRONG></A> Available in Apache 1.3 and later -<P><DirectoryMatch> and </DirectoryMatch> are used to enclose a group of +<P><DirectoryMatch> and </DirectoryMatch> are used to enclose a +group of directives which will apply only to the named directory and sub-directories of that directory, the same as <A HREF="#directory"><Directory></A>. However, it takes as an @@ -729,7 +739,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" @@ -738,7 +748,8 @@ please avoid that. <A HREF="directive-dict.html#Context" REL="Help" -><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess<BR> +><STRONG>Context:</STRONG></A> server config, virtual host, directory, +.htaccess<BR> <A HREF="directive-dict.html#Status" REL="Help" @@ -793,12 +804,13 @@ 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" REL="Help" -><STRONG>Syntax:</STRONG></A> ErrorLog <EM>filename</EM>|<CODE>syslog</CODE><BR> +><STRONG>Syntax:</STRONG></A> ErrorLog <EM>filename</EM>|<CODE>syslog</CODE> +<BR> <A HREF="directive-dict.html#Default" REL="Help" @@ -823,7 +835,8 @@ Using <CODE>syslog</CODE> instead of a filename enables logging via syslogd(8) if the system supports it. <P> -SECURITY: See the <A HREF="../misc/security_tips.html#serverroot">security tips</A> +SECURITY: See the +<A HREF="../misc/security_tips.html#serverroot">security tips</A> document for details on why your security could be compromised if the directory where logfiles are stored is writable by anyone other than the user that starts the server. @@ -831,7 +844,7 @@ than the user that starts the server. <P><STRONG>See also:</STRONG> <A HREF="#loglevel">LogLevel</A> <P><HR> -<H2><A name="files"><Files> directive</A></H2> +<H2><A NAME="files"><Files> directive</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" @@ -896,7 +909,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" @@ -932,7 +945,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" @@ -978,7 +991,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" @@ -991,7 +1004,8 @@ considerations.<P><HR> <A HREF="directive-dict.html#Context" REL="Help" -><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess<BR> +><STRONG>Context:</STRONG></A> server config, virtual host, directory, +.htaccess<BR> <A HREF="directive-dict.html#Status" REL="Help" @@ -999,13 +1013,14 @@ considerations.<P><HR> <A HREF="directive-dict.html#Compatibility" REL="Help" -><STRONG>Compatibility:</STRONG></A> <CODE>double</CODE> available only in Apache +><STRONG>Compatibility:</STRONG></A> <CODE>double</CODE> available only in +Apache 1.3 and above.<BR> <A HREF="directive-dict.html#Compatibility" REL="Help" -><STRONG>Compatibility:</STRONG></A> Default was <CODE>on</CODE> prior to Apache -1.3.<P> +><STRONG>Compatibility:</STRONG></A> Default was <CODE>on</CODE> prior to +Apache 1.3.<P> This directive enables DNS lookups so that host names can be logged (and passed to CGIs/SSIs in <CODE>REMOTE_HOST</CODE>). @@ -1036,7 +1051,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" @@ -1074,7 +1089,8 @@ servers accessible from the Internet. <A HREF="directive-dict.html#Syntax" REL="Help" -><STRONG>Syntax:</STRONG></A> <IfModule [!]<EM>module-name</EM>> <EM>...</EM> +><STRONG>Syntax:</STRONG></A> <IfModule [!]<EM>module-name</EM>> + <EM>...</EM> </IfModule><BR> <A HREF="directive-dict.html#Default" @@ -1125,7 +1141,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" @@ -1138,13 +1154,15 @@ simple multiple-module tests. <A HREF="directive-dict.html#Compatibility" REL="Help" -><STRONG>Compatibility:</STRONG></A> Include is only available in Apache 1.3 and later. +><STRONG>Compatibility:</STRONG></A> Include is only available in Apache 1.3 +and later. <P> -This directive allows inclusion of other configuration files from within the server configuration files. +This directive allows inclusion of other configuration files from within the +server configuration files. <P> <HR> -<H2><A name="keepalive">KeepAlive directive</A></H2> +<H2><A NAME="keepalive">KeepAlive directive</A></H2> <STRONG>Syntax: (Apache 1.1)</STRONG> KeepAlive <EM>max-requests</EM><BR> <STRONG>Default: (Apache 1.1)</STRONG> <CODE>KeepAlive 5</CODE><BR> <STRONG>Syntax: (Apache 1.2)</STRONG> KeepAlive <EM>on/off</EM><BR> @@ -1176,7 +1194,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" @@ -1196,8 +1214,8 @@ HREF="#maxkeepaliverequests">MaxKeepAliveRequests</A> directive.</P><HR> <A HREF="directive-dict.html#Compatibility" REL="Help" -><STRONG>Compatibility:</STRONG></A> KeepAliveTimeout is only available in Apache -1.1 and later.<P> +><STRONG>Compatibility:</STRONG></A> KeepAliveTimeout is only available in +Apache 1.1 and later.<P> The number of seconds Apache will wait for a subsequent request before closing the connection. Once a request has been received, the timeout @@ -1206,7 +1224,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" @@ -1240,7 +1258,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" @@ -1303,7 +1321,8 @@ interfaces and port numbers, use <STRONG>See Also:</STRONG> <A HREF="../bind.html">Setting which addresses and ports Apache uses</A><BR> <STRONG>See Also:</STRONG> -<A HREF="http//www.apache.org/info/known_bugs.html#listenbug">Known Bugs</A></P> +<A HREF="http://www.apache.org/info/known_bugs.html#listenbug">Known Bugs</A> +</P> <HR> <H2><A NAME="listenbacklog">ListenBacklog directive</A></H2> @@ -1334,7 +1353,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" @@ -1364,17 +1383,17 @@ order they appear in the configuration file, after the <Directory> sections and <CODE>.htaccess</CODE> files are read, and after the <Files> sections.</P> -<p>Note that URLs do not have to line up with the filesystem at all, +<P>Note that URLs do not have to line up with the filesystem at all, it should be emphasized that <Location> operates completely outside the filesystem. -<p>For all origin (non-proxy) requests, the URL to be matched is -of the form <code>/path/</code>, and you should not include any -<code>http://servername</code> prefix. For proxy requests, the URL -to be matched is of the form <code>scheme://servername/path</code>, +<P>For all origin (non-proxy) requests, the URL to be matched is +of the form <CODE>/path/</CODE>, and you should not include any +<CODE>http://servername</CODE> prefix. For proxy requests, the URL +to be matched is of the form <CODE>scheme://servername/path</CODE>, and you must include the prefix. -<p>The URL may use wildcards In a wild-card string, `?' matches any +<P>The URL may use wildcards In a wild-card string, `?' matches any single character, and `*' matches any sequences of characters. <P><STRONG>Apache 1.2 and above:</STRONG> @@ -1391,11 +1410,12 @@ For example:</P> "/special/data". In Apache 1.3 and above, a new directive <A HREF="#locationmatch"><LocationMatch></A> exists which behaves identical to the regex version of -<code><Location></code>. +<CODE><Location></CODE>. <P>The <CODE>Location</CODE> functionality is especially useful when combined with the <CODE><A -HREF="mod_mime.html#sethandler">SetHandler</A></CODE> directive. For example, to enable status requests, but allow them only +HREF="mod_mime.html#sethandler">SetHandler</A></CODE> directive. For example, +to enable status requests, but allow them only from browsers at foo.com, you might use: <PRE> @@ -1407,22 +1427,23 @@ from browsers at foo.com, you might use: </Location> </PRE> -<p><strong>Apache 1.3 and above note about / (slash)</strong>: The slash character has special +<P><STRONG>Apache 1.3 and above note about / (slash)</STRONG>: The slash +character has special meaning depending on where in a URL it appears. People may be used to its behaviour in the filesystem where multiple adjacent slashes are -frequently collapsed to a single slash (i.e. <code>/home///foo</code> -is the same as <code>/home/foo</code>). In URL-space this is not -necessarily true. The <code><LocationMatch></code> directive -and the regex version of <code><Location></code> require you +frequently collapsed to a single slash (i.e. <CODE>/home///foo</CODE> +is the same as <CODE>/home/foo</CODE>). In URL-space this is not +necessarily true. The <CODE><LocationMatch></CODE> directive +and the regex version of <CODE><Location></CODE> require you to explicitly specify multiple slashes if that is your intention. -For example, <code><LocationMatch ^/abc></code> would match the -request URL <code>/abc</code> but not the request URL <code>//abc</code>. -The (non-regex) <code><Location></code> directive behaves +For example, <CODE><LocationMatch ^/abc></CODE> would match the +request URL <CODE>/abc</CODE> but not the request URL <CODE>//abc</CODE>. +The (non-regex) <CODE><Location></CODE> directive behaves similarly when used for proxy requests. But when (non-regex) -<code><Location></code> is used for non-proxy requests it will +<CODE><Location></CODE> is used for non-proxy requests it will implicitly match multiple slashes with a single slash. For example, -if you specify <code><Location /abc/def></code> and the request -is to <code>/abc//def</code> then it will match. +if you specify <CODE><Location /abc/def></CODE> and the request +is to <CODE>/abc//def</CODE> then it will match. <P> <STRONG>See also</STRONG>: <A HREF="../sections.html">How Directory, @@ -1431,7 +1452,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" @@ -1524,7 +1545,8 @@ server will try to create.<P> <A HREF="directive-dict.html#Compatibility" REL="Help" -><STRONG>Compatibility:</STRONG></A> LogLevel is only available in 1.3 or later. +><STRONG>Compatibility:</STRONG></A> LogLevel is only available in 1.3 or +later. <P>LogLevel adjusts the verbosity of the messages recorded in the error logs (see <A HREF="#errorlog">ErrorLog</A> directive). @@ -1555,7 +1577,8 @@ decreasing significance: <TR><TD><TD>"httpd: caught SIGBUS, attempting to dump core in ..." <TR><TD><CODE>info</CODE> <TD>Informational. - <TR><TD><TD>"Server seems busy, (you may need to increase StartServers, or Min/MaxSpareServers)..." + <TR><TD><TD>"Server seems busy, (you may need to increase StartServers, or + Min/MaxSpareServers)..." <TR><TD><CODE>debug</CODE> <TD>Debug-level messages <TR><TD><TD>"Opening config file ..." @@ -1569,7 +1592,7 @@ of higher significance will be reported as well. E.g., when Using a level of at least <CODE>crit</CODE> is recommended. <P><HR> -<H2><A name="maxclients">MaxClients directive</A></H2> +<H2><A NAME="maxclients">MaxClients directive</A></H2> <!--%plaintext <?INDEX {\tt MaxClients} directive> --> <A HREF="directive-dict.html#Syntax" @@ -1593,7 +1616,7 @@ requests that can be supported; not more than this number of child server processes will be created. To configure more than 256 clients, you must edit the HARD_SERVER_LIMIT entry in httpd.h and recompile.<P><HR> -<H2><A name="maxkeepaliverequests">MaxKeepAliveRequests directive</A></H2> +<H2><A NAME="maxkeepaliverequests">MaxKeepAliveRequests directive</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" @@ -1622,7 +1645,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" @@ -1654,7 +1677,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" @@ -1689,7 +1712,7 @@ Microsoft Windows platform. 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" @@ -1723,7 +1746,7 @@ This directive has no effect on Microsoft Windows. 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" @@ -1740,7 +1763,8 @@ See also <A HREF="#maxspareservers">MaxSpareServers</A> and <A HREF="directive-dict.html#Compatibility" REL="Help" -><STRONG>Compatibility:</STRONG></A> NameVirtualHost is only available in Apache 1.3 and later<P> +><STRONG>Compatibility:</STRONG></A> NameVirtualHost is only available in +Apache 1.3 and later<P> The NameVirtualHost directive is a required directive if you want to configure <A HREF="../vhosts/index.html">name-based virtual hosts</A>.<P> @@ -1754,10 +1778,10 @@ With the NameVirtualHost directive you specify the address to which your name-based virtual host names resolve. If you have multiple name-based hosts on multiple addresses, repeat the directive for each address.<P> -Note: the "main server" and any _default_ servers will <b>never</b> +Note: the "main server" and any _default_ servers will <STRONG>never</STRONG> be served for a request to a NameVirtualHost IP Address (unless for some reason you specify NameVirtualHost but then don't define any VirtualHosts -for that address).<p> +for that address).<P> Optionally you can specify a port number on which the name-based virtual hosts should be used, e.g. @@ -1767,7 +1791,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" @@ -1776,7 +1800,8 @@ virtual hosts should be used, e.g. <A HREF="directive-dict.html#Context" REL="Help" -><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess<BR> +><STRONG>Context:</STRONG></A> server config, virtual host, directory, +.htaccess<BR> <A HREF="directive-dict.html#Override" REL="Help" @@ -1802,7 +1827,8 @@ Execution of CGI scripts is permitted. <DD> <!--%plaintext <?INDEX {\tt FollowSymLinks} option> --> The server will follow symbolic links in this directory. -<STRONG>Note</STRONG>: even though the server follows the symlink it does <EM>not</EM> +<STRONG>Note</STRONG>: even though the server follows the symlink it +does <EM>not</EM> change the pathname used to match against <CODE><Directory></CODE> sections. <DT>Includes @@ -1865,13 +1891,14 @@ Options +Includes -Indexes<BR> then the options <CODE>FollowSymLinks</CODE> and <CODE>Includes</CODE> are set for the /web/docs/spec directory.<P> -<STRONG>Note:</STRONG> Using <CODE>-IncludesNOEXEC</CODE> or <CODE>-Includes</CODE> +<STRONG>Note:</STRONG> Using <CODE>-IncludesNOEXEC</CODE> or +<CODE>-Includes</CODE> disables server-side includes completely regardless of the previous setting.<P> The default in the absence of any other settings is <CODE>All</CODE>.<P> <HR> -<H2><A name="pidfile">PidFile directive</A></H2> +<H2><A NAME="pidfile">PidFile directive</A></H2> <!--%plaintext <?INDEX {\tt PidFile} directive> --> <A HREF="directive-dict.html#Syntax" @@ -1905,7 +1932,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" @@ -1924,7 +1951,8 @@ The PidFile is subject to the same warnings about log file placement and REL="Help" ><STRONG>Status:</STRONG></A> core<P> -<EM>Number</EM> is a number from 0 to 65535; some port numbers (especially below +<EM>Number</EM> is a number from 0 to 65535; some port numbers +(especially below 1024) are reserved for particular protocols. See <CODE>/etc/services</CODE> for a list of some defined ports; the standard port for the http protocol is 80.<P> @@ -1978,7 +2006,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" @@ -2027,7 +2055,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" @@ -2058,16 +2086,19 @@ sections; in fact it can now contain any server directive allowed in the See also <A HREF="#accessconfig">AccessConfig</A>.<P><HR> -<H2><A name="rlimit">RLimitCPU</A> <A NAME="rlimitcpu">directive</A></H2> +<H2><A NAME="rlimit">RLimitCPU</A> <A NAME="rlimitcpu">directive</A></H2> <!--%plaintext <?INDEX {\tt RLimitCPU} directive> --> <A HREF="directive-dict.html#Syntax" REL="Help" -><STRONG>Syntax:</STRONG></A> RLimitCPU <EM># or 'max'</EM> <EM>[# or 'max']</EM><BR> +><STRONG>Syntax:</STRONG></A> RLimitCPU <EM># or 'max'</EM> + <EM>[# or 'max']</EM> +<BR> <A HREF="directive-dict.html#Default" REL="Help" -><STRONG>Default:</STRONG></A> <EM>Unset; uses operating system defaults</EM><BR> +><STRONG>Default:</STRONG></A> <EM>Unset; uses operating system defaults</EM> +<BR> <A HREF="directive-dict.html#Context" REL="Help" @@ -2079,29 +2110,33 @@ See also <A HREF="#accessconfig">AccessConfig</A>.<P><HR> <A HREF="directive-dict.html#Compatibility" REL="Help" -><STRONG>Compatibility:</STRONG></A> RLimitCPU is only available in Apache 1.2 and later<P> +><STRONG>Compatibility:</STRONG></A> RLimitCPU is only available in Apache 1.2 +and later<P> -Takes 1 or 2 parameters. The first parameter sets the soft resource limit for all -processes and the second parameter sets the maximum resource limit. Either parameter -can be a number, or <EM>max</EM> to indicate to the server that the limit should -be set to the maximum allowed by the operating system configuration. Raising the -maximum resource limit requires that the server is running as root, or in the initial -startup phase.<P> +Takes 1 or 2 parameters. The first parameter sets the soft resource limit +for all processes and the second parameter sets the maximum resource limit. +Either parameter can be a number, or <EM>max</EM> to indicate to the server +that the limit should be set to the maximum allowed by the operating system +configuration. Raising the maximum resource limit requires that the server +is running as root, or in the initial startup phase.<P> CPU resource limits are expressed in seconds per process.<P> -See also <A HREF="#rlimitmem">RLimitMEM</A> or <A HREF="#rlimitnproc">RLimitNPROC</A>.<P><HR> +See also <A HREF="#rlimitmem">RLimitMEM</A> or +<A HREF="#rlimitnproc">RLimitNPROC</A>.<P><HR> -<H2><A name="rlimitmem">RLimitMEM directive</A></H2> +<H2><A NAME="rlimitmem">RLimitMEM directive</A></H2> <!--%plaintext <?INDEX {\tt RLimitMEM} directive> --> <A HREF="directive-dict.html#Syntax" REL="Help" -><STRONG>Syntax:</STRONG></A> RLimitMEM <EM># or 'max'</EM> <EM>[# or 'max']</EM><BR> +><STRONG>Syntax:</STRONG></A> RLimitMEM <EM># or 'max'</EM> + <EM>[# or 'max']</EM><BR> <A HREF="directive-dict.html#Default" REL="Help" -><STRONG>Default:</STRONG></A> <EM>Unset; uses operating system defaults</EM><BR> +><STRONG>Default:</STRONG></A> <EM>Unset; uses operating system defaults</EM> +<BR> <A HREF="directive-dict.html#Context" REL="Help" @@ -2113,29 +2148,33 @@ See also <A HREF="#rlimitmem">RLimitMEM</A> or <A HREF="#rlimitnproc">RLimitNPRO <A HREF="directive-dict.html#Compatibility" REL="Help" -><STRONG>Compatibility:</STRONG></A> RLimitMEM is only available in Apache 1.2 and later<P> +><STRONG>Compatibility:</STRONG></A> RLimitMEM is only available in Apache 1.2 +and later<P> -Takes 1 or 2 parameters. The first parameter sets the soft resource limit for all -processes and the second parameter sets the maximum resource limit. Either parameter -can be a number, or <EM>max</EM> to indicate to the server that the limit should -be set to the maximum allowed by the operating system configuration. Raising the -maximum resource limit requires that the server is running as root, or in the initial -startup phase.<P> +Takes 1 or 2 parameters. The first parameter sets the soft resource limit for +all processes and the second parameter sets the maximum resource limit. Either +parameter can be a number, or <EM>max</EM> to indicate to the server that the +limit should be set to the maximum allowed by the operating system +configuration. Raising the maximum resource limit requires that the +server is running as root, or in the initial startup phase.<P> Memory resource limits are expressed in bytes per process.<P> -See also <A HREF="#rlimitcpu">RLimitCPU</A> or <A HREF="#rlimitnproc">RLimitNPROC</A>.<P><HR> +See also <A HREF="#rlimitcpu">RLimitCPU</A> or +<A HREF="#rlimitnproc">RLimitNPROC</A>.<P><HR> -<H2><A name="rlimitnproc">RLimitNPROC directive</A></H2> +<H2><A NAME="rlimitnproc">RLimitNPROC directive</A></H2> <!--%plaintext <?INDEX {\tt RLimitNPROC} directive> --> <A HREF="directive-dict.html#Syntax" REL="Help" -><STRONG>Syntax:</STRONG></A> RLimitNPROC <EM># or 'max'</EM> <EM>[# or 'max']</EM><BR> +><STRONG>Syntax:</STRONG></A> RLimitNPROC <EM># or 'max'</EM> + <EM>[# or 'max']</EM><BR> <A HREF="directive-dict.html#Default" REL="Help" -><STRONG>Default:</STRONG></A> <EM>Unset; uses operating system defaults</EM><BR> +><STRONG>Default:</STRONG></A> <EM>Unset; uses operating system defaults</EM> +<BR> <A HREF="directive-dict.html#Context" REL="Help" @@ -2147,27 +2186,30 @@ See also <A HREF="#rlimitcpu">RLimitCPU</A> or <A HREF="#rlimitnproc">RLimitNPRO <A HREF="directive-dict.html#Compatibility" REL="Help" -><STRONG>Compatibility:</STRONG></A> RLimitNPROC is only available in Apache 1.2 and later<P> +><STRONG>Compatibility:</STRONG></A> RLimitNPROC is only available in Apache +1.2 and later<P> -Takes 1 or 2 parameters. The first parameter sets the soft resource limit for all -processes and the second parameter sets the maximum resource limit. Either parameter -can be a number, or <EM>max</EM> to indicate to the server that the limit should -be set to the maximum allowed by the operating system configuration. Raising the -maximum resource limit requires that the server is running as root, or in the initial -startup phase.<P> +Takes 1 or 2 parameters. The first parameter sets the soft resource limit +for all processes and the second parameter sets the maximum resource limit. +Either parameter can be a number, or <EM>max</EM> to indicate to the server +that the limit should be set to the maximum allowed by the operating system +configuration. Raising the maximum resource limit requires that the server +is running as root, or in the initial startup phase.<P> Process limits control the number of processes per user.<P> -Note: If CGI processes are <STRONG>not</STRONG> running under userids other than the +Note: If CGI processes are <STRONG>not</STRONG> running under userids other +than the web server userid, this directive will limit the number of processes that the server itself can create. Evidence of this situation will be indicated by <STRONG><EM>cannot fork</EM></STRONG> messages in the error_log.<P> -See also <A HREF="#rlimitmem">RLimitMEM</A> or <A HREF="#rlimitcpu">RLimitCPU</A>. +See also <A HREF="#rlimitmem">RLimitMEM</A> or +<A HREF="#rlimitcpu">RLimitCPU</A>. <P><HR> -<H2><A name="satisfy">Satisfy directive</A></H2> +<H2><A NAME="satisfy">Satisfy directive</A></H2> <!--%plaintext <?INDEX {\tt Satisfy} directive> --> <A HREF="directive-dict.html#Syntax" @@ -2188,7 +2230,8 @@ See also <A HREF="#rlimitmem">RLimitMEM</A> or <A HREF="#rlimitcpu">RLimitCPU</A <A HREF="directive-dict.html#Compatibility" REL="Help" -><STRONG>Compatibility:</STRONG></A> Satisfy is only available in Apache 1.2 and later<P> +><STRONG>Compatibility:</STRONG></A> Satisfy is only available in Apache 1.2 +and later<P> Access policy if both allow and require used. The parameter can be either <EM>'all'</EM> or <EM>'any'</EM>. This directive is only useful @@ -2204,7 +2247,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" @@ -2213,7 +2256,8 @@ clients from particular addresses in without prompting for a password. <A HREF="directive-dict.html#Default" REL="Help" -><STRONG>Default:</STRONG></A> <CODE>ScoreBoardFile logs/apache_status</CODE><BR> +><STRONG>Default:</STRONG></A> <CODE>ScoreBoardFile logs/apache_status</CODE> +<BR> <A HREF="directive-dict.html#Context" REL="Help" @@ -2255,7 +2299,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" @@ -2276,7 +2320,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" @@ -2298,7 +2342,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" @@ -2327,12 +2371,13 @@ 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" REL="Help" -><STRONG>Syntax:</STRONG></A> ServerName <EM>fully-qualified domain name</EM><BR> +><STRONG>Syntax:</STRONG></A> ServerName <EM>fully-qualified domain name</EM> +<BR> <A HREF="directive-dict.html#Context" REL="Help" @@ -2355,7 +2400,7 @@ were <CODE>monster.wibble.com</CODE>.<P> </P> <HR> -<H2><A name="serverpath">ServerPath directive</A></H2> +<H2><A NAME="serverpath">ServerPath directive</A></H2> <A HREF="directive-dict.html#Syntax" @@ -2383,7 +2428,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" @@ -2426,7 +2471,8 @@ for information on how to properly set permissions on the ServerRoot.<P> <A HREF="directive-dict.html#Context" REL="Help" -><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess<BR> +><STRONG>Context:</STRONG></A> server config, virtual host, directory, +.htaccess<BR> <A HREF="directive-dict.html#Status" REL="Help" @@ -2434,7 +2480,8 @@ for information on how to properly set permissions on the ServerRoot.<P> <A HREF="directive-dict.html#Compatibility" REL="Help" -><STRONG>Compatibility:</STRONG></A> ServerSignature is only available in Apache +><STRONG>Compatibility:</STRONG></A> ServerSignature is only available in +Apache 1.3 and later.<P> The ServerSignature directive allows the configuration of a trailing @@ -2454,7 +2501,7 @@ referenced document. <HR> -<H2><A name="servertokens">ServerTokens directive</A></H2> +<H2><A NAME="servertokens">ServerTokens directive</A></H2> <!--%plaintext <?INDEX {\tt ServerTokens} directive> --> <A HREF="directive-dict.html#Syntax" @@ -2490,7 +2537,8 @@ OS-type of the server as well as information about compiled-in modules. </DD> <DT><CODE>ServerTokens Full</CODE> (or not specified) </DT> - <DD>Server sends (e.g.): <SAMP>Server: Apache/1.3.0 (UNIX) PHP/3.0 MyMod/1.2</SAMP> + <DD>Server sends (e.g.): <SAMP>Server: Apache/1.3.0 (UNIX) PHP/3.0 + MyMod/1.2</SAMP> </DD> </DL> <P> @@ -2504,7 +2552,7 @@ identity string. <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" @@ -2548,7 +2596,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" @@ -2584,7 +2632,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" @@ -2615,7 +2663,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" @@ -2654,18 +2702,20 @@ a packet is sent. <P><HR> -<H2><A name="usecanonicalname">UseCanonicalName directive</A></H2> +<H2><A NAME="usecanonicalname">UseCanonicalName directive</A></H2> <!--%plaintext <?INDEX {\tt UseCanonicalName} directive> --> <A HREF="directive-dict.html#Syntax" REL="Help"> <STRONG>Syntax:</STRONG></A> UseCanonicalName <EM>on|off</EM><BR> <A HREF="directive-dict.html#Default" REL="Help"> <STRONG>Default:</STRONG></A> <CODE>UseCanonicalName on</CODE><BR> <A HREF="directive-dict.html#Context" REL="Help"> -<STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess<BR> +<STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess +<BR> <A HREF="directive-dict.html#Override" REL="Help"> <STRONG>Override:</STRONG></A> AuthConfig<BR> <A HREF="directive-dict.html#Compatibility" REL="Help"> -<STRONG>Compatibility:</STRONG></A> UseCanonicalName is only available in Apache 1.3 and later<P> +<STRONG>Compatibility:</STRONG></A> UseCanonicalName is only available in +Apache 1.3 and later<P> In many situations Apache has to construct a <EM>self-referential</EM> URL. That is, a URL which refers back to the same server. @@ -2707,7 +2757,7 @@ self-referential URLs then it should be just fine. <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" @@ -2758,12 +2808,13 @@ 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" REL="Help" -><STRONG>Syntax:</STRONG></A> <VirtualHost <EM>addr</EM>[:<EM>port</EM>] ...> ... +><STRONG>Syntax:</STRONG></A> <VirtualHost <EM>addr</EM>[:<EM>port</EM>] + ...> ... </VirtualHost> <BR> <A HREF="directive-dict.html#Context" @@ -2805,7 +2856,8 @@ TransferLog logs/host.foo.com-access_log <BR> </VirtualHost> </CODE></BLOCKQUOTE> -Each VirtualHost must correspond to a different IP address, different port number or a +Each VirtualHost must correspond to a different IP address, different port +number or a different host name for the server, in the latter case the server machine must be configured to accept IP packets for multiple addresses. (If the machine does not have multiple network interfaces, diff --git a/docs/manual/mod/mod_access.html b/docs/manual/mod/mod_access.html index c004dd1936..3e5675b3d6 100644 --- a/docs/manual/mod/mod_access.html +++ b/docs/manual/mod/mod_access.html @@ -31,7 +31,7 @@ hostname or IP address. <HR> -<H2><A name="allow">allow directive</A></H2> +<H2><A NAME="allow">allow directive</A></H2> <P> <!--%plaintext <?INDEX {\tt allow} directive> --> <A @@ -92,7 +92,8 @@ See also <A HREF="#deny">deny</A>, <A HREF="#order">order</A>, and </P> <P> -<A name="allowfromenv"><STRONG>Syntax:</STRONG> allow from env=<EM>variablename</EM></A><BR> +<A NAME="allowfromenv"><STRONG>Syntax:</STRONG> allow from + env=<EM>variablename</EM></A><BR> <A HREF="directive-dict.html#Context" REL="Help" @@ -137,7 +138,7 @@ and <A HREF="#order">order</A>. </P> <HR> -<H2><A name="deny">deny directive</A></H2> +<H2><A NAME="deny">deny directive</A></H2> <P> <!--%plaintext <?INDEX {\tt deny} directive> --> <A @@ -197,7 +198,8 @@ See also <A HREF="#allow">allow</A> and <A HREF="#order">order</A>. </P> <P> -<A name="denyfromenv"><STRONG>Syntax:</STRONG> deny from env=<EM>variablename</EM></A><BR> +<A NAME="denyfromenv"><STRONG>Syntax:</STRONG> deny from + env=<EM>variablename</EM></A><BR> <A HREF="directive-dict.html#Context" REL="Help" @@ -243,7 +245,7 @@ and <A HREF="#order">order</A>. </P> <HR> -<H2><A name="order">order directive</A></H2> +<H2><A NAME="order">order directive</A></H2> <P> <!--%plaintext <?INDEX {\tt order} directive> --> <A diff --git a/docs/manual/mod/mod_actions.html b/docs/manual/mod/mod_actions.html index d3cc9d3542..a9f449002c 100644 --- a/docs/manual/mod/mod_actions.html +++ b/docs/manual/mod/mod_actions.html @@ -34,7 +34,7 @@ process files. <HR> -<H2><A name="action">Action directive</A></H2> +<H2><A NAME="action">Action directive</A></H2> <P> <A HREF="directive-dict.html#Syntax" @@ -43,7 +43,8 @@ process files. <A HREF="directive-dict.html#Context" REL="Help" -><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess<BR> +><STRONG>Context:</STRONG></A> server config, virtual host, directory, + .htaccess<BR> <A HREF="directive-dict.html#Override" REL="Help" @@ -70,7 +71,7 @@ CGI PATH_INFO and PATH_TRANSLATED environment variables. </P> <HR> -<H2><A name="script">Script directive</A></H2> +<H2><A NAME="script">Script directive</A></H2> <P> <A HREF="directive-dict.html#Syntax" diff --git a/docs/manual/mod/mod_alias.html b/docs/manual/mod/mod_alias.html index 79bbb0c70f..6ec10f13e4 100644 --- a/docs/manual/mod/mod_alias.html +++ b/docs/manual/mod/mod_alias.html @@ -35,7 +35,7 @@ host filesystem in the the document tree, and for URL redirection. <HR> -<H2><A name="alias">Alias directive</A></H2> +<H2><A NAME="alias">Alias directive</A></H2> <P> <!--%plaintext <?INDEX {\tt Alias} directive> --> <A @@ -74,13 +74,13 @@ server will require a trailing / in order to expand the alias. That is, if you use <CODE>Alias /icons/ /usr/local/apache/icons/</CODE> then the url <CODE>/icons</CODE> will not be aliased. </P> -<p> +<P> Note that you may need to specify additional -<a href="core.html#directory"><code><Directory></code></a> sections -which cover the <i>destination</i> of aliases. Aliasing occurs -before <code><Directory></code> sections are checked, so only +<A HREF="core.html#directory"><CODE><Directory></CODE></A> sections +which cover the <EM>destination</EM> of aliases. Aliasing occurs +before <CODE><Directory></CODE> sections are checked, so only the destination of aliases are affected. (Note however -<a href="core.html#location"><code><Location></code></a> +<A HREF="core.html#location"><CODE><Location></CODE></A> sections are run through once before aliases are performed, so they will apply.) <P> @@ -88,7 +88,7 @@ See also <A HREF="#scriptalias">ScriptAlias</A>. </P> <HR> -<H2><A name="aliasmatch">AliasMatch</A></H2> +<H2><A NAME="aliasmatch">AliasMatch</A></H2> <P> <A HREF="directive-dict.html#Syntax" @@ -125,17 +125,19 @@ to activate the <CODE>/icons</CODE> directory, one might use: <HR> -<H2><A name="redirect">Redirect directive</A></H2> +<H2><A NAME="redirect">Redirect directive</A></H2> <P> <!--%plaintext <?INDEX {\tt Redirect} directive> --> <A HREF="directive-dict.html#Syntax" REL="Help" -><STRONG>Syntax:</STRONG></A> Redirect [ <EM>status</EM> ] <EM>url-path url</EM><BR> +><STRONG>Syntax:</STRONG></A> Redirect [ <EM>status</EM> ] + <EM>url-path url</EM><BR> <A HREF="directive-dict.html#Context" REL="Help" -><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess<BR> +><STRONG>Context:</STRONG></A> server config, virtual host, directory, + .htaccess<BR> <A HREF="directive-dict.html#Status" REL="Help" @@ -204,12 +206,13 @@ the function <CODE>send_error_response</CODE> in http_protocol.c). </P> <HR> -<H2><A name="redirectmatch">RedirectMatch</A></H2> +<H2><A NAME="redirectmatch">RedirectMatch</A></H2> <P> <A HREF="directive-dict.html#Syntax" REL="Help" -><STRONG>Syntax:</STRONG></A> RedirectMatch [<EM>status</EM> <EM>regex url</EM><BR> +><STRONG>Syntax:</STRONG></A> RedirectMatch [<EM>status</EM> <EM>regex url</EM> +<BR> <A HREF="directive-dict.html#Context" REL="Help" @@ -242,7 +245,7 @@ one might use: <HR> -<H2><A name="redirecttemp">RedirectTemp directive</A></H2> +<H2><A NAME="redirecttemp">RedirectTemp directive</A></H2> <P> <!--%plaintext <?INDEX {\tt Redirect} directive> --> <A @@ -252,7 +255,8 @@ one might use: <A HREF="directive-dict.html#Context" REL="Help" -><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess<BR> +><STRONG>Context:</STRONG></A> server config, virtual host, directory, + .htaccess<BR> <A HREF="directive-dict.html#Status" REL="Help" @@ -273,7 +277,7 @@ temporary</CODE>. </P> <HR> -<H2><A name="redirectperm">RedirectPermanent directive</A></H2> +<H2><A NAME="redirectperm">RedirectPermanent directive</A></H2> <P> <!--%plaintext <?INDEX {\tt Redirect} directive> --> <A @@ -283,7 +287,8 @@ temporary</CODE>. <A HREF="directive-dict.html#Context" REL="Help" -><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess<BR> +><STRONG>Context:</STRONG></A> server config, virtual host, directory, + .htaccess<BR> <A HREF="directive-dict.html#Status" REL="Help" @@ -303,13 +308,14 @@ This directive makes the client know that the Redirect is permanent </P> <HR> -<H2><A name="scriptalias">ScriptAlias directive</A></H2> +<H2><A NAME="scriptalias">ScriptAlias directive</A></H2> <P> <!--%plaintext <?INDEX {\tt ScriptAlias} directive> --> <A HREF="directive-dict.html#Syntax" REL="Help" -><STRONG>Syntax:</STRONG></A> ScriptAlias <EM>url-path directory-filename</EM><BR> +><STRONG>Syntax:</STRONG></A> ScriptAlias <EM>url-path directory-filename</EM> +<BR> <A HREF="directive-dict.html#Context" REL="Help" @@ -340,12 +346,13 @@ run the script /web/cgi-bin/foo. <HR> -<H2><A name="scriptaliasmatch">ScriptAliasMatch</A></H2> +<H2><A NAME="scriptaliasmatch">ScriptAliasMatch</A></H2> <P> <A HREF="directive-dict.html#Syntax" REL="Help" -><STRONG>Syntax:</STRONG></A> ScriptAliasMatch <EM>regex directory-filename</EM><BR> +><STRONG>Syntax:</STRONG></A> ScriptAliasMatch + <EM>regex directory-filename</EM><BR> <A HREF="directive-dict.html#Context" REL="Help" diff --git a/docs/manual/mod/mod_auth.html b/docs/manual/mod/mod_auth.html index ba673dfcb1..0d1fb8184d 100644 --- a/docs/manual/mod/mod_auth.html +++ b/docs/manual/mod/mod_auth.html @@ -122,7 +122,8 @@ See also <A HREF="core.html#authname">AuthName</A>, <A HREF="directive-dict.html#Syntax" REL="Help" -><STRONG>Syntax:</STRONG></A> AuthAuthoritative < <STRONG> on</STRONG>(default) | off > <BR> +><STRONG>Syntax:</STRONG></A> AuthAuthoritative < + <STRONG> on</STRONG>(default) | off > <BR> <A HREF="directive-dict.html#Context" REL="Help" @@ -172,7 +173,8 @@ well protected AuthUserFile. <A HREF="directive-dict.html#Default" REL="Help" -><STRONG>Default:</STRONG></A> By default; control is not passed on; and an unknown +><STRONG>Default:</STRONG></A> By default; control is not passed on; and an + unknown userID or rule will result in an Authorization Required reply. Not setting it thus keeps the system secure; and forces an NSCA compliant behaviour. diff --git a/docs/manual/mod/mod_auth_anon.html b/docs/manual/mod/mod_auth_anon.html index e97787e08e..3ab8b2cef2 100644 --- a/docs/manual/mod/mod_auth_anon.html +++ b/docs/manual/mod/mod_auth_anon.html @@ -40,7 +40,7 @@ allows users to share URLs. <A HREF="#Sourcecode">Sourcecode</A> <P> -<H2><A name="Directives">Directives</A></H2> +<H2><A NAME="Directives">Directives</A></H2> <UL> <LI><A HREF="#anonymous">Anonymous</A> <LI><A HREF="#Authoritative">Anonymous_Authoritative</A> @@ -52,7 +52,7 @@ allows users to share URLs. <HR> -<H2><A name="anonymous">Anonymous directive</A></H2> +<H2><A NAME="anonymous">Anonymous directive</A></H2> <!--%plaintext <?INDEX {\tt Anonymous} directive> --> <A HREF="directive-dict.html#Syntax" @@ -98,7 +98,7 @@ allows users to share URLs. 'I Don't Know'. <HR> -<H2><A name="Authoritative">Anonymous_Authoritative directive</A></H2> +<H2><A NAME="Authoritative">Anonymous_Authoritative directive</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" @@ -135,7 +135,7 @@ allows users to share URLs. in which the Authorization modules are queried. <HR> -<H2><A name="LogEmail">Anonymous_LogEmail directive</A></H2> +<H2><A NAME="LogEmail">Anonymous_LogEmail directive</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" @@ -165,12 +165,13 @@ allows users to share URLs. contains a sensible email address) is logged in the httpd-log file. <HR> -<H2><A name="MustGiveEmail">Anonymous_MustGiveEmail directive</A></H2> +<H2><A NAME="MustGiveEmail">Anonymous_MustGiveEmail directive</A></H2> <!--%plaintext <?INDEX {\tt Anonymous_MustGiveEmail} directive> --> <A HREF="directive-dict.html#Syntax" REL="Help" -><STRONG>Syntax:</STRONG></A> Anonymous_MustGiveEmail <EM>on</EM> | <EM>off</EM><BR> +><STRONG>Syntax:</STRONG></A> Anonymous_MustGiveEmail <EM>on</EM> + | <EM>off</EM><BR> <A HREF="directive-dict.html#Default" REL="Help" @@ -196,7 +197,7 @@ allows users to share URLs. address as the password. This prohibits blank passwords. <HR> -<H2><A name="NoUserID">Anonymous_NoUserID directive</A></H2> +<H2><A NAME="NoUserID">Anonymous_NoUserID directive</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" @@ -230,7 +231,7 @@ allows users to share URLs. <HR> -<H2><A name="VerifyEmail">Anonymous_VerifyEmail directive</A></H2> +<H2><A NAME="VerifyEmail">Anonymous_VerifyEmail directive</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" @@ -261,7 +262,7 @@ allows users to share URLs. valid email addresses (see the above <CODE>Auth_LogEmail</CODE>). <HR> -<H2><A name="Example">Example</A></H2> +<H2><A NAME="Example">Example</A></H2> The example below (when combined with the Auth directives of a htpasswd-file based (or GDM, mSQL <EM>etc.</EM>) base access @@ -271,10 +272,11 @@ following properties: <LI> It insists that the user enters a userId. (<CODE>Anonymous_NoUserId</CODE>) <LI> -It insists that the user enters a password. (<CODE>Anonymous_MustGiveEmail</CODE>) +It insists that the user enters a password. +(<CODE>Anonymous_MustGiveEmail</CODE>) <LI> -The password entered must be a valid email address, ie. contain at least one '@' and a '.'. -(<CODE>Anonymous_VerifyEmail</CODE>) +The password entered must be a valid email address, ie. contain at least one +'@' and a '.'. (<CODE>Anonymous_VerifyEmail</CODE>) <LI> The userID must be one of <CODE>anonymous guest www test welcome</CODE> and comparison is <STRONG>not</STRONG> case sensitive. @@ -309,12 +311,12 @@ require valid-user <BR> <HR> -<H2><A name="CompileTimeOptions">Compile Time Options</A></H2> +<H2><A NAME="CompileTimeOptions">Compile Time Options</A></H2> Currently there are no Compile options. <HR> -<H2><A name="RevisionHistory">Revision History</A></H2> +<H2><A NAME="RevisionHistory">Revision History</A></H2> This version: 23 Nov 1995, 24 Feb 1996, 16 May 1996. @@ -332,11 +334,13 @@ This version: 23 Nov 1995, 24 Feb 1996, 16 May 1996. <HR> -<H2><A name="Person">Contact/person to blame</A></H2> +<H2><A NAME="Person">Contact/person to blame</A></H2> This module was written for the <A HREF="http://ewse.ceo.org">European Wide Service Exchange</A> by -<<A HREF="mailto:Dirk.vanGulik@jrc.it"><CODE>Dirk.vanGulik@jrc.it</CODE></A>>. +<<A + HREF="mailto:Dirk.vanGulik@jrc.it" + ><CODE>Dirk.vanGulik@jrc.it</CODE></A>>. Feel free to contact me if you have any problems, ice-creams or bugs. This documentation, courtesy of Nick Himba, <A HREF="mailto:himba@cs.utwente.nl"> <CODE><himba@cs.utwente.nl></CODE></A>. diff --git a/docs/manual/mod/mod_auth_db.html b/docs/manual/mod/mod_auth_db.html index 111865a28e..707e4586b9 100644 --- a/docs/manual/mod/mod_auth_db.html +++ b/docs/manual/mod/mod_auth_db.html @@ -26,8 +26,8 @@ On some BSD systems (e.g. FreeBSD and NetBSD) dbm is automatically mapped to Berkeley DB. You can use either <A HREF="mod_auth_dbm.html">mod_auth_dbm</A> or mod_auth_db. The latter makes it more obvious that it's Berkeley DB. On other platforms where you want to use the DB library you usually have to -install it first. See <A -HREF="http://www.sleepycat.com/">http://www.sleepycat.com/</A> for the +install it first. See +<A HREF="http://www.sleepycat.com/">http://www.sleepycat.com/</A> for the distribution. The interface this module uses is the one from DB version 1.85 and 1.86, but DB version 2.x can also be used when compatibility mode is enabled. @@ -157,7 +157,8 @@ See also <A HREF="core.html#authname">AuthName</A>, <A HREF="directive-dict.html#Syntax" REL="Help" -><STRONG>Syntax:</STRONG></A> AuthDBAuthoritative < <STRONG> on</STRONG>(default) | off > <BR> +><STRONG>Syntax:</STRONG></A> AuthDBAuthoritative < + <STRONG> on</STRONG>(default) | off > <BR> <A HREF="directive-dict.html#Context" REL="Help" @@ -197,7 +198,8 @@ a lower level with a well protected .htpasswd file. <P> <A HREF="directive-dict.html#Default" REL="Help" -><STRONG>Default:</STRONG></A> By default; control is not passed on; and an unknown +><STRONG>Default:</STRONG></A> By default; control is not passed on; and an +unknown userID or rule will result in an Authorization Required reply. Not setting it thus keeps the system secure; and forces an NSCA compliant behaviour. <P> diff --git a/docs/manual/mod/mod_auth_dbm.html b/docs/manual/mod/mod_auth_dbm.html index 41f105bda1..cf194ce149 100644 --- a/docs/manual/mod/mod_auth_dbm.html +++ b/docs/manual/mod/mod_auth_dbm.html @@ -29,7 +29,7 @@ DBM files. <HR> -<H2><A name="authdbmgroupfile">AuthDbmGroupFile</A></H2> +<H2><A NAME="authdbmgroupfile">AuthDbmGroupFile</A></H2> <!--%plaintext <?INDEX {\tt AuthDbmGroupFile} directive> --> <A HREF="directive-dict.html#Syntax" @@ -93,7 +93,7 @@ See also <A HREF="core.html#authname">AuthName</A>, <A HREF="core.html#authtype">AuthType</A> and <A HREF="#authdbmuserfile">AuthDBMUserFile</A>.<P><HR> -<H2><A name="authdbmuserfile">AuthDBMUserFile</A></H2> +<H2><A NAME="authdbmuserfile">AuthDBMUserFile</A></H2> <!--%plaintext <?INDEX {\tt AuthDBMUserFile} directive> --> <A HREF="directive-dict.html#Syntax" @@ -143,7 +143,7 @@ See also <A HREF="core.html#authname">AuthName</A>, <A HREF="#authdbmgroupfile">AuthDBMGroupFile</A>.<P> <HR> -<H2><A name="authdbmauthoritative">AuthDBMAuthoritative</A></H2> +<H2><A NAME="authdbmauthoritative">AuthDBMAuthoritative</A></H2> <!--%plaintext <?INDEX {\tt AuthDBMAuthoritative} directive> --> <A HREF="directive-dict.html#Syntax" diff --git a/docs/manual/mod/mod_autoindex.html b/docs/manual/mod/mod_autoindex.html index d2685a4b71..2dc71e5411 100644 --- a/docs/manual/mod/mod_autoindex.html +++ b/docs/manual/mod/mod_autoindex.html @@ -78,7 +78,7 @@ order) even though they both are shown as "1K". </MENU> <HR> -<H2><A name="addalt">AddAlt</A></H2> +<H2><A NAME="addalt">AddAlt</A></H2> <!--%plaintext <?INDEX {\tt AddAlt} directive> --> <A HREF="directive-dict.html#Syntax" @@ -109,7 +109,7 @@ to describe. <EM>String</EM> is enclosed in double quotes image-incapable or has image loading disabled. <HR> -<H2><A name="addaltbyencoding">AddAltByEncoding</A></H2> +<H2><A NAME="addaltbyencoding">AddAltByEncoding</A></H2> <!--%plaintext <?INDEX {\tt AddAltByEncoding} directive> --> <A HREF="directive-dict.html#Syntax" @@ -141,7 +141,7 @@ valid content-encoding, such as <SAMP>x-compress</SAMP>. image-incapable or has image loading disabled. <HR> -<H2><A name="addaltbytype">AddAltByType</A></H2> +<H2><A NAME="addaltbytype">AddAltByType</A></H2> <!--%plaintext <?INDEX {\tt AddAltByType} directive> --> <A HREF="directive-dict.html#Syntax" @@ -173,7 +173,7 @@ image-incapable or has image loading disabled. <HR> -<H2><A name="adddescription">AddDescription</A></H2> +<H2><A NAME="adddescription">AddDescription</A></H2> <!--%plaintext <?INDEX {\tt AddDescription} directive> --> <A HREF="directive-dict.html#Syntax" @@ -204,7 +204,7 @@ to describe. <EM>String</EM> is enclosed in double quotes <BLOCKQUOTE><CODE>AddDescription "The planet Mars" /web/pics/mars.gif </CODE></BLOCKQUOTE><P><HR> -<H2><A name="addicon">AddIcon</A></H2> +<H2><A NAME="addicon">AddIcon</A></H2> <!--%plaintext <?INDEX {\tt AddIcon} directive> --> <A HREF="directive-dict.html#Syntax" @@ -244,7 +244,7 @@ AddIcon /icons/backup.xbm *~ <A HREF="#addiconbytype">AddIconByType</A> should be used in preference to AddIcon, when possible.<P><HR> -<H2><A name="addiconbyencoding">AddIconByEncoding</A></H2> +<H2><A NAME="addiconbyencoding">AddIconByEncoding</A></H2> <!--%plaintext <?INDEX {\tt AddIconByEncoding} directive> --> <A HREF="directive-dict.html#Syntax" @@ -280,7 +280,7 @@ content-encoding. Examples: AddIconByEncoding /icons/compress.xbm x-compress </CODE></BLOCKQUOTE><P><HR> -<H2><A name="addiconbytype">AddIconByType</A></H2> +<H2><A NAME="addiconbytype">AddIconByType</A></H2> <!--%plaintext <?INDEX {\tt AddIconByType} directive> --> <A HREF="directive-dict.html#Syntax" @@ -314,7 +314,7 @@ Examples: AddIconByType (IMG,/icons/image.xbm) image/* </CODE></BLOCKQUOTE><P><HR> -<H2><A name="defaulticon">DefaultIcon</A></H2> +<H2><A NAME="defaulticon">DefaultIcon</A></H2> <!--%plaintext <?INDEX {\tt DefaultIcon} directive> --> <A HREF="directive-dict.html#Syntax" @@ -344,7 +344,7 @@ specific icon is known, for <A HREF="#fancyindexing">FancyIndexing</A>. DefaultIcon /icon/unknown.xbm </CODE></BLOCKQUOTE><P><HR> -<H2><A name="fancyindexing">FancyIndexing</A></H2> +<H2><A NAME="fancyindexing">FancyIndexing</A></H2> <!--%plaintext <?INDEX {\tt FancyIndexing} directive> --> <A HREF="directive-dict.html#Syntax" @@ -380,7 +380,7 @@ preference. </BLOCKQUOTE> <HR> -<H2><A name="headername">HeaderName</A></H2> +<H2><A NAME="headername">HeaderName</A></H2> <!--%plaintext <?INDEX {\tt HeaderName} directive> --> <A HREF="directive-dict.html#Syntax" @@ -416,7 +416,7 @@ it will include the plain text file <CODE>/web/HEADER</CODE>, if it exists. <P>See also <A HREF="#readmename">ReadmeName</A>.<P><HR> -<H2><A name="indexignore">IndexIgnore</A></H2> +<H2><A NAME="indexignore">IndexIgnore</A></H2> <!--%plaintext <?INDEX {\tt IndexIgnore} directive> --> <A HREF="directive-dict.html#Syntax" @@ -448,7 +448,7 @@ of ignored files. By default, the list contains `<CODE>.</CODE>'. Example: IndexIgnore README .htaccess *~ </CODE></BLOCKQUOTE><P><HR> -<H2><A name="indexoptions">IndexOptions</A></H2> +<H2><A NAME="indexoptions">IndexOptions</A></H2> <!--%plaintext <?INDEX {\tt IndexOptions} directive> --> <A HREF="directive-dict.html#Syntax" @@ -563,7 +563,7 @@ IndexOptions ScanHTMLTitles <BR> then only <CODE>ScanHTMLTitles</CODE> will be set for the /web/docs/spec directory.<P><HR> -<H2><A name="readmename">ReadmeName</A></H2> +<H2><A NAME="readmename">ReadmeName</A></H2> <!--%plaintext <?INDEX {\tt ReadmeName} directive> --> <A HREF="directive-dict.html#Syntax" diff --git a/docs/manual/mod/mod_cern_meta.html b/docs/manual/mod/mod_cern_meta.html index 5d273db342..0a212830b2 100644 --- a/docs/manual/mod/mod_cern_meta.html +++ b/docs/manual/mod/mod_cern_meta.html @@ -43,7 +43,7 @@ who can exploit this module. <HR> -<H2><A name="metafiles">MetaFiles</A></H2> +<H2><A NAME="metafiles">MetaFiles</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" @@ -72,7 +72,7 @@ and later.<P> Turns on/off Meta file processing on a per-directory basis. This option was introduced in Apache 1.3. -<H2><A name="metadir">MetaDir</A></H2> +<H2><A NAME="metadir">MetaDir</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" @@ -103,7 +103,7 @@ subdirectory of the directory that contains the file being accessed. Set to "<CODE>.</CODE>" to look in the same directory as the file. -<H2><A name="metasuffix">MetaSuffix</A></H2> +<H2><A NAME="metasuffix">MetaSuffix</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" diff --git a/docs/manual/mod/mod_cgi.html b/docs/manual/mod/mod_cgi.html index f5067393ab..94201f0fb5 100644 --- a/docs/manual/mod/mod_cgi.html +++ b/docs/manual/mod/mod_cgi.html @@ -55,7 +55,7 @@ following provisions: <HR> -<H2><A name="cgi_debug">CGI Debugging</A></H2> +<H2><A NAME="cgi_debug">CGI Debugging</A></H2> Debugging CGI scripts has traditionally been difficult, mainly because it has @@ -113,7 +113,7 @@ anything on standard output or standard error). <H2>Directives</H2> -<H3><A name="scriptlog">ScriptLog</A></H3> +<H3><A NAME="scriptlog">ScriptLog</A></H3> <A HREF="directive-dict.html#Syntax" @@ -153,7 +153,7 @@ running servers. It is not optimized for speed or efficiency, and may have security problems if used in a manner other than that for which it was designed.</P> -<H3><A name="scriptloglength">ScriptLogLength</A></H3> +<H3><A NAME="scriptloglength">ScriptLogLength</A></H3> <A HREF="directive-dict.html#Syntax" @@ -180,7 +180,7 @@ file. To prevent problems due to unbounded growth, this directive can be used to set an maximum file-size for the CGI logfile. If the file exceeds this size, no more information will be written to it. -<H3><A name="scriptlogbuffer">ScriptLogBuffer</A></H3> +<H3><A NAME="scriptlogbuffer">ScriptLogBuffer</A></H3> <A HREF="directive-dict.html#Syntax" diff --git a/docs/manual/mod/mod_dir.html b/docs/manual/mod/mod_dir.html index aac0752213..f150aa2e11 100644 --- a/docs/manual/mod/mod_dir.html +++ b/docs/manual/mod/mod_dir.html @@ -44,7 +44,7 @@ slash, so <CODE>mod_dir</CODE> issues a redirect to </MENU> <HR> -<H2><A name="directoryindex">DirectoryIndex</A></H2> +<H2><A NAME="directoryindex">DirectoryIndex</A></H2> <!--%plaintext <?INDEX {\tt DirectoryIndex} directive> --> <A HREF="directive-dict.html#Syntax" diff --git a/docs/manual/mod/mod_env.html b/docs/manual/mod/mod_env.html index d7404b1930..0908220153 100644 --- a/docs/manual/mod/mod_env.html +++ b/docs/manual/mod/mod_env.html @@ -37,7 +37,7 @@ rewriting all their scripts <HR> -<H2><A name="passenv">PassEnv</A></H2> +<H2><A NAME="passenv">PassEnv</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" @@ -68,7 +68,7 @@ from the server's own environment. Example: <HR> -<H2><A name="setenv">SetEnv</A></H2> +<H2><A NAME="setenv">SetEnv</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" @@ -99,7 +99,7 @@ scripts. Example: <HR> -<H2><A name="unsetenv">UnsetEnv</A></H2> +<H2><A NAME="unsetenv">UnsetEnv</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" diff --git a/docs/manual/mod/mod_expires.html b/docs/manual/mod/mod_expires.html index f8f2f5f798..870501e659 100644 --- a/docs/manual/mod/mod_expires.html +++ b/docs/manual/mod/mod_expires.html @@ -3,7 +3,7 @@ <HEAD> <TITLE>Apache module mod_expires</TITLE> </HEAD> - <!-- Background white, links blue (unvisited), navy (visited), red (active) --> +<!-- Background white, links blue (unvisited), navy (visited), red (active) --> <BODY BGCOLOR="#FFFFFF" TEXT="#000000" @@ -64,7 +64,8 @@ <A HREF="directive-dict.html#Context" REL="Help" - ><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess + ><STRONG>Context:</STRONG></A> server config, virtual host, directory, + .htaccess <BR> <A HREF="directive-dict.html#Override" @@ -115,12 +116,14 @@ <A HREF="directive-dict.html#Syntax" REL="Help" - ><STRONG>Syntax:</STRONG></A> ExpiresByType <EM>mime-type <code>seconds</EM> + ><STRONG>Syntax:</STRONG></A> ExpiresByType <EM>mime-type + <code>seconds</EM> <BR> <A HREF="directive-dict.html#Context" REL="Help" - ><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess + ><STRONG>Context:</STRONG></A> server config, virtual host, directory, + .htaccess <BR> <A HREF="directive-dict.html#Override" @@ -205,7 +208,8 @@ <A HREF="directive-dict.html#Context" REL="Help" - ><STRONG>Context:</STRONG></A> server config, virtual host, directory, .htaccess + ><STRONG>Context:</STRONG></A> server config, virtual host, directory, + .htaccess <BR> <A HREF="directive-dict.html#Override" @@ -254,7 +258,8 @@ <DL> <DD><CODE>ExpiresDefault "<base> [plus] {<num> <type>}*" <BR> - ExpiresByType type/encoding "<base> [plus] {<num> <type>}*"</CODE> + ExpiresByType type/encoding "<base> [plus] + {<num> <type>}*"</CODE> </DD> </DL> <P> @@ -302,8 +307,8 @@ </DD> </DL> <P> - The expiry time can be fine-tuned by adding several '<num> <type>' - clauses: + The expiry time can be fine-tuned by adding several '<num> + <type>' clauses: </P> <DL> <DD><CODE>ExpiresByType text/html "access plus 1 month 15 days 2 hours" diff --git a/docs/manual/mod/mod_headers.html b/docs/manual/mod/mod_headers.html index 9d34c3bbef..7d62d5d1fd 100644 --- a/docs/manual/mod/mod_headers.html +++ b/docs/manual/mod/mod_headers.html @@ -29,11 +29,12 @@ compiled with <STRONG>mod_headers.c</STRONG>. <HR> -<H2><A name="header">Header</A></H2> +<H2><A NAME="header">Header</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" -><STRONG>Syntax:</STRONG></A> Header [ set | append | add ] <EM>header</EM> <EM>value</EM><BR> +><STRONG>Syntax:</STRONG></A> Header [ set | append | add ] + <EM>header</EM> <EM>value</EM><BR> <A HREF="directive-dict.html#Syntax" REL="Help" @@ -41,7 +42,8 @@ compiled with <STRONG>mod_headers.c</STRONG>. <A HREF="directive-dict.html#Context" REL="Help" -><STRONG>Context:</STRONG></A> server config, virtual host, access.conf, .htaccess<BR> +><STRONG>Context:</STRONG></A> server config, virtual host, access.conf, + .htaccess<BR> <A HREF="directive-dict.html#Status" REL="Help" diff --git a/docs/manual/mod/mod_imap.html b/docs/manual/mod/mod_imap.html index 5a45100380..69517721ab 100644 --- a/docs/manual/mod/mod_imap.html +++ b/docs/manual/mod/mod_imap.html @@ -62,7 +62,7 @@ possible with previously distributed imagemap programs.<P> <P> -<H3><A name="imapmenu">ImapMenu</A></H3> +<H3><A NAME="imapmenu">ImapMenu</A></H3> <A HREF="directive-dict.html#Syntax" REL="Help" @@ -115,7 +115,7 @@ is called without valid coordinates. <P> -<H3><A name="imapdefault">ImapDefault</A></H3> +<H3><A NAME="imapdefault">ImapDefault</A></H3> <A HREF="directive-dict.html#Syntax" REL="Help" @@ -149,7 +149,7 @@ case, the client should continue to display the original page. <P> -<H3><A name="imapbase">ImapBase</A></H3> +<H3><A NAME="imapbase">ImapBase</A></H3> <A HREF="directive-dict.html#Syntax" REL="Help" diff --git a/docs/manual/mod/mod_include.html b/docs/manual/mod/mod_include.html index 92bac8dee8..fe355d28b1 100644 --- a/docs/manual/mod/mod_include.html +++ b/docs/manual/mod/mod_include.html @@ -358,7 +358,7 @@ elements are: <HR> -<H2><A name="xbithack">XBitHack</A></H2> +<H2><A NAME="xbithack">XBitHack</A></H2> <!--%plaintext <?INDEX {\tt XBitHack} directive> --> <A HREF="directive-dict.html#Syntax" diff --git a/docs/manual/mod/mod_log_agent.html b/docs/manual/mod/mod_log_agent.html index 5f1483f7d7..1506885aba 100644 --- a/docs/manual/mod/mod_log_agent.html +++ b/docs/manual/mod/mod_log_agent.html @@ -25,7 +25,7 @@ compiled in by default. It provides for logging of the client user agents. <HR> -<H2><A name="agentlog">AgentLog</A></H2> +<H2><A NAME="agentlog">AgentLog</A></H2> <!--%plaintext <?INDEX {\tt AgentLog} directive> --> <A HREF="directive-dict.html#Syntax" diff --git a/docs/manual/mod/mod_log_config.html b/docs/manual/mod/mod_log_config.html index 62b526f159..f23ac3daf4 100644 --- a/docs/manual/mod/mod_log_config.html +++ b/docs/manual/mod/mod_log_config.html @@ -154,13 +154,13 @@ Note that the common log format is defined by the string <CODE>"%h %l extending for format if desired (e.g. to add extra fields at the end). NCSA's extended/combined log format would be <CODE>"%h %l %u %t \"%r\" %s %b \"%{Referer}i\" \"%{User-agent}i\""</CODE>. -<p> +<P> -Note that the canonical <a href="core.html#servername">ServerName</a> -and <a href="core.html#port">Port</a> of the server serving the request -are used for <code>%v</code> and <code>%p</code> respectively. This +Note that the canonical <A HREF="core.html#servername">ServerName</A> +and <A HREF="core.html#port">Port</A> of the server serving the request +are used for <CODE>%v</CODE> and <CODE>%p</CODE> respectively. This happens regardless of the -<a href="core.html#usecanonicalname">UseCanonicalName</a> setting because +<A HREF="core.html#usecanonicalname">UseCanonicalName</A> setting because otherwise log analysis programs would have to duplicate the entire vhost matching algorithm in order to decide what host really served the request. @@ -201,7 +201,7 @@ the user that starts the server. <HR> -<H2><A name="cookielog">CookieLog</A></H2> +<H2><A NAME="cookielog">CookieLog</A></H2> <!--%plaintext <?INDEX {\tt CookieLog} directive> --> <A HREF="directive-dict.html#Syntax" @@ -275,7 +275,7 @@ the directive. </P> <HR> -<H2><A name="logformat">LogFormat</A></H2> +<H2><A NAME="logformat">LogFormat</A></H2> <!--%plaintext <?INDEX {\tt LogFormat} directive> --> <A HREF="directive-dict.html#Syntax" @@ -327,7 +327,7 @@ it doesn't actually apply the format and make it the default. </P> <HR> -<H2><A name="transferlog">TransferLog</A></H2> +<H2><A NAME="transferlog">TransferLog</A></H2> <!--%plaintext <?INDEX {\tt TransferLog} directive> --> <A HREF="directive-dict.html#Syntax" diff --git a/docs/manual/mod/mod_log_referer.html b/docs/manual/mod/mod_log_referer.html index 9702128f42..6e500a1f99 100644 --- a/docs/manual/mod/mod_log_referer.html +++ b/docs/manual/mod/mod_log_referer.html @@ -36,7 +36,7 @@ local URL to the document being referred to. <HR> -<H2><A name="refererignore">RefererIgnore</A></H2> +<H2><A NAME="refererignore">RefererIgnore</A></H2> <!--%plaintext <?INDEX {\tt RefererIgnore} directive> --> <A HREF="directive-dict.html#Syntax" @@ -64,7 +64,7 @@ This avoids logging references from www.ncsa.uiuc.edu. <P><HR> -<H2><A name="refererlog">RefererLog</A></H2> +<H2><A NAME="refererlog">RefererLog</A></H2> <!--%plaintext <?INDEX {\tt RefererLog} directive> --> <A HREF="directive-dict.html#Syntax" diff --git a/docs/manual/mod/mod_mime.html b/docs/manual/mod/mod_mime.html index 508fd139fb..08d7e85852 100644 --- a/docs/manual/mod/mod_mime.html +++ b/docs/manual/mod/mod_mime.html @@ -84,7 +84,7 @@ copies may still be used by a client or proxy. <HR> -<H2><A name="addencoding">AddEncoding</A></H2> +<H2><A NAME="addencoding">AddEncoding</A></H2> <!--%plaintext <?INDEX {\tt AddEncoding} directive> --> <A HREF="directive-dict.html#Syntax" @@ -119,21 +119,21 @@ AddEncoding x-compress Z This will cause files ending in .gz to be marked as encoded using the x-gzip encoding, and .Z files to be marked as encoded with x-compress.<P> -Old clients expect <code>x-gzip</code> and <code>x-compress</code>, -however the standard dictates that they're equivalent to <code>gzip</code> -and <code>compress</code> respectively. Apache does content encoding -comparisons by ignoring any leading <code>x-</code>. When responding -with an encoding Apache will use whatever form (i.e. <code>x-foo</code> -or <code>foo</code>) the client requested. If the client didn't +Old clients expect <CODE>x-gzip</CODE> and <CODE>x-compress</CODE>, +however the standard dictates that they're equivalent to <CODE>gzip</CODE> +and <CODE>compress</CODE> respectively. Apache does content encoding +comparisons by ignoring any leading <CODE>x-</CODE>. When responding +with an encoding Apache will use whatever form (i.e. <CODE>x-foo</CODE> +or <CODE>foo</CODE>) the client requested. If the client didn't specifically request a particular form Apache will use the form given by -the <code>AddEncoding</code> directive. To make this long story short, -you should always use <code>x-gzip</code> and <code>x-compress</code> +the <CODE>AddEncoding</CODE> directive. To make this long story short, +you should always use <CODE>x-gzip</CODE> and <CODE>x-compress</CODE> for these two specific encodings. More recent encodings, such as -<code>deflate</code> should be specified without the <code>x-</code>. +<CODE>deflate</CODE> should be specified without the <CODE>x-</CODE>. <P><HR> -<H2><A name="addhandler">AddHandler</A></H2> +<H2><A NAME="addhandler">AddHandler</A></H2> <A HREF="directive-dict.html#Syntax" @@ -170,7 +170,7 @@ file ending with "<CODE>.cgi</CODE>" will be treated as a CGI program.</P> <HR> -<H2><A name="addlanguage">AddLanguage</A></H2> +<H2><A NAME="addlanguage">AddLanguage</A></H2> <!--%plaintext <?INDEX {\tt AddLanguage} directive> --> <A HREF="directive-dict.html#Syntax" @@ -209,7 +209,7 @@ the browser is unlikely to use this information. The AddLanguage directive is more useful for content negotiation, where the server returns one from several documents based on the client's language preference.<P><HR> -<H2><A name="addtype">AddType</A></H2> +<H2><A NAME="addtype">AddType</A></H2> <!--%plaintext <?INDEX {\tt AddType} directive> --> <A HREF="directive-dict.html#Syntax" @@ -244,7 +244,7 @@ rather than changing the <A HREF="#typesconfig">TypesConfig</A> file.<P> Note that, unlike the NCSA httpd, this directive cannot be used to set the type of particular files.<P><HR> -<H2><A name="forcetype">ForceType</A></H2> +<H2><A NAME="forcetype">ForceType</A></H2> <A HREF="directive-dict.html#Syntax" @@ -280,7 +280,7 @@ had a directory full of GIF files, but did not want to label them all with <P>Note that this will override any filename extensions that might determine the media type.</P><HR> -<H2><A name="sethandler">SetHandler</A></H2> +<H2><A NAME="sethandler">SetHandler</A></H2> <A HREF="directive-dict.html#Syntax" @@ -326,7 +326,7 @@ called, you might put the following into access.conf: </PRE> <HR> -<H2><A name="typesconfig">TypesConfig</A></H2> +<H2><A NAME="typesconfig">TypesConfig</A></H2> <!--%plaintext <?INDEX {\tt TypesConfig} directive> --> <A HREF="directive-dict.html#Syntax" diff --git a/docs/manual/mod/mod_mime_magic.html b/docs/manual/mod/mod_mime_magic.html index 2eefce1ee5..8efde7ea56 100644 --- a/docs/manual/mod/mod_mime_magic.html +++ b/docs/manual/mod/mod_mime_magic.html @@ -205,7 +205,7 @@ <P> <HR> - <H2><A name="notes">Notes</A></H2> + <H2><A NAME="notes">Notes</A></H2> The following notes apply to the mod_mime_magic module and are included here for compliance with contributors' copyright restrictions diff --git a/docs/manual/mod/mod_mmap_static.html b/docs/manual/mod/mod_mmap_static.html index 57b1273b59..77100488ea 100644 --- a/docs/manual/mod/mod_mmap_static.html +++ b/docs/manual/mod/mod_mmap_static.html @@ -30,7 +30,7 @@ This is an <STRONG>experimental</STRONG> module and should be used with care. You can easily create a broken site using this module, read this document carefully. - <code>mod_mmap_static</code> maps a list of statically configured files (via + <CODE>mod_mmap_static</CODE> maps a list of statically configured files (via <CODE>MMapFile</CODE> directives in the main server configuration) into memory through the system call <CODE>mmap()</CODE>. This system call is available on most modern Unix derivates, but not on all. There @@ -41,7 +41,7 @@ This mmap()ing is done once at server start or restart, only. So whenever one of the mapped files changes on the filesystem you <EM>have</EM> to restart the server by at least sending it a HUP or USR1 signal (see the - <a href="../stopping.html">Stopping and Restarting</a> documentation). To + <A HREF="../stopping.html">Stopping and Restarting</A> documentation). To reiterate that point: if the files are modified <EM>in place</EM> without restarting the server you may end up serving requests that are completely bogus. You should update files by unlinking the old copy and putting a new @@ -110,8 +110,8 @@ create. We cannot compare inodes or other stuff to match paths through symbolic links etc. because that again would cost extra <CODE>stat()</CODE> system calls which is not acceptable. This module may or may not work - with filenames rewritten by <code>mod_alias</code> or - <code>mod_rewrite</code>... it is an experiment after all. + with filenames rewritten by <CODE>mod_alias</CODE> or + <CODE>mod_rewrite</CODE>... it is an experiment after all. </P> <P> @@ -127,13 +127,15 @@ </PRE> <P> - <b>Note</b>: don't bother asking for a for a <code>MMapDir</code> directive which + <STRONG>Note</STRONG>: don't bother asking for a for a <CODE>MMapDir</CODE> + directive which recursively maps all the files in a directory. Use Unix the way it was meant to be used. For example, see the - <a href="core.html#include">Include</a> directive, and consider this command: - <blockquote><pre> - find /www/htdocs -type f -print | sed -e 's/.*/mmapfile &/' > /www/conf/mmap.conf - </pre></blockquote> + <A HREF="core.html#include">Include</A> directive, and consider this command: + <PRE> + find /www/htdocs -type f -print \ + | sed -e 's/.*/mmapfile &/' > /www/conf/mmap.conf + </PRE> <!--#include virtual="footer.html" --> </BODY> diff --git a/docs/manual/mod/mod_negotiation.html b/docs/manual/mod/mod_negotiation.html index 4102fc4996..e2578bd27d 100644 --- a/docs/manual/mod/mod_negotiation.html +++ b/docs/manual/mod/mod_negotiation.html @@ -94,7 +94,7 @@ requirements, and returns that document.<P> <HR> -<H2><A name="cachenegotiateddocs">CacheNegotiatedDocs</A></H2> +<H2><A NAME="cachenegotiateddocs">CacheNegotiatedDocs</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" @@ -131,7 +131,7 @@ HTTP/1.1 requests. -<H2><A name="languagepriority">LanguagePriority</A></H2> +<H2><A NAME="languagepriority">LanguagePriority</A></H2> <!--%plaintext <?INDEX {\tt LanguagePriority} directive> --> <A HREF="directive-dict.html#Syntax" diff --git a/docs/manual/mod/mod_rewrite.html b/docs/manual/mod/mod_rewrite.html index 9392768162..ce5f5e14fa 100644 --- a/docs/manual/mod/mod_rewrite.html +++ b/docs/manual/mod/mod_rewrite.html @@ -1316,8 +1316,8 @@ Some hints about the syntax of regular expressions: <STRONG>Quantifiers:</STRONG> <STRONG><CODE>?</CODE></STRONG> 0 or 1 of the preceding text - <STRONG><CODE>*</CODE></STRONG> 0 or N of the preceding text (N > 1) - <STRONG><CODE>+</CODE></STRONG> 1 or N of the preceding text (N > 1) + <STRONG><CODE>*</CODE></STRONG> 0 or N of the preceding text (N > 1) + <STRONG><CODE>+</CODE></STRONG> 1 or N of the preceding text (N > 1) <STRONG>Grouping:</STRONG> <STRONG><CODE>(</CODE></STRONG>text<STRONG><CODE>)</CODE></STRONG> Grouping of text diff --git a/docs/manual/mod/mod_setenvif.html b/docs/manual/mod/mod_setenvif.html index 46a91d5db8..4d2b26fac7 100644 --- a/docs/manual/mod/mod_setenvif.html +++ b/docs/manual/mod/mod_setenvif.html @@ -26,15 +26,15 @@ regular expressions you specify. These envariables can be used by other parts of the server to make decisions about actions to be taken. </P> - <p>The directives are considered in the order they appear in the + <P>The directives are considered in the order they appear in the configuration files. So more complex sequences can be used, such - as this example, which sets <code>netscape</code> if the browser + as this example, which sets <CODE>netscape</CODE> if the browser is mozilla but not MSIE. - <blockquote><pre> + <BLOCKQUOTE><PRE> BrowserMatch ^Mozilla netscape BrowserMatch MSIE !netscape - </pre></blockquote> - </p> + </PRE></BLOCKQUOTE> + </P> <H2>Directives</H2> <UL> @@ -154,7 +154,8 @@ <A HREF="directive-dict.html#Syntax" REL="Help" - ><STRONG>Syntax:</STRONG></A> BrowserMatchNoCase <EM>regex envar[=value] [...]</EM> + ><STRONG>Syntax:</STRONG></A> BrowserMatchNoCase <EM>regex envar[=value] + [...]</EM> <BR> <A HREF="directive-dict.html#Default" @@ -226,7 +227,8 @@ <A HREF="directive-dict.html#Syntax" REL="Help" - ><STRONG>Syntax:</STRONG></A> SetEnvIf <EM> attribute regex envar[=value] [...]</EM> + ><STRONG>Syntax:</STRONG></A> SetEnvIf <EM> attribute regex envar[=value] + [...]</EM> <BR> <A HREF="directive-dict.html#Default" diff --git a/docs/manual/mod/mod_so.html b/docs/manual/mod/mod_so.html index 71bf56feb3..789e7b1afa 100644 --- a/docs/manual/mod/mod_so.html +++ b/docs/manual/mod/mod_so.html @@ -44,7 +44,7 @@ Shared Object</A> (DSO) mechanism, rather than requiring a recompilation. <HR> -<H2><A name="loadfile">LoadFile</A></H2> +<H2><A NAME="loadfile">LoadFile</A></H2> <!--%plaintext <?INDEX {\tt LoadFile} directive> --> <A HREF="directive-dict.html#Syntax" @@ -69,7 +69,7 @@ additional code which may be required for some module to work. <EM>Filename</EM> is either and absolute path or relative to <A HREF="core.html#serverroot">ServerRoot</A>.<P><HR> -<H2><A name="loadmodule">LoadModule</A></H2> +<H2><A NAME="loadmodule">LoadModule</A></H2> <!--%plaintext <?INDEX {\tt LoadModule} directive> --> <A HREF="directive-dict.html#Syntax" @@ -108,7 +108,7 @@ ServerRoot.<P> <HR> -<H2><A name="creating">Creating DLL Modules for Windows</A></H2> +<H2><A NAME="creating">Creating DLL Modules for Windows</A></H2> <P>The Apache module API is unchanged between the Unix and Windows versions. Many modules will run on Windows with no or little change diff --git a/docs/manual/mod/mod_speling.html b/docs/manual/mod/mod_speling.html index 4bb933f88c..95f926de6d 100644 --- a/docs/manual/mod/mod_speling.html +++ b/docs/manual/mod/mod_speling.html @@ -57,7 +57,7 @@ </MENU> <HR> <!-- the HR is part of the directive description --> - <H2><A name="checkspelling">CheckSpelling</A></H2> + <H2><A NAME="checkspelling">CheckSpelling</A></H2> <!--%plaintext <?INDEX {\tt CheckSpelling} directive> --> <A HREF="directive-dict.html#Syntax" @@ -82,9 +82,10 @@ <A HREF="directive-dict.html#Compatibility" REL="Help" - ><STRONG>Compatibility:</STRONG></A> CheckSpelling was available as a separately + ><STRONG>Compatibility:</STRONG></A> CheckSpelling was available as a + separately available module for Apache 1.1, but was limited to miscapitalizations. - As of Apache 1.3, it is part of the apache distribution<!-- or: + As of Apache 1.3, it is part of the Apache distribution<!-- or: available as a separate module-->.<P> This directive enables or disables the spelling module. When enabled, diff --git a/docs/manual/mod/mod_status.html b/docs/manual/mod/mod_status.html index 565273581c..6b61adfa26 100644 --- a/docs/manual/mod/mod_status.html +++ b/docs/manual/mod/mod_status.html @@ -1,7 +1,9 @@ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> -<HTML><HEAD> -<TITLE>Apache module mod_status</TITLE> -</HEAD><!-- Background white, links blue (unvisited), navy (visited), red (active) --> +<HTML> + <HEAD> + <TITLE>Apache module mod_status</TITLE> + </HEAD> +<!-- Background white, links blue (unvisited), navy (visited), red (active) --> <BODY BGCOLOR="#FFFFFF" TEXT="#000000" @@ -69,8 +71,8 @@ Note that mod_status will only work when you are running Apache in <H3>Automatic Updates</H3> You can get the status page to update itself automatically if you have a browser that supports "refresh". Access the page -<CODE>http://your.server.name/server-status?refresh=N</CODE> to refresh the page -every N seconds. +<CODE>http://your.server.name/server-status?refresh=N</CODE> to refresh the +page every N seconds. <H3>Machine Readable Status File</H3> A machine-readable version of the status file is available by accessing the page <CODE>http://your.server.name/server-status?auto</CODE>. This is useful diff --git a/docs/manual/mod/mod_userdir.html b/docs/manual/mod/mod_userdir.html index 8b7b36308c..570b1b042a 100644 --- a/docs/manual/mod/mod_userdir.html +++ b/docs/manual/mod/mod_userdir.html @@ -25,7 +25,7 @@ is compiled in by default. It provides for user-specific directories. <HR> -<H2><A name="userdir">UserDir</A></H2> +<H2><A NAME="userdir">UserDir</A></H2> <!--%plaintext <?INDEX {\tt UserDir} directive> --> <A HREF="directive-dict.html#Syntax" @@ -90,9 +90,9 @@ UserDir /home/*/www -> /home/bob/www/one/two.html </PRE> The following directives will send redirects to the client: <PRE> -UserDir http://www.foo.com/users -> http//www.foo.com/users/bob/one/two.html -UserDir http://www.foo.com/*/usr -> http://www.foo.com/bob/usr/one/two.html -UserDir http://www.foo.com/~*/ -> http://www.foo.com/~bob/one/two.html +UserDir http://www.foo.com/users -> http://www.foo.com/users/bob/one/two.html +UserDir http://www.foo.com/*/usr -> http://www.foo.com/bob/usr/one/two.html +UserDir http://www.foo.com/~*/ -> http://www.foo.com/~bob/one/two.html </PRE> </P> <BLOCKQUOTE> diff --git a/docs/manual/mod/mod_usertrack.html b/docs/manual/mod/mod_usertrack.html index a733235cd7..024e509ba6 100644 --- a/docs/manual/mod/mod_usertrack.html +++ b/docs/manual/mod/mod_usertrack.html @@ -52,7 +52,7 @@ above <TT>CustomLog</TT> directive. <HR> -<H2><A name="cookieexpires">CookieExpires</A></H2> +<H2><A NAME="cookieexpires">CookieExpires</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" @@ -81,7 +81,7 @@ double quotes. <P>If this directive is not used, cookies last only for the current browser session.</P> -<H2><A name="cookietracking">CookieTracking</A></H2> +<H2><A NAME="cookietracking">CookieTracking</A></H2> <A HREF="directive-dict.html#Syntax" REL="Help" |