<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Core</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in Apache 2.0.30 and later</td></tr>
+<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td><compatibility>Available in Apache 2.0.30 and later</compatibility></td></tr>
</table>
<p>This directive controls whether requests that contain trailing
<span class="indent">
Options +Includes<br />
SetOutputFilter INCLUDES<br />
- AcceptPathInfo on<br />
+ AcceptPathInfo On<br />
</span>
</Files>
</code></p></div>
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Core</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in Apache 2.0.33 and later</td></tr>
+<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td><compatibility>Available in Apache 2.0.33 and later</compatibility></td></tr>
</table>
<p>This directive activates a particular output <a href="../filter.html">filter</a> for a request depending on the
response MIME-type.</p>
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Core</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>NetWare only</td></tr>
+<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td><compatibility>NetWare only</compatibility></td></tr>
</table>
<p>This directive is used to control how Apache finds the
interpreter used to run CGI scripts. For example, setting
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Core</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in version 2.0.44 and later</td></tr>
+<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td><compatibility>Available in version 2.0.44 and later</compatibility></td></tr>
</table>
<p>This directive controls whether <code>httpd</code> may use the sendfile
support from the kernel to transmit file contents to the client.
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Core</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Quoting syntax for text messages is different in Apache
-2.0</td></tr>
+<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td><compatibility>Quoting syntax for text messages is different in Apache
+2.0</compatibility></td></tr>
</table>
<p>In the event of a problem or error, Apache can be configured
to do one of four things,</p>
</table>
<p>The <code class="directive">ErrorLog</code> directive sets the name of
the file to which the server will log any errors it encounters. If
- the <var>file-path</var> does not begin with a slash (/) then it is
- assumed to be relative to the <code class="directive"><a href="#serverroot">ServerRoot</a></code>.</p>
+ the <var>file-path</var> is not absolute (in general: does not begin
+ with a slash (/)) then it is assumed to be relative to the <code class="directive"><a href="#serverroot">ServerRoot</a></code>.</p>
<div class="example"><h3>Example</h3><p><code>
ErrorLog /var/log/httpd/error_log
</table>
<p>The <code class="directive"><Files></code> directive
provides for access control by filename. It is comparable to the
- <code class="directive"><a href="#directory">Directory</a></code>
- directive and <code class="directive"><a href="#location">Location</a></code> directives. It should be
- matched with a <code></Files></code> directive. The
+ <code class="directive"><a href="#directory"><Directory></a></code>
+ directive and <code class="directive"><a href="#location"><Location></a></code> directives. It should be
+ matched with a <code class="directive"><Files></code> directive. The
directives given within this section will be applied to any object
with a basename (last component of filename) matching the
specified filename. <code class="directive"><Files></code>
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Core</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Moved to the core in Apache 2.0</td></tr>
+<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td><compatibility>Moved to the core in Apache 2.0</compatibility></td></tr>
</table>
<p>When placed into an <code>.htaccess</code> file or a
<code class="directive"><a href="#directory"><Directory></a></code>, or
<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Core</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Wildcard matching available in 2.0.41 and later</td></tr>
+<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td><compatibility>Wildcard matching available in 2.0.41 and later</compatibility></td></tr>
</table>
<p>This directive allows inclusion of other configuration files
from within the server configuration files.</p>
- <p>Shell-style (fnmatch) wildcard characters can be used to
+ <p>Shell-style (<code>fnmatch()</code>) wildcard characters can be used to
include several files at once, in alphabetical order. In
addition, if <code class="directive">Include</code> points to a directory,
rather than a file, Apache will read all files in that directory
<p>For example:</p>
<div class="example"><p><code>
- LimitRequestFieldSize 16380
+ LimitRequestFieldSize 4094
</code></p></div>
<div class="note">Under normal conditions, the value should not be changed from
<p>For example:</p>
<div class="example"><p><code>
- LimitRequestLine 16380
+ LimitRequestLine 4094
</code></p></div>
<div class="note">Under normal conditions, the value should not be changed from
<p>This directive selects which authenticated users can access
a directory. The allowed syntaxes are:</p>
- <ul>
- <li>
- Require user <var>userid</var> [<var>userid</var>] ...
-
- <p>Only the named users can access the resource.</p>
- </li>
-
- <li>
- Require group <var>group-name</var> [<var>group-name</var>] ...
-
-
- <p>Only users in the named groups can access the
- resource.</p>
- </li>
+ <dl>
+ <dt><code>Require user <var>userid</var> [<var>userid</var>]
+ ...</code></dt>
+ <dd>Only the named users can access the resource.</dd>
- <li>
- Require valid-user
+ <dt><code>Require group <var>group-name</var> [<var>group-name</var>]
+ ...</code></dt>
+ <dd>Only users in the named groups can access the resource.</dd>
- <p>All valid users can access the resource.</p>
- </li>
- </ul>
+ <dt><code>Require valid-user</code></dt>
+ <dd>All valid users can access the resource.</dd>
+ </dl>
<p><code class="directive">Require</code> must be accompanied by
<code class="directive"><a href="#authname">AuthName</a></code> and <code class="directive"><a href="#authtype">AuthType</a></code> directives, and directives such
<table class="directive">
<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Limits the CPU consumption of processes launched
by Apache children</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>RLimitCPU <var>number</var>|max [<var>number</var>|max]</code></td></tr>
+<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>RLimitCPU <var>seconds</var>|max [<var>seconds</var>|max]</code></td></tr>
<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>Unset; uses operating system defaults</code></td></tr>
<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>All</td></tr>
or <code>max</code> 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
+ the server is running as <code>root</code>, or in the initial startup
phase.</p>
<p>This applies to processes forked off from Apache children
<table class="directive">
<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Limits the memory consumption of processes launched
by Apache children</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>RLimitMEM <var>number</var>|max [<var>number</var>|max]</code></td></tr>
+<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>RLimitMEM <var>bytes</var>|max [<var>bytes</var>|max]</code></td></tr>
<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>Unset; uses operating system defaults</code></td></tr>
<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>All</td></tr>
or <code>max</code> 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
+ the server is running as <code>root</code>, or in the initial startup
phase.</p>
<p>This applies to processes forked off from Apache children
or <code>max</code> 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
+ the server is running as <code>root</code>, or in the initial startup
phase.</p>
<p>This applies to processes forked off from Apache children
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Core</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Win32 only
-option Registry-Strict is available in Apache 2.0 and later</td></tr>
+<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td><compatibility>Win32 only<br />
+option <code>Registry-Strict</code> is available in Apache 2.0 and
+later</compatibility></td></tr>
</table>
<p>This directive is used to control how Apache finds the
interpreter used to run CGI scripts. The default technique is to
<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Core</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>In version 2.0, this
- directive supersedes the functionality of the Port
- directive from version 1.3.</td></tr>
+<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td><compatibility>In version 2.0, this
+ directive supersedes the functionality of the <code class="directive">Port</code>
+ directive from version 1.3.</compatibility></td></tr>
</table>
<p>The <code class="directive">ServerName</code> directive sets the hostname and
port that the server uses to identify itself. This is used when
<h3>See also</h3>
<ul>
-<li><a href="../dns-caveats.html">DNS Issues</a></li>
+<li><a href="../dns-caveats.html">Issues Regarding DNS and
+ Apache</a></li>
<li><a href="../vhosts/">Apache virtual host
documentation</a></li>
<li><code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code></li>
option to <code>httpd</code></a></li>
<li><a href="../misc/security_tips.html#serverroot">the
security tips</a> for information on how to properly set
- permissions on the ServerRoot</li>
+ permissions on the <code class="directive">ServerRoot</code></li>
</ul>
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
listings, <code class="module"><a href="../mod/mod_info.html">mod_info</a></code> output, ...). The reason why you
would want to enable such a footer line is that in a chain of proxies,
the user often has no possibility to tell which of the chained servers
- actually produced a returned error message.<br /> The <code>Off</code>
+ actually produced a returned error message.</p>
+
+ <p>The <code>Off</code>
setting, which is the default, suppresses the footer line (and is
therefore compatible with the behavior of Apache-1.2 and
below). The <code>On</code> setting simply adds a line with the
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="directive-section"><h2><a name="ServerTokens" id="ServerTokens">ServerTokens</a> <a name="servertokens" id="servertokens">Directive</a></h2>
<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Configures the Server HTTP response header</td></tr>
+<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Configures the Server HTTP response
+header</td></tr>
<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>ServerTokens Major|Minor|Min[imal]|Prod[uctOnly]|OS|Full</code></td></tr>
<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>ServerTokens Full</code></td></tr>
<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr>
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Core</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Moved into the core in Apache 2.0</td></tr>
+<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td><compatibility>Moved into the core in Apache 2.0</compatibility></td></tr>
</table>
<p>When placed into an <code>.htaccess</code> file or a
<code class="directive"><a href="#directory"><Directory></a></code> or
<table class="directive">
<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Amount of time the server will wait for
certain events before failing a request</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>TimeOut <var>number</var></code></td></tr>
+<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>TimeOut <var>second</var></code></td></tr>
<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>TimeOut 300</code></td></tr>
<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Core</td></tr>
<h3>See also</h3>
<ul>
<li><a href="../vhosts/">Apache Virtual Host documentation</a></li>
-<li><a href="../dns-caveats.html">Warnings about DNS and
- Apache</a></li>
+<li><a href="../dns-caveats.html">Issues Regarding DNS and
+ Apache</a></li>
<li><a href="../bind.html">Setting
which addresses and ports Apache uses</a></li>
<li><a href="../sections.html">How <Directory>, <Location>
<indent>
Options +Includes<br />
SetOutputFilter INCLUDES<br />
- AcceptPathInfo on<br />
+ AcceptPathInfo On<br />
</indent>
</Files>
</example>
<usage>
<p>The <directive>ErrorLog</directive> directive sets the name of
the file to which the server will log any errors it encounters. If
- the <var>file-path</var> does not begin with a slash (/) then it is
- assumed to be relative to the <directive
+ the <var>file-path</var> is not absolute (in general: does not begin
+ with a slash (/)) then it is assumed to be relative to the <directive
module="core">ServerRoot</directive>.</p>
<example><title>Example</title>
<usage>
<p>The <directive type="section">Files</directive> directive
provides for access control by filename. It is comparable to the
- <directive module="core" type="directive">Directory</directive>
+ <directive module="core" type="section">Directory</directive>
directive and <directive module="core"
- type="directive">Location</directive> directives. It should be
- matched with a <code></Files></code> directive. The
+ type="section">Location</directive> directives. It should be
+ matched with a <directive type="section">Files</directive> directive. The
directives given within this section will be applied to any object
with a basename (last component of filename) matching the
specified filename. <directive type="section">Files</directive>
<p>This directive allows inclusion of other configuration files
from within the server configuration files.</p>
- <p>Shell-style (fnmatch) wildcard characters can be used to
+ <p>Shell-style (<code>fnmatch()</code>) wildcard characters can be used to
include several files at once, in alphabetical order. In
addition, if <directive>Include</directive> points to a directory,
rather than a file, Apache will read all files in that directory
<p>For example:</p>
<example>
- LimitRequestFieldSize 16380
+ LimitRequestFieldSize 4094
</example>
<note>Under normal conditions, the value should not be changed from
<p>For example:</p>
<example>
- LimitRequestLine 16380
+ LimitRequestLine 4094
</example>
<note>Under normal conditions, the value should not be changed from
<p>This directive selects which authenticated users can access
a directory. The allowed syntaxes are:</p>
- <ul>
- <li>
- Require user <var>userid</var> [<var>userid</var>] ...
-
- <p>Only the named users can access the resource.</p>
- </li>
-
- <li>
- Require group <var>group-name</var> [<var>group-name</var>] ...
-
-
- <p>Only users in the named groups can access the
- resource.</p>
- </li>
+ <dl>
+ <dt><code>Require user <var>userid</var> [<var>userid</var>]
+ ...</code></dt>
+ <dd>Only the named users can access the resource.</dd>
- <li>
- Require valid-user
+ <dt><code>Require group <var>group-name</var> [<var>group-name</var>]
+ ...</code></dt>
+ <dd>Only users in the named groups can access the resource.</dd>
- <p>All valid users can access the resource.</p>
- </li>
- </ul>
+ <dt><code>Require valid-user</code></dt>
+ <dd>All valid users can access the resource.</dd>
+ </dl>
<p><directive>Require</directive> must be accompanied by
<directive module="core">AuthName</directive> and <directive
<name>RLimitCPU</name>
<description>Limits the CPU consumption of processes launched
by Apache children</description>
-<syntax>RLimitCPU <var>number</var>|max [<var>number</var>|max]</syntax>
+<syntax>RLimitCPU <var>seconds</var>|max [<var>seconds</var>|max]</syntax>
<default>Unset; uses operating system defaults</default>
<contextlist><context>server config</context><context>virtual host</context>
<context>directory</context><context>.htaccess</context></contextlist>
or <code>max</code> 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
+ the server is running as <code>root</code>, or in the initial startup
phase.</p>
<p>This applies to processes forked off from Apache children
<name>RLimitMEM</name>
<description>Limits the memory consumption of processes launched
by Apache children</description>
-<syntax>RLimitMEM <var>number</var>|max [<var>number</var>|max]</syntax>
+<syntax>RLimitMEM <var>bytes</var>|max [<var>bytes</var>|max]</syntax>
<default>Unset; uses operating system defaults</default>
<contextlist><context>server config</context><context>virtual host</context>
<context>directory</context><context>.htaccess</context></contextlist>
or <code>max</code> 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
+ the server is running as <code>root</code>, or in the initial startup
phase.</p>
<p>This applies to processes forked off from Apache children
or <code>max</code> 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
+ the server is running as <code>root</code>, or in the initial startup
phase.</p>
<p>This applies to processes forked off from Apache children
<context>directory</context><context>.htaccess</context></contextlist>
<override>FileInfo</override>
<compatibility>Win32 only<br />
-option Registry-Strict is available in Apache 2.0 and later</compatibility>
+option <code>Registry-Strict</code> is available in Apache 2.0 and
+later</compatibility>
<usage>
<p>This directive is used to control how Apache finds the
</p>
</usage>
-<seealso><a href="../dns-caveats.html">DNS Issues</a></seealso>
+<seealso><a href="../dns-caveats.html">Issues Regarding DNS and
+ Apache</a></seealso>
<seealso><a href="../vhosts/">Apache virtual host
documentation</a></seealso>
<seealso><directive module="core">UseCanonicalName</directive></seealso>
option to <code>httpd</code></a></seealso>
<seealso><a href="../misc/security_tips.html#serverroot">the
security tips</a> for information on how to properly set
- permissions on the ServerRoot</seealso>
+ permissions on the <directive>ServerRoot</directive></seealso>
</directivesynopsis>
<directivesynopsis>
listings, <module>mod_info</module> output, ...). The reason why you
would want to enable such a footer line is that in a chain of proxies,
the user often has no possibility to tell which of the chained servers
- actually produced a returned error message.<br /> The <code>Off</code>
+ actually produced a returned error message.</p>
+
+ <p>The <code>Off</code>
setting, which is the default, suppresses the footer line (and is
therefore compatible with the behavior of Apache-1.2 and
below). The <code>On</code> setting simply adds a line with the
<directivesynopsis>
<name>ServerTokens</name>
-<description>Configures the Server HTTP response header</description>
+<description>Configures the <code>Server</code> HTTP response
+header</description>
<syntax>ServerTokens Major|Minor|Min[imal]|Prod[uctOnly]|OS|Full</syntax>
<default>ServerTokens Full</default>
<contextlist><context>server config</context></contextlist>
<name>TimeOut</name>
<description>Amount of time the server will wait for
certain events before failing a request</description>
-<syntax>TimeOut <var>number</var></syntax>
+<syntax>TimeOut <var>second</var></syntax>
<default>TimeOut 300</default>
<contextlist><context>server config</context></contextlist>
</note>
</usage>
<seealso><a href="../vhosts/">Apache Virtual Host documentation</a></seealso>
-<seealso><a href="../dns-caveats.html">Warnings about DNS and
- Apache</a></seealso>
+<seealso><a href="../dns-caveats.html">Issues Regarding DNS and
+ Apache</a></seealso>
<seealso><a href="../bind.html">Setting
which addresses and ports Apache uses</a></seealso>
<seealso><a href="../sections.html">How <Directory>, <Location>