<dt><code>Default</code></dt><dd>The treatment of requests with
trailing pathname information is determined by the <a href="../handler.html">handler</a> responsible for the request.
The core handler for normal files defaults to rejecting
- <code>PATH_INFO</code>. Handlers that serve scripts, such as <a href="mod_cgi.html">cgi-script</a> and <a href="mod_isapi.html">isapi-isa</a>, generally accept
+ <code>PATH_INFO</code>
requests. Handlers that serve scripts, such as <a href="mod_cgi.html">cgi-script</a> and <a href="mod_isapi.html">isapi-isa</a>, generally accept
<code>PATH_INFO</code> by default.</dd>
</dl>
<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
- example:</p>
+ configuration files are <a href="#allowoverride">enabled for that
+ directory</a>. For example:</p>
<div class="example"><p><code>
AccessFileName .acl
AddOutputFilterByType DEFLATE text/html text/plain
</code></p></div>
- <p>If you want the content to be processed by more than one filter, they
- have to be separated by semicolons. It's also possible to use one
+ <p>If you want the content to be processed by more than one filter, their
+ names have to be separated by semicolons. It's also possible to use one
<code class="directive">AddOutputFilterByType</code> directive for each of
- them.</p>
+ these filters.</p>
<p>The configuration below causes all script output labeled as
<code>text/html</code> to be processed at first by the
<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>
+ filters are applied if the MIME-type could not be determined and falls
+ back to the <code class="directive"><a href="#defaulttype">DefaultType</a></code> setting,
+ even if the <code class="directive"><a href="#defaulttype">DefaultType</a></code> is the
+ same.</p>
<p>However, if you want to make sure, that the filters will be
applied, assign the content type to a resource explicitely, for
<p>When the server finds an <code>.htaccess</code> file (as
specified by <code class="directive"><a href="#accessfilename">AccessFileName</a></code>)
it needs to know which directives declared in that file can override
- earlier access information.</p>
+ earlier configuration directives.</p>
<div class="note"><h3>Only available in <Directory> sections</h3>
<code class="directive">AllowOverride</code> is valid only in
DefaultType image/gif
</code></p></div>
- <p>would be appropriate for a directory which contained many gif
+ <p>would be appropriate for a directory which contained many GIF
images with filenames missing the <code>.gif</code> extension.</p>
- <p>Note that unlike <code class="directive"><a href="#forcetype">ForceType</a></code>, this directive is only
+ <p>Note that unlike <code class="directive"><a href="#forcetype">ForceType</a></code>, this directive 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>
<p>would match directories in <code>/www/</code> that consisted of
three numbers.</p>
- <p>If multiple (non-regular expression) <code class="directive"><Directory></code> sections
- match the directory (or its parents) containing a document,
+ <p>If multiple (non-regular expression) <code class="directive"><Directory></code> sections
+ match the directory (or one of 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,
with</p>
(disabling <code>.htaccess</code> files).</li>
<li>Apply directive <code>AllowOverride FileInfo</code> (for
- directory <code>/home/web</code>).</li>
+ directory <code>/home</code>).</li>
<li>Apply any <code>FileInfo</code> directives in
- <code>/home/web/.htaccess</code></li>
+ <code>/home/.htaccess</code>, <code>/home/web/.htaccess</code> and
+ <code>/home/web/dir/.htaccess</code> in that order.</li>
</ul>
<p>Regular expressions are not considered until after all of the
</code></p></div>
<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>
+ all normal <code class="directive"><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
+ the corresponding <code class="directive"><Directory></code> will
+ be applied.</p>
<p><strong>Note that the default Apache access for
<code><Directory /></code> is <code>Allow from All</code>.
without ever reading the file if the OS supports it.</p>
<p>This sendfile mechanism avoids seperate read and send operations,
- and buffer allocations. But on some platforms or within some
+ and buffer allocations. But on some platforms or within some
filesystems, it is better to disable this feature to avoid
operational problems:</p>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
</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 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
+ limits the scope of the enclosed directives by filename. It is comparable
+
to the <code class="directive"><a href="#directory"><Directory></a></code>
+ and <code class="directive"><a href="#location"><Location></a></code>
+ directives. It should be matched with a <code></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>
sections are processed in the order they appear in the
configuration file, after the <code class="directive"><a href="#directory"><Directory></a></code> sections and
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
</table>
<p>The <code class="directive"><FilesMatch></code> directive
- provides for access control by filename, just as the <code class="directive"><a href="#files"><Files></a></code> directive
+ limits the scope of the enclosed directives by filename, just as the
+ <code class="directive"><a href="#files"><Files></a></code> directive
does. However, it accepts a regular expression. For example:</p>
<div class="example"><p><code>
files in a directory that can cause <code>httpd</code> to
fail.</p>
- <p>The file path specified may be a fully qualified path (i.e.
+ <p>The file path specified may be an absolute path (i.e.
starting with a slash), or may be relative to the
<code class="directive"><a href="#serverroot">ServerRoot</a></code> directory.</p>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
</table>
<p>The <code class="directive"><Location></code> directive
- provides for access control by URL. It is similar to the
+ limits the scope of the enclosed directives by URL. It is similar to the
<code class="directive"><a href="#directory"><Directory></a></code>
directive, and starts a subsection which is terminated with a
<code></Location></code> directive. <code class="directive"><Location></code> sections are processed in the
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr>
</table>
<p>The <code class="directive"><LocationMatch></code> directive
- provides for access control by URL, in an identical manner to
- <code class="directive"><a href="#location"><Location></a></code>. However,
+ limits the scope of the enclosed directives by URL, in an identical manner
+
to <code class="directive"><a href="#location"><Location></a></code>. However,
it takes a regular expression as an argument instead of a simple
string. For example:</p>
<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>
+ <dd>Only users in the named groups can access the resource.</dd>
<dt><code>Require valid-user</code></dt>
<dd>All valid users can access the resource.</dd>
<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>second</var></code></td></tr>
+<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>TimeOut <var>seconds</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>
trailing pathname information is determined by the <a
href="../handler.html">handler</a> responsible for the request.
The core handler for normal files defaults to rejecting
- <code>PATH_INFO</code>. Handlers that serve scripts, such as <a
+ <code>PATH_INFO</code>
requests. Handlers that serve scripts, such as <a
href="mod_cgi.html">cgi-script</a> and <a
href="mod_isapi.html">isapi-isa</a>, generally accept
<code>PATH_INFO</code> by default.</dd>
<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
- example:</p>
+ configuration files are <a href="#allowoverride">enabled for that
+ directory</a>. For example:</p>
<example>
AccessFileName .acl
AddOutputFilterByType DEFLATE text/html text/plain
</example>
- <p>If you want the content to be processed by more than one filter, they
- have to be separated by semicolons. It's also possible to use one
+ <p>If you want the content to be processed by more than one filter, their
+ names have to be separated by semicolons. It's also possible to use one
<directive>AddOutputFilterByType</directive> directive for each of
- them.</p>
+ these filters.</p>
<p>The configuration below causes all script output labeled as
<code>text/html</code> to be processed at first by the
<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
- module="core">DefaultType</directive>, even if the <directive
- module="core">DefaultType</directive> is the same.</p>
+ filters are applied if the MIME-type could not be determined and falls
+ back to the <directive module="core">DefaultType</directive> setting,
+ even if the <directive module="core">DefaultType</directive> is the
+ same.</p>
<p>However, if you want to make sure, that the filters will be
applied, assign the content type to a resource explicitely, for
<p>When the server finds an <code>.htaccess</code> file (as
specified by <directive module="core">AccessFileName</directive>)
it needs to know which directives declared in that file can override
- earlier access information.</p>
+ earlier configuration directives.</p>
<note><title>Only available in <Directory> sections</title>
<directive>AllowOverride</directive> is valid only in
DefaultType image/gif
</example>
- <p>would be appropriate for a directory which contained many gif
+ <p>would be appropriate for a directory which contained many GIF
images with filenames missing the <code>.gif</code> extension.</p>
<p>Note that unlike <directive
- module="core">ForceType</directive>, this directive is only
+ module="core">ForceType</directive>, this directive 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>
<p>would match directories in <code>/www/</code> that consisted of
three numbers.</p>
- <p>If multiple (non-regular expression) <directive
+ <p>If multiple (non-regular expression) <directive
type="section">Directory</directive> sections
- match the directory (or its parents) containing a document,
+ match the directory (or one of 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,
(disabling <code>.htaccess</code> files).</li>
<li>Apply directive <code>AllowOverride FileInfo</code> (for
- directory <code>/home/web</code>).</li>
+ directory <code>/home</code>).</li>
<li>Apply any <code>FileInfo</code> directives in
- <code>/home/web/.htaccess</code></li>
+ <code>/home/.htaccess</code>, <code>/home/web/.htaccess</code> and
+ <code>/home/web/dir/.htaccess</code> in that order.</li>
</ul>
<p>Regular expressions are not considered until after all of the
</example>
<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>
+ all normal <directive type="section">Directory</directive>s and
+ <code>.htaccess</code> files have been applied. Then the regular
+ expression will match on <code>/home/abc/public_html/abc</code> and
+ the corresponding <directive type="section">Directory</directive> will
+ be applied.</p>
<p><strong>Note that the default Apache access for
<code><Directory /></code> is <code>Allow from All</code>.
without ever reading the file if the OS supports it.</p>
<p>This sendfile mechanism avoids seperate read and send operations,
- and buffer allocations. But on some platforms or within some
+ and buffer allocations. But on some platforms or within some
filesystems, it is better to disable this feature to avoid
operational problems:</p>
<usage>
<p>The <directive type="section">Files</directive> directive
- provides for access control by filename. It is comparable to the
- <directive module="core" type="section">Directory</directive>
- directive and <directive module="core"
- 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
+ limits the scope of the enclosed directives by filename. It is comparable
+ to the <directive module="core" type="section">Directory</directive>
+ and <directive module="core" type="section">Location</directive>
+ directives. It should be matched with a <code></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. <directive type="section">Files</directive>
sections are processed in the order they appear in the
configuration file, after the <directive module="core"
<usage>
<p>The <directive type="section">FilesMatch</directive> directive
- provides for access control by filename, just as the <directive
- module="core" type="section">Files</directive> directive
+ limits the scope of the enclosed directives by filename, just as the
+ <directive module="core" type="section">Files</directive> directive
does. However, it accepts a regular expression. For example:</p>
<example>
<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>
files in a directory that can cause <code>httpd</code> to
fail.</p>
- <p>The file path specified may be a fully qualified path (i.e.
+ <p>The file path specified may be an absolute path (i.e.
starting with a slash), or may be relative to the
<directive module="core">ServerRoot</directive> directory.</p>
<usage>
<p>The <directive type="section">Location</directive> directive
- provides for access control by URL. It is similar to the
+ limits the scope of the enclosed directives by URL. It is similar to the
<directive type="section" module="core">Directory</directive>
directive, and starts a subsection which is terminated with a
<code></Location></code> directive. <directive
<usage>
<p>The <directive type="section">LocationMatch</directive> directive
- provides for access control by URL, in an identical manner to
- <directive module="core" type="section">Location</directive>. However,
+ limits the scope of the enclosed directives by URL, in an identical manner
+ to <directive module="core" type="section">Location</directive>. However,
it takes a regular expression as an argument instead of a simple
string. For example:</p>
<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>
+ <dd>Only users in the named groups can access the resource.</dd>
<dt><code>Require valid-user</code></dt>
<dd>All valid users can access the resource.</dd>
<name>TimeOut</name>
<description>Amount of time the server will wait for
certain events before failing a request</description>
-<syntax>TimeOut <var>second</var></syntax>
+<syntax>TimeOut <var>seconds</var></syntax>
<default>TimeOut 300</default>
<contextlist><context>server config</context></contextlist>
per child process</td></tr>
<tr><td><a href="mpm_common.html#threadsperchild">ThreadsPerChild <var>number</var></a></td><td /><td>s</td><td>M</td></tr><tr><td class="descr" colspan="4">Number of threads created by each child process</td></tr>
<tr class="odd"><td><a href="mpm_netware.html#threadstacksize">ThreadStackSize <var>number</var></a></td><td> 65536 </td><td>s</td><td>M</td></tr><tr class="odd"><td class="descr" colspan="4">Determine the stack size for each thread</td></tr>
-<tr><td><a href="core.html#timeout">TimeOut <var>second</var></a></td><td> 300 </td><td>s</td><td>C</td></tr><tr><td class="descr" colspan="4">Amount of time the server will wait for
+<tr><td><a href="core.html#timeout">TimeOut <var>seconds</var></a></td><td> 300 </td><td>s</td><td>C</td></tr><tr><td class="descr" colspan="4">Amount of time the server will wait for
certain events before failing a request</td></tr>
<tr class="odd"><td><a href="mod_log_config.html#transferlog">TransferLog <var>file</var>|<var>pipe</var></a></td><td /><td>sv</td><td>B</td></tr><tr class="odd"><td class="descr" colspan="4">Specifly location of a log file</td></tr>
<tr><td><a href="mod_mime.html#typesconfig">TypesConfig <var>file-path</var></a></td><td> conf/mime.types </td><td>s</td><td>B</td></tr><tr><td class="descr" colspan="4">The location of the <code>mime.types</code> file</td></tr>
projects / apache / commitdiff