core.xml revision b12b918ae6baf9c5762ed61b7393d0e2198378c0
530eba85dbd41b8a0fa5255d3648d1440199a661slive<!DOCTYPE modulesynopsis SYSTEM "/style/modulesynopsis.dtd">
e942c741056732f50da2074b36fe59805d370650slive<?xml-stylesheet type="text/xsl" href="/style/manual.en.xsl"?>
5f5d1b4cc970b7f06ff8ef6526128e9a27303d88nd<!-- $Revision: 1.85 $ -->
db479b48bd4d75423ed4a45e15b75089d1a8ad72fielding Copyright 2002-2004 The Apache Software Foundation
db479b48bd4d75423ed4a45e15b75089d1a8ad72fielding Licensed under the Apache License, Version 2.0 (the "License");
db479b48bd4d75423ed4a45e15b75089d1a8ad72fielding you may not use this file except in compliance with the License.
db479b48bd4d75423ed4a45e15b75089d1a8ad72fielding You may obtain a copy of the License at
d5d794fc2f4cc9ca6d6da17cfa2cdcd8d244bacdnd Unless required by applicable law or agreed to in writing, software
d5d794fc2f4cc9ca6d6da17cfa2cdcd8d244bacdnd distributed under the License is distributed on an "AS IS" BASIS,
d5d794fc2f4cc9ca6d6da17cfa2cdcd8d244bacdnd WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
d5d794fc2f4cc9ca6d6da17cfa2cdcd8d244bacdnd See the License for the specific language governing permissions and
d5d794fc2f4cc9ca6d6da17cfa2cdcd8d244bacdnd limitations under the License.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Core Apache HTTP Server features that are always
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveavailable</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna<description>Resources accept trailing pathname information</description>
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen<context>virtual host</context><context>directory</context>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna<compatibility>Available in Apache 2.0.30 and later</compatibility>
e4e60c2f7ba8f12b687f588b89e413842e9f2d76igalic <p>This directive controls whether requests that contain trailing
e4e60c2f7ba8f12b687f588b89e413842e9f2d76igalic pathname information that follows an actual filename (or
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor non-existent file in an existing directory) will be accepted or
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe rejected. The trailing pathname information can be made
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe available to scripts in the <code>PATH_INFO</code> environment
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe variable.</p>
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe <p>For example, assume the location <code>/test/</code> points to
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe a directory that contains only the single file
4e9f8c5414e5fe39b5393641533edca65f6e8b91poirier <p>The three possible arguments for the
4e9f8c5414e5fe39b5393641533edca65f6e8b91poirier <directive>AcceptPathInfo</directive> directive are:</p>
4e9f8c5414e5fe39b5393641533edca65f6e8b91poirier <dt><code>Off</code></dt><dd>A request will only be accepted if it
4e9f8c5414e5fe39b5393641533edca65f6e8b91poirier maps to a literal path that exists. Therefore a request with
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna trailing pathname information after the true filename such as
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <code>/test/here.html/more</code> in the above example will return
2aa51ed61adb484602e94de3d2214ec267aecedbigalic a 404 NOT FOUND error.</dd>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <dt><code>On</code></dt><dd>A request will be accepted if a
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor leading path component maps to a file that exists. The above
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna example <code>/test/here.html/more</code> will be accepted if
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor <code>/test/here.html</code> maps to a valid file.</dd>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna <dt><code>Default</code></dt><dd>The treatment of requests with
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor trailing pathname information is determined by the <a
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna href="/handler.html">handler</a> responsible for the request.
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna The core handler for normal files defaults to rejecting
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna <code>PATH_INFO</code> requests. Handlers that serve scripts, such as <a
2aa51ed61adb484602e94de3d2214ec267aecedbigalic href="mod_isapi.html">isapi-isa</a>, generally accept
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna <p>The primary purpose of the <code>AcceptPathInfo</code>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna directive is to allow you to override the handler's choice of
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor accepting or rejecting <code>PATH_INFO</code>. This override is required,
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna for example, when you use a <a href="/filter.html">filter</a>, such
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor as <a href="mod_include.html">INCLUDES</a>, to generate content
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna based on <code>PATH_INFO</code>. The core handler would usually reject
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna the request, so you can use the following configuration to enable
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna such a script:</p>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic Options +Includes<br />
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe SetOutputFilter INCLUDES<br />
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe AcceptPathInfo On<br />
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe </Files>
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe</directivesynopsis>
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe<directivesynopsis>
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe<description>Name of the distributed configuration file</description>
e4e60c2f7ba8f12b687f588b89e413842e9f2d76igalic<syntax>AccessFileName <var>filename</var> [<var>filename</var>] ...</syntax>
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe<contextlist><context>server config</context><context>virtual host</context>
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe</contextlist>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna <p>While processing a request the server looks for
abad96c7b1becfc55c29a2933d909aa0b37b0fe0humbedooh the first existing configuration file from this list of names in
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna every directory of the path to the document, if distributed
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna configuration files are <a href="#allowoverride">enabled for that
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive AccessFileName .acl
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>before returning the document
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>/usr/local/web/index.html</code>, the server will read
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen <code>/usr/local/.acl</code> and <code>/usr/local/web/.acl</code>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive for directives, unless they have been disabled with</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <Directory /><br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive AllowOverride None<br />
fb77c505254b6e9c925e23e734463e87574f8f40kess </Directory>
fb77c505254b6e9c925e23e734463e87574f8f40kess </example>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">AllowOverride</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><a href="/configuring.html">Configuration Files</a></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><a href="/howto/htaccess.html">.htaccess Files</a></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
fb77c505254b6e9c925e23e734463e87574f8f40kess<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Default character set to be added for a
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveresponse without an explicit character set</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax>AddDefaultCharset On|Off|<var>charset</var></syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>virtual host</context><context>directory</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive specifies the name of the character set that
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive will be added to any response that does not have any parameter on
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the content type in the HTTP headers. This will override any
fb77c505254b6e9c925e23e734463e87574f8f40kess character set specified in the body of the document via a
fb77c505254b6e9c925e23e734463e87574f8f40kess <code>META</code> tag. A setting of <code>AddDefaultCharset
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Off</code> disables this
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive functionality. <code>AddDefaultCharset On</code> enables
fb77c505254b6e9c925e23e734463e87574f8f40kess Apache's internal default charset of <code>iso-8859-1</code> as
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess required by the directive. You can also specify an alternate
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive AddDefaultCharset utf-8
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
fb77c505254b6e9c925e23e734463e87574f8f40kess<directivesynopsis>
fb77c505254b6e9c925e23e734463e87574f8f40kess<description>assigns an output filter to a particular MIME-type</description>
fb77c505254b6e9c925e23e734463e87574f8f40kess<syntax>AddOutputFilterByType <var>filter</var>[;<var>filter</var>...]
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<var>MIME-type</var> [<var>MIME-type</var>] ...</syntax>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<context>virtual host</context><context>directory</context>
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh<compatibility>Available in Apache 2.0.33 and later</compatibility>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd href="/filter.html">filter</a> for a request depending on the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive response MIME-type.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The following example uses the <code>DEFLATE</code> filter, which
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive is provided by <module>mod_deflate</module>. It will compress all
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive output (either static or dynamic) which is labeled as
003f0c9fda6664daf5092a0e42f65ede20098153slive <code>text/html</code> or <code>text/plain</code> before it is sent
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd to the client.</p>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <p>If you want the content to be processed by more than one filter, their
003f0c9fda6664daf5092a0e42f65ede20098153slive names have to be separated by semicolons. It's also possible to use one
003f0c9fda6664daf5092a0e42f65ede20098153slive <directive>AddOutputFilterByType</directive> directive for each of
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess these filters.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The configuration below causes all script output labeled as
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh <code>text/html</code> to be processed at first by the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>INCLUDES</code> filter and then by the <code>DEFLATE</code>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive filter.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <Location /cgi-bin/><br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Options Includes<br />
2aa51ed61adb484602e94de3d2214ec267aecedbigalic AddOutputFilterByType INCLUDES;DEFLATE text/html<br />
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh </Location>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Enabling filters with <directive>AddOutputFilterByType</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive may fail partially or completely in some cases. For expample, no
1a3f62ca37273a15a06bb94a61d3c6fcf4bf38c9rbowen filters are applied if the MIME-type could not be determined and falls
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive back to the <directive module="core">DefaultType</directive> setting,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive even if the <directive module="core">DefaultType</directive> is the
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding <p>However, if you want to make sure, that the filters will be
684f2a9a422185adda0692a1203c5ad6687fc5c5nd applied, assign the content type to a resource explicitely, for
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd example with <directive module="mod_mime">AddType</directive> or
530eba85dbd41b8a0fa5255d3648d1440199a661slive <directive module="core">ForceType</directive>. Setting the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive content type within a (non-nph) CGI script is also safe.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The by-type output filters are never applied on proxy requests.</p>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding<seealso><directive module="mod_mime">AddOutputFilter</directive></seealso>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding<seealso><directive module="core">SetOutputFilter</directive></seealso>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding<seealso><a href="/filter.html">filters</a></seealso>
684f2a9a422185adda0692a1203c5ad6687fc5c5nd</directivesynopsis>
684f2a9a422185adda0692a1203c5ad6687fc5c5nd<directivesynopsis>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding<description>Determines whether encoded path separators in URLs are allowed to
843a03fe0b138a4c1f64cb90a014e9417ac30691fieldingbe passed through</description>
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding<contextlist><context>server config</context><context>virtual host</context>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<compatibility>Available in Apache 2.0.46 and later</compatibility>
684f2a9a422185adda0692a1203c5ad6687fc5c5nd <p>The <directive>AllowEncodedSlashes</directive> directive allows URLs
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding which contain encoded path separators (<code>%2F</code> for <code>/</code>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding and additionally <code>%5C</code> for <code>\</code> on according systems)
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding to be used. Normally such URLs are refused with a 404 (Not found) error.</p>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding <p>Turning <directive>AllowEncodedSlashes</directive> <code>On</code> is
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding mostly useful when used in conjunction with <code>PATH_INFO</code>.</p>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding <p>Allowing encoded slashes does <em>not</em> imply <em>decoding</em>.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Occurences of <code>%2F</code> or <code>%5C</code> (<em>only</em> on
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding according systems) will be left as such in the otherwise decoded URL
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive string.</p>
77ead9e0262e4f08ec336d1a65b2edef7705c839nd<seealso><directive module="core">AcceptPathInfo</directive></seealso>
9583adab6bc4b3758e41963c905d9dad9f067131nd</directivesynopsis>
77ead9e0262e4f08ec336d1a65b2edef7705c839nd<directivesynopsis>
77ead9e0262e4f08ec336d1a65b2edef7705c839nd<description>Types of directives that are allowed in
3770ed746d69c7a4111cba9966169bd5d7a509a6poirier<syntax>AllowOverride All|None|<var>directive-type</var>
3770ed746d69c7a4111cba9966169bd5d7a509a6poirier <p>When the server finds an <code>.htaccess</code> file (as
3770ed746d69c7a4111cba9966169bd5d7a509a6poirier specified by <directive module="core">AccessFileName</directive>)
3770ed746d69c7a4111cba9966169bd5d7a509a6poirier it needs to know which directives declared in that file can override
3770ed746d69c7a4111cba9966169bd5d7a509a6poirier earlier configuration directives.</p>
3770ed746d69c7a4111cba9966169bd5d7a509a6poirier <note><title>Only available in <Directory> sections</title>
3770ed746d69c7a4111cba9966169bd5d7a509a6poirier <directive>AllowOverride</directive> is valid only in
3770ed746d69c7a4111cba9966169bd5d7a509a6poirier <directive type="section" module="core">Directory</directive>
3770ed746d69c7a4111cba9966169bd5d7a509a6poirier sections specified without regular expressions, not in <directive
3770ed746d69c7a4111cba9966169bd5d7a509a6poirier type="section" module="core">Location</directive>, <directive
77ead9e0262e4f08ec336d1a65b2edef7705c839nd module="core" type="section">DirectoryMatch</directive> or
77ead9e0262e4f08ec336d1a65b2edef7705c839nd <directive type="section" module="core">Files</directive> sections.
3770ed746d69c7a4111cba9966169bd5d7a509a6poirier <a href="#accessfilename">.htaccess</a> files are completely ignored.
3770ed746d69c7a4111cba9966169bd5d7a509a6poirier In this case, the server will not even attempt to read
77ead9e0262e4f08ec336d1a65b2edef7705c839nd <p>When this directive is set to <code>All</code>, then any
77ead9e0262e4f08ec336d1a65b2edef7705c839nd directive which has the .htaccess <a
77ead9e0262e4f08ec336d1a65b2edef7705c839nd href="directive-dict.html#Context">Context</a> is allowed in
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <var>directive-type</var> can be one of the following
003f0c9fda6664daf5092a0e42f65ede20098153slive groupings of directives.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Allow use of the authorization directives (<directive
fb77c505254b6e9c925e23e734463e87574f8f40kess <directive module="mod_authn_dbm">AuthDBMUserFile</directive>,
fb77c505254b6e9c925e23e734463e87574f8f40kess <directive module="mod_authz_groupfile">AuthGroupFile</directive>,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="core">AuthType</directive>, <directive
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess module="mod_authn_file">AuthUserFile</directive>, <directive
10673857794a4b3d9568ca2d983722a87ed352f1rbowen module="core">Require</directive>, <em>etc.</em>).</dd>
b12b918ae6baf9c5762ed61b7393d0e2198378c0nd Allow use of the directives controlling document types (<directive
113961f0559eb026ea0d379cb7350f82bc09d710druggeri module="mod_negotiation">LanguagePriority</directive>,
113961f0559eb026ea0d379cb7350f82bc09d710druggeri <directive module="core">SetHandler</directive>, <directive
113961f0559eb026ea0d379cb7350f82bc09d710druggeri module="core">SetInputFilter</directive>, <directive
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd Allow use of the directives controlling directory indexing
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive (<directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="mod_autoindex">AddIcon</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="mod_autoindex">AddIconByType</directive>,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="mod_autoindex">DefaultIcon</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_dir">DirectoryIndex</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_autoindex">FancyIndexing</directive>, <directive
0834a50e694f91f4bf20ddf030fd0812e65cafc7rbowen module="mod_autoindex">HeaderName</directive>, <directive
1f53e295ebd19aed1767d12da7abfab9936c148cjerenkrantz module="mod_autoindex">IndexIgnore</directive>, <directive
9ed9eaf871c58d281af02e76125ceadb5060afa5nd module="mod_autoindex">IndexOptions</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Allow use of the directives controlling host access (<directive
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding module="mod_authz_host">Deny</directive> and <directive
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding Allow use of the directives controlling specific directory
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding features (<directive module="core">Options</directive> and
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding <directive module="mod_include">XBitHack</directive>).</dd>
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem AllowOverride AuthConfig Indexes
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem <p>In the example above all directives that are neither in the group
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem <code>AuthConfig</code> nor <code>Indexes</code> cause an internal
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem server error.</p>
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem<seealso><directive module="core">AccessFileName</directive></seealso>
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem<seealso><a href="/configuring.html">Configuration Files</a></seealso>
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem<seealso><a href="/howto/htaccess.html">.htaccess Files</a></seealso>
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem</directivesynopsis>
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Authorization realm for use in HTTP
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveauthentication</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>directory</context><context>.htaccess</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive sets the name of the authorization realm for a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directory. This realm is given to the client so that the user
0834a50e694f91f4bf20ddf030fd0812e65cafc7rbowen knows which username and password to send.
0834a50e694f91f4bf20ddf030fd0812e65cafc7rbowen <directive>AuthName</directive> takes a single argument; if the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive realm name contains spaces, it must be enclosed in quotation
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive marks. It must be accompanied by <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="core">Require</directive> directives, and directives such
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive as <directive module="mod_authn_file">AuthUserFile</directive> and
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="mod_authz_groupfile">AuthGroupFile</directive> to
8cb1b3a3753304d51919865f588cbe19cbd0182arbowen AuthName "Top Secret"
eb73941bd697cd7e8226ceaf04183ade6c66934dniq <p>The string provided for the <code>AuthName</code> is what will
e67969aeb443b18bbb3837690c4010c3f1961842jim appear in the password dialog provided by most browsers.</p>
eb73941bd697cd7e8226ceaf04183ade6c66934dniq href="/howto/auth.html">Authentication, Authorization, and
eb73941bd697cd7e8226ceaf04183ade6c66934dniq</directivesynopsis>
eb73941bd697cd7e8226ceaf04183ade6c66934dniq<directivesynopsis>
eb73941bd697cd7e8226ceaf04183ade6c66934dniq<contextlist><context>directory</context><context>.htaccess</context>
eb73941bd697cd7e8226ceaf04183ade6c66934dniq</contextlist>
184255c60354393e95feca30bbc8dec660f612abnd <p>This directive selects the type of user authentication for a
eb73941bd697cd7e8226ceaf04183ade6c66934dniq directory. Only <code>Basic</code> and <code>Digest</code> are
eb73941bd697cd7e8226ceaf04183ade6c66934dniq currently implemented.
eb73941bd697cd7e8226ceaf04183ade6c66934dniq It must be accompanied by <directive
beefdf2539f2cd75fd45f5d560cbb26783ff9db1jim module="core">Require</directive> directives, and directives such
beefdf2539f2cd75fd45f5d560cbb26783ff9db1jim as <directive module="mod_authn_file">AuthUserFile</directive> and
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="mod_authz_groupfile">AuthGroupFile</directive> to
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><a href="/howto/auth.html">Authentication, Authorization,
103a93c625bcde1a6a7a5155b64dcda36f612180pquerna</directivesynopsis>
9970ad80054f477c708284a0d030a5bd26e412a9covener<directivesynopsis>
9970ad80054f477c708284a0d030a5bd26e412a9covener<description>Technique for locating the interpreter for CGI
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjimscripts</description>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim<syntax>CGIMapExtension <var>cgi-path</var> <var>.extension</var></syntax>
9970ad80054f477c708284a0d030a5bd26e412a9covener<contextlist><context>directory</context><context>.htaccess</context>
9970ad80054f477c708284a0d030a5bd26e412a9covener</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive is used to control how Apache finds the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive interpreter used to run CGI scripts. For example, setting
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive cause all CGI script files with a <code>.foo</code> extension to
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh be passed to the FOO interpreter.</p>
b12b918ae6baf9c5762ed61b7393d0e2198378c0nd</directivesynopsis>
b12b918ae6baf9c5762ed61b7393d0e2198378c0nd<directivesynopsis>
da637bcae7b6e150470e701af29da5604a34a17erbowen<description>Enables the generation of <code>Content-MD5</code> HTTP Response
031bbbc0d1189b07330e38d0c126820a9ab7795egryzorheaders</description>
da637bcae7b6e150470e701af29da5604a34a17erbowen<contextlist><context>server config</context><context>virtual host</context>
da637bcae7b6e150470e701af29da5604a34a17erbowen<context>directory</context><context>.htaccess</context>
da637bcae7b6e150470e701af29da5604a34a17erbowen</contextlist>
7802d43d20007fa575e43b6ae77d5177ceffdb71sf <p>This directive enables the generation of
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive respectively RFC2068.</p>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri <p>MD5 is an algorithm for computing a "message digest"
113961f0559eb026ea0d379cb7350f82bc09d710druggeri (sometimes called "fingerprint") of arbitrary-length data, with
113961f0559eb026ea0d379cb7350f82bc09d710druggeri a high degree of confidence that any alterations in the data
113961f0559eb026ea0d379cb7350f82bc09d710druggeri will be reflected in alterations in the message digest.</p>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri <p>The <code>Content-MD5</code> header provides an end-to-end
113961f0559eb026ea0d379cb7350f82bc09d710druggeri message integrity check (MIC) of the entity-body. A proxy or
113961f0559eb026ea0d379cb7350f82bc09d710druggeri client may check this header for detecting accidental
113961f0559eb026ea0d379cb7350f82bc09d710druggeri modification of the entity-body in transit. Example header:</p>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri Content-MD5: AuLb7Dp1rqtRtxz2m9kRpA==
113961f0559eb026ea0d379cb7350f82bc09d710druggeri <p>Note that this can cause performance problems on your server
113961f0559eb026ea0d379cb7350f82bc09d710druggeri since the message digest is computed on every request (the
113961f0559eb026ea0d379cb7350f82bc09d710druggeri values are not cached).</p>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri <p><code>Content-MD5</code> is only sent for documents served
113961f0559eb026ea0d379cb7350f82bc09d710druggeri by the <module>core</module>, and not by any module. For example,
113961f0559eb026ea0d379cb7350f82bc09d710druggeri SSI documents, output from CGI scripts, and byte range responses
113961f0559eb026ea0d379cb7350f82bc09d710druggeri do not have this header.</p>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri</directivesynopsis>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri<directivesynopsis>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri<description>MIME content-type that will be sent if the
113961f0559eb026ea0d379cb7350f82bc09d710druggeriserver cannot determine a type in any other way</description>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<contextlist><context>server config</context><context>virtual host</context>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<context>directory</context><context>.htaccess</context>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic</contextlist>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri <p>There will be times when the server is asked to provide a
113961f0559eb026ea0d379cb7350f82bc09d710druggeri document whose type cannot be determined by its MIME types
113961f0559eb026ea0d379cb7350f82bc09d710druggeri mappings.</p>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri <p>The server must inform the client of the content-type of the
2aa51ed61adb484602e94de3d2214ec267aecedbigalic document, so in the event of an unknown type it uses the
113961f0559eb026ea0d379cb7350f82bc09d710druggeri <p>would be appropriate for a directory which contained many GIF
113961f0559eb026ea0d379cb7350f82bc09d710druggeri images with filenames missing the <code>.gif</code> extension.</p>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri module="core">ForceType</directive>, this directive only
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive provides the default mime-type. All other mime-type definitions,
113961f0559eb026ea0d379cb7350f82bc09d710druggeri including filename extensions, that might identify the media type
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive will override this default.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
fb77c505254b6e9c925e23e734463e87574f8f40kess<description>Enclose a group of directives that apply only to the
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholesnamed file-system directory and sub-directories</description>
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes... </Directory></syntax>
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes<contextlist><context>server config</context><context>virtual host</context>
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes</contextlist>
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes <p><directive type="section">Directory</directive> and
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen <code></Directory></code> are used to enclose a group of
fb77c505254b6e9c925e23e734463e87574f8f40kess directives that will apply only to the named directory and
fb77c505254b6e9c925e23e734463e87574f8f40kess sub-directories of that directory. Any directive that is allowed
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess in a directory context may be used. <var>Directory-path</var> is
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess either the full path to a directory, or a wild-card string using
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes Unix shell-style matching. In a wild-card string, <code>?</code> matches
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes any single character, and <code>*</code> matches any sequences of
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes characters. You may also use <code>[]</code> character ranges. None
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive of the wildcards match a `/' character, so <code><Directory
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive /*/public_html></code> will not match
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <code>/home/user/public_html</code>, but <code><Directory
fb77c505254b6e9c925e23e734463e87574f8f40kess /home/*/public_html></code> will match. Example:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Options Indexes FollowSymLinks<br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </Directory>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Be careful with the <var>directory-path</var> arguments:
5bb5fba250bf526bc51d13b25378d54acb93c1cbnoodl They have to literally match the filesystem path which Apache uses
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive to access the files. Directives applied to a particular
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code><Directory></code> will not apply to files accessed from
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive that same directory via a different path, such as via different symbolic
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Extended regular
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive expressions can also be used, with the addition of the
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <Directory ~ "^/www/.*/[0-9]{3}">
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd </example>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>would match directories in <code>/www/</code> that consisted of
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive three numbers.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive match the directory (or one of its parents) containing a document,
fb77c505254b6e9c925e23e734463e87574f8f40kess then the directives are applied in the order of shortest match
fb77c505254b6e9c925e23e734463e87574f8f40kess first, interspersed with the directives from the <a
fb77c505254b6e9c925e23e734463e87574f8f40kess href="#accessfilename">.htaccess</a> files. For example,
2dada762fb99649c2a57bb9e19fe1666f2c20c38jim <Directory /><br />
2dada762fb99649c2a57bb9e19fe1666f2c20c38jim AllowOverride None<br />
2dada762fb99649c2a57bb9e19fe1666f2c20c38jim </Directory><br />
2dada762fb99649c2a57bb9e19fe1666f2c20c38jim <Directory /home/><br />
2dada762fb99649c2a57bb9e19fe1666f2c20c38jim AllowOverride FileInfo<br />
2dada762fb99649c2a57bb9e19fe1666f2c20c38jim </Directory>
2dada762fb99649c2a57bb9e19fe1666f2c20c38jim </example>
c8b79d4b8796531f19dd54bd59d88c3b68338ceahumbedooh <p>for access to the document <code>/home/web/dir/doc.html</code>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic the steps are:</p>
2dada762fb99649c2a57bb9e19fe1666f2c20c38jim <li>Apply directive <code>AllowOverride FileInfo</code> (for
2dada762fb99649c2a57bb9e19fe1666f2c20c38jim <code>/home/.htaccess</code>, <code>/home/web/.htaccess</code> and
2dada762fb99649c2a57bb9e19fe1666f2c20c38jim <code>/home/web/dir/.htaccess</code> in that order.</li>
2dada762fb99649c2a57bb9e19fe1666f2c20c38jim <p>Regular expressions are not considered until after all of the
2dada762fb99649c2a57bb9e19fe1666f2c20c38jim normal sections have been applied. Then all of the regular
2dada762fb99649c2a57bb9e19fe1666f2c20c38jim expressions are tested in the order they appeared in the
2dada762fb99649c2a57bb9e19fe1666f2c20c38jim configuration file. For example, with</p>
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding <Directory ~ abc$><br />
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding # ... directives here ...<br />
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding </Directory>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>the regular expression section won't be considered until after
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive all normal <directive type="section">Directory</directive>s and
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>.htaccess</code> files have been applied. Then the regular
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive expression will match on <code>/home/abc/public_html/abc</code> and
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen the corresponding <directive type="section">Directory</directive> will
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive be applied.</p>
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding <code><Directory /></code> is <code>Allow from All</code>.
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding This means that Apache will serve any file mapped from an URL. It is
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive recommended that you change this with a block such
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding <Directory /><br />
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding Order Deny,Allow<br />
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding Deny from All<br />
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding </Directory>
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding <p><strong>and then override this for directories you
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive href="/misc/security_tips.html">Security Tips</a> page for more
6e483e0b8aa3fa574288a7452221392a03e2b9a3noodl <p>The directory sections occur in the <code>httpd.conf</code> file.
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf <directive type="section">Directory</directive> directives
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf cannot nest, and cannot appear in a <directive module="core"
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf type="section">Limit</directive> or <directive module="core"
6e483e0b8aa3fa574288a7452221392a03e2b9a3noodl<seealso><a href="/sections.html">How <Directory>,
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf <Location> and <Files> sections work</a> for an
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf explanation of how these different sections are combined when a
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf request is received</seealso>
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf</directivesynopsis>
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf<description>Enclose directives that apply to
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsffile-system directories matching a regular expression and their
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsfsubdirectories</description>
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf... </DirectoryMatch></syntax>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<contextlist><context>server config</context><context>virtual host</context>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic</contextlist>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <p><directive type="section">DirectoryMatch</directive> and
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <code></DirectoryMatch></code> are used to enclose a group
2aa51ed61adb484602e94de3d2214ec267aecedbigalic of directives which will apply only to the named directory and
2aa51ed61adb484602e94de3d2214ec267aecedbigalic sub-directories of that directory, the same as <directive
2aa51ed61adb484602e94de3d2214ec267aecedbigalic module="core" type="section">Directory</directive>. However, it
cba8c0896ba04d42cf9a9e50df5040fd6bae14a4sf takes as an argument a regular expression. For example:</p>
6e483e0b8aa3fa574288a7452221392a03e2b9a3noodl <DirectoryMatch "^/www/.*/[0-9]{3}">
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>would match directories in <code>/www/</code> that consisted of three
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive numbers.</p>
898475b582dd849de5915df0f2089b72ed8b2e2bcovener<seealso><directive type="section" module="core">Directory</directive> for
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnda description of how regular expressions are mixed in with normal
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directive type="section">Directory</directive>s</seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivehref="/sections.html">How <Directory>, <Location> and
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<Files> sections work</a> for an explanation of how these different
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivesections are combined when a request is received</seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
898475b582dd849de5915df0f2089b72ed8b2e2bcovener<directivesynopsis>
898475b582dd849de5915df0f2089b72ed8b2e2bcovener<description>Directory that forms the main document tree visible
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cndfrom the web</description>
003f0c9fda6664daf5092a0e42f65ede20098153slive<syntax>DocumentRoot <var>directory-path</var></syntax>
fb77c505254b6e9c925e23e734463e87574f8f40kess<default>DocumentRoot /usr/local/apache/htdocs</default>
fb77c505254b6e9c925e23e734463e87574f8f40kess<contextlist><context>server config</context><context>virtual host</context>
fb77c505254b6e9c925e23e734463e87574f8f40kess</contextlist>
003f0c9fda6664daf5092a0e42f65ede20098153slive <p>This directive sets the directory from which <code>httpd</code>
003f0c9fda6664daf5092a0e42f65ede20098153slive will serve files. Unless matched by a directive like <directive
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd module="mod_alias">Alias</directive>, the server appends the
2aa51ed61adb484602e94de3d2214ec267aecedbigalic path from the requested URL to the document root to make the
2aa51ed61adb484602e94de3d2214ec267aecedbigalic path to the document. Example:</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd </example>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>then an access to
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen <code>http://www.my.host.com/index.html</code> refers to
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <code>/usr/web/index.html</code>. If the <var>directory-path</var> is
fb77c505254b6e9c925e23e734463e87574f8f40kess not absolute then it is assumed to be relative to the <directive
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>The <directive>DocumentRoot</directive> should be specified without
b06660a3ed3d885e15d99c0209a46c4657df33fbrbowen a trailing slash.</p>
030108b1816bcda3d925df65357feabdce83bc94slive<seealso><a href="/urlmapping.html">Mapping URLs to Filesystem
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</directivesynopsis>
f03f2609a2fc7a0d920842390738080bc0e1304bhumbedooh<directivesynopsis>
f03f2609a2fc7a0d920842390738080bc0e1304bhumbedooh<description>Use memory-mapping to read files during delivery</description>
fb77c505254b6e9c925e23e734463e87574f8f40kess<contextlist><context>server config</context><context>virtual host</context>
fb77c505254b6e9c925e23e734463e87574f8f40kess<context>directory</context><context>.htaccess</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive controls whether the <code>httpd</code> may use
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive memory-mapping if it needs to read the contents of a file during
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive delivery. By default, when the handling of a request requires
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive access to the data within a file -- for example, when delivering a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive server-parsed file using <module>mod_include</module> -- Apache
2aa51ed61adb484602e94de3d2214ec267aecedbigalic memory-maps the file if the OS supports it.</p>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <p>This memory-mapping sometimes yields a performance improvement.
2aa51ed61adb484602e94de3d2214ec267aecedbigalic But in some environments, it is better to disable the memory-mapping
2aa51ed61adb484602e94de3d2214ec267aecedbigalic to prevent operational problems:</p>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <li>On some multiprocessor systems, memory-mapping can reduce the
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <li>With an NFS-mounted <directive module="core">DocumentRoot</directive>,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the <code>httpd</code> may crash due to a segmentation fault if a file
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive is deleted or truncated while the <code>httpd</code> has it
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive memory-mapped.</li>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>For server configurations that are vulnerable to these problems,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive you should disable memory-mapping of delivered files by specifying:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive EnableMMAP Off
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess </example>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess <p>For NFS mounted files, this feature may be disabled explicitly for
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the offending files by specifying:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <Directory "/path-to-nfs-files">
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive EnableMMAP Off
2aa51ed61adb484602e94de3d2214ec267aecedbigalic </Directory>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess<description>Use the kernel sendfile support to deliver files to the client</description>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess<contextlist><context>server config</context><context>virtual host</context>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess<context>directory</context><context>.htaccess</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
4e10c61d7f924071cad435df940a8f325015b2d3rbowen<compatibility>Available in version 2.0.44 and later</compatibility>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive controls whether <code>httpd</code> may use the sendfile
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive support from the kernel to transmit file contents to the client.
2aa51ed61adb484602e94de3d2214ec267aecedbigalic By default, when the handling of a request requires no access
2aa51ed61adb484602e94de3d2214ec267aecedbigalic to the data within a file -- for example, when delivering a
2aa51ed61adb484602e94de3d2214ec267aecedbigalic static file -- Apache uses sendfile to deliver the file contents
2aa51ed61adb484602e94de3d2214ec267aecedbigalic without ever reading the file if the OS supports it.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This sendfile mechanism avoids seperate read and send operations,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive and buffer allocations. But on some platforms or within some
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive filesystems, it is better to disable this feature to avoid
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive operational problems:</p>
fb77c505254b6e9c925e23e734463e87574f8f40kess <li>Some platforms may have broken sendfile support that the build
fb77c505254b6e9c925e23e734463e87574f8f40kess system did not detect, especially if the binaries were built on
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive another box and moved to such a machine with broken sendfile
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive support.</li>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <li>On Linux the use of sendfile triggers TCP-checksum
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive offloading bugs on certain networking cards when using IPv6.</li>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess module="core">DocumentRoot</directive> (e.g., NFS or SMB),
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the kernel may be unable to serve the network file through
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive its own cache.</li>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>For server configurations that are vulnerable to these problems,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive you should disable this feature by specifying:</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd EnableSendfile Off
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>For NFS or SMB mounted files, this feature may be disabled explicitly
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive for the offending files by specifying:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <Directory "/path-to-nfs-files">
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor EnableSendfile Off
fa1c7ce09927decc1eecd1e9a35cc5331078a052covener </Directory>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd </example>
f03f2609a2fc7a0d920842390738080bc0e1304bhumbedooh</directivesynopsis>
f03f2609a2fc7a0d920842390738080bc0e1304bhumbedooh<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>What the server will return to the client
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivein case of an error</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax>ErrorDocument <var>error-code</var> <var>document</var></syntax>
fa1c7ce09927decc1eecd1e9a35cc5331078a052covener<contextlist><context>server config</context><context>virtual host</context>
fa1c7ce09927decc1eecd1e9a35cc5331078a052covener<context>directory</context><context>.htaccess</context>
fa1c7ce09927decc1eecd1e9a35cc5331078a052covener</contextlist>
fa1c7ce09927decc1eecd1e9a35cc5331078a052covener<compatibility>Quoting syntax for text messages is different in Apache
fa1c7ce09927decc1eecd1e9a35cc5331078a052covener2.0</compatibility>
fa1c7ce09927decc1eecd1e9a35cc5331078a052covener <p>In the event of a problem or error, Apache can be configured
fa1c7ce09927decc1eecd1e9a35cc5331078a052covener to do one of four things,</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <li>redirect to a local <var>URL-path</var> to handle the
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <li>redirect to an external <var>URL</var> to handle the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The first option is the default, while options 2-4 are
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive configured using the <directive>ErrorDocument</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directive, which is followed by the HTTP response code and a URL
003f0c9fda6664daf5092a0e42f65ede20098153slive or a message. Apache will sometimes offer additional information
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>URLs can begin with a slash (/) for local URLs, or be a full
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive URL which the client can resolve. Alternatively, a message can
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive be provided to be displayed by the browser. Examples:</p>
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd ErrorDocument 500 http://foo.example.com/cgi-bin/tester<br />
fb77c505254b6e9c925e23e734463e87574f8f40kess ErrorDocument 403 "Sorry can't allow you access today"
fb77c505254b6e9c925e23e734463e87574f8f40kess </example>
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh <p>Additionally, the special value <code>default</code> can be used
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd to specify Apache's simple hardcoded message. While not required
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive under normal circumstances, <code>default</code> will restore
ffe8ed2cd88be2c415ddef11f50394c52df9190ctrawick Apache's simple hardcoded message for configurations that would
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor otherwise inherit an existing <directive>ErrorDocument</directive>.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive ErrorDocument 404 default<br />
1b01d1ee11c612226cb3141eed4581dc179266c1rbowen </Directory>
6b15044d54a096e6323ff1540f1a491e8de7622dsf <p>Note that when you specify an <directive>ErrorDocument</directive>
6b15044d54a096e6323ff1540f1a491e8de7622dsf that points to a remote URL (ie. anything with a method such as
6b15044d54a096e6323ff1540f1a491e8de7622dsf <code>http</code> in front of it), Apache will send a redirect to the
6b15044d54a096e6323ff1540f1a491e8de7622dsf client to tell it where to find the document, even if the
6b15044d54a096e6323ff1540f1a491e8de7622dsf document ends up being on the same server. This has several
6b15044d54a096e6323ff1540f1a491e8de7622dsf implications, the most important being that the client will not
6b15044d54a096e6323ff1540f1a491e8de7622dsf receive the original error status code, but instead will
6b15044d54a096e6323ff1540f1a491e8de7622dsf receive a redirect status code. This in turn can confuse web
6b15044d54a096e6323ff1540f1a491e8de7622dsf robots and other clients which try to determine if a URL is
6b15044d54a096e6323ff1540f1a491e8de7622dsf valid using the status code. In addition, if you use a remote
6b15044d54a096e6323ff1540f1a491e8de7622dsf URL in an <code>ErrorDocument 401</code>, the client will not
6b15044d54a096e6323ff1540f1a491e8de7622dsf know to prompt the user for a password since it will not
6b15044d54a096e6323ff1540f1a491e8de7622dsf receive the 401 status code. Therefore, <strong>if you use an
6b15044d54a096e6323ff1540f1a491e8de7622dsf <code>ErrorDocument 401</code> directive then it must refer to a local
6b15044d54a096e6323ff1540f1a491e8de7622dsf <p>Microsoft Internet Explorer (MSIE) will by default ignore
6b15044d54a096e6323ff1540f1a491e8de7622dsf server-generated error messages when they are "too small" and substitute
6b15044d54a096e6323ff1540f1a491e8de7622dsf its own "friendly" error messages. The size threshold varies depending on
6b15044d54a096e6323ff1540f1a491e8de7622dsf the type of error, but in general, if you make your error document
2aa51ed61adb484602e94de3d2214ec267aecedbigalic greater than 512 bytes, then MSIE will show the server-generated
2aa51ed61adb484602e94de3d2214ec267aecedbigalic error rather than masking it. More information is available in
c8b79d4b8796531f19dd54bd59d88c3b68338ceahumbedooh Microsoft Knowledgebase article <a
2aa51ed61adb484602e94de3d2214ec267aecedbigalic href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q294807"
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <p>Prior to version 2.0, messages were indicated by prefixing
2aa51ed61adb484602e94de3d2214ec267aecedbigalic them with a single unmatched double quote character.</p>
6b15044d54a096e6323ff1540f1a491e8de7622dsf</directivesynopsis>
6b15044d54a096e6323ff1540f1a491e8de7622dsf<directivesynopsis>
6b15044d54a096e6323ff1540f1a491e8de7622dsf<description>Location where the server will log errors</description>
6b15044d54a096e6323ff1540f1a491e8de7622dsf<syntax> ErrorLog <var>file-path</var>|syslog[:<var>facility</var>]</syntax>
6b15044d54a096e6323ff1540f1a491e8de7622dsf<default>ErrorLog logs/error_log (Unix) ErrorLog logs/error.log (Windows and OS/2)</default>
6b15044d54a096e6323ff1540f1a491e8de7622dsf<contextlist><context>server config</context><context>virtual host</context>
6b15044d54a096e6323ff1540f1a491e8de7622dsf</contextlist>
6b15044d54a096e6323ff1540f1a491e8de7622dsf <p>The <directive>ErrorLog</directive> directive sets the name of
6b15044d54a096e6323ff1540f1a491e8de7622dsf the file to which the server will log any errors it encounters. If
6b15044d54a096e6323ff1540f1a491e8de7622dsf the <var>file-path</var> is not absolute then it is assumed to be
6b15044d54a096e6323ff1540f1a491e8de7622dsf relative to the <directive module="core">ServerRoot</directive>.</p>
6b15044d54a096e6323ff1540f1a491e8de7622dsf </example>
6b15044d54a096e6323ff1540f1a491e8de7622dsf begins with a pipe (|) then it is assumed to be a command to spawn
6b15044d54a096e6323ff1540f1a491e8de7622dsf to handle the error log.</p>
6b15044d54a096e6323ff1540f1a491e8de7622dsf </example>
6b15044d54a096e6323ff1540f1a491e8de7622dsf <p>Using <code>syslog</code> instead of a filename enables logging
6b15044d54a096e6323ff1540f1a491e8de7622dsf via syslogd(8) if the system supports it. The default is to use
6b15044d54a096e6323ff1540f1a491e8de7622dsf syslog facility <code>local7</code>, but you can override this by
6b15044d54a096e6323ff1540f1a491e8de7622dsf using the <code>syslog:<var>facility</var></code> syntax where
6b15044d54a096e6323ff1540f1a491e8de7622dsf <var>facility</var> can be one of the names usually documented in
2aa51ed61adb484602e94de3d2214ec267aecedbigalic syslog(1).</p>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic ErrorLog syslog:user
2aa51ed61adb484602e94de3d2214ec267aecedbigalic href="/misc/security_tips.html#serverroot">security tips</a>
e32a6a51d27e311db1e1d5920ac7bd0de33823cfhumbedooh document for details on why your security could be compromised
2aa51ed61adb484602e94de3d2214ec267aecedbigalic if the directory where logfiles are stored is writable by
2aa51ed61adb484602e94de3d2214ec267aecedbigalic anyone other than the user that starts the server.</p>
6b15044d54a096e6323ff1540f1a491e8de7622dsf <p>When entering a file path on non-Unix platforms, care should be taken
6b15044d54a096e6323ff1540f1a491e8de7622dsf to make sure that only forward slashed are used even though the platform
6b15044d54a096e6323ff1540f1a491e8de7622dsf may allow the use of back slashes. In general it is a good idea to always
6b15044d54a096e6323ff1540f1a491e8de7622dsf use forward slashes throughout the configuration files.</p>
6b15044d54a096e6323ff1540f1a491e8de7622dsf<seealso><directive module="core">LogLevel</directive></seealso>
6b15044d54a096e6323ff1540f1a491e8de7622dsf<seealso><a href="/logs.html">Apache Log Files</a></seealso>
6b15044d54a096e6323ff1540f1a491e8de7622dsf</directivesynopsis>
6b15044d54a096e6323ff1540f1a491e8de7622dsf<directivesynopsis>
6b15044d54a096e6323ff1540f1a491e8de7622dsf<description>File attributes used to create the ETag
6b15044d54a096e6323ff1540f1a491e8de7622dsfHTTP response header</description>
6b15044d54a096e6323ff1540f1a491e8de7622dsf<contextlist><context>server config</context><context>virtual host</context>
6b15044d54a096e6323ff1540f1a491e8de7622dsf</contextlist>
fb77c505254b6e9c925e23e734463e87574f8f40kess The <directive>FileETag</directive> directive configures the file
af18698b10b429b270551ca3a5d51a75e1c9db22brianp attributes that are used to create the <code>ETag</code> (entity
af18698b10b429b270551ca3a5d51a75e1c9db22brianp tag) response header field when the document is based on a file.
af18698b10b429b270551ca3a5d51a75e1c9db22brianp (The <code>ETag</code> value is used in cache management to save
003f0c9fda6664daf5092a0e42f65ede20098153slive network bandwidth.) In Apache 1.3.22 and earlier, the
af18698b10b429b270551ca3a5d51a75e1c9db22brianp from the file's inode, size, and last-modified time (mtime). The
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd <directive>FileETag</directive> directive allows you to choose
003f0c9fda6664daf5092a0e42f65ede20098153slive which of these -- if any -- should be used. The recognized keywords are:
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <dd>The file's i-node number will be included in the calculation</dd>
af18698b10b429b270551ca3a5d51a75e1c9db22brianp <dd>The date and time the file was last modified will be included</dd>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <dd>The number of bytes in the file will be included</dd>
af18698b10b429b270551ca3a5d51a75e1c9db22brianp <dd>All available fields will be used. This is equivalent to:
13cbe1d8f52c8097cb581e7eb259693b64d41d10poirier <dd>If a document is file-based, no <code>ETag</code> field will be
13cbe1d8f52c8097cb581e7eb259693b64d41d10poirier included in the response</dd>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>The <code>INode</code>, <code>MTime</code>, and <code>Size</code>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd keywords may be prefixed with either <code>+</code> or <code>-</code>,
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd which allow changes to be made to the default setting inherited
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd from a broader scope. Any keyword appearing without such a prefix
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh immediately and completely cancels the inherited setting.</p>
41ef8b3051855b802104193ee0a587515af60a37wrowe <p>If a directory's configuration includes
41ef8b3051855b802104193ee0a587515af60a37wrowe <code>FileETag INode MTime Size</code>, and a
41ef8b3051855b802104193ee0a587515af60a37wrowe subdirectory's includes <code>FileETag -INode</code>,
2aa51ed61adb484602e94de3d2214ec267aecedbigalic the setting for that subdirectory (which will be inherited by
2aa51ed61adb484602e94de3d2214ec267aecedbigalic any sub-subdirectories that don't override it) will be equivalent to
2aa51ed61adb484602e94de3d2214ec267aecedbigalic</directivesynopsis>
41ef8b3051855b802104193ee0a587515af60a37wrowe<description>Contains directives that apply to matched
41ef8b3051855b802104193ee0a587515af60a37wrowefilenames</description>
41ef8b3051855b802104193ee0a587515af60a37wrowe<syntax><Files <var>filename</var>> ... </Files></syntax>
fb77c505254b6e9c925e23e734463e87574f8f40kess<contextlist><context>server config</context><context>virtual host</context>
41ef8b3051855b802104193ee0a587515af60a37wrowe</contextlist>
9c233808c898095865fcc0a2dc1cf594d0d8faf3sf <p>The <directive type="section">Files</directive> directive
9c233808c898095865fcc0a2dc1cf594d0d8faf3sf limits the scope of the enclosed directives by filename. It is comparable
41ef8b3051855b802104193ee0a587515af60a37wrowe to the <directive module="core" type="section">Directory</directive>
41ef8b3051855b802104193ee0a587515af60a37wrowe and <directive module="core" type="section">Location</directive>
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd directives. It should be matched with a <code></Files></code>
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd directive. The directives given within this section will be applied to
41ef8b3051855b802104193ee0a587515af60a37wrowe any object with a basename (last component of filename) matching the
41ef8b3051855b802104193ee0a587515af60a37wrowe specified filename. <directive type="section">Files</directive>
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen sections are processed in the order they appear in the
41ef8b3051855b802104193ee0a587515af60a37wrowe configuration file, after the <directive module="core"
9b5e2c5e769dc678a1aca06df75c32022b2f1492trawick <code>.htaccess</code> files are read, but before <directive
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess type="section" module="core">Location</directive> sections. Note
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess that <directive type="section">Files</directive> can be nested
41ef8b3051855b802104193ee0a587515af60a37wrowe module="core">Directory</directive> sections to restrict the
41ef8b3051855b802104193ee0a587515af60a37wrowe portion of the filesystem they apply to.</p>
41ef8b3051855b802104193ee0a587515af60a37wrowe <p>The <var>filename</var> argument should include a filename, or
9fb925624300c864fe3969a264e52aa83f3c2dd0slive a wild-card string, where <code>?</code> matches any single character,
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess and <code>*</code> matches any sequences of characters. Extended regular
78f4d313fd5edf76dc5cfb8725e082a08cd29740jwoolley expressions can also be used, with the addition of the
9fb925624300c864fe3969a264e52aa83f3c2dd0slive <Files ~ "\.(gif|jpe?g|png)$">
9c233808c898095865fcc0a2dc1cf594d0d8faf3sf </example>
9fb925624300c864fe3969a264e52aa83f3c2dd0slive <p>would match most common Internet graphics formats. <directive
41ef8b3051855b802104193ee0a587515af60a37wrowe module="core" type="section">FilesMatch</directive> is preferred,
41ef8b3051855b802104193ee0a587515af60a37wrowe however.</p>
41ef8b3051855b802104193ee0a587515af60a37wrowe module="core">Directory</directive> and <directive type="section"
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh module="core">Location</directive> sections, <directive
41ef8b3051855b802104193ee0a587515af60a37wrowe type="section">Files</directive> sections can be used inside
9c233808c898095865fcc0a2dc1cf594d0d8faf3sf <code>.htaccess</code> files. This allows users to control access to
9fb925624300c864fe3969a264e52aa83f3c2dd0slive their own files, at a file-by-file level.</p>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<seealso><a href="/sections.html">How <Directory>, <Location>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic and <Files> sections work</a> for an explanation of how these
2aa51ed61adb484602e94de3d2214ec267aecedbigalic different sections are combined when a request is received</seealso>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic</directivesynopsis>
832853bb93c1831daf24e4727c5ca0e1b1786e83lars<description>Contains directives that apply to regular-expression matched
832853bb93c1831daf24e4727c5ca0e1b1786e83larsfilenames</description>
832853bb93c1831daf24e4727c5ca0e1b1786e83lars<syntax><FilesMatch <var>regex</var>> ... </FilesMatch></syntax>
af18698b10b429b270551ca3a5d51a75e1c9db22brianp<contextlist><context>server config</context><context>virtual host</context>
af18698b10b429b270551ca3a5d51a75e1c9db22brianp<context>directory</context><context>.htaccess</context>
af18698b10b429b270551ca3a5d51a75e1c9db22brianp</contextlist>
79c754eb51681c3389cd966753e902c429f78939trawick <p>The <directive type="section">FilesMatch</directive> directive
79c754eb51681c3389cd966753e902c429f78939trawick limits the scope of the enclosed directives by filename, just as the
79c754eb51681c3389cd966753e902c429f78939trawick <directive module="core" type="section">Files</directive> directive
79c754eb51681c3389cd966753e902c429f78939trawick does. However, it accepts a regular expression. For example:</p>
79c754eb51681c3389cd966753e902c429f78939trawick <FilesMatch "\.(gif|jpe?g|png)$">
79c754eb51681c3389cd966753e902c429f78939trawick <p>would match most common Internet graphics formats.</p>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<seealso><a href="/sections.html">How <Directory>, <Location>
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh and <Files> sections work</a> for an explanation of how these
2aa51ed61adb484602e94de3d2214ec267aecedbigalic different sections are combined when a request is received</seealso>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic</directivesynopsis>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<directivesynopsis>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<description>Forces all matching files to be served with the specified
2aa51ed61adb484602e94de3d2214ec267aecedbigalicMIME content-type</description>
e2c56835b9788101b569d70661151ba7bb0ea2d6humbedooh<contextlist><context>directory</context><context>.htaccess</context>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic</contextlist>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<compatibility>Moved to the core in Apache 2.0</compatibility>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <p>When placed into an <code>.htaccess</code> file or a
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <directive type="section" module="core">Directory</directive>, or
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <directive type="section" module="core">Location</directive> or
79c754eb51681c3389cd966753e902c429f78939trawick <directive type="section" module="core">Files</directive>
79c754eb51681c3389cd966753e902c429f78939trawick section, this directive forces all matching files to be served
79c754eb51681c3389cd966753e902c429f78939trawick with the content type identification given by
79c754eb51681c3389cd966753e902c429f78939trawick <var>MIME-type</var>. For example, if you had a directory full of
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive GIF files, but did not want to label them all with <code>.gif</code>,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive you might want to use:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Note that unlike <directive module="core">DefaultType</directive>,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive this directive overrides all mime-type associations, including
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive filename extensions, that might identify the media type.</p>
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen <p>You can override any <directive>ForceType</directive> setting
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <Location /images><br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </Location><br />
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd # but normal mime-type associations here:<br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive ForceType None<br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </Location>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
69fba5b8aa0b0dc408f649cfdaab064ce120b05bslive<directivesynopsis>
69fba5b8aa0b0dc408f649cfdaab064ce120b05bslive<description>Enables DNS lookups on client IP addresses</description>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<contextlist><context>server config</context><context>virtual host</context>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <p>This directive enables DNS lookups so that host names can be
2aa51ed61adb484602e94de3d2214ec267aecedbigalic logged (and passed to CGIs/SSIs in <code>REMOTE_HOST</code>).
2aa51ed61adb484602e94de3d2214ec267aecedbigalic The value <code>Double</code> refers to doing double-reverse
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive DNS lookup. That is, after a reverse lookup is performed, a forward
f7fe99050600166042c04b8e595fb75499eed7f0geoff lookup is then performed on that result. At least one of the ip
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen addresses in the forward lookup must match the original
f7fe99050600166042c04b8e595fb75499eed7f0geoff address. (In "tcpwrappers" terminology this is called
f7fe99050600166042c04b8e595fb75499eed7f0geoff <p>Regardless of the setting, when <module>mod_authz_host</module> is
2aa51ed61adb484602e94de3d2214ec267aecedbigalic used for controlling access by hostname, a double reverse lookup
2aa51ed61adb484602e94de3d2214ec267aecedbigalic will be performed. This is necessary for security. Note that the
2aa51ed61adb484602e94de3d2214ec267aecedbigalic result of this double-reverse isn't generally available unless you
2aa51ed61adb484602e94de3d2214ec267aecedbigalic set <code>HostnameLookups Double</code>. For example, if only
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <code>HostnameLookups On</code> and a request is made to an object
2aa51ed61adb484602e94de3d2214ec267aecedbigalic that is protected by hostname restrictions, regardless of whether
2aa51ed61adb484602e94de3d2214ec267aecedbigalic the double-reverse fails or not, CGIs will still be passed the
f7fe99050600166042c04b8e595fb75499eed7f0geoff single-reverse result in <code>REMOTE_HOST</code>.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The default is <code>Off</code> in order to save the network
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen traffic for those sites that don't truly need the reverse
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive lookups done. It is also better for the end users because they
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive don't have to suffer the extra latency that a lookup entails.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Heavily loaded sites should leave this directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>Off</code>, since DNS lookups can take considerable
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive amounts of time. The utility <a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive href="/programs/logresolve.html">logresolve</a>, compiled by default
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive to the <code>bin</code> subdirectory of your installation directory, can
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive be used to look up host names from logged IP addresses offline.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
fb77c505254b6e9c925e23e734463e87574f8f40kess<description>Encloses directives that will be processed only
fb77c505254b6e9c925e23e734463e87574f8f40kessif a test is true at startup</description>
fb77c505254b6e9c925e23e734463e87574f8f40kess<syntax><IfDefine [!]<var>parameter-name</var>> ...
4f854c24127e28f7ad72ce9a39d4448aaf910fc1slive </IfDefine></syntax>
4f854c24127e28f7ad72ce9a39d4448aaf910fc1slive<contextlist><context>server config</context><context>virtual host</context>
4f854c24127e28f7ad72ce9a39d4448aaf910fc1slive<context>directory</context><context>.htaccess</context>
9b5e2c5e769dc678a1aca06df75c32022b2f1492trawick</contextlist>
e32a6a51d27e311db1e1d5920ac7bd0de33823cfhumbedooh <p>The <code><IfDefine <var>test</var>>...</IfDefine>
69fba5b8aa0b0dc408f649cfdaab064ce120b05bslive </code> section is used to mark directives that are conditional. The
69fba5b8aa0b0dc408f649cfdaab064ce120b05bslive directives within an <directive type="section">IfDefine</directive>
69fba5b8aa0b0dc408f649cfdaab064ce120b05bslive section are only processed if the <var>test</var> is true. If <var>
69fba5b8aa0b0dc408f649cfdaab064ce120b05bslive test</var> is false, everything between the start and end markers is
69fba5b8aa0b0dc408f649cfdaab064ce120b05bslive ignored.</p>
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor <p>The <var>test</var> in the <directive type="section"
b5d3d68a9f683722eac7a3ca507c3e571908dfc0rbowen >IfDefine</directive> section directive can be one of two forms:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>In the former case, the directives between the start and end
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive markers are only processed if the parameter named
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <var>parameter-name</var> is defined. The second format reverses
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the test, and only processes the directives if
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <var>parameter-name</var> is <strong>not</strong> defined.</p>
4a13940dc2990df0a798718d3a3f9cf1566c2217bjh <p>The <var>parameter-name</var> argument is a define as given on
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the <code>httpd</code> command line via <code>-D<var>parameter-</var>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p><directive type="section">IfDefine</directive> sections are
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive nest-able, which can be used to implement simple
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive multiple-parameter tests. Example:</p>
fb109b84906e3ee61680aa289953c2f9e859354erbowen httpd -DReverseProxy ...<br />
fb109b84906e3ee61680aa289953c2f9e859354erbowen <IfDefine ReverseProxy><br />
960188481b7025ac8ef7221b67af83dd27e46cd0rjung LoadModule rewrite_module modules/mod_rewrite.so<br />
fb109b84906e3ee61680aa289953c2f9e859354erbowen </IfDefine>
960188481b7025ac8ef7221b67af83dd27e46cd0rjung</directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<description>Encloses directives that are processed conditional on the
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cndpresence or absence of a specific module</description>
5155e92c6100b47513159eee1b2b9914ab204a5acovener<syntax><IfModule [!]<var>module-name</var>> ...
5155e92c6100b47513159eee1b2b9914ab204a5acovener </IfModule></syntax>
5155e92c6100b47513159eee1b2b9914ab204a5acovener<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>directory</context><context>.htaccess</context>
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <code><IfModule <var>test</var>>...</IfModule></code>
9b5e2c5e769dc678a1aca06df75c32022b2f1492trawick section is used to mark directives that are conditional on the presence of
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive a specific module. The directives within an <directive type="section"
2bac697634d965d9d9a921a99a68b2c454c8a95dbnicholes >IfModule</directive> section are only processed if the <var>test</var>
2bac697634d965d9d9a921a99a68b2c454c8a95dbnicholes is true. If <var>test</var> is false, everything between the start and
d950cf9262224a223e2ff5c51393708071e14b94covener end markers is ignored.</p>
2bac697634d965d9d9a921a99a68b2c454c8a95dbnicholes <p>The <var>test</var> in the <directive type="section"
2bac697634d965d9d9a921a99a68b2c454c8a95dbnicholes >IfModule</directive> section directive can be one of two forms:</p>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf <p>In the former case, the directives between the start and end
2851546ce44280e54301016a7e92b00a87745509sf markers are only processed if the module named <var>module
e302f38fd646764ce1a1e1c578d794aef514a9e5sf name</var> is included in Apache -- either compiled in or
e302f38fd646764ce1a1e1c578d794aef514a9e5sf >LoadModule</directive>. The second format reverses the test,
e302f38fd646764ce1a1e1c578d794aef514a9e5sf and only processes the directives if <var>module name</var> is
e302f38fd646764ce1a1e1c578d794aef514a9e5sf <p>The <var>module name</var> argument is the file name of the
e302f38fd646764ce1a1e1c578d794aef514a9e5sf module, at the time it was compiled. For example,
e302f38fd646764ce1a1e1c578d794aef514a9e5sf <code>mod_rewrite.c</code>. If a module consists of several
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh source files, use the name of the file containing the string
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <p><directive type="section">IfModule</directive> sections are
e302f38fd646764ce1a1e1c578d794aef514a9e5sf nest-able, which can be used to implement simple multiple-module
e302f38fd646764ce1a1e1c578d794aef514a9e5sf tests.</p>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf <note>This section should only be used if you need to have one
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen configuration file that works whether or not a specific module
e302f38fd646764ce1a1e1c578d794aef514a9e5sf is available. In normal operation, directives need not be
e302f38fd646764ce1a1e1c578d794aef514a9e5sf sections.</note>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf</directivesynopsis>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<directivesynopsis>
e32a6a51d27e311db1e1d5920ac7bd0de33823cfhumbedooh<description>Includes other configuration files from within
e302f38fd646764ce1a1e1c578d794aef514a9e5sfthe server configuration files</description>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<syntax>Include <var>file-path</var>|<var>directory-path</var></syntax>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<contextlist><context>server config</context><context>virtual host</context>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf</contextlist>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<compatibility>Wildcard matching available in 2.0.41 and later</compatibility>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf <p>This directive allows inclusion of other configuration files
e302f38fd646764ce1a1e1c578d794aef514a9e5sf from within the server configuration files.</p>
b5c4b00201fdc3ed11c6cc05cf3f9a7912ac0cfbsf <p>Shell-style (<code>fnmatch()</code>) wildcard characters can be used to
e302f38fd646764ce1a1e1c578d794aef514a9e5sf include several files at once, in alphabetical order. In
b5c4b00201fdc3ed11c6cc05cf3f9a7912ac0cfbsf addition, if <directive>Include</directive> points to a directory,
b5c4b00201fdc3ed11c6cc05cf3f9a7912ac0cfbsf rather than a file, Apache will read all files in that directory
e32a6a51d27e311db1e1d5920ac7bd0de33823cfhumbedooh and any subdirectory. But including entire directories is not
e302f38fd646764ce1a1e1c578d794aef514a9e5sf recommended, because it is easy to accidentally leave temporary
b5c4b00201fdc3ed11c6cc05cf3f9a7912ac0cfbsf files in a directory that can cause <code>httpd</code> to
b5c4b00201fdc3ed11c6cc05cf3f9a7912ac0cfbsf <p>The file path specified may be an absolute path, or may be relative
b5c4b00201fdc3ed11c6cc05cf3f9a7912ac0cfbsf to the <directive module="core">ServerRoot</directive> directory.</p>
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen <p>Running <code>apachectl configtest</code> will give you a list
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen of the files that are being processed during the configuration
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen root@host# apachectl configtest<br />
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen Processing config file: /usr/local/apache2/conf/ssl.conf<br />
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen Processing config file: /usr/local/apache2/conf/vhosts/vhost1.conf<br />
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen Processing config file: /usr/local/apache2/conf/vhosts/vhost2.conf<br />
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<seealso><a href="/programs/apachectl.html">apachectl</a></seealso>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf</directivesynopsis>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<directivesynopsis>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<description>Enables HTTP persistent connections</description>
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen<contextlist><context>server config</context><context>virtual host</context>
2d391792b33e3c27e070739f74d74989c77fea8eminfrin</contextlist>
2d391792b33e3c27e070739f74d74989c77fea8eminfrin <p>The Keep-Alive extension to HTTP/1.0 and the persistent
2a781ea98a32c069ae57a89566ee9628e19a2ec2minfrin connection feature of HTTP/1.1 provide long-lived HTTP sessions
2a781ea98a32c069ae57a89566ee9628e19a2ec2minfrin which allow multiple requests to be sent over the same TCP
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen connection. In some cases this has been shown to result in an
e302f38fd646764ce1a1e1c578d794aef514a9e5sf almost 50% speedup in latency times for HTML documents with
e302f38fd646764ce1a1e1c578d794aef514a9e5sf many images. To enable Keep-Alive connections, set
4497075b5e08b0c8ee89425a1758258ae80550fcsf <p>For HTTP/1.0 clients, Keep-Alive connections will only be
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen used if they are specifically requested by a client. In
e302f38fd646764ce1a1e1c578d794aef514a9e5sf addition, a Keep-Alive connection with an HTTP/1.0 client can
e302f38fd646764ce1a1e1c578d794aef514a9e5sf only be used when the length of the content is known in
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen advance. This implies that dynamic content such as CGI output,
e302f38fd646764ce1a1e1c578d794aef514a9e5sf SSI pages, and server-generated directory listings will
e302f38fd646764ce1a1e1c578d794aef514a9e5sf generally not use Keep-Alive connections to HTTP/1.0 clients.
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen For HTTP/1.1 clients, persistent connections are the default
0b5f11662dee7135ff8dd04311a4ee6df7fe2b1crbowen unless otherwise specified. If the client requests it, chunked
e302f38fd646764ce1a1e1c578d794aef514a9e5sf encoding will be used in order to send content of unknown
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen length over persistent connections.</p>
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen<seealso><directive module="core">MaxKeepAliveRequests</directive></seealso>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf</directivesynopsis>
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen<directivesynopsis>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<description>Amount of time the server will wait for subsequent
b89fea36d9c12cec3344576824f4e6798da90ad4rbowenrequests on a persistent connection</description>
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen<contextlist><context>server config</context><context>virtual host</context>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf</contextlist>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf <p>The number of seconds Apache will wait for a subsequent
e302f38fd646764ce1a1e1c578d794aef514a9e5sf request before closing the connection. Once a request has been
e302f38fd646764ce1a1e1c578d794aef514a9e5sf received, the timeout value specified by the
e302f38fd646764ce1a1e1c578d794aef514a9e5sf <directive module="core">Timeout</directive> directive applies.</p>
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen <p>Setting <directive>KeepAliveTimeout</directive> to a high value
0b5f11662dee7135ff8dd04311a4ee6df7fe2b1crbowen may cause performance problems in heavily loaded servers. The
4497075b5e08b0c8ee89425a1758258ae80550fcsf higher the timeout, the more server processes will be kept
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen occupied waiting on connections with idle clients.</p>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf</directivesynopsis>
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen<description>Restrict enclosed access controls to only certain HTTP
b08558bf6a64f9501ad3eca34eaf4d978bd928cfsfmethods</description>
b08558bf6a64f9501ad3eca34eaf4d978bd928cfsf<syntax><Limit <var>method</var> [<var>method</var>] ... > ...
b08558bf6a64f9501ad3eca34eaf4d978bd928cfsf </Limit></syntax>
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen<contextlist><context>server config</context><context>virtual host</context>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf</contextlist>
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen <p>Access controls are normally effective for
e302f38fd646764ce1a1e1c578d794aef514a9e5sf <strong>all</strong> access methods, and this is the usual
e302f38fd646764ce1a1e1c578d794aef514a9e5sf desired behavior. <strong>In the general case, access control
e302f38fd646764ce1a1e1c578d794aef514a9e5sf directives should not be placed within a
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen <directive type="section">Limit</directive> section.</strong></p>
9228509ac5da8374df4a5d50b7da139e7b31f8a3sf <p>The purpose of the <directive type="section">Limit</directive>
9228509ac5da8374df4a5d50b7da139e7b31f8a3sf directive is to restrict the effect of the access controls to the
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen nominated HTTP methods. For all other methods, the access
9228509ac5da8374df4a5d50b7da139e7b31f8a3sf restrictions that are enclosed in the <directive
9228509ac5da8374df4a5d50b7da139e7b31f8a3sf type="section">Limit</directive> bracket <strong>will have no
9228509ac5da8374df4a5d50b7da139e7b31f8a3sf effect</strong>. The following example applies the access control
9228509ac5da8374df4a5d50b7da139e7b31f8a3sf only to the methods <code>POST</code>, <code>PUT</code>, and
e302f38fd646764ce1a1e1c578d794aef514a9e5sf <code>DELETE</code>, leaving all other methods unprotected:</p>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf <Limit POST PUT DELETE><br />
e302f38fd646764ce1a1e1c578d794aef514a9e5sf Require valid-user<br />
e302f38fd646764ce1a1e1c578d794aef514a9e5sf </Limit>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf </example>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf <p>The method names listed can be one or more of: <code>GET</code>,
e302f38fd646764ce1a1e1c578d794aef514a9e5sf <code>POST</code>, <code>PUT</code>, <code>DELETE</code>,
ce4dc40a4e87991087488f70d96d3447d7557294sf <code>PATCH</code>, <code>PROPFIND</code>, <code>PROPPATCH</code>,
e302f38fd646764ce1a1e1c578d794aef514a9e5sf <code>MKCOL</code>, <code>COPY</code>, <code>MOVE</code>,
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh <code>LOCK</code>, and <code>UNLOCK</code>. <strong>The method name is
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh case-sensitive.</strong> If <code>GET</code> is used it will also
2aa51ed61adb484602e94de3d2214ec267aecedbigalic restrict <code>HEAD</code> requests. The <code>TRACE</code> method
2aa51ed61adb484602e94de3d2214ec267aecedbigalic cannot be limited.</p>
abdaaa23d72ef7e7ff91eab9c5581d40130680c1rbowen module="core">LimitExcept</directive> section should always be
abdaaa23d72ef7e7ff91eab9c5581d40130680c1rbowen module="core">Limit</directive> section when restricting access,
abdaaa23d72ef7e7ff91eab9c5581d40130680c1rbowen module="core">LimitExcept</directive> section provides protection
e32a6a51d27e311db1e1d5920ac7bd0de33823cfhumbedooh against arbitrary methods.</note>
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh</directivesynopsis>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<description>Restrict access controls to all HTTP methods
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedoohexcept the named ones</description>
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh<syntax><LimitExcept <var>method</var> [<var>method</var>] ... > ...
2aa51ed61adb484602e94de3d2214ec267aecedbigalic </LimitExcept></syntax>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<contextlist><context>server config</context><context>virtual host</context>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<context>directory</context><context>.htaccess</context>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic</contextlist>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf a group of access control directives which will then apply to any
e302f38fd646764ce1a1e1c578d794aef514a9e5sf HTTP access method <strong>not</strong> listed in the arguments;
e302f38fd646764ce1a1e1c578d794aef514a9e5sf module="core">Limit</directive> section and can be used to control
a8ee031b2224ce5473826c9d4f603681589245fawrowe both standard and nonstandard/unrecognized methods. See the
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor type="section">Limit</directive> for more details.</p>
a8ee031b2224ce5473826c9d4f603681589245fawrowe <LimitExcept POST GET><br />
a8ee031b2224ce5473826c9d4f603681589245fawrowe Require valid-user<br />
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor </LimitExcept>
a8ee031b2224ce5473826c9d4f603681589245fawrowe</directivesynopsis>
a8ee031b2224ce5473826c9d4f603681589245fawrowe<directivesynopsis>
a8ee031b2224ce5473826c9d4f603681589245fawrowe<description>Determine maximum number of internal redirects and nested
a8ee031b2224ce5473826c9d4f603681589245fawrowesubrequests</description>
34b157732214cedcd129cd9fe7c4290757505d60minfrin<syntax>LimitInternalRecursion <var>number</var> [<var>number</var>]</syntax>
a8ee031b2224ce5473826c9d4f603681589245fawrowe<contextlist><context>server config</context><context>virtual host</context>
a8ee031b2224ce5473826c9d4f603681589245fawrowe</contextlist>
a8ee031b2224ce5473826c9d4f603681589245fawrowe<compatibility>Available in Apache 2.0.47 and later</compatibility>
34b157732214cedcd129cd9fe7c4290757505d60minfrin <p>An internal redirect happens, for example, when using the <directive
34b157732214cedcd129cd9fe7c4290757505d60minfrin module="mod_actions">Action</directive> directive, which internally
34b157732214cedcd129cd9fe7c4290757505d60minfrin redirects the original request to a CGI script. A subrequest is Apache's
34b157732214cedcd129cd9fe7c4290757505d60minfrin mechanism to find out what would happen for some URI if it were requested.
a8ee031b2224ce5473826c9d4f603681589245fawrowe For example, <module>mod_dir</module> uses subrequests to look for the
a8ee031b2224ce5473826c9d4f603681589245fawrowe files listed in the <directive module="mod_dir">DirectoryIndex</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directive.</p>
003f0c9fda6664daf5092a0e42f65ede20098153slive <p><directive>LimitInternalRecursion</directive> prevents the server
a5f060e0c74a44cb8896ae794c08f94f7c9a46a7covener from crashing when entering an infinite loop of internal redirects or
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd subrequests. Such loops are usually caused by misconfigurations.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The directive stores two different limits, which are evaluated on
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive per-request basis. The first <var>number</var> is the maximum number of
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive internal redirects, that may follow each other. The second <var>number</var>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive determines, how deep subrequests may be nested. If you specify only one
fec106c7688e279dfde4403bc3c935fec97c1d62sf <var>number</var>, it will be assigned to both limits.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive LimitInternalRecursion 5
fb77c505254b6e9c925e23e734463e87574f8f40kess</directivesynopsis>
fb77c505254b6e9c925e23e734463e87574f8f40kess<directivesynopsis>
fb77c505254b6e9c925e23e734463e87574f8f40kess<description>Restricts the total size of the HTTP request body sent
fb77c505254b6e9c925e23e734463e87574f8f40kessfrom the client</description>
530eba85dbd41b8a0fa5255d3648d1440199a661slive<contextlist><context>server config</context><context>virtual host</context>
530eba85dbd41b8a0fa5255d3648d1440199a661slive<context>directory</context><context>.htaccess</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive specifies the number of <var>bytes</var> from 0
530eba85dbd41b8a0fa5255d3648d1440199a661slive (meaning unlimited) to 2147483647 (2GB) that are allowed in a
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd request body.</p>
530eba85dbd41b8a0fa5255d3648d1440199a661slive <p>The <directive>LimitRequestBody</directive> directive allows
fb77c505254b6e9c925e23e734463e87574f8f40kess the user to set a limit on the allowed size of an HTTP request
fb77c505254b6e9c925e23e734463e87574f8f40kess message body within the context in which the directive is given
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive (server, per-directory, per-file or per-location). If the client
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd request exceeds that limit, the server will return an error
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd response instead of servicing the request. The size of a normal
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd request message body will vary greatly depending on the nature of
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd the resource and the methods allowed on that resource. CGI scripts
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd typically use the message body for retrieving form information.
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd Implementations of the <code>PUT</code> method will require
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd a value at least as large as any representation that the server
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd wishes to accept for that resource.</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>This directive gives the server administrator greater
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive control over abnormal client request behavior, which may be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive useful for avoiding some forms of denial-of-service
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd attacks.</p>
0db981f8fdfb62c5149efa079f0369b73d472d04rpluem <p>If, for example, you are permitting file upload to a particular
0db981f8fdfb62c5149efa079f0369b73d472d04rpluem location, and wish to limit the size of the uploaded file to 100K,
fec106c7688e279dfde4403bc3c935fec97c1d62sf you might use the following directive:</p>
0db981f8fdfb62c5149efa079f0369b73d472d04rpluem LimitRequestBody 102400
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor</directivesynopsis>
a5f060e0c74a44cb8896ae794c08f94f7c9a46a7covener<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Limits the number of HTTP request header fields that
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivewill be accepted from the client</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context></contextlist>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p><var>Number</var> is an integer from 0 (meaning unlimited) to
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive 32767. The default value is defined by the compile-time
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive constant <code>DEFAULT_LIMIT_REQUEST_FIELDS</code> (100 as
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive distributed).</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive>LimitRequestFields</directive> directive allows
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the server administrator to modify the limit on the number of
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive request header fields allowed in an HTTP request. A server needs
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess this value to be larger than the number of fields that a normal
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess client request might include. The number of request header fields
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess used by a client rarely exceeds 20, but this may vary among
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess different client implementations, often depending upon the extent
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess to which a user has configured their browser to support detailed
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess content negotiation. Optional HTTP extensions are often expressed
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive using request header fields.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive gives the server administrator greater
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive control over abnormal client request behavior, which may be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive useful for avoiding some forms of denial-of-service attacks.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive The value should be increased if normal clients see an error
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive response from the server that indicates too many fields were
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive sent in the request.</p>
fb77c505254b6e9c925e23e734463e87574f8f40kess LimitRequestFields 50
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
f03f2609a2fc7a0d920842390738080bc0e1304bhumbedooh<directivesynopsis>
f03f2609a2fc7a0d920842390738080bc0e1304bhumbedooh<description>Limits the size of the HTTP request header allowed from the
f03f2609a2fc7a0d920842390738080bc0e1304bhumbedoohclient</description>
f03f2609a2fc7a0d920842390738080bc0e1304bhumbedooh<syntax>LimitRequestFieldsize <var>bytes</var></syntax>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<contextlist><context>server config</context></contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive specifies the number of <var>bytes</var> from 0
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive to the value of the compile-time constant
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive distributed) that will be allowed in an HTTP request
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive header.</p>
fb77c505254b6e9c925e23e734463e87574f8f40kess <p>The <directive>LimitRequestFieldSize</directive> directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive allows the server administrator to reduce the limit on the allowed
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive size of an HTTP request header field below the normal input buffer
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess size compiled with the server. A server needs this value to be
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess large enough to hold any one header field from a normal client
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess request. The size of a normal request header field will vary
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive greatly among different client implementations, often depending
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive upon the extent to which a user has configured their browser to
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive support detailed content negotiation.</p>
003f0c9fda6664daf5092a0e42f65ede20098153slive <p>This directive gives the server administrator greater
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive control over abnormal client request behavior, which may be
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd useful for avoiding some forms of denial-of-service attacks.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive LimitRequestFieldSize 4094
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess <note>Under normal conditions, the value should not be changed from
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess the default.</note>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</directivesynopsis>
8f5222d1bb4ace11af7add6932362e4c3822e548humbedooh<directivesynopsis>
8f5222d1bb4ace11af7add6932362e4c3822e548humbedooh<description>Limit the size of the HTTP request line that will be accepted
8f5222d1bb4ace11af7add6932362e4c3822e548humbedoohfrom the client</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context></contextlist>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <p>This directive sets the number of <var>bytes</var> from 0 to
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess the value of the compile-time constant
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>DEFAULT_LIMIT_REQUEST_LINE</code> (8190 as distributed)
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive that will be allowed on the HTTP request-line.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive>LimitRequestLine</directive> directive allows
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the server administrator to reduce the limit on the allowed size
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding of a client's HTTP request-line below the normal input buffer size
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding compiled with the server. Since the request-line consists of the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive HTTP method, URI, and protocol version, the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive>LimitRequestLine</directive> directive places a
003f0c9fda6664daf5092a0e42f65ede20098153slive restriction on the length of a request-URI allowed for a request
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen on the server. A server needs this value to be large enough to
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive hold any of its resource names, including any information that
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive might be passed in the query part of a <code>GET</code> request.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive gives the server administrator greater
fb77c505254b6e9c925e23e734463e87574f8f40kess control over abnormal client request behavior, which may be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive useful for avoiding some forms of denial-of-service attacks.</p>
fb77c505254b6e9c925e23e734463e87574f8f40kess LimitRequestLine 4094
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd </example>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <note>Under normal conditions, the value should not be changed from
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding the default.</note>
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding</directivesynopsis>
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding<directivesynopsis>
c97e8972ab1f4dd167e3dc4db87daf91114009fbnd<description>Limits the size of an XML-based request body</description>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<contextlist><context>server config</context><context>virtual host</context>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<context>directory</context><context>.htaccess</context></contextlist>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <p>Limit (in bytes) on maximum size of an XML-based request
2aa51ed61adb484602e94de3d2214ec267aecedbigalic body. A value of <code>0</code> will disable any checking.</p>
439acee10571861c670c438038a62f90a08bf137covener LimitXMLRequestBody 0
439acee10571861c670c438038a62f90a08bf137covener</directivesynopsis>
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener<description>Applies the enclosed directives only to matching
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covenerURLs</description>
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener<syntax><Location
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener <var>URL-path</var>|<var>URL</var>> ... </Location></syntax>
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener<contextlist><context>server config</context><context>virtual host</context>
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener</contextlist>
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener <p>The <directive type="section">Location</directive> directive
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener limits the scope of the enclosed directives by URL. It is similar to the
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener <directive type="section" module="core">Directory</directive>
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener directive, and starts a subsection which is terminated with a
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener <code></Location></code> directive. <directive
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor type="section">Location</directive> sections are processed in the
df5042f69eea159c73cd7b16542d4ca7d879b0b5trawick order they appear in the configuration file, after the <directive
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener type="section" module="core">Directory</directive> sections and
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener <code>.htaccess</code> files are read, and after the <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive type="section" module="core">Files</directive> sections.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p><directive type="section">Location</directive> sections operate
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive completely outside the filesystem. This has several consequences.
fb77c505254b6e9c925e23e734463e87574f8f40kess Most importantly, <directive type="section">Location</directive>
fb77c505254b6e9c925e23e734463e87574f8f40kess directives should not be used to control access to filesystem
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive locations. Since several different URLs may map to the same
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive filesystem location, such access controls may by circumvented.</p>
fb77c505254b6e9c925e23e734463e87574f8f40kess <p>Use <directive type="section">Location</directive> to apply
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess directives to content that lives outside the filesystem. For
9b5e2c5e769dc678a1aca06df75c32022b2f1492trawick content that lives in the filesystem, use <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive type="section" module="core">Directory</directive> and <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive type="section" module="core">Files</directive>. An exception is
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code><Location /></code>, which is an easy way to
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive apply a configuration to the entire server.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>For all origin (non-proxy) requests, the URL to be matched is a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive URL-path of the form <code>/path/</code>. No scheme, hostname,
fb77c505254b6e9c925e23e734463e87574f8f40kess port, or query string may be included. For proxy requests, the
fb77c505254b6e9c925e23e734463e87574f8f40kess URL to be matched is of the form
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>scheme://servername/path</code>, and you must include the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive prefix.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The URL may use wildcards. In a wild-card string, <code>?</code> matches
fb77c505254b6e9c925e23e734463e87574f8f40kess any single character, and <code>*</code> matches any sequences of
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive characters.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Extended regular
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive expressions can also be used, with the addition of the
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd <Location ~ "/(extra|special)/data">
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd </example>
e40b2d66f8592e45981ea1cbdac42db076ea1da6rbowen <p>would match URLs that contained the substring <code>/extra/data</code>
e40b2d66f8592e45981ea1cbdac42db076ea1da6rbowen or <code>/special/data</code>. The directive <directive
e40b2d66f8592e45981ea1cbdac42db076ea1da6rbowen type="section" module="core">LocationMatch</directive> behaves
e40b2d66f8592e45981ea1cbdac42db076ea1da6rbowen identical to the regex version of <directive
750d12c59545dbbac70390988de94f7e901b08f2niq functionality is especially useful when combined with the
750d12c59545dbbac70390988de94f7e901b08f2niq directive. For example, to enable status requests, but allow them
750d12c59545dbbac70390988de94f7e901b08f2niq only from browsers at <code>foo.com</code>, you might use:</p>
750d12c59545dbbac70390988de94f7e901b08f2niq <Location /status><br />
750d12c59545dbbac70390988de94f7e901b08f2niq SetHandler server-status<br />
750d12c59545dbbac70390988de94f7e901b08f2niq Order Deny,Allow<br />
750d12c59545dbbac70390988de94f7e901b08f2niq Deny from all<br />
750d12c59545dbbac70390988de94f7e901b08f2niq </Location>
750d12c59545dbbac70390988de94f7e901b08f2niq </example>
750d12c59545dbbac70390988de94f7e901b08f2niq <p>The slash character has special meaning depending on where in a
6b15044d54a096e6323ff1540f1a491e8de7622dsf URL it appears. People may be used to its behavior in the filesystem
6b15044d54a096e6323ff1540f1a491e8de7622dsf where multiple adjacent slashes are frequently collapsed to a single
6b15044d54a096e6323ff1540f1a491e8de7622dsf slash (<em>i.e.</em>, <code>/home///foo</code> is the same as
6b15044d54a096e6323ff1540f1a491e8de7622dsf <code>/home/foo</code>). In URL-space this is not necessarily true.
6b15044d54a096e6323ff1540f1a491e8de7622dsf The <directive type="section" module="core">LocationMatch</directive>
6b15044d54a096e6323ff1540f1a491e8de7622dsf directive and the regex version of <directive type="section"
1a0ca5f6b566a5eb77d63f466fcf78fb388a4182igalic >Location</directive> require you to explicitly specify multiple
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh slashes if that is your intention.</p>
6b15044d54a096e6323ff1540f1a491e8de7622dsf <p>For example, <code><LocationMatch ^/abc></code> would match
6b15044d54a096e6323ff1540f1a491e8de7622dsf the request URL <code>/abc</code> but not the request URL <code>
6b15044d54a096e6323ff1540f1a491e8de7622dsf >Location</directive> directive behaves similarly when used for
6b15044d54a096e6323ff1540f1a491e8de7622dsf proxy requests. But when (non-regex) <directive type="section"
6b15044d54a096e6323ff1540f1a491e8de7622dsf >Location</directive> is used for non-proxy requests it will
750d12c59545dbbac70390988de94f7e901b08f2niq implicitly match multiple slashes with a single slash. For example,
750d12c59545dbbac70390988de94f7e901b08f2niq if you specify <code><Location /abc/def></code> and the
94aba9caa9b2f7a0e95a55f51264c908b69470e2igalic request is to <code>/abc//def</code> then it will match.</p>
6b15044d54a096e6323ff1540f1a491e8de7622dsf<seealso><a href="/sections.html">How <Directory>, <Location>
750d12c59545dbbac70390988de94f7e901b08f2niq and <Files> sections work</a> for an explanation of how these
750d12c59545dbbac70390988de94f7e901b08f2niq different sections are combined when a request is received</seealso>
750d12c59545dbbac70390988de94f7e901b08f2niq</directivesynopsis>
750d12c59545dbbac70390988de94f7e901b08f2niq<description>Applies the enclosed directives only to regular-expression
750d12c59545dbbac70390988de94f7e901b08f2niqmatching URLs</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax><LocationMatch
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <var>regex</var>> ... </LocationMatch></syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive type="section">LocationMatch</directive> directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive limits the scope of the enclosed directives by URL, in an identical manner
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive to <directive module="core" type="section">Location</directive>. However,
003f0c9fda6664daf5092a0e42f65ede20098153slive it takes a regular expression as an argument instead of a simple
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive string. For example:</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <LocationMatch "/(extra|special)/data">
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd </example>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>would match URLs that contained the substring <code>/extra/data</code>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<seealso><a href="/sections.html">How <Directory>, <Location>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive and <Files> sections work</a> for an explanation of how these
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive different sections are combined when a request is received</seealso>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Controls the verbosity of the ErrorLog</description>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
6e483e0b8aa3fa574288a7452221392a03e2b9a3noodl <p><directive>LogLevel</directive> adjusts the verbosity of the
6e483e0b8aa3fa574288a7452221392a03e2b9a3noodl messages recorded in the error logs (see <directive
6e483e0b8aa3fa574288a7452221392a03e2b9a3noodl module="core">ErrorLog</directive> directive). The following
6e483e0b8aa3fa574288a7452221392a03e2b9a3noodl <var>level</var>s are available, in order of decreasing
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive significance:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <columnspec><column width=".2"/><column width=".3"/><column width=".5"/>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </columnspec>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <td>"getpwuid: couldn't determine user name from uid"</td>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <td>"child process 1234 did not exit, sending another
55d36f9b61520c2374ab463e77e8a62daa416398nd SIGHUP"</td>
55d36f9b61520c2374ab463e77e8a62daa416398nd <td>"httpd: caught SIGBUS, attempting to dump core in
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <td>"Server seems busy, (you may need to increase
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>When a particular level is specified, messages from all
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive other levels of higher significance will be reported as well.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <em>E.g.</em>, when <code>LogLevel info</code> is specified,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive then messages with log levels of <code>notice</code> and
003f0c9fda6664daf5092a0e42f65ede20098153slive recommended.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive LogLevel notice
cf8a8738330694e60bad421fcc8361d80b0e9124minfrin <p>When logging to a regular file messages of the level
cf8a8738330694e60bad421fcc8361d80b0e9124minfrin <code>notice</code> cannot be suppressed and thus are always
cf8a8738330694e60bad421fcc8361d80b0e9124minfrin logged. However, this doesn't apply when logging is done
cf8a8738330694e60bad421fcc8361d80b0e9124minfrin</directivesynopsis>
cf8a8738330694e60bad421fcc8361d80b0e9124minfrin<directivesynopsis>
69d4a64874fd7161f80bb0484341c60857b6fd6esf<description>Number of requests allowed on a persistent
cb43dee5b65f707dfd575fc681ef863d6f6b0385sfconnection</description>
03aa31ad82759363ba1a55589e517b16308ef635minfrin<contextlist><context>server config</context><context>virtual host</context>
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive>MaxKeepAliveRequests</directive> directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive limits the number of requests allowed per connection when
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <directive module="core" >KeepAlive</directive> is on. If it is
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh set to <code>0</code>, unlimited requests will be allowed. We
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh recommend that this setting be kept to a high value for maximum
2aa51ed61adb484602e94de3d2214ec267aecedbigalic server performance.</p>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic MaxKeepAliveRequests 500
2aa51ed61adb484602e94de3d2214ec267aecedbigalic</directivesynopsis>
cf8a8738330694e60bad421fcc8361d80b0e9124minfrin<directivesynopsis>
cb43dee5b65f707dfd575fc681ef863d6f6b0385sf<description>Designates an IP address for name-virtual
031bbbc0d1189b07330e38d0c126820a9ab7795egryzorhosting</description>
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh<syntax>NameVirtualHost <var>addr</var>[:<var>port</var>]</syntax>
cf8a8738330694e60bad421fcc8361d80b0e9124minfrin<contextlist><context>server config</context></contextlist>
03aa31ad82759363ba1a55589e517b16308ef635minfrin <p>The <directive>NameVirtualHost</directive> directive is a
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh required directive if you want to configure <a
03aa31ad82759363ba1a55589e517b16308ef635minfrin <p>Although <var>addr</var> can be hostname it is recommended
03aa31ad82759363ba1a55589e517b16308ef635minfrin NameVirtualHost 111.22.33.44
69d4a64874fd7161f80bb0484341c60857b6fd6esf </example>
69d4a64874fd7161f80bb0484341c60857b6fd6esf <p>With the <directive>NameVirtualHost</directive> directive you
69d4a64874fd7161f80bb0484341c60857b6fd6esf specify the IP address on which the server will receive requests
69d4a64874fd7161f80bb0484341c60857b6fd6esf for the name-based virtual hosts. This will usually be the address
69d4a64874fd7161f80bb0484341c60857b6fd6esf to which your name-based virtual host names resolve. In cases
69d4a64874fd7161f80bb0484341c60857b6fd6esf where a firewall or other proxy receives the requests and forwards
69d4a64874fd7161f80bb0484341c60857b6fd6esf them on a different IP address to the server, you must specify the
69d4a64874fd7161f80bb0484341c60857b6fd6esf IP address of the physical interface on the machine which will be
69d4a64874fd7161f80bb0484341c60857b6fd6esf servicing the requests. If you have multiple name-based hosts on
69d4a64874fd7161f80bb0484341c60857b6fd6esf multiple addresses, repeat the directive for each address.</p>
69d4a64874fd7161f80bb0484341c60857b6fd6esf <p>Note, that the "main server" and any <code>_default_</code> servers
69d4a64874fd7161f80bb0484341c60857b6fd6esf <directive>NameVirtualHost</directive> IP Address (unless for some
69d4a64874fd7161f80bb0484341c60857b6fd6esf reason you specify <directive>NameVirtualHost</directive> but then
03aa31ad82759363ba1a55589e517b16308ef635minfrin don't define any <directive>VirtualHost</directive>s for that
03aa31ad82759363ba1a55589e517b16308ef635minfrin address).</p>
03aa31ad82759363ba1a55589e517b16308ef635minfrin <p>Optionally you can specify a port number on which the
003f0c9fda6664daf5092a0e42f65ede20098153slive NameVirtualHost 111.22.33.44:8080
fb77c505254b6e9c925e23e734463e87574f8f40kess </example>
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele <p>IPv6 addresses must be enclosed in square brackets, as shown
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele in the following example:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive NameVirtualHost [fe80::a00:20ff:fea7:ccea]:8080
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>To receive requests on all interfaces, you can use an argument of
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive NameVirtualHost *
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <note><title>Argument to <directive type="section">VirtualHost</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directive</title>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive exactly match the argument to the <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive NameVirtualHost 1.2.3.4<br />
891df99fdfa41fc8a486568f4d31ddf4a571258adreid <VirtualHost 1.2.3.4><br />
891df99fdfa41fc8a486568f4d31ddf4a571258adreid # ...<br />
59368b594c9b09b59ae58c7de26d2d5ce1c99a29takashi </VirtualHost><br />
be192cefa381d5bae6868034687471754cb43175sf </example>
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick</directivesynopsis>
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick<directivesynopsis>
9f38f3ec3e8087985d108a24ae796962fef83644takashi<description>Configures what features are available in a particular
98f5034c8cbf2ef025b317b3e01acae82e143b11trawickdirectory</description>
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick<syntax>Options
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick [+|-]<var>option</var> [[+|-]<var>option</var>] ...</syntax>
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen<contextlist><context>server config</context><context>virtual host</context>
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick<context>directory</context><context>.htaccess</context>
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick</contextlist>
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick <p>The <directive>Options</directive> directive controls which
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick server features are available in a particular directory.</p>
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick <p><var>option</var> can be set to <code>None</code>, in which
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick case none of the extra features are enabled, or one or more of
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick the following:</p>
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick <dd>All options except for <code>MultiViews</code>. This is the default
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick setting.</dd>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess Execution of CGI scripts using <module>mod_cgi</module>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd is permitted.</dd>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive The server will follow symbolic links in this directory.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Even though the server follows the symlink it does <em>not</em>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive change the pathname used to match against <directive type="section"
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>Note also, that this option <strong>gets ignored</strong> if set
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive inside a <directive type="section" module="core">Location</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive section.</p>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess Server-side includes provided by <module>mod_include</module>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess are permitted.</dd>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic Server-side includes are permitted, but the <code>#exec
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd cmd</code> and <code>#exec cgi</code> are disabled. It is still
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd possible to <code>#include virtual</code> CGI scripts from
6c5c651b0b97607b8c8b4965c1385c67699f217fnd directories.</dd>
6c5c651b0b97607b8c8b4965c1385c67699f217fnd If a URL which maps to a directory is requested, and there
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd is no <directive module="mod_dir">DirectoryIndex</directive>
750d12c59545dbbac70390988de94f7e901b08f2niq (<em>e.g.</em>, <code>index.html</code>) in that directory, then
4bb78e7cdd53f50240cff4ad7a97c7ed36483797slive <module>mod_autoindex</module> will return a formatted listing
4bb78e7cdd53f50240cff4ad7a97c7ed36483797slive of the directory.</dd>
4bb78e7cdd53f50240cff4ad7a97c7ed36483797slive <a href="/content-negotiation.html">Content negotiated</a>
4bb78e7cdd53f50240cff4ad7a97c7ed36483797slive "MultiViews" are allowed using
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd <dd>The server will only follow symbolic links for which the
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd target file or directory is owned by the same user id as the
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd <note><title>Note</title> This option gets ignored if
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd <p>Normally, if multiple <directive>Options</directive> could
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd apply to a directory, then the most specific one is used and
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd others are ignored; the options are not merged. (See <a
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd href="/sections.html#mergin">how sections are merged</a>.)
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd <directive>Options</directive> directive are preceded by a
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <code>+</code> or <code>-</code> symbol, the options are
2aa51ed61adb484602e94de3d2214ec267aecedbigalic merged. Any options preceded by a <code>+</code> are added to the
2aa51ed61adb484602e94de3d2214ec267aecedbigalic options currently in force, and any options preceded by a
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <code>-</code> are removed from the options currently in
2aa51ed61adb484602e94de3d2214ec267aecedbigalic force. </p>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <p>For example, without any <code>+</code> and <code>-</code> symbols:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Options Indexes FollowSymLinks<br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </Directory><br />
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd Options Includes<br />
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd </Directory>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>then only <code>Includes</code> will be set for the
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen <code>/web/docs/spec</code> directory. However if the second
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen <directive>Options</directive> directive uses the <code>+</code> and
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Options Indexes FollowSymLinks<br />
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen </Directory><br />
2aa51ed61adb484602e94de3d2214ec267aecedbigalic Options +Includes -Indexes<br />
2aa51ed61adb484602e94de3d2214ec267aecedbigalic </Directory>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>Includes</code> are set for the <code>/web/docs/spec</code>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd directory.</p>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd <code>-Includes</code> disables server-side includes completely
03e0a375c2435102fb2b51e34cccff52acbfddcdnd regardless of the previous setting.</p>
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen <p>The default in the absence of any other settings is
03e0a375c2435102fb2b51e34cccff52acbfddcdnd</directivesynopsis>
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen<directivesynopsis>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd<description>Selects which authenticated users can access
03e0a375c2435102fb2b51e34cccff52acbfddcdnda resource</description>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd<syntax>Require <var>entity-name</var> [<var>entity-name</var>] ...</syntax>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd<contextlist><context>directory</context><context>.htaccess</context>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd</contextlist>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd <p>This directive selects which authenticated users can access
03e0a375c2435102fb2b51e34cccff52acbfddcdnd a directory. The allowed syntaxes are:</p>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd <dt><code>Require user <var>userid</var> [<var>userid</var>]
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh <dd>Only the named users can access the resource.</dd>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd <dt><code>Require group <var>group-name</var> [<var>group-name</var>]
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <dd>Only users in the named groups can access the resource.</dd>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p><directive>Require</directive> must be accompanied by
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="core">AuthName</directive> and <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="core">AuthType</directive> directives, and directives such
003f0c9fda6664daf5092a0e42f65ede20098153slive as <directive module="mod_authn_file">AuthUserFile</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive and <directive module="mod_authz_groupfile">AuthGroupFile</directive> (to
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive define users and groups) in order to work correctly. Example:</p>
6fad623c3cc52b4a84d4d36538f6eed886f49f98covener AuthType Basic<br />
6fad623c3cc52b4a84d4d36538f6eed886f49f98covener AuthName "Restricted Directory"<br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Require group admin
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Access controls which are applied in this way are effective for
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <strong>all</strong> methods. <strong>This is what is normally
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive desired.</strong> If you wish to apply access controls only to
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive specific methods, while leaving other methods unprotected, then
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess place the <directive>Require</directive> statement into a
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <directive module="core" type="section">Limit</directive>
fb77c505254b6e9c925e23e734463e87574f8f40kess section.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">Satisfy</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<description>Limits the CPU consumption of processes launched
313bb560bc5c323cfd40c9cad7335b4b8e060aedkessby Apache children</description>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<syntax>RLimitCPU <var>seconds</var>|max [<var>seconds</var>|max]</syntax>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<default>Unset; uses operating system defaults</default>
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh<contextlist><context>server config</context><context>virtual host</context>
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor<context>directory</context><context>.htaccess</context></contextlist>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen <p>Takes 1 or 2 parameters. The first parameter sets the soft
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive resource limit for all processes and the second parameter sets
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the maximum resource limit. Either parameter can be a number,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive or <code>max</code> to indicate to the server that the limit should
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive be set to the maximum allowed by the operating system
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive configuration. Raising the maximum resource limit requires that
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess the server is running as <code>root</code>, or in the initial startup
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This applies to processes forked off from Apache children
e0ef044feba0082771091af42798cada5bb1f4fcrbowen servicing requests, not the Apache children themselves. This
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive includes CGI scripts and SSI exec commands, but not any
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive processes forked off from the Apache parent such as piped
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>CPU resource limits are expressed in seconds per
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive process.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">RLimitMEM</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">RLimitNPROC</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Limits the memory consumption of processes launched
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveby Apache children</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax>RLimitMEM <var>bytes</var>|max [<var>bytes</var>|max]</syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<default>Unset; uses operating system defaults</default>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>directory</context><context>.htaccess</context></contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Takes 1 or 2 parameters. The first parameter sets the soft
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive resource limit for all processes and the second parameter sets
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen the maximum resource limit. Either parameter can be a number,
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen or <code>max</code> to indicate to the server that the limit should
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen be set to the maximum allowed by the operating system
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh configuration. Raising the maximum resource limit requires that
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen the server is running as <code>root</code>, or in the initial startup
611f7fd8a0a5ee4a29eeed79dfd8bf6faaa3c613covener <p>This applies to processes forked off from Apache children
ffec3e56ff5331a2d732ec07e9d107303fed43f4covener servicing requests, not the Apache children themselves. This
611f7fd8a0a5ee4a29eeed79dfd8bf6faaa3c613covener includes CGI scripts and SSI exec commands, but not any
611f7fd8a0a5ee4a29eeed79dfd8bf6faaa3c613covener processes forked off from the Apache parent such as piped
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Memory resource limits are expressed in bytes per
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive process.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">RLimitCPU</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">RLimitNPROC</directive></seealso>
ae134ecc8faf4e6a8eb68e1c3724506771442a46rbowen</directivesynopsis>
e0ef044feba0082771091af42798cada5bb1f4fcrbowen<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Limits the number of processes that can be launched by
72580dbc2a55511f13f377063725b9f143b20826stoddardprocesses launched by Apache children</description>
72580dbc2a55511f13f377063725b9f143b20826stoddard<syntax>RLimitNPROC <var>number</var>|max [<var>number</var>|max]</syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<default>Unset; uses operating system defaults</default>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<contextlist><context>server config</context><context>virtual host</context>
4cc747f0aeda5b90c72e7e3ad22d5e58d6c48bc9rbowen<context>directory</context><context>.htaccess</context></contextlist>
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor <p>Takes 1 or 2 parameters. The first parameter sets the soft
72580dbc2a55511f13f377063725b9f143b20826stoddard resource limit for all processes and the second parameter sets
56d7eed7205462540aec7202cd82d9f5516fc537kess the maximum resource limit. Either parameter can be a number,
72580dbc2a55511f13f377063725b9f143b20826stoddard or <code>max</code> to indicate to the server that the limit
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive should be set to the maximum allowed by the operating system
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive configuration. Raising the maximum resource limit requires that
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the server is running as <code>root</code>, or in the initial startup
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen <p>This applies to processes forked off from Apache children
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen servicing requests, not the Apache children themselves. This
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh includes CGI scripts and SSI exec commands, but not any
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen processes forked off from the Apache parent such as piped
4cc747f0aeda5b90c72e7e3ad22d5e58d6c48bc9rbowen <p>Process limits control the number of processes per user.</p>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim under userids other than the web server userid, this directive
ffec3e56ff5331a2d732ec07e9d107303fed43f4covener will limit the number of processes that the server itself can
611f7fd8a0a5ee4a29eeed79dfd8bf6faaa3c613covener create. Evidence of this situation will be indicated by
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <strong><code>cannot fork</code></strong> messages in the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">RLimitMEM</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">RLimitCPU</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Interaction between host-level access control and
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveuser authentication</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>directory</context><context>.htaccess</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_authz_host">Allow</directive> and <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="core">Require</directive> used. The parameter can be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive either <code>All</code> or <code>Any</code>. This directive is only
fb77c505254b6e9c925e23e734463e87574f8f40kess useful if access to a particular area is being restricted by both
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive username/password <em>and</em> client host address. In this case
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the default behavior (<code>All</code>) is to require that the client
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive passes the address access restriction <em>and</em> enters a valid
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen username and password. With the <code>Any</code> option the client will be
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen granted access if they either pass the host restriction or enter a
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen valid username and password. This can be used to password restrict
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen an area, but to let clients from particular addresses in without
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh prompting for a password.</p>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen <p>For example, if you wanted to let people on your network have
4cc747f0aeda5b90c72e7e3ad22d5e58d6c48bc9rbowen unrestricted access to a portion of your website, but require that
4cc747f0aeda5b90c72e7e3ad22d5e58d6c48bc9rbowen people outside of your network provide a password, you could use a
611f7fd8a0a5ee4a29eeed79dfd8bf6faaa3c613covener configuration similar to the following:</p>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim Require valid-user<br />
ffec3e56ff5331a2d732ec07e9d107303fed43f4covener Allow from 192.168.1<br />
611f7fd8a0a5ee4a29eeed79dfd8bf6faaa3c613covener Satisfy Any
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <seealso><directive module="mod_authz_host">Allow</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <seealso><directive module="core">Require</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<directivesynopsis>
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele<description>Technique for locating the interpreter for CGI
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabelescripts</description>
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele<syntax>ScriptInterpreterSource Registry|Registry-Strict|Script</syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>directory</context><context>.htaccess</context></contextlist>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<compatibility>Win32 only;
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowenoption <code>Registry-Strict</code> is available in Apache 2.0 and
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowenlater</compatibility>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive is used to control how Apache finds the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive interpreter used to run CGI scripts. The default setting is
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>Script</code>. This causes Apache to use the interpreter pointed to
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive by the shebang line (first line, starting with <code>#!</code>) in the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive script. On Win32 systems this line usually looks like:</p>
fb77c505254b6e9c925e23e734463e87574f8f40kess </example>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>or, if perl is in the <code>PATH</code>, simply:</p>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess </example>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Setting <code>ScriptInterpreterSource Registry</code> will
7852e17fb37b2a02ccdcab107f2c7f5fd41fd201nd cause the Windows Registry tree <code>HKEY_CLASSES_ROOT</code> to be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive searched using the script file extension (e.g., <code>.pl</code>) as a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive search key. The command defined by the registry subkey
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>Shell\ExecCGI\Command</code> or, if it does not exist, by the subkey
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>Shell\Open\Command</code> is used to open the script file. If the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive registry keys cannot be found, Apache falls back to the behavior of the
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive <p>Be careful when using <code>ScriptInterpreterSource
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive module="mod_alias">ScriptAlias</directive>'ed directories, because
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive Apache will try to execute <strong>every</strong> file within this
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive directory. The <code>Registry</code> setting may cause undesired
d950cf9262224a223e2ff5c51393708071e14b94covener program calls on files which are typically not executed. For
d950cf9262224a223e2ff5c51393708071e14b94covener example, the default open command on <code>.htm</code> files on
e4e60c2f7ba8f12b687f588b89e413842e9f2d76igalic most Windows systems will execute Microsoft Internet Explorer, so
d950cf9262224a223e2ff5c51393708071e14b94covener any HTTP request for an <code>.htm</code> file existing within the
d950cf9262224a223e2ff5c51393708071e14b94covener script directory would start the browser in the background on the
d950cf9262224a223e2ff5c51393708071e14b94covener server. This is a good way to crash your system within a minute or
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor <p>The option <code>Registry-Strict</code> which is new in Apache
d950cf9262224a223e2ff5c51393708071e14b94covener 2.0 does the same thing as <code>Registry</code> but uses only the
d950cf9262224a223e2ff5c51393708071e14b94covener <code>ExecCGI</code> key is not a common one. It must be
e4e60c2f7ba8f12b687f588b89e413842e9f2d76igalic configured manually in the windows registry and hence prevents
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor accidental program calls on your system.</p>
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor</directivesynopsis>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<directivesynopsis>
f03f2609a2fc7a0d920842390738080bc0e1304bhumbedooh<description>Email address that the server includes in error
f03f2609a2fc7a0d920842390738080bc0e1304bhumbedoohmessages sent to the client</description>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<syntax>ServerAdmin <var>email-address</var>|<var>URL</var></syntax>
e4e60c2f7ba8f12b687f588b89e413842e9f2d76igalic<contextlist><context>server config</context><context>virtual host</context>
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor</contextlist>
e4e60c2f7ba8f12b687f588b89e413842e9f2d76igalic <p>The <directive>ServerAdmin</directive> sets the contact address
2aa51ed61adb484602e94de3d2214ec267aecedbigalic that the server includes in any error messages it returns to the
2aa51ed61adb484602e94de3d2214ec267aecedbigalic client. If the httpd doesn't recognize the supplied argument as an URL, it
f03f2609a2fc7a0d920842390738080bc0e1304bhumbedooh assumes, that it's an <var>email-address</var> and prepends it with
f03f2609a2fc7a0d920842390738080bc0e1304bhumbedooh <code>mailto:</code> in hyperlink targets. However, it's recommended to
2aa51ed61adb484602e94de3d2214ec267aecedbigalic actually use an email address, since there are a lot of CGI scripts that
d950cf9262224a223e2ff5c51393708071e14b94covener make that assumption. If you want to use an URL, it should point to another
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor server under your control. Otherwise users may not be able to contact you in
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive case of errors.</p>
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive <p>It may be worth setting up a dedicated address for this, e.g.</p>
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive ServerAdmin www-admin@foo.example.com
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor <p>as users do not always mention that they are talking about the
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive server!</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
beb923bec9bff2b49ce5027df2fe944e2b74e28brederpj<directivesynopsis>
dc223428958ad9ff05011545bcdda000887b93e5slive<description>Alternate names for a host used when matching requests
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveto name-virtual hosts</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax>ServerAlias <var>hostname</var> [<var>hostname</var>] ...</syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>virtual host</context></contextlist>
d8c44cd75cf575fe51319280c12445109e878523noodl <p>The <directive>ServerAlias</directive> directive sets the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive alternate names for a host, for use with <a
030108b1816bcda3d925df65357feabdce83bc94slive href="/vhosts/name-based.html">name-based virtual hosts</a>.</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <VirtualHost *><br />
f03f2609a2fc7a0d920842390738080bc0e1304bhumbedooh ServerAlias server server2.domain.com server2<br />
f03f2609a2fc7a0d920842390738080bc0e1304bhumbedooh </VirtualHost>
fb77c505254b6e9c925e23e734463e87574f8f40kess<seealso><a href="/vhosts/">Apache Virtual Host documentation</a></seealso>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess</directivesynopsis>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<directivesynopsis>
37742b630743e470b94618ecb3560fbd82e50b59rbowen<description>Hostname and port that the server uses to identify
37742b630743e470b94618ecb3560fbd82e50b59rbowenitself</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax>ServerName <var>fully-qualified-domain-name</var>[:<var>port</var>]</syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<compatibility>In version 2.0, this
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directive supersedes the functionality of the <directive>Port</directive>
e8811b6d38f756b325446ded5d96857d13856511takashi directive from version 1.3.</compatibility>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <p>The <directive>ServerName</directive> directive sets the hostname and
2aa51ed61adb484602e94de3d2214ec267aecedbigalic port that the server uses to identify itself. This is used when
2aa51ed61adb484602e94de3d2214ec267aecedbigalic creating redirection URLs. For example, if the name of the
2aa51ed61adb484602e94de3d2214ec267aecedbigalic machine hosting the webserver is <code>simple.example.com</code>,
2aa51ed61adb484602e94de3d2214ec267aecedbigalic but the machine also has the DNS alias <code>www.example.com</code>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd and you wish the webserver to be so identified, the following
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd directive should be used:</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd ServerName www.example.com:80
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>If no <directive>ServerName</directive> is specified, then the
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd server attempts to deduce the hostname by performing a reverse
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd lookup on the IP address. If no port is specified in the
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd servername, then the server will use the port from the incoming
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess request. For optimal reliability and predictability, you should
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd specify an explicit hostname and port using the
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd href="/vhosts/name-based.html">name-based virtual hosts</a>,
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <directive type="section" module="core">VirtualHost</directive>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd section specifies what hostname must appear in the request's
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <code>Host:</code> header to match this virtual host.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>See the description of the
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <directive module="core">UseCanonicalName</directive> directive for
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess settings which determine whether self-referential URL's (e.g., by the
37742b630743e470b94618ecb3560fbd82e50b59rbowen specified port, or to the port number given in the client's request.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><a href="/dns-caveats.html">Issues Regarding DNS and
8490b2f9f6469d5089163f6dd303d9a81f8e908ctrawick<seealso><directive module="core">UseCanonicalName</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">NameVirtualHost</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">ServerAlias</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess<description>Legacy URL pathname for a name-based virtual host that
030108b1816bcda3d925df65357feabdce83bc94sliveis accessed by an incompatible browser</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>virtual host</context></contextlist>
f03f2609a2fc7a0d920842390738080bc0e1304bhumbedooh <p>The <directive>ServerPath</directive> directive sets the legacy
f03f2609a2fc7a0d920842390738080bc0e1304bhumbedooh URL pathname for a host, for use with <a
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<seealso><a href="/vhosts/">Apache Virtual Host documentation</a></seealso>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<description>Base directory for the server installation</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context></contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive>ServerRoot</directive> directive sets the
7fbd7281d06cec1918aa370214df77c572f871a9sf directory in which the server lives. Typically it will contain the
7fbd7281d06cec1918aa370214df77c572f871a9sf subdirectories <code>conf/</code> and <code>logs/</code>. Relative
7fbd7281d06cec1918aa370214df77c572f871a9sf paths for other configuration files are taken as relative to this
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directory.</p>
7fbd7281d06cec1918aa370214df77c572f871a9sf </example>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><a href="/misc/security_tips.html#serverroot">the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive security tips</a> for information on how to properly set
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd permissions on the <directive>ServerRoot</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<directivesynopsis>
1597043cec6ad37fa4154bf09b0fccdabed1a239slive<description>Configures the footer on server-generated documents</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
530eba85dbd41b8a0fa5255d3648d1440199a661slive<context>directory</context><context>.htaccess</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive>ServerSignature</directive> directive allows the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive configuration of a trailing footer line under server-generated
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive documents (error messages, <module>mod_proxy</module> ftp directory
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive listings, <module>mod_info</module> output, ...). The reason why you
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive would want to enable such a footer line is that in a chain of proxies,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the user often has no possibility to tell which of the chained servers
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive actually produced a returned error message.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive setting, which is the default, suppresses the footer line (and is
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive therefore compatible with the behavior of Apache-1.2 and
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive below). The <code>On</code> setting simply adds a line with the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive server version number and <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="core">ServerName</directive> of the serving virtual host,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive and the <code>EMail</code> setting additionally creates a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive "mailto:" reference to the <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="core">ServerAdmin</directive> of the referenced
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive document.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>After version 2.0.44, the details of the server version number
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive presented are controlled by the <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">ServerTokens</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Configures the <code>Server</code> HTTP response
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveheader</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax>ServerTokens Major|Minor|Min[imal]|Prod[uctOnly]|OS|Full</syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context></contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive controls whether <code>Server</code> response
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive header field which is sent back to clients includes a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive description of the generic OS-type of the server as well as
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive information about compiled-in modules.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <dd>Server sends (<em>e.g.</em>): <code>Server: Apache/2.0.41
7fbd7281d06cec1918aa370214df77c572f871a9sf <dt><code>ServerTokens Full</code> (or not specified)</dt>
7fbd7281d06cec1918aa370214df77c572f871a9sf <dd>Server sends (<em>e.g.</em>): <code>Server: Apache/2.0.41
7fbd7281d06cec1918aa370214df77c572f871a9sf <p>This setting applies to the entire server, and cannot be
7fbd7281d06cec1918aa370214df77c572f871a9sf enabled or disabled on a virtualhost-by-virtualhost basis.</p>
7fbd7281d06cec1918aa370214df77c572f871a9sf <p>After version 2.0.44, this directive also controls the
7fbd7281d06cec1918aa370214df77c572f871a9sf information presented by the <directive
7fbd7281d06cec1918aa370214df77c572f871a9sf<seealso><directive module="core">ServerSignature</directive></seealso>
7fbd7281d06cec1918aa370214df77c572f871a9sf</directivesynopsis>
7fbd7281d06cec1918aa370214df77c572f871a9sf<directivesynopsis>
7fbd7281d06cec1918aa370214df77c572f871a9sf<description>Forces all matching files to be processed by a
7fbd7281d06cec1918aa370214df77c572f871a9sfhandler</description>
7fbd7281d06cec1918aa370214df77c572f871a9sf<contextlist><context>server config</context><context>virtual host</context>
7fbd7281d06cec1918aa370214df77c572f871a9sf</contextlist>
7fbd7281d06cec1918aa370214df77c572f871a9sf<compatibility>Moved into the core in Apache 2.0</compatibility>
7fbd7281d06cec1918aa370214df77c572f871a9sf <directive type="section" module="core">Directory</directive> or
7fbd7281d06cec1918aa370214df77c572f871a9sf <directive type="section" module="core">Location</directive>
7fbd7281d06cec1918aa370214df77c572f871a9sf section, this directive forces all matching files to be parsed
7fbd7281d06cec1918aa370214df77c572f871a9sf <var>handler-name</var>. For example, if you had a directory you
7fbd7281d06cec1918aa370214df77c572f871a9sf wanted to be parsed entirely as imagemap rule files, regardless
7fbd7281d06cec1918aa370214df77c572f871a9sf of extension, you might put the following into an
7fbd7281d06cec1918aa370214df77c572f871a9sf SetHandler imap-file
7fbd7281d06cec1918aa370214df77c572f871a9sf </example>
7fbd7281d06cec1918aa370214df77c572f871a9sf <p>Another example: if you wanted to have the server display a
7fbd7281d06cec1918aa370214df77c572f871a9sf status report whenever a URL of
7fbd7281d06cec1918aa370214df77c572f871a9sf <code>http://servername/status</code> was called, you might put
7fbd7281d06cec1918aa370214df77c572f871a9sf <Location /status><br />
7fbd7281d06cec1918aa370214df77c572f871a9sf SetHandler server-status<br />
7fbd7281d06cec1918aa370214df77c572f871a9sf </Location>
7fbd7281d06cec1918aa370214df77c572f871a9sf </example>
7fbd7281d06cec1918aa370214df77c572f871a9sf <p>You can override an earlier defined <directive>SetHandler</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="mod_mime">AddHandler</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Sets the filters that will process client requests and POST
d3f27ec18dfa6283e852aa98253212edafaa0e2brboweninput</description>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<syntax>SetInputFilter <var>filter</var>[;<var>filter</var>...]</syntax>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<contextlist><context>server config</context><context>virtual host</context>
2e4a251ce928e74ed84fd089cdceaf5f6b5c53f2humbedooh<context>directory</context><context>.htaccess</context>
8b052d682204371decc64f942aede5ef1da98955erikabele</contextlist>
8b052d682204371decc64f942aede5ef1da98955erikabele <p>The <directive>SetInputFilter</directive> directive sets the
8b052d682204371decc64f942aede5ef1da98955erikabele filter or filters which will process client requests and POST
8b052d682204371decc64f942aede5ef1da98955erikabele input when they are received by the server. This is in addition to
7fbd7281d06cec1918aa370214df77c572f871a9sf any filters defined elsewhere, including the
7fbd7281d06cec1918aa370214df77c572f871a9sf directive.</p>
7fbd7281d06cec1918aa370214df77c572f871a9sf <p>If more than one filter is specified, they must be separated
fd410ae1fa431e734e6d0cd3c006002d4904466apoirier by semicolons in the order in which they should process the
7fbd7281d06cec1918aa370214df77c572f871a9sf content.</p>
7fbd7281d06cec1918aa370214df77c572f871a9sf<seealso><a href="/filter.html">Filters</a> documentation</seealso>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic</directivesynopsis>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<directivesynopsis>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<description>Sets the filters that will process responses from the
7fbd7281d06cec1918aa370214df77c572f871a9sfserver</description>
7fbd7281d06cec1918aa370214df77c572f871a9sf<syntax>SetOutputFilter <var>filter</var>[;<var>filter</var>...]</syntax>
7fbd7281d06cec1918aa370214df77c572f871a9sf<contextlist><context>server config</context><context>virtual host</context>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic<context>directory</context><context>.htaccess</context>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic</contextlist>
2aa51ed61adb484602e94de3d2214ec267aecedbigalic <p>The <directive>SetOutputFilter</directive> directive sets the filters
7fbd7281d06cec1918aa370214df77c572f871a9sf which will process responses from the server before they are
7fbd7281d06cec1918aa370214df77c572f871a9sf sent to the client. This is in addition to any filters defined
7fbd7281d06cec1918aa370214df77c572f871a9sf elsewhere, including the
7fbd7281d06cec1918aa370214df77c572f871a9sf directive.</p>
7fbd7281d06cec1918aa370214df77c572f871a9sf <p>For example, the following configuration will process all files
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive in the <code>/www/data/</code> directory for server-side
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive includes.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive SetOutputFilter INCLUDES<br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </Directory>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>If more than one filter is specified, they must be separated
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive by semicolons in the order in which they should process the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive content.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><a href="/filter.html">Filters</a> documentation</seealso>
fb77c505254b6e9c925e23e734463e87574f8f40kess</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<description>Amount of time the server will wait for
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowencertain events before failing a request</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context></contextlist>
6beba165aeced2ca77a6f1593ee08c47a32099efcovener <p>The <directive>TimeOut</directive> directive currently defines
6beba165aeced2ca77a6f1593ee08c47a32099efcovener the amount of time Apache will wait for three things:</p>
6beba165aeced2ca77a6f1593ee08c47a32099efcovener <li>The total amount of time it takes to receive a GET
6beba165aeced2ca77a6f1593ee08c47a32099efcovener request.</li>
6beba165aeced2ca77a6f1593ee08c47a32099efcovener <li>The amount of time between receipt of TCP packets on a
6beba165aeced2ca77a6f1593ee08c47a32099efcovener POST or PUT request.</li>
6beba165aeced2ca77a6f1593ee08c47a32099efcovener <li>The amount of time between ACKs on transmissions of TCP
6beba165aeced2ca77a6f1593ee08c47a32099efcovener packets in responses.</li>
6beba165aeced2ca77a6f1593ee08c47a32099efcovener <p>We plan on making these separately configurable at some point
7a975d0413ba303546b7619e4785cb641f7f09fdcovener down the road. The timer used to default to 1200 before 1.2,
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim but has been lowered to 300 which is still far more than
7a975d0413ba303546b7619e4785cb641f7f09fdcovener necessary in most situations. It is not set any lower by
7a975d0413ba303546b7619e4785cb641f7f09fdcovener default because there may still be odd places in the code where
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim the timer is not reset when a packet is sent. </p>
7a975d0413ba303546b7619e4785cb641f7f09fdcovener</directivesynopsis>
7a975d0413ba303546b7619e4785cb641f7f09fdcovener<directivesynopsis>
7a975d0413ba303546b7619e4785cb641f7f09fdcovener<description>Configures how the server determines its own name and
7a975d0413ba303546b7619e4785cb641f7f09fdcovenerport</description>
7a975d0413ba303546b7619e4785cb641f7f09fdcovener<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>In many situations Apache must construct a <em>self-referential</em>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim URL -- that is, a URL that refers back to the same server. With
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <code>UseCanonicalName On</code> Apache will use the hostname and port
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim specified in the <directive module="core">ServerName</directive>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim directive to construct the canonical name for the server. This name
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim is used in all self-referential URLs, and for the values of
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <code>SERVER_NAME</code> and <code>SERVER_PORT</code> in CGIs.</p>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <p>With <code>UseCanonicalName Off</code> Apache will form
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim self-referential URLs using the hostname and port supplied by
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim the client if any are supplied (otherwise it will use the
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim canonical name, as defined above). These values are the same
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim that are used to implement <a
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim href="/vhosts/name-based.html">name based virtual hosts</a>,
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim and are available with the same clients. The CGI variables
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <code>SERVER_NAME</code> and <code>SERVER_PORT</code> will be
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim constructed from the client supplied values as well.</p>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <p>An example where this may be useful is on an intranet server
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim where you have users connecting to the machine using short
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim names such as <code>www</code>. You'll notice that if the users
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim type a shortname, and a URL which is a directory, such as
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim slash</em> then Apache will redirect them to
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim authentication enabled, this will cause the user to have to
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim authenticate twice (once for <code>www</code> and once again
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim href="http://httpd.apache.org/docs/misc/FAQ.html#prompted-twice">the
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim FAQ on this subject for more information</a>). But if
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <directive>UseCanonicalName</directive> is set <code>Off</code>, then
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim Apache will redirect to <code>http://www/splat/</code>.</p>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <p>There is a third option, <code>UseCanonicalName DNS</code>,
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim which is intended for use with mass IP-based virtual hosting to
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim support ancient clients that do not provide a
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <code>Host:</code> header. With this option Apache does a
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim reverse DNS lookup on the server IP address that the client
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim connected to in order to work out self-referential URLs.</p>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <p>If CGIs make assumptions about the values of <code>SERVER_NAME</code>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim they may be broken by this option. The client is essentially free
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim to give whatever value they want as a hostname. But if the CGI is
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim only using <code>SERVER_NAME</code> to construct self-referential URLs
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim then it should be just fine.</p>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim<seealso><directive module="core">ServerName</directive></seealso>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim<seealso><directive module="mpm_common">Listen</directive></seealso>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim</directivesynopsis>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim<description>Contains directives that apply only to a specific
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjimhostname or IP address</description>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim<syntax><VirtualHost
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <var>addr</var>[:<var>port</var>] [<var>addr</var>[:<var>port</var>]]
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim ...> ... </VirtualHost></syntax>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim<contextlist><context>server config</context></contextlist>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <p><directive type="section">VirtualHost</directive> and
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <code></VirtualHost></code> are used to enclose a group of
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim directives that will apply only to a particular virtual host. Any
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim directive that is allowed in a virtual host context may be
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim used. When the server receives a request for a document on a
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim particular virtual host, it uses the configuration directives
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim enclosed in the <directive type="section">VirtualHost</directive>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick <li>A fully qualified domain name for the IP address of the
2b6c7b8eb5fbc43564898aedac730df7e91da475trawick virtual host;</li>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick <li>The character <code>*</code>, which is used only in combination with
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen <code>NameVirtualHost *</code> to match all IP addresses; or</li>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick <li>The string <code>_default_</code>, which is used only
a0fed3e26656887c8458aa1081d516d08ced3c84trawick with IP virtual hosting to catch unmatched IP addresses.</li>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick <VirtualHost 10.1.2.3><br />
a0fed3e26656887c8458aa1081d516d08ced3c84trawick ServerAdmin webmaster@host.foo.com<br />
a0fed3e26656887c8458aa1081d516d08ced3c84trawick </VirtualHost>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick <p>IPv6 addresses must be specified in square brackets because
a0fed3e26656887c8458aa1081d516d08ced3c84trawick the optional port number could not be determined otherwise. An
a0fed3e26656887c8458aa1081d516d08ced3c84trawick IPv6 example is shown below:</p>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick <VirtualHost [fe80::a00:20ff:fea7:ccea]><br />
a0fed3e26656887c8458aa1081d516d08ced3c84trawick ServerAdmin webmaster@host.example.com<br />
a0fed3e26656887c8458aa1081d516d08ced3c84trawick </VirtualHost>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick <p>Each Virtual Host must correspond to a different IP address,
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor different port number or a different host name for the server,
a0fed3e26656887c8458aa1081d516d08ced3c84trawick in the former case the server machine must be configured to
a0fed3e26656887c8458aa1081d516d08ced3c84trawick accept IP packets for multiple addresses. (If the machine does
a0fed3e26656887c8458aa1081d516d08ced3c84trawick not have multiple network interfaces, then this can be
a0fed3e26656887c8458aa1081d516d08ced3c84trawick accomplished with the <code>ifconfig alias</code> command -- if
a0fed3e26656887c8458aa1081d516d08ced3c84trawick your OS supports it).</p>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick <p>The use of <directive type="section">VirtualHost</directive> does
bf0e7f6393e91c0a7c15cb0d889a4238c973dc2etrawick <strong>not</strong> affect what addresses Apache listens on. You
bf0e7f6393e91c0a7c15cb0d889a4238c973dc2etrawick may need to ensure that Apache is listening on the correct addresses
bf0e7f6393e91c0a7c15cb0d889a4238c973dc2etrawick using <directive module="mpm_common">Listen</directive>.</p>
bf0e7f6393e91c0a7c15cb0d889a4238c973dc2etrawick <p>When using IP-based virtual hosting, the special name
a0fed3e26656887c8458aa1081d516d08ced3c84trawick which case this virtual host will match any IP address that is
a0fed3e26656887c8458aa1081d516d08ced3c84trawick not explicitly listed in another virtual host. In the absence
a0fed3e26656887c8458aa1081d516d08ced3c84trawick of any <code>_default_</code> virtual host the "main" server config,
a0fed3e26656887c8458aa1081d516d08ced3c84trawick consisting of all those definitions outside any VirtualHost
a0fed3e26656887c8458aa1081d516d08ced3c84trawick section, is used when no IP-match occurs. (But note that any IP
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor address that matches a <directive
a0fed3e26656887c8458aa1081d516d08ced3c84trawick module="core">NameVirtualHost</directive> directive will use neither
a0fed3e26656887c8458aa1081d516d08ced3c84trawick the "main" server config nor the <code>_default_</code> virtual host.
bf0e7f6393e91c0a7c15cb0d889a4238c973dc2etrawick See the <a href="/vhosts/name-based.html">name-based virtual hosting</a>
bf0e7f6393e91c0a7c15cb0d889a4238c973dc2etrawick documentation for further details.)</p>
bf0e7f6393e91c0a7c15cb0d889a4238c973dc2etrawick <p>You can specify a <code>:port</code> to change the port that is
bf0e7f6393e91c0a7c15cb0d889a4238c973dc2etrawick matched. If unspecified then it defaults to the same port as the
bf0e7f6393e91c0a7c15cb0d889a4238c973dc2etrawick most recent <directive module="mpm_common">Listen</directive>
bf0e7f6393e91c0a7c15cb0d889a4238c973dc2etrawick statement of the main server. You may also specify <code>:*</code>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick to match all ports on that address. (This is recommended when used
a0fed3e26656887c8458aa1081d516d08ced3c84trawick <p>See the <a href="/misc/security_tips.html">security tips</a>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick document for details on why your security could be compromised if the
a0fed3e26656887c8458aa1081d516d08ced3c84trawick directory where logfiles are stored is writable by anyone other
a0fed3e26656887c8458aa1081d516d08ced3c84trawick than the user that starts the server.</p>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick<seealso><a href="/vhosts/">Apache Virtual Host documentation</a></seealso>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick<seealso><a href="/dns-caveats.html">Issues Regarding DNS and
a0fed3e26656887c8458aa1081d516d08ced3c84trawick<seealso><a href="/sections.html">How <Directory>, <Location>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick and <Files> sections work</a> for an explanation of how these
a0fed3e26656887c8458aa1081d516d08ced3c84trawick different sections are combined when a request is received</seealso>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick</directivesynopsis>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick</modulesynopsis>