<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>
</table>
- <p>When returning a document to the client the server looks for
+ <p>While processing a request the server looks for
the first existing configuration file from this list of names in
every directory of the path to the document, if distributed
configuration files are enabled for that directory. For
</Location>
</code></p></div>
- <div class="warning"><h3>Note:</h3>
+ <div class="warning"><h3>Note</h3>
<p>Enabling filters with <code class="directive">AddOutputFilterByType</code>
may fail partially or completely in some cases. For expample, no
filters are applied if the content type falls back to the <code class="directive"><a href="#defaulttype">DefaultType</a></code>, even if the <code class="directive"><a href="#defaulttype">DefaultType</a></code> is the same.</p>
it needs to know which directives declared in that file can override
earlier access information.</p>
- <div class="note"><h3>Only available in Directory sections</h3>
+ <div class="note"><h3>Only available in <Directory> sections</h3>
<code class="directive">AllowOverride</code> is valid only in
<code class="directive"><a href="#directory"><Directory></a></code>
sections, not in <code class="directive"><a href="#location"><Location></a></code> or <code class="directive"><a href="#files"><Files></a></code> sections.
Allow use of the authorization directives (<code class="directive"><a href="../mod/mod_authn_dbm.html#authdbmgroupfile">AuthDBMGroupFile</a></code>,
<code class="directive"><a href="../mod/mod_authn_dbm.html#authdbmuserfile">AuthDBMUserFile</a></code>,
<code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code>,
- <code class="directive"><a href="#authname">AuthName</a></code>,
+ <code class="directive"><a href="#authname">AuthName</a></code>,
<code class="directive"><a href="#authtype">AuthType</a></code>, <code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code>, <code class="directive"><a href="#require">Require</a></code>, <em>etc.</em>).</dd>
<dt>FileInfo</dt>
<dd>
Allow use of the directives controlling document types (<code class="directive"><a href="#defaulttype">DefaultType</a></code>, <code class="directive"><a href="#errordocument">ErrorDocument</a></code>, <code class="directive"><a href="#forcetype">ForceType</a></code>, <code class="directive"><a href="../mod/mod_negotiation.html#languagepriority">LanguagePriority</a></code>,
- <code class="directive"><a href="#sethandler">SetHandler</a></code>, <code class="directive"><a href="#setinputfilter">SetInputFilter</a></code>, <code class="directive"><a href="#setoutputfilter">SetOutputFilter</a></code>, and
+ <code class="directive"><a href="#sethandler">SetHandler</a></code>, <code class="directive"><a href="#setinputfilter">SetInputFilter</a></code>, <code class="directive"><a href="#setoutputfilter">SetOutputFilter</a></code>, and
<code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code> Add* and Remove*
directives, <em>etc.</em>).</dd>
<h3>See also</h3>
<ul>
-<li><a href="../howto/auth.html">Authentication, Authorization, and
+<li><a href="../howto/auth.html">Authentication, Authorization, and
Access Control</a></li>
</ul>
</div>
</table>
<p>This directive selects the type of user authentication for a
directory. Only <code>Basic</code> and <code>Digest</code> are
- currently implemented.
+ currently implemented.
It must be accompanied by <code class="directive"><a href="#authname">AuthName</a></code> and <code class="directive"><a href="#require">Require</a></code> directives, and directives such
as <code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code> and
<p>This directive is used to control how Apache finds the
interpreter used to run CGI scripts. For example, setting
<code>CGIMapExtension sys:\foo.nlm .foo</code> will
- cause all CGI script files with a .foo extension to be passed to the
- FOO interpreter.</p>
+ cause all CGI script files with a <code>.foo</code> extension to
+ be passed to the FOO interpreter.</p>
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<p>Note that unlike <code class="directive"><a href="#forcetype">ForceType</a></code>, this directive is only
provides the default mime-type. All other mime-type definitions,
including filename extensions, that might identify the media type
- will override this default.</p>
+ will override this default.</p>
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<p>would match directories in <code>/www/</code> that consisted of
three numbers.</p>
- <p>If multiple (non-regular expression) directory sections
+ <p>If multiple (non-regular expression) <code class="directive"><Directory></code> sections
match the directory (or its parents) containing a document,
then the directives are applied in the order of shortest match
first, interspersed with the directives from the <a href="#accessfilename">.htaccess</a> files. For example,
<li>Apply directive <code>AllowOverride FileInfo</code> (for
directory <code>/home/web</code>).</li>
- <li>Apply any FileInfo directives in
+ <li>Apply any <code>FileInfo</code> directives in
<code>/home/web/.htaccess</code></li>
</ul>
</Directory>
</code></p></div>
- <p>The regular expression section won't be considered until after
+ <p>the regular expression section won't be considered until after
all normal <code><Directory></code>s and <code>.htaccess</code>
files have been applied. Then the regular expression will match on
<code>/home/abc/public_html/abc</code> and be applied.</p>
<h3>See also</h3>
<ul>
-<li><a href="../sections.html">How
- Directory, Location and Files sections work</a> for an
+<li><a href="../sections.html">How <Directory>,
+ <Location> and <Files> sections work</a> for an
explanation of how these different sections are combined when a
request is received</li>
</ul>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="directive-section"><h2><a name="DirectoryMatch" id="DirectoryMatch"><DirectoryMatch></a> <a name="directorymatch" id="directorymatch">Directive</a></h2>
<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Enclose directives that apply to
+<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Enclose directives that apply to
file-system directories matching a regular expression and their
subdirectories</td></tr>
<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code><DirectoryMatch <var>regex</var>>
<ul>
<li><code class="directive"><a href="#directory"><Directory></a></code> for
a description of how regular expressions are mixed in with normal
-<code><Directory></code>s</li>
-<li><a href="../sections.html">How Directory, Location and Files sections
-work</a> for an explanation of how these different sections are
-combined when a request is received</li>
+<code class="directive"><Directory></code>s</li>
+<li><a href="../sections.html">How <Directory>, <Location> and
+<Files> sections work</a> for an explanation of how these different
+sections are combined when a request is received</li>
</ul>
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="example"><p><code>
<Directory "/path-to-nfs-files">
- EnableMMAP Off
+ <span class="indent">
+ EnableMMAP Off
+ </span>
</Directory>
</code></p></div>
<p>This sendfile mechanism avoids seperate read and send operations,
and buffer allocations. But on some platforms or within some
- filesystems, it is better to disable this feature to avoid
+ filesystems, it is better to disable this feature to avoid
operational problems:</p>
<ul>
<li>Some platforms may have broken sendfile support that the build
system did not detect, especially if the binaries were built on
another box and moved to such a machine with broken sendfile
- support.</li>
- <li>With a network-mounted <code class="directive"><a href="#documentroot">DocumentRoot</a></code> (e.g., NFS or SMB),
- the kernel may be unable to serve the network file through
+ support.</li>
+ <li>With a network-mounted <code class="directive"><a href="#documentroot">DocumentRoot</a></code> (e.g., NFS or SMB),
+ the kernel may be unable to serve the network file through
its own cache.</li>
</ul>
for the offending files by specifying:</p>
<div class="example"><p><code>
- <Directory "/path-to-nfs-files"><br />
- EnableSendfile Off<br />
+ <Directory "/path-to-nfs-files">
+ <span class="indent">
+ EnableSendfile Off
+ </span>
</Directory>
</code></p></div>
URL in an <code>ErrorDocument 401</code>, the client will not
know to prompt the user for a password since it will not
receive the 401 status code. Therefore, <strong>if you use an
- "ErrorDocument 401" directive then it must refer to a local
+ <code>ErrorDocument 401</code> directive then it must refer to a local
document.</strong></p>
<p>Microsoft Internet Explorer (MSIE) will by default ignore
<table class="directive">
<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Location where the server will log errors</td></tr>
<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code> ErrorLog <var>file-path</var>|syslog[:<var>facility</var>]</code></td></tr>
-<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>ErrorLog logs/error_log (Unix)
+<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>ErrorLog logs/error_log (Unix)<br />
ErrorLog logs/error.log (Windows and OS/2)</code></td></tr>
<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>
<div class="example"><h3>Example</h3><p><code>
ErrorLog /var/log/httpd/error_log
</code></p></div>
-
+
<p>If the <var>file-path</var>
begins with a pipe (|) then it is assumed to be a command to spawn
to handle the error log.</p>
<Files ~ "\.(gif|jpe?g|png)$">
</code></p></div>
- <p>would match most common Internet graphics formats. In Apache 1.3
- and later, <code class="directive"><a href="#filesmatch"><FilesMatch></a></code> is preferred, however.</p>
+ <p>would match most common Internet graphics formats. <code class="directive"><a href="#filesmatch"><FilesMatch></a></code> is preferred,
+ however.</p>
<p>Note that unlike <code class="directive"><a href="#directory"><Directory></a></code> and <code class="directive"><a href="#location"><Location></a></code> sections, <code class="directive"><Files></code> sections can be used inside
<code>.htaccess</code> files. This allows users to control access to
<h3>See also</h3>
<ul>
-<li><a href="../sections.html">How
- Directory, Location and Files sections work</a> for an
- explanation of how these different sections are combined when a
- request is received</li>
+<li><a href="../sections.html">How <Directory>, <Location>
+ and <Files> sections work</a> for an explanation of how these
+ different sections are combined when a request is received</li>
</ul>
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<h3>See also</h3>
<ul>
-<li><a href="../sections.html">How
- Directory, Location and Files sections work</a> for an
- explanation of how these different sections are combined when a
- request is received</li>
+<li><a href="../sections.html">How <Directory>, <Location>
+ and <Files> sections work</a> for an explanation of how these
+ different sections are combined when a request is received</li>
</ul>
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<p>This directive enables DNS lookups so that host names can be
logged (and passed to CGIs/SSIs in <code>REMOTE_HOST</code>).
The value <code>Double</code> refers to doing double-reverse
- DNS. That is, after a reverse lookup is performed, a forward
+ DNS lookup. That is, after a reverse lookup is performed, a forward
lookup is then performed on that result. At least one of the ip
addresses in the forward lookup must match the original
address. (In "tcpwrappers" terminology this is called
don't have to suffer the extra latency that a lookup entails.
Heavily loaded sites should leave this directive
<code>Off</code>, since DNS lookups can take considerable
- amounts of time. The utility <a href="../programs/logresolve.html">logresolve</a>, provided in
- the <var>/support</var> directory, can be used to look up host
- names from logged IP addresses offline.</p>
+ amounts of time. The utility <a href="../programs/logresolve.html">logresolve</a>, compiled by default
+ to the <code>bin</code> subdirectory of your installation directory, can
+ be used to look up host names from logged IP addresses offline.</p>
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
fail.</p>
<p>The file path specified may be a fully qualified path (i.e.
- starting with a slash), or may be relative to the
+ starting with a slash), or may be relative to the
<code class="directive"><a href="#serverroot">ServerRoot</a></code> directory.</p>
<p>Examples:</p>
which allow multiple requests to be sent over the same TCP
connection. In some cases this has been shown to result in an
almost 50% speedup in latency times for HTML documents with
- many images. To enable Keep-Alive connections in Apache 1.2 and
- later, set <code>KeepAlive On</code>.</p>
+ many images. To enable Keep-Alive connections, set
+ <code>KeepAlive On</code>.</p>
<p>For HTTP/1.0 clients, Keep-Alive connections will only be
used if they are specifically requested by a client. In
<p>The purpose of the <code class="directive"><Limit></code>
directive is to restrict the effect of the access controls to the
nominated HTTP methods. For all other methods, the access
- restrictions that are enclosed in the <code><Limit></code>
- bracket <strong>will have no effect</strong>. The following
- example applies the access control only to the methods <code>POST</code>,
- <code>PUT</code>, and <code>DELETE</code>, leaving all other methods
- unprotected:</p>
+ restrictions that are enclosed in the <code class="directive"><Limit></code> bracket <strong>will have no
+ effect</strong>. The following example applies the access control
+ only to the methods <code>POST</code>, <code>PUT</code>, and
+ <code>DELETE</code>, leaving all other methods unprotected:</p>
<div class="example"><p><code>
<Limit POST PUT DELETE><br />
<p><code class="directive"><LimitExcept></code> and
<code></LimitExcept></code> are used to enclose
a group of access control directives which will then apply to any
- HTTP access method <strong>not</strong> listed in the arguments;
+ HTTP access method <strong>not</strong> listed in the arguments;
i.e., it is the opposite of a <code class="directive"><a href="#limit"><Limit></a></code> section and can be used to control
both standard and nonstandard/unrecognized methods. See the
documentation for <code class="directive"><a href="#limit"><Limit></a></code> for more details.</p>
response instead of servicing the request. The size of a normal
request message body will vary greatly depending on the nature of
the resource and the methods allowed on that resource. CGI scripts
- typically use the message body for passing form information to the
- server. Implementations of the <code>PUT</code> method will require
+ typically use the message body for retrieving form information.
+ Implementations of the <code>PUT</code> method will require
a value at least as large as any representation that the server
wishes to accept for that resource.</p>
attacks.</p>
<p>If, for example, you are permitting file upload to a particular
- location, and wich to limit the size of the uploaded file to 100K,
+ location, and wish to limit the size of the uploaded file to 100K,
you might use the following directive:</p>
<div class="example"><p><code>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="directive-section"><h2><a name="LimitRequestFields" id="LimitRequestFields">LimitRequestFields</a> <a name="limitrequestfields" id="limitrequestfields">Directive</a></h2>
<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Limits the number of HTTP request header fields that
+<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Limits the number of HTTP request header fields that
will be accepted from the client</td></tr>
<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>LimitRequestFields <var>number</var></code></td></tr>
<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>LimitRequestFields 100</code></td></tr>
distributed) that will be allowed in an HTTP request
header.</p>
- <p>The <code class="directive">LimitRequestFieldsize</code> directive
+ <p>The <code class="directive">LimitRequestFieldSize</code> directive
allows the server administrator to reduce the limit on the allowed
size of an HTTP request header field below the normal input buffer
size compiled with the server. A server needs this value to be
<div class="directive-section"><h2><a name="LimitXMLRequestBody" id="LimitXMLRequestBody">LimitXMLRequestBody</a> <a name="limitxmlrequestbody" id="limitxmlrequestbody">Directive</a></h2>
<table class="directive">
<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Limits the size of an XML-based request body</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>LimitXMLRequestBody <var>number</var></code></td></tr>
+<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>LimitXMLRequestBody <var>bytes</var></code></td></tr>
<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>LimitXMLRequestBody 1000000</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>
<code>.htaccess</code> files are read, and after the <code class="directive"><a href="#files"><Files></a></code> sections.</p>
<p>Note that URLs do not have to line up with the filesystem at
- all, it should be emphasized that <code><Location></code> operates
- completely outside the filesystem.</p>
+ all, it should be emphasized that <code class="directive"><Location></code> operates completely
+ outside the filesystem.</p>
<p>For all origin (non-proxy) requests, the URL to be matched is a
URL-path of the form <code>/path/</code>. No scheme, hostname,
<code>scheme://servername/path</code>, and you must include the
prefix.</p>
- <p>The URL may use wildcards In a wild-card string, <code>?</code> matches
+ <p>The URL may use wildcards. In a wild-card string, <code>?</code> matches
any single character, and <code>*</code> matches any sequences of
characters.</p>
</code></p></div>
<p>would match URLs that contained the substring <code>/extra/data</code>
- or <code>/special/data</code>. In Apache 1.3 and above, a new directive
- <code class="directive"><a href="#locationmatch"><LocationMatch></a></code>
- exists which behaves identical to the regex version of
- <code class="directive"><Location></code>.</p>
+ or <code>/special/data</code>. The directive <code class="directive"><a href="#locationmatch"><LocationMatch></a></code> behaves
+ identical to the regex version of <code class="directive"><Location></code>.</p>
<p>The <code class="directive"><Location></code>
functionality is especially useful when combined with the
The <code class="directive"><a href="#locationmatch"><LocationMatch></a></code>
directive and the regex version of <code class="directive"><Location></code> require you to explicitly specify multiple
slashes if that is your intention.</p>
-
+
<p>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 class="directive"><Location></code> directive behaves similarly when used for
<h3>See also</h3>
<ul>
-<li><a href="../sections.html">How
- Directory, Location and Files sections work</a> for an
- explanation of how these different sections are combined when a
- request is received</li>
+<li><a href="../sections.html">How <Directory>, <Location>
+ and <Files> sections work</a> for an explanation of how these
+ different sections are combined when a request is received</li>
</ul>
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="directive-section"><h2><a name="LocationMatch" id="LocationMatch"><LocationMatch></a> <a name="locationmatch" id="locationmatch">Directive</a></h2>
<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Applies the enclosed directives only to regular-expression
+<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Applies the enclosed directives only to regular-expression
matching URLs</td></tr>
<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code><LocationMatch
<var>regex</var>> ... </LocationMatch></code></td></tr>
<h3>See also</h3>
<ul>
-<li><a href="../sections.html">How
- Directory, Location and Files sections work</a> for an
- explanation of how these different sections are combined when a
- request is received</li>
+<li><a href="../sections.html">How <Directory>, <Location>
+ and <Files> sections work</a> for an explanation of how these
+ different sections are combined when a request is received</li>
</ul>
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="directive-section"><h2><a name="MaxKeepAliveRequests" id="MaxKeepAliveRequests">MaxKeepAliveRequests</a> <a name="maxkeepaliverequests" id="maxkeepaliverequests">Directive</a></h2>
<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Number of requests allowed on a persistent
+<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Number of requests allowed on a persistent
connection</td></tr>
<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MaxKeepAliveRequests <var>number</var></code></td></tr>
<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>MaxKeepAliveRequests 100</code></td></tr>
servicing the requests. If you have multiple name-based hosts on
multiple addresses, repeat the directive for each address.</p>
- <p>Note: the "main server" and any <code>_default_</code> servers will
- <strong>never</strong> be served for a request to a
- <code class="directive">NameVirtualHost</code> IP Address (unless for some
- reason you specify <code class="directive">NameVirtualHost</code> but then
- don't define any <code class="directive">VirtualHost</code>s for that address).</p>
+ <div class="note"><h3>Note</h3>
+ <p>Note, that the "main server" and any <code>_default_</code> servers
+ will <strong>never</strong> be served for a request to a
+ <code class="directive">NameVirtualHost</code> IP Address (unless for some
+ reason you specify <code class="directive">NameVirtualHost</code> but then
+ don't define any <code class="directive">VirtualHost</code>s for that
+ address).</p>
+ </div>
<p>Optionally you can specify a port number on which the
name-based virtual hosts should be used, e.g.</p>
the following:</p>
<dl>
- <dt>All</dt>
+ <dt><code>All</code></dt>
<dd>All options except for <code>MultiViews</code>. This is the default
setting.</dd>
- <dt>ExecCGI</dt>
+ <dt><code>ExecCGI</code></dt>
<dd>
Execution of CGI scripts is permitted.</dd>
- <dt>FollowSymLinks</dt>
+ <dt><code>FollowSymLinks</code></dt>
<dd>
section.</p>
</div></dd>
- <dt>Includes</dt>
+ <dt><code>Includes</code></dt>
<dd>
Server-side includes are permitted.</dd>
- <dt>IncludesNOEXEC</dt>
+ <dt><code>IncludesNOEXEC</code></dt>
<dd>
<code>#include virtual</code> CGI scripts from
<code class="directive">ScriptAlias</code>e'd directories.</dd>
- <dt>Indexes</dt>
+ <dt><code>Indexes</code></dt>
<dd>
If a URL which maps to a directory is requested, and the
<code>index.html</code>) in that directory, then the server will
return a formatted listing of the directory.</dd>
- <dt>MultiViews</dt>
+ <dt><code>MultiViews</code></dt>
<dd>
<a href="../content-negotiation.html">Content negotiated</a>
"MultiViews" are allowed.</dd>
- <dt>SymLinksIfOwnerMatch</dt>
+ <dt><code>SymLinksIfOwnerMatch</code></dt>
<dd>
<code>Includes</code> are set for the <code>/web/docs/spec</code>
directory.</p>
-
- <p><strong>Note:</strong> Using <code>-IncludesNOEXEC</code> or
- <code>-Includes</code> disables server-side includes completely
- regardless of the previous setting.</p>
+ <div class="note"><h3>Note</h3>
+ <p>Using <code>-IncludesNOEXEC</code> or
+ <code>-Includes</code> disables server-side includes completely
+ regardless of the previous setting.</p>
+ </div>
<p>The default in the absence of any other settings is
<code>All</code>.</p>
<ul>
<li>
- Require user <var>userid</var> [<var>userid</var>] ...
+ Require user <var>userid</var> [<var>userid</var>] ...
- <p>Only the named users can access the directory.</p>
+ <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
- directory.</p>
+ resource.</p>
</li>
<li>
- Require valid-user
+ Require valid-user
- <p>All valid users can access the directory.</p>
+ <p>All valid users can access the resource.</p>
</li>
</ul>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="directive-section"><h2><a name="RLimitNPROC" id="RLimitNPROC">RLimitNPROC</a> <a name="rlimitnproc" id="rlimitnproc">Directive</a></h2>
<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Limits the number of processes that can be launched by
+<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Limits the number of processes that can be launched by
processes launched by Apache children</td></tr>
<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>RLimitNPROC <var>number</var>|max [<var>number</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>
<p>Process limits control the number of processes per user.</p>
- <p>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><code>cannot fork</code></strong> messages in the
- error_log.</p>
+ <div class="note"><h3>Note</h3>
+ <p>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><code>cannot fork</code></strong> messages in the
+ <code>error_log</code>.</p>
+ </div>
<h3>See also</h3>
<ul>
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>
- setting, which is the default, suppresses the error line (and is
+ 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
server version number and <code class="directive"><a href="#servername">ServerName</a></code> of the serving virtual host,
<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Moved into the core in Apache 2.0</td></tr>
</table>
<p>When placed into an <code>.htaccess</code> file or a
- <code class="directive"><a href="#directory"><Directory></a></code> or
+ <code class="directive"><a href="#directory"><Directory></a></code> or
<code class="directive"><a href="#location"><Location></a></code>
section, this directive forces all matching files to be parsed
through the <a href="../handler.html">handler</a> given by
<p>Another example: if you wanted to have the server display a
status report whenever a URL of
<code>http://servername/status</code> was called, you might put
- the following into httpd.conf:</p>
+ the following into <code>httpd.conf</code>:</p>
<div class="example"><p><code>
<Location /status><br />
<li>The amount of time between ACKs on transmissions of TCP
packets in responses.</li>
</ol>
-
+
<p>We plan on making these separately configurable at some point
down the road. The timer used to default to 1200 before 1.2,
but has been lowered to 300 which is still far more than
</table>
<p>In many situations Apache must construct a <em>self-referential</em>
URL -- that is, a URL that refers back to the same server. With
- <code>UseCanonicalName on</code> Apache will use the hostname and port
+ <code>UseCanonicalName On</code> Apache will use the hostname and port
specified in the <code class="directive"><a href="#servername">ServerName</a></code>
directive to construct the canonical name for the server. This name
is used in all self-referential URLs, and for the values of
the client if any are supplied (otherwise it will use the
canonical name, as defined above). These values are the same
that are used to implement <a href="../vhosts/name-based.html">name based virtual hosts</a>,
- and are available with the same clients. The CGI variables
+ and are available with the same clients. The CGI variables
<code>SERVER_NAME</code> and <code>SERVER_PORT</code> will be
constructed from the client supplied values as well.</p>
reverse DNS lookup on the server IP address that the client
connected to in order to work out self-referential URLs.</p>
- <div class="warning"><h3>Warning:</h3>
+ <div class="warning"><h3>Warning</h3>
<p>If CGIs make assumptions about the values of <code>SERVER_NAME</code>
they may be broken by this option. The client is essentially free
to give whatever value they want as a hostname. But if the CGI is
<li>The string <code>_default_</code>, which is used only
with IP virtual hosting to catch unmatched IP addresses.</li>
</ul>
-
+
<div class="example"><h3>Example</h3><p><code>
<VirtualHost 10.1.2.3><br />
<span class="indent">
</VirtualHost>
</code></p></div>
-
+
<p>IPv6 addresses must be specified in square brackets because
the optional port number could not be determined otherwise. An
IPv6 example is shown below:</p>
TransferLog logs/host.example.com-access_log<br />
</span>
</VirtualHost>
- </code></p></div>
+ </code></p></div>
<p>Each Virtual Host must correspond to a different IP address,
different port number or a different host name for the server,
in the former case the server machine must be configured to
accept IP packets for multiple addresses. (If the machine does
not have multiple network interfaces, then this can be
- accomplished with the <code>ifconfig alias</code> command (if
+ accomplished with the <code>ifconfig alias</code> command -- if
your OS supports it).</p>
<div class="note"><h3>Note</h3>
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 and Files sections work</a> for an
- explanation of how these different sections are combined when a
- request is received</li>
+<li><a href="../sections.html">How <Directory>, <Location>
+ and <Files> sections work</a> for an explanation of how these
+ different sections are combined when a request is received</li>
</ul>
</div>
</div>
<directivesynopsis>
<name>AcceptPathInfo</name>
-<description>Resources accept trailing pathname information</description>
+<description>Resources accept trailing pathname information</description>
<syntax>AcceptPathInfo On|Off|Default</syntax>
<default>AcceptPathInfo Default</default>
<contextlist><context>server config</context>
</contextlist>
<usage>
- <p>When returning a document to the client the server looks for
+ <p>While processing a request the server looks for
the first existing configuration file from this list of names in
every directory of the path to the document, if distributed
configuration files are enabled for that directory. For
</Location>
</example>
- <note type="warning"><title>Note:</title>
+ <note type="warning"><title>Note</title>
<p>Enabling filters with <directive>AddOutputFilterByType</directive>
may fail partially or completely in some cases. For expample, no
filters are applied if the content type falls back to the <directive
<directivesynopsis>
<name>AllowOverride</name>
<description>Types of directives that are allowed in
-.htaccess files</description>
+<code>.htaccess</code> files</description>
<syntax>AllowOverride All|None|<var>directive-type</var>
[<var>directive-type</var>] ...</syntax>
<default>AllowOverride All</default>
it needs to know which directives declared in that file can override
earlier access information.</p>
- <note><title>Only available in Directory sections</title>
+ <note><title>Only available in <Directory> sections</title>
<directive>AllowOverride</directive> is valid only in
<directive type="section" module="core">Directory</directive>
sections, not in <directive type="section"
module="mod_authn_dbm">AuthDBMGroupFile</directive>,
<directive module="mod_authn_dbm">AuthDBMUserFile</directive>,
<directive module="mod_authz_groupfile">AuthGroupFile</directive>,
- <directive module="core">AuthName</directive>,
+ <directive module="core">AuthName</directive>,
<directive module="core">AuthType</directive>, <directive
module="mod_authn_file">AuthUserFile</directive>, <directive
module="core">Require</directive>, <em>etc.</em>).</dd>
module="mod_negotiation">LanguagePriority</directive>,
<directive module="core">SetHandler</directive>, <directive
module="core">SetInputFilter</directive>, <directive
- module="core">SetOutputFilter</directive>, and
+ module="core">SetOutputFilter</directive>, and
<module>mod_mime</module> Add* and Remove*
directives, <em>etc.</em>).</dd>
<p>The string provided for the <code>AuthName</code> is what will
appear in the password dialog provided by most browsers.</p>
</usage>
-<seealso><a
- href="../howto/auth.html">Authentication, Authorization, and
+<seealso><a
+ href="../howto/auth.html">Authentication, Authorization, and
Access Control</a></seealso>
</directivesynopsis>
<usage>
<p>This directive selects the type of user authentication for a
directory. Only <code>Basic</code> and <code>Digest</code> are
- currently implemented.
+ currently implemented.
It must be accompanied by <directive
module="core">AuthName</directive> and <directive
<p>This directive is used to control how Apache finds the
interpreter used to run CGI scripts. For example, setting
<code>CGIMapExtension sys:\foo.nlm .foo</code> will
- cause all CGI script files with a .foo extension to be passed to the
- FOO interpreter.</p>
+ cause all CGI script files with a <code>.foo</code> extension to
+ be passed to the FOO interpreter.</p>
</usage>
</directivesynopsis>
<directivesynopsis>
<name>ContentDigest</name>
-<description>Enables the generation of Content-MD5 HTTP Response
+<description>Enables the generation of <code>Content-MD5</code> HTTP Response
headers</description>
<syntax>ContentDigest On|Off</syntax>
<default>ContentDigest Off</default>
module="core">ForceType</directive>, this directive is only
provides the default mime-type. All other mime-type definitions,
including filename extensions, that might identify the media type
- will override this default.</p>
+ will override this default.</p>
</usage>
</directivesynopsis>
<p>would match directories in <code>/www/</code> that consisted of
three numbers.</p>
- <p>If multiple (non-regular expression) directory sections
+ <p>If multiple (non-regular expression) <directive
+ type="section">Directory</directive> sections
match the directory (or its parents) containing a document,
then the directives are applied in the order of shortest match
first, interspersed with the directives from the <a
<li>Apply directive <code>AllowOverride FileInfo</code> (for
directory <code>/home/web</code>).</li>
- <li>Apply any FileInfo directives in
+ <li>Apply any <code>FileInfo</code> directives in
<code>/home/web/.htaccess</code></li>
</ul>
</Directory>
</example>
- <p>The regular expression section won't be considered until after
+ <p>the regular expression section won't be considered until after
all normal <code><Directory></code>s and <code>.htaccess</code>
files have been applied. Then the regular expression will match on
<code>/home/abc/public_html/abc</code> and be applied.</p>
type="section">Limit</directive> or <directive module="core"
type="section">LimitExcept</directive> section.</p>
</usage>
-<seealso><a href="../sections.html">How
- Directory, Location and Files sections work</a> for an
+<seealso><a href="../sections.html">How <Directory>,
+ <Location> and <Files> sections work</a> for an
explanation of how these different sections are combined when a
request is received</seealso>
</directivesynopsis>
<directivesynopsis type="section">
<name>DirectoryMatch</name>
-<description>Enclose directives that apply to
+<description>Enclose directives that apply to
file-system directories matching a regular expression and their
subdirectories</description>
<syntax><DirectoryMatch <var>regex</var>>
</usage>
<seealso><directive type="section" module="core">Directory</directive> for
a description of how regular expressions are mixed in with normal
-<code><Directory></code>s</seealso>
+<directive type="section">Directory</directive>s</seealso>
<seealso><a
-href="../sections.html">How Directory, Location and Files sections
-work</a> for an explanation of how these different sections are
-combined when a request is received</seealso>
+href="../sections.html">How <Directory>, <Location> and
+<Files> sections work</a> for an explanation of how these different
+sections are combined when a request is received</seealso>
</directivesynopsis>
<directivesynopsis>
<example>
<Directory "/path-to-nfs-files">
- EnableMMAP Off
+ <indent>
+ EnableMMAP Off
+ </indent>
</Directory>
</example>
</usage>
<p>This sendfile mechanism avoids seperate read and send operations,
and buffer allocations. But on some platforms or within some
- filesystems, it is better to disable this feature to avoid
+ filesystems, it is better to disable this feature to avoid
operational problems:</p>
<ul>
<li>Some platforms may have broken sendfile support that the build
system did not detect, especially if the binaries were built on
another box and moved to such a machine with broken sendfile
- support.</li>
+ support.</li>
<li>With a network-mounted <directive
- module="core">DocumentRoot</directive> (e.g., NFS or SMB),
- the kernel may be unable to serve the network file through
+ module="core">DocumentRoot</directive> (e.g., NFS or SMB),
+ the kernel may be unable to serve the network file through
its own cache.</li>
</ul>
for the offending files by specifying:</p>
<example>
- <Directory "/path-to-nfs-files"><br />
- EnableSendfile Off<br />
+ <Directory "/path-to-nfs-files">
+ <indent>
+ EnableSendfile Off
+ </indent>
</Directory>
</example>
</usage>
URL in an <code>ErrorDocument 401</code>, the client will not
know to prompt the user for a password since it will not
receive the 401 status code. Therefore, <strong>if you use an
- "ErrorDocument 401" directive then it must refer to a local
+ <code>ErrorDocument 401</code> directive then it must refer to a local
document.</strong></p>
<p>Microsoft Internet Explorer (MSIE) will by default ignore
<directivesynopsis>
<name>ErrorLog</name>
-<description>Location where the server will log errors</description>
+<description>Location where the server will log errors</description>
<syntax> ErrorLog <var>file-path</var>|syslog[:<var>facility</var>]</syntax>
-<default>ErrorLog logs/error_log (Unix)
+<default>ErrorLog logs/error_log (Unix)<br />
ErrorLog logs/error.log (Windows and OS/2)</default>
<contextlist><context>server config</context><context>virtual host</context>
</contextlist>
<example><title>Example</title>
ErrorLog /var/log/httpd/error_log
</example>
-
+
<p>If the <var>file-path</var>
begins with a pipe (|) then it is assumed to be a command to spawn
to handle the error log.</p>
<Files ~ "\.(gif|jpe?g|png)$">
</example>
- <p>would match most common Internet graphics formats. In Apache 1.3
- and later, <directive module="core"
- type="section">FilesMatch</directive> is preferred, however.</p>
+ <p>would match most common Internet graphics formats. <directive
+ module="core" type="section">FilesMatch</directive> is preferred,
+ however.</p>
<p>Note that unlike <directive type="section"
module="core">Directory</directive> and <directive type="section"
their own files, at a file-by-file level.</p>
</usage>
-<seealso><a href="../sections.html">How
- Directory, Location and Files sections work</a> for an
- explanation of how these different sections are combined when a
- request is received</seealso>
+<seealso><a href="../sections.html">How <Directory>, <Location>
+ and <Files> sections work</a> for an explanation of how these
+ different sections are combined when a request is received</seealso>
</directivesynopsis>
<directivesynopsis type="section">
<p>would match most common Internet graphics formats.</p>
</usage>
-
-<seealso><a href="../sections.html">How
- Directory, Location and Files sections work</a> for an
- explanation of how these different sections are combined when a
- request is received</seealso>
+<seealso><a href="../sections.html">How <Directory>, <Location>
+ and <Files> sections work</a> for an explanation of how these
+ different sections are combined when a request is received</seealso>
</directivesynopsis>
<directivesynopsis>
<p>This directive enables DNS lookups so that host names can be
logged (and passed to CGIs/SSIs in <code>REMOTE_HOST</code>).
The value <code>Double</code> refers to doing double-reverse
- DNS. That is, after a reverse lookup is performed, a forward
+ DNS lookup. That is, after a reverse lookup is performed, a forward
lookup is then performed on that result. At least one of the ip
addresses in the forward lookup must match the original
address. (In "tcpwrappers" terminology this is called
Heavily loaded sites should leave this directive
<code>Off</code>, since DNS lookups can take considerable
amounts of time. The utility <a
- href="../programs/logresolve.html">logresolve</a>, provided in
- the <var>/support</var> directory, can be used to look up host
- names from logged IP addresses offline.</p>
+ href="../programs/logresolve.html">logresolve</a>, compiled by default
+ to the <code>bin</code> subdirectory of your installation directory, can
+ be used to look up host names from logged IP addresses offline.</p>
</usage>
</directivesynopsis>
<description>Encloses directives that are processed conditional on the
presence or absence of a specific module</description>
<syntax><IfModule [!]<var>module-name</var>> ...
- </IfModule></syntax>
+ </IfModule></syntax>
<contextlist><context>server config</context><context>virtual host</context>
<context>directory</context><context>.htaccess</context>
</contextlist>
fail.</p>
<p>The file path specified may be a fully qualified path (i.e.
- starting with a slash), or may be relative to the
+ starting with a slash), or may be relative to the
<directive module="core">ServerRoot</directive> directory.</p>
<p>Examples:</p>
which allow multiple requests to be sent over the same TCP
connection. In some cases this has been shown to result in an
almost 50% speedup in latency times for HTML documents with
- many images. To enable Keep-Alive connections in Apache 1.2 and
- later, set <code>KeepAlive On</code>.</p>
+ many images. To enable Keep-Alive connections, set
+ <code>KeepAlive On</code>.</p>
<p>For HTTP/1.0 clients, Keep-Alive connections will only be
used if they are specifically requested by a client. In
<directivesynopsis type="section">
<name>Limit</name>
<description>Restrict enclosed access controls to only certain HTTP
-methods</description>
+methods</description>
<syntax><Limit <var>method</var> [<var>method</var>] ... > ...
</Limit></syntax>
<contextlist><context>server config</context><context>virtual host</context>
<p>The purpose of the <directive type="section">Limit</directive>
directive is to restrict the effect of the access controls to the
nominated HTTP methods. For all other methods, the access
- restrictions that are enclosed in the <code><Limit></code>
- bracket <strong>will have no effect</strong>. The following
- example applies the access control only to the methods <code>POST</code>,
- <code>PUT</code>, and <code>DELETE</code>, leaving all other methods
- unprotected:</p>
+ restrictions that are enclosed in the <directive
+ type="section">Limit</directive> bracket <strong>will have no
+ effect</strong>. The following example applies the access control
+ only to the methods <code>POST</code>, <code>PUT</code>, and
+ <code>DELETE</code>, leaving all other methods unprotected:</p>
<example>
<Limit POST PUT DELETE><br />
<directivesynopsis type="section">
<name>LimitExcept</name>
<description>Restrict access controls to all HTTP methods
-except the named ones</description>
+except the named ones</description>
<syntax><LimitExcept <var>method</var> [<var>method</var>] ... > ...
</LimitExcept></syntax>
<contextlist><context>server config</context><context>virtual host</context>
<p><directive type="section">LimitExcept</directive> and
<code></LimitExcept></code> are used to enclose
a group of access control directives which will then apply to any
- HTTP access method <strong>not</strong> listed in the arguments;
+ HTTP access method <strong>not</strong> listed in the arguments;
i.e., it is the opposite of a <directive type="section"
module="core">Limit</directive> section and can be used to control
both standard and nonstandard/unrecognized methods. See the
response instead of servicing the request. The size of a normal
request message body will vary greatly depending on the nature of
the resource and the methods allowed on that resource. CGI scripts
- typically use the message body for passing form information to the
- server. Implementations of the <code>PUT</code> method will require
+ typically use the message body for retrieving form information.
+ Implementations of the <code>PUT</code> method will require
a value at least as large as any representation that the server
wishes to accept for that resource.</p>
attacks.</p>
<p>If, for example, you are permitting file upload to a particular
- location, and wich to limit the size of the uploaded file to 100K,
+ location, and wish to limit the size of the uploaded file to 100K,
you might use the following directive:</p>
<example>
<directivesynopsis>
<name>LimitRequestFields</name>
-<description>Limits the number of HTTP request header fields that
+<description>Limits the number of HTTP request header fields that
will be accepted from the client</description>
<syntax>LimitRequestFields <var>number</var></syntax>
<default>LimitRequestFields 100</default>
distributed) that will be allowed in an HTTP request
header.</p>
- <p>The <directive>LimitRequestFieldsize</directive> directive
+ <p>The <directive>LimitRequestFieldSize</directive> directive
allows the server administrator to reduce the limit on the allowed
size of an HTTP request header field below the normal input buffer
size compiled with the server. A server needs this value to be
<directivesynopsis>
<name>LimitXMLRequestBody</name>
<description>Limits the size of an XML-based request body</description>
-<syntax>LimitXMLRequestBody <var>number</var></syntax>
+<syntax>LimitXMLRequestBody <var>bytes</var></syntax>
<default>LimitXMLRequestBody 1000000</default>
<contextlist><context>server config</context><context>virtual host</context>
<context>directory</context><context>.htaccess</context></contextlist>
type="section" module="core">Files</directive> sections.</p>
<p>Note that URLs do not have to line up with the filesystem at
- all, it should be emphasized that <code><Location></code> operates
- completely outside the filesystem.</p>
+ all, it should be emphasized that <directive
+ type="section">Location</directive> operates completely
+ outside the filesystem.</p>
<p>For all origin (non-proxy) requests, the URL to be matched is a
URL-path of the form <code>/path/</code>. No scheme, hostname,
<code>scheme://servername/path</code>, and you must include the
prefix.</p>
- <p>The URL may use wildcards In a wild-card string, <code>?</code> matches
+ <p>The URL may use wildcards. In a wild-card string, <code>?</code> matches
any single character, and <code>*</code> matches any sequences of
characters.</p>
</example>
<p>would match URLs that contained the substring <code>/extra/data</code>
- or <code>/special/data</code>. In Apache 1.3 and above, a new directive
- <directive type="section" module="core">LocationMatch</directive>
- exists which behaves identical to the regex version of
- <directive type="section">Location</directive>.</p>
+ or <code>/special/data</code>. The directive <directive
+ type="section" module="core">LocationMatch</directive> behaves
+ identical to the regex version of <directive
+ type="section">Location</directive>.</p>
<p>The <directive type="section">Location</directive>
functionality is especially useful when combined with the
directive and the regex version of <directive type="section"
>Location</directive> require you to explicitly specify multiple
slashes if that is your intention.</p>
-
+
<p>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) <directive type="section"
request is to <code>/abc//def</code> then it will match.</p>
</note>
</usage>
-<seealso><a href="../sections.html">How
- Directory, Location and Files sections work</a> for an
- explanation of how these different sections are combined when a
- request is received</seealso>
+<seealso><a href="../sections.html">How <Directory>, <Location>
+ and <Files> sections work</a> for an explanation of how these
+ different sections are combined when a request is received</seealso>
</directivesynopsis>
<directivesynopsis type="section">
<name>LocationMatch</name>
-<description>Applies the enclosed directives only to regular-expression
+<description>Applies the enclosed directives only to regular-expression
matching URLs</description>
<syntax><LocationMatch
<var>regex</var>> ... </LocationMatch></syntax>
or <code>/special/data</code>.</p>
</usage>
-<seealso><a href="../sections.html">How
- Directory, Location and Files sections work</a> for an
- explanation of how these different sections are combined when a
- request is received</seealso>
+<seealso><a href="../sections.html">How <Directory>, <Location>
+ and <Files> sections work</a> for an explanation of how these
+ different sections are combined when a request is received</seealso>
</directivesynopsis>
<directivesynopsis>
<directivesynopsis>
<name>MaxKeepAliveRequests</name>
-<description>Number of requests allowed on a persistent
+<description>Number of requests allowed on a persistent
connection</description>
<syntax>MaxKeepAliveRequests <var>number</var></syntax>
<default>MaxKeepAliveRequests 100</default>
servicing the requests. If you have multiple name-based hosts on
multiple addresses, repeat the directive for each address.</p>
- <p>Note: the "main server" and any <code>_default_</code> servers will
- <strong>never</strong> be served for a request to a
- <directive>NameVirtualHost</directive> IP Address (unless for some
- reason you specify <directive>NameVirtualHost</directive> but then
- don't define any <directive>VirtualHost</directive>s for that address).</p>
+ <note><title>Note</title>
+ <p>Note, that the "main server" and any <code>_default_</code> servers
+ will <strong>never</strong> be served for a request to a
+ <directive>NameVirtualHost</directive> IP Address (unless for some
+ reason you specify <directive>NameVirtualHost</directive> but then
+ don't define any <directive>VirtualHost</directive>s for that
+ address).</p>
+ </note>
<p>Optionally you can specify a port number on which the
name-based virtual hosts should be used, e.g.</p>
NameVirtualHost *
</example>
- <note><title>Argument to <directive><VirtualHost></directive>
+ <note><title>Argument to <directive type="section">VirtualHost</directive>
directive</title>
<p>Note that the argument to the <directive
- ><VirtualHost></directive> directive must
+ type="section">VirtualHost</directive> directive must
exactly match the argument to the <directive
>NameVirtualHost</directive> directive.</p>
the following:</p>
<dl>
- <dt>All</dt>
+ <dt><code>All</code></dt>
<dd>All options except for <code>MultiViews</code>. This is the default
setting.</dd>
- <dt>ExecCGI</dt>
+ <dt><code>ExecCGI</code></dt>
<dd>
Execution of CGI scripts is permitted.</dd>
- <dt>FollowSymLinks</dt>
+ <dt><code>FollowSymLinks</code></dt>
<dd>
section.</p>
</note></dd>
- <dt>Includes</dt>
+ <dt><code>Includes</code></dt>
<dd>
Server-side includes are permitted.</dd>
- <dt>IncludesNOEXEC</dt>
+ <dt><code>IncludesNOEXEC</code></dt>
<dd>
<code>#include virtual</code> CGI scripts from
<directive>ScriptAlias</directive>e'd directories.</dd>
- <dt>Indexes</dt>
+ <dt><code>Indexes</code></dt>
<dd>
If a URL which maps to a directory is requested, and the
<code>index.html</code>) in that directory, then the server will
return a formatted listing of the directory.</dd>
- <dt>MultiViews</dt>
+ <dt><code>MultiViews</code></dt>
<dd>
<a href="../content-negotiation.html">Content negotiated</a>
"MultiViews" are allowed.</dd>
- <dt>SymLinksIfOwnerMatch</dt>
+ <dt><code>SymLinksIfOwnerMatch</code></dt>
<dd>
<code>Includes</code> are set for the <code>/web/docs/spec</code>
directory.</p>
-
- <p><strong>Note:</strong> Using <code>-IncludesNOEXEC</code> or
- <code>-Includes</code> disables server-side includes completely
- regardless of the previous setting.</p>
+ <note><title>Note</title>
+ <p>Using <code>-IncludesNOEXEC</code> or
+ <code>-Includes</code> disables server-side includes completely
+ regardless of the previous setting.</p>
+ </note>
<p>The default in the absence of any other settings is
<code>All</code>.</p>
<directivesynopsis>
<name>Require</name>
<description>Selects which authenticated users can access
-a resource</description>
+a resource</description>
<syntax>Require <var>entity-name</var> [<var>entity-name</var>] ...</syntax>
<contextlist><context>directory</context><context>.htaccess</context>
</contextlist>
<ul>
<li>
- Require user <var>userid</var> [<var>userid</var>] ...
+ Require user <var>userid</var> [<var>userid</var>] ...
- <p>Only the named users can access the directory.</p>
+ <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
- directory.</p>
+ resource.</p>
</li>
<li>
- Require valid-user
+ Require valid-user
- <p>All valid users can access the directory.</p>
+ <p>All valid users can access the resource.</p>
</li>
</ul>
<directivesynopsis>
<name>RLimitNPROC</name>
-<description>Limits the number of processes that can be launched by
+<description>Limits the number of processes that can be launched by
processes launched by Apache children</description>
<syntax>RLimitNPROC <var>number</var>|max [<var>number</var>|max]</syntax>
<default>Unset; uses operating system defaults</default>
<p>Process limits control the number of processes per user.</p>
- <p>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><code>cannot fork</code></strong> messages in the
- error_log.</p>
+ <note><title>Note</title>
+ <p>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><code>cannot fork</code></strong> messages in the
+ <code>error_log</code>.</p>
+ </note>
</usage>
<seealso><directive module="core">RLimitMEM</directive></seealso>
<seealso><directive module="core">RLimitCPU</directive></seealso>
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>
- setting, which is the default, suppresses the error line (and is
+ 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
server version number and <directive
<usage>
<p>When placed into an <code>.htaccess</code> file or a
- <directive type="section" module="core">Directory</directive> or
+ <directive type="section" module="core">Directory</directive> or
<directive type="section" module="core">Location</directive>
section, this directive forces all matching files to be parsed
through the <a href="../handler.html">handler</a> given by
<p>Another example: if you wanted to have the server display a
status report whenever a URL of
<code>http://servername/status</code> was called, you might put
- the following into httpd.conf:</p>
+ the following into <code>httpd.conf</code>:</p>
<example>
<Location /status><br />
<li>The amount of time between ACKs on transmissions of TCP
packets in responses.</li>
</ol>
-
+
<p>We plan on making these separately configurable at some point
down the road. The timer used to default to 1200 before 1.2,
but has been lowered to 300 which is still far more than
<usage>
<p>In many situations Apache must construct a <em>self-referential</em>
URL -- that is, a URL that refers back to the same server. With
- <code>UseCanonicalName on</code> Apache will use the hostname and port
+ <code>UseCanonicalName On</code> Apache will use the hostname and port
specified in the <directive module="core">ServerName</directive>
directive to construct the canonical name for the server. This name
is used in all self-referential URLs, and for the values of
self-referential URLs using the hostname and port supplied by
the client if any are supplied (otherwise it will use the
canonical name, as defined above). These values are the same
- that are used to implement <a
+ that are used to implement <a
href="../vhosts/name-based.html">name based virtual hosts</a>,
- and are available with the same clients. The CGI variables
+ and are available with the same clients. The CGI variables
<code>SERVER_NAME</code> and <code>SERVER_PORT</code> will be
constructed from the client supplied values as well.</p>
reverse DNS lookup on the server IP address that the client
connected to in order to work out self-referential URLs.</p>
- <note type="warning"><title>Warning:</title>
+ <note type="warning"><title>Warning</title>
<p>If CGIs make assumptions about the values of <code>SERVER_NAME</code>
they may be broken by this option. The client is essentially free
to give whatever value they want as a hostname. But if the CGI is
<directivesynopsis type="section">
<name>VirtualHost</name>
<description>Contains directives that apply only to a specific
-hostname or IP address</description>
+hostname or IP address</description>
<syntax><VirtualHost
<var>addr</var>[:<var>port</var>] [<var>addr</var>[:<var>port</var>]]
...> ... </VirtualHost></syntax>
<li>The string <code>_default_</code>, which is used only
with IP virtual hosting to catch unmatched IP addresses.</li>
</ul>
-
+
<example><title>Example</title>
<VirtualHost 10.1.2.3><br />
<indent>
</VirtualHost>
</example>
-
+
<p>IPv6 addresses must be specified in square brackets because
the optional port number could not be determined otherwise. An
IPv6 example is shown below:</p>
TransferLog logs/host.example.com-access_log<br />
</indent>
</VirtualHost>
- </example>
+ </example>
<p>Each Virtual Host must correspond to a different IP address,
different port number or a different host name for the server,
in the former case the server machine must be configured to
accept IP packets for multiple addresses. (If the machine does
not have multiple network interfaces, then this can be
- accomplished with the <code>ifconfig alias</code> command (if
+ accomplished with the <code>ifconfig alias</code> command -- if
your OS supports it).</p>
<note><title>Note</title>
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 and Files sections work</a> for an
- explanation of how these different sections are combined when a
- request is received</seealso>
+<seealso><a href="../sections.html">How <Directory>, <Location>
+ and <Files> sections work</a> for an explanation of how these
+ different sections are combined when a request is received</seealso>
</directivesynopsis>
-</modulesynopsis>
+</modulesynopsis>
\ No newline at end of file
projects / apache / commitdiff