core.xml revision 56d7eed7205462540aec7202cd82d9f5516fc537
530eba85dbd41b8a0fa5255d3648d1440199a661slive<!DOCTYPE modulesynopsis SYSTEM "/style/modulesynopsis.dtd">
e942c741056732f50da2074b36fe59805d370650slive<?xml-stylesheet type="text/xsl" href="/style/manual.en.xsl"?>
5f5d1b4cc970b7f06ff8ef6526128e9a27303d88nd<!-- $LastChangedRevision$ -->
db479b48bd4d75423ed4a45e15b75089d1a8ad72fielding Copyright 2002-2005 The Apache Software Foundation or its licensors, as
db479b48bd4d75423ed4a45e15b75089d1a8ad72fielding applicable.
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>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna<directivesynopsis>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna<description>Resources accept trailing pathname information</description>
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen<context>virtual host</context><context>directory</context>
e4e60c2f7ba8f12b687f588b89e413842e9f2d76igalic<compatibility>Available in Apache 2.0.30 and later</compatibility>
e4e60c2f7ba8f12b687f588b89e413842e9f2d76igalic <p>This directive controls whether requests that contain trailing
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor pathname information that follows an actual filename (or
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe 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
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor 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>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna <dt><code>Off</code></dt><dd>A request will only be accepted if it
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna maps to a literal path that exists. Therefore a request with
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna trailing pathname information after the true filename such as
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna <code>/test/here.html/more</code> in the above example will return
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor a 404 NOT FOUND error.</dd>
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor <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
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna 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
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna href="mod_isapi.html">isapi-isa</a>, generally accept
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna <p>The primary purpose of the <code>AcceptPathInfo</code>
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor directive is to allow you to override the handler's choice of
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna 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
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna as <a href="mod_include.html">INCLUDES</a>, to generate content
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe based on <code>PATH_INFO</code>. The core handler would usually reject
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe the request, so you can use the following configuration to enable
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe such a script:</p>
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe Options +Includes<br />
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe SetOutputFilter INCLUDES<br />
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe AcceptPathInfo On<br />
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe </Files>
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe</directivesynopsis>
e4e60c2f7ba8f12b687f588b89e413842e9f2d76igalic<directivesynopsis>
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe<description>Name of the distributed configuration file</description>
5ae609a8a09239d20f48a4a95c4f21b713995babwrowe<syntax>AccessFileName <var>filename</var> [<var>filename</var>] ...</syntax>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna<contextlist><context>server config</context><context>virtual host</context>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna</contextlist>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna <p>While processing a request the server looks for
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the first existing configuration file from this list of names in
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive every directory of the path to the document, if distributed
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess configuration files are <a href="#allowoverride">enabled for that
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive AccessFileName .acl
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen <p>before returning the document
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>/usr/local/web/index.html</code>, the server will read
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <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 />
fb77c505254b6e9c925e23e734463e87574f8f40kess AllowOverride None<br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </Directory>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">AllowOverride</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><a href="/configuring.html">Configuration Files</a></seealso>
fb77c505254b6e9c925e23e734463e87574f8f40kess<seealso><a href="/howto/htaccess.html">.htaccess Files</a></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
fb77c505254b6e9c925e23e734463e87574f8f40kess<description>Default charset parameter to be added when a response
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivecontent-type is <code>text/plain</code> or <code>text/html</code></description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax>AddDefaultCharset On|Off|<var>charset</var></syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>virtual host</context><context>directory</context>
fb77c505254b6e9c925e23e734463e87574f8f40kess <p>This directive specifies a default value for the media type
fb77c505254b6e9c925e23e734463e87574f8f40kess charset parameter (the name of a character encoding) to be added
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive to a response if and only if the response's content-type is either
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>text/plain</code> or <code>text/html</code>. This should override
fb77c505254b6e9c925e23e734463e87574f8f40kess any charset specified in the body of the response via a <code>META</code>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess element, though the exact behavior is often dependent on the user's client
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive configuration. A setting of <code>AddDefaultCharset Off</code>
bc4b55ec8f31569d606d5680d50189a355bcd7a6rbowen disables this functionality. <code>AddDefaultCharset On</code> enables
fb77c505254b6e9c925e23e734463e87574f8f40kess a default charset of <code>iso-8859-1</code>. Any other value is assumed
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive to be the <var>charset</var> to be used, which should be one of the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <a href="http://www.iana.org/assignments/character-sets">IANA registered
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive charset values</a> for use in MIME media types.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive For example:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive AddDefaultCharset utf-8
fb77c505254b6e9c925e23e734463e87574f8f40kess </example>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p><directive>AddDefaultCharset</directive> should only be used when all
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd of the text resources to which it applies are known to be in that
130d299c4b2b15be45532a176604c71fdc7bea5bnd character encoding and it is too inconvenient to label their charset
130d299c4b2b15be45532a176604c71fdc7bea5bnd individually. One such example is to add the charset parameter
130d299c4b2b15be45532a176604c71fdc7bea5bnd to resources containing generated content, such as legacy CGI
130d299c4b2b15be45532a176604c71fdc7bea5bnd scripts, that might be vulnerable to cross-site scripting attacks
130d299c4b2b15be45532a176604c71fdc7bea5bnd due to user-provided data being included in the output. Note, however,
ef8e89e090461194ecadd31e8796a2c51e0531a2kess that a better solution is to just fix (or delete) those scripts, since
130d299c4b2b15be45532a176604c71fdc7bea5bnd setting a default charset does not protect users that have enabled
130d299c4b2b15be45532a176604c71fdc7bea5bnd the "auto-detect character encoding" feature on their browser.</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<seealso><directive module="mod_mime">AddCharset</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>assigns an output filter to a particular MIME-type</description>
003f0c9fda6664daf5092a0e42f65ede20098153slive<syntax>AddOutputFilterByType <var>filter</var>[;<var>filter</var>...]
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>virtual host</context><context>directory</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<compatibility>Available in Apache 2.0.33 and later</compatibility>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess href="/filter.html">filter</a> for a request depending on the
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess response MIME-type.</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>The following example uses the <code>DEFLATE</code> filter, which
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd is provided by <module>mod_deflate</module>. It will compress all
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd output (either static or dynamic) which is labeled as
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>text/html</code> or <code>text/plain</code> before it is sent
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive to the client.</p>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>If you want the content to be processed by more than one filter, their
130d299c4b2b15be45532a176604c71fdc7bea5bnd names have to be separated by semicolons. It's also possible to use one
130d299c4b2b15be45532a176604c71fdc7bea5bnd <directive>AddOutputFilterByType</directive> directive for each of
130d299c4b2b15be45532a176604c71fdc7bea5bnd these filters.</p>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>The configuration below causes all script output labeled as
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>INCLUDES</code> filter and then by the <code>DEFLATE</code>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive filter.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <Location /cgi-bin/><br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Options Includes<br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive AddOutputFilterByType INCLUDES;DEFLATE text/html<br />
684f2a9a422185adda0692a1203c5ad6687fc5c5nd </Location>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd </example>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Enabling filters with <directive>AddOutputFilterByType</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive may fail partially or completely in some cases. For example, no
003f0c9fda6664daf5092a0e42f65ede20098153slive 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 explicitly, for
a8ce9095d102e43fecb81093a132b90b9a227f78kess example with <directive module="mod_mime">AddType</directive> or
684f2a9a422185adda0692a1203c5ad6687fc5c5nd <directive module="core">ForceType</directive>. Setting the
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding content type within a (non-nph) CGI script is also safe.</p>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding <p>The by-type output filters are never applied on proxy requests.</p>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding<seealso><directive module="mod_mime">AddOutputFilter</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">SetOutputFilter</directive></seealso>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</directivesynopsis>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding<directivesynopsis>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding<description>Determines whether encoded path separators in URLs are allowed to
843a03fe0b138a4c1f64cb90a014e9417ac30691fieldingbe passed through</description>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding<contextlist><context>server config</context><context>virtual host</context>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding</contextlist>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding<compatibility>Available in Apache 2.0.46 and later</compatibility>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive>AllowEncodedSlashes</directive> directive allows URLs
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding which contain encoded path separators (<code>%2F</code> for <code>/</code>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive and additionally <code>%5C</code> for <code>\</code> on according systems)
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive to be used. Normally such URLs are refused with a 404 (Not found) error.</p>
77ead9e0262e4f08ec336d1a65b2edef7705c839nd <p>Turning <directive>AllowEncodedSlashes</directive> <code>On</code> is
9583adab6bc4b3758e41963c905d9dad9f067131nd mostly useful when used in conjunction with <code>PATH_INFO</code>.</p>
77ead9e0262e4f08ec336d1a65b2edef7705c839nd <p>Allowing encoded slashes does <em>not</em> imply <em>decoding</em>.
77ead9e0262e4f08ec336d1a65b2edef7705c839nd Occurrences of <code>%2F</code> or <code>%5C</code> (<em>only</em> on
77ead9e0262e4f08ec336d1a65b2edef7705c839nd according systems) will be left as such in the otherwise decoded URL
3770ed746d69c7a4111cba9966169bd5d7a509a6poirier string.</p>
77ead9e0262e4f08ec336d1a65b2edef7705c839nd<seealso><directive module="core">AcceptPathInfo</directive></seealso>
77ead9e0262e4f08ec336d1a65b2edef7705c839nd</directivesynopsis>
77ead9e0262e4f08ec336d1a65b2edef7705c839nd<directivesynopsis>
3770ed746d69c7a4111cba9966169bd5d7a509a6poirier<description>Types of directives that are allowed in
3770ed746d69c7a4111cba9966169bd5d7a509a6poirier<syntax>AllowOverride All|None|<var>directive-type</var>
3770ed746d69c7a4111cba9966169bd5d7a509a6poirier<contextlist><context>directory</context></contextlist>
3770ed746d69c7a4111cba9966169bd5d7a509a6poirier <p>When the server finds an <code>.htaccess</code> file (as
77ead9e0262e4f08ec336d1a65b2edef7705c839nd specified by <directive module="core">AccessFileName</directive>)
77ead9e0262e4f08ec336d1a65b2edef7705c839nd it needs to know which directives declared in that file can override
77ead9e0262e4f08ec336d1a65b2edef7705c839nd earlier configuration directives.</p>
77ead9e0262e4f08ec336d1a65b2edef7705c839nd <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
77ead9e0262e4f08ec336d1a65b2edef7705c839nd type="section" module="core">Location</directive>, <directive
77ead9e0262e4f08ec336d1a65b2edef7705c839nd module="core" type="section">DirectoryMatch</directive> or
77ead9e0262e4f08ec336d1a65b2edef7705c839nd <directive type="section" module="core">Files</directive> sections.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>When this directive is set to <code>None</code>, then
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <a href="#accessfilename">.htaccess</a> files are completely ignored.
003f0c9fda6664daf5092a0e42f65ede20098153slive In this case, the server will not even attempt to read
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>When this directive is set to <code>All</code>, then any
4ea161d94782fa56f4b36d496f35ff8577c43065covener directive which has the .htaccess <a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive href="directive-dict.html#Context">Context</a> is allowed in
fb77c505254b6e9c925e23e734463e87574f8f40kess <p>The <var>directive-type</var> can be one of the following
fb77c505254b6e9c925e23e734463e87574f8f40kess groupings of directives.</p>
b12b918ae6baf9c5762ed61b7393d0e2198378c0nd Allow use of the authorization directives (<directive
b12b918ae6baf9c5762ed61b7393d0e2198378c0nd <directive module="mod_authn_dbm">AuthDBMUserFile</directive>,
b12b918ae6baf9c5762ed61b7393d0e2198378c0nd <directive module="mod_authz_groupfile">AuthGroupFile</directive>,
10673857794a4b3d9568ca2d983722a87ed352f1rbowen <directive module="core">AuthType</directive>, <directive
113961f0559eb026ea0d379cb7350f82bc09d710druggeri module="mod_authn_file">AuthUserFile</directive>, <directive
113961f0559eb026ea0d379cb7350f82bc09d710druggeri module="core">Require</directive>, <em>etc.</em>).</dd>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Allow use of the directives controlling document types (<directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_negotiation">LanguagePriority</directive>,
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <directive module="core">SetHandler</directive>, <directive
1f53e295ebd19aed1767d12da7abfab9936c148cjerenkrantz Allow use of the directives controlling directory indexing
9cd3b05d7b70f07a742bbaf548fa4fa2bdbe5ce6noodl <directive module="mod_autoindex">AddIcon</directive>, <directive
1f53e295ebd19aed1767d12da7abfab9936c148cjerenkrantz <directive module="mod_autoindex">AddIconByType</directive>,
9cd3b05d7b70f07a742bbaf548fa4fa2bdbe5ce6noodl <directive module="mod_autoindex">DefaultIcon</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_dir">DirectoryIndex</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_autoindex">FancyIndexing</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_autoindex">HeaderName</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_autoindex">IndexIgnore</directive>, <directive
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding module="mod_autoindex">IndexOptions</directive>, <directive
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding Allow use of the directives controlling host access (<directive
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding module="mod_authz_host">Allow</directive>, <directive
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem module="mod_authz_host">Deny</directive> and <directive
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem Allow use of the directives controlling specific directory
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem features (<directive module="core">Options</directive> and
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem <directive module="mod_include">XBitHack</directive>).
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem An equal sign may be given followed by a comma (but no spaces)
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem separated lists of options that may be set using the <directive
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem AllowOverride AuthConfig Indexes
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>In the example above all directives that are neither in the group
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>AuthConfig</code> nor <code>Indexes</code> cause an internal
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive server error.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">AccessFileName</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>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<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
9ed9eaf871c58d281af02e76125ceadb5060afa5nd knows which username and password to send.
9ed9eaf871c58d281af02e76125ceadb5060afa5nd <directive>AuthName</directive> takes a single argument; if the
9ed9eaf871c58d281af02e76125ceadb5060afa5nd 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
9970ad80054f477c708284a0d030a5bd26e412a9covener AuthName "Top Secret"
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <p>The string provided for the <code>AuthName</code> is what will
9970ad80054f477c708284a0d030a5bd26e412a9covener appear in the password dialog provided by most browsers.</p>
9970ad80054f477c708284a0d030a5bd26e412a9covener href="/howto/auth.html">Authentication, Authorization, and
9970ad80054f477c708284a0d030a5bd26e412a9covener</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<contextlist><context>directory</context><context>.htaccess</context>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</contextlist>
b12b918ae6baf9c5762ed61b7393d0e2198378c0nd <p>This directive selects the type of user authentication for a
da637bcae7b6e150470e701af29da5604a34a17erbowen directory. Only <code>Basic</code> and <code>Digest</code> are
da637bcae7b6e150470e701af29da5604a34a17erbowen currently implemented.
da637bcae7b6e150470e701af29da5604a34a17erbowen It must be accompanied by <directive
da637bcae7b6e150470e701af29da5604a34a17erbowen module="core">Require</directive> directives, and directives such
da637bcae7b6e150470e701af29da5604a34a17erbowen as <directive module="mod_authn_file">AuthUserFile</directive> and
da637bcae7b6e150470e701af29da5604a34a17erbowen <directive module="mod_authz_groupfile">AuthGroupFile</directive> to
7802d43d20007fa575e43b6ae77d5177ceffdb71sf<seealso><a href="/howto/auth.html">Authentication, Authorization,
7802d43d20007fa575e43b6ae77d5177ceffdb71sf</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri<description>Technique for locating the interpreter for CGI
113961f0559eb026ea0d379cb7350f82bc09d710druggeriscripts</description>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri<syntax>CGIMapExtension <var>cgi-path</var> <var>.extension</var></syntax>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri<contextlist><context>directory</context><context>.htaccess</context>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri</contextlist>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri <p>This directive is used to control how Apache finds the
113961f0559eb026ea0d379cb7350f82bc09d710druggeri interpreter used to run CGI scripts. For example, setting
113961f0559eb026ea0d379cb7350f82bc09d710druggeri <code>CGIMapExtension sys:\foo.nlm .foo</code> will
113961f0559eb026ea0d379cb7350f82bc09d710druggeri cause all CGI script files with a <code>.foo</code> extension to
113961f0559eb026ea0d379cb7350f82bc09d710druggeri be passed to the FOO interpreter.</p>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri</directivesynopsis>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri<directivesynopsis>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri<description>Enables the generation of <code>Content-MD5</code> HTTP Response
113961f0559eb026ea0d379cb7350f82bc09d710druggeriheaders</description>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri<contextlist><context>server config</context><context>virtual host</context>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri<context>directory</context><context>.htaccess</context>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri</contextlist>
113961f0559eb026ea0d379cb7350f82bc09d710druggeri <p>This directive enables the generation of
113961f0559eb026ea0d379cb7350f82bc09d710druggeri <code>Content-MD5</code> headers as defined in RFC1864
113961f0559eb026ea0d379cb7350f82bc09d710druggeri 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,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive SSI documents, output from CGI scripts, and byte range responses
113961f0559eb026ea0d379cb7350f82bc09d710druggeri do not have this header.</p>
54bcd0e21a5c79158afd3b78bf707a493a5fb33crbowen</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes<description>MIME content-type that will be sent if the
fb77c505254b6e9c925e23e734463e87574f8f40kessserver cannot determine a type in any other way</description>
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes<contextlist><context>server config</context><context>virtual host</context>
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes<context>directory</context><context>.htaccess</context>
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes</contextlist>
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen <p>There will be times when the server is asked to provide a
fb77c505254b6e9c925e23e734463e87574f8f40kess document whose type cannot be determined by its MIME types
fb77c505254b6e9c925e23e734463e87574f8f40kess mappings.</p>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <p>The server must inform the client of the content-type of the
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes document, so in the event of an unknown type it uses the
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess </example>
fb77c505254b6e9c925e23e734463e87574f8f40kess <p>would be appropriate for a directory which contained many GIF
fb77c505254b6e9c925e23e734463e87574f8f40kess images with filenames missing the <code>.gif</code> extension.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="core">ForceType</directive>, this directive only
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive provides the default mime-type. All other mime-type definitions,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive including filename extensions, that might identify the media type
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive will override this default.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Enclose a group of directives that apply only to the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivenamed file-system directory and sub-directories</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive... </Directory></syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p><directive type="section">Directory</directive> and
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <code></Directory></code> are used to enclose a group of
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd directives that will apply only to the named directory and
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd sub-directories of that directory. Any directive that is allowed
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd in a directory context may be used. <var>Directory-path</var> is
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive either the full path to a directory, or a wild-card string using
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Unix shell-style matching. In a wild-card string, <code>?</code> matches
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive any single character, and <code>*</code> matches any sequences of
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive 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
fb77c505254b6e9c925e23e734463e87574f8f40kess <code>/home/user/public_html</code>, but <code><Directory
fb77c505254b6e9c925e23e734463e87574f8f40kess /home/*/public_html></code> will match. Example:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Options Indexes FollowSymLinks<br />
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding </Directory>
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding <p>Be careful with the <var>directory-path</var> arguments:
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding They have to literally match the filesystem path which Apache uses
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding 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
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <Directory ~ "^/www/.*/[0-9]{3}">
e4881891552e185a7408318dfc7f62ebabe73cf6niq </example>
e4881891552e185a7408318dfc7f62ebabe73cf6niq <p>would match directories in <code>/www/</code> that consisted of
e4881891552e185a7408318dfc7f62ebabe73cf6niq three numbers.</p>
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding match the directory (or one of its parents) containing a document,
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding then the directives are applied in the order of shortest match
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding first, interspersed with the directives from the <a
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding href="#accessfilename">.htaccess</a> files. For example,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <Directory /><br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive AllowOverride None<br />
6e483e0b8aa3fa574288a7452221392a03e2b9a3noodl </Directory><br />
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf <Directory /home/><br />
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf AllowOverride FileInfo<br />
6e483e0b8aa3fa574288a7452221392a03e2b9a3noodl </Directory>
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf </example>
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf <p>for access to the document <code>/home/web/dir/doc.html</code>
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf the steps are:</p>
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf <li>Apply directive <code>AllowOverride FileInfo</code> (for
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf <code>/home/.htaccess</code>, <code>/home/web/.htaccess</code> and
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf <p>Regular expressions are not considered until after all of the
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf normal sections have been applied. Then all of the regular
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf expressions are tested in the order they appeared in the
141fd59714368d3bbe3a3d8f5b8dc8a516c48f9fsf configuration file. For example, with</p>
cba8c0896ba04d42cf9a9e50df5040fd6bae14a4sf <Directory ~ abc$><br />
6e483e0b8aa3fa574288a7452221392a03e2b9a3noodl # ... directives here ...<br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </Directory>
898475b582dd849de5915df0f2089b72ed8b2e2bcovener <p>the regular expression section won't be considered until after
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd 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
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the corresponding <directive type="section">Directory</directive> will
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive be applied.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code><Directory /></code> is <code>Allow from All</code>.
898475b582dd849de5915df0f2089b72ed8b2e2bcovener This means that Apache will serve any file mapped from an URL. It is
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor recommended that you change this with a block such
fb77c505254b6e9c925e23e734463e87574f8f40kess <Directory /><br />
fb77c505254b6e9c925e23e734463e87574f8f40kess Order Deny,Allow<br />
fb77c505254b6e9c925e23e734463e87574f8f40kess Deny from All<br />
003f0c9fda6664daf5092a0e42f65ede20098153slive </Directory>
130d299c4b2b15be45532a176604c71fdc7bea5bnd href="/misc/security_tips.html">Security Tips</a> page for more
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>The directory sections occur in the <code>httpd.conf</code> file.
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <directive type="section">Directory</directive> directives
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd cannot nest, and cannot appear in a <directive module="core"
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd type="section">Limit</directive> or <directive module="core"
fb77c505254b6e9c925e23e734463e87574f8f40kess <Location> and <Files> sections work</a> for an
fb77c505254b6e9c925e23e734463e87574f8f40kess explanation of how these different sections are combined when a
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd request is received</seealso>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Enclose directives that apply to
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cndfile-system directories matching a regular expression and their
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cndsubdirectories</description>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd... </DirectoryMatch></syntax>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<contextlist><context>server config</context><context>virtual host</context>
fb77c505254b6e9c925e23e734463e87574f8f40kess</contextlist>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess <p><directive type="section">DirectoryMatch</directive> and
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <code></DirectoryMatch></code> are used to enclose a group
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess of directives which will apply only to the named directory and
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive sub-directories of that directory, the same as <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="core" type="section">Directory</directive>. However, it
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive takes as an argument a regular expression. For example:</p>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <DirectoryMatch "^/www/(.+/)?[0-9]{3}">
130d299c4b2b15be45532a176604c71fdc7bea5bnd </example>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>would match directories in <code>/www/</code> that consisted of three
130d299c4b2b15be45532a176604c71fdc7bea5bnd numbers.</p>
130d299c4b2b15be45532a176604c71fdc7bea5bnd<seealso><directive type="section" module="core">Directory</directive> for
cdffd1263801c18587cefdebc4510df486d5906brbowena description of how regular expressions are mixed in with normal
130d299c4b2b15be45532a176604c71fdc7bea5bnd<directive type="section">Directory</directive>s</seealso>
130d299c4b2b15be45532a176604c71fdc7bea5bndhref="/sections.html">How <Directory>, <Location> and
130d299c4b2b15be45532a176604c71fdc7bea5bnd<Files> sections work</a> for an explanation of how these different
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cndsections are combined when a request is received</seealso>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Directory that forms the main document tree visible
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivefrom the web</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax>DocumentRoot <var>directory-path</var></syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<default>DocumentRoot /usr/local/apache/htdocs</default>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess</contextlist>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess <p>This directive sets the directory from which <program>httpd</program>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess will serve files. Unless matched by a directive like <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_alias">Alias</directive>, the server appends the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive path from the requested URL to the document root to make the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive path to the document. Example:</p>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>then an access to
130d299c4b2b15be45532a176604c71fdc7bea5bnd <code>/usr/web/index.html</code>. If the <var>directory-path</var> is
130d299c4b2b15be45532a176604c71fdc7bea5bnd not absolute then it is assumed to be relative to the <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive>DocumentRoot</directive> should be specified without
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess a trailing slash.</p>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess<seealso><a href="/urlmapping.html">Mapping URLs to Filesystem
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
4e10c61d7f924071cad435df940a8f325015b2d3rbowen<description>Use memory-mapping to read files during delivery</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>directory</context><context>.htaccess</context>
130d299c4b2b15be45532a176604c71fdc7bea5bnd</contextlist>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>This directive controls whether the <program>httpd</program> may use
130d299c4b2b15be45532a176604c71fdc7bea5bnd memory-mapping if it needs to read the contents of a file during
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd 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
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive memory-maps the file if the OS supports it.</p>
fb77c505254b6e9c925e23e734463e87574f8f40kess <p>This memory-mapping sometimes yields a performance improvement.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive But in some environments, it is better to disable the memory-mapping
fb77c505254b6e9c925e23e734463e87574f8f40kess to prevent operational problems:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <li>On some multiprocessor systems, memory-mapping can reduce the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <li>With an NFS-mounted <directive module="core">DocumentRoot</directive>,
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess the <program>httpd</program> may crash due to a segmentation fault if a file
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess is deleted or truncated while the <program>httpd</program> 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>
898475b582dd849de5915df0f2089b72ed8b2e2bcovener EnableMMAP Off
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd </example>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <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">
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor EnableMMAP Off
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor </Directory>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Use the kernel sendfile support to deliver files to the client</description>
fa1c7ce09927decc1eecd1e9a35cc5331078a052covener<contextlist><context>server config</context><context>virtual host</context>
fa1c7ce09927decc1eecd1e9a35cc5331078a052covener<context>directory</context><context>.htaccess</context>
fa1c7ce09927decc1eecd1e9a35cc5331078a052covener</contextlist>
fa1c7ce09927decc1eecd1e9a35cc5331078a052covener<compatibility>Available in version 2.0.44 and later</compatibility>
fa1c7ce09927decc1eecd1e9a35cc5331078a052covener <p>This directive controls whether <program>httpd</program> may use the
fa1c7ce09927decc1eecd1e9a35cc5331078a052covener sendfile support from the kernel to transmit file contents to the client.
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor By default, when the handling of a request requires no access
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor to the data within a file -- for example, when delivering a
fa1c7ce09927decc1eecd1e9a35cc5331078a052covener static file -- Apache uses sendfile to deliver the file contents
fa1c7ce09927decc1eecd1e9a35cc5331078a052covener without ever reading the file if the OS supports it.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This sendfile mechanism avoids separate read and send operations,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive and buffer allocations. But on some platforms or within some
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess filesystems, it is better to disable this feature to avoid
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive operational problems:</p>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <li>Some platforms may have broken sendfile support that the build
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive 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
003f0c9fda6664daf5092a0e42f65ede20098153slive offloading bugs on certain networking cards when using IPv6.</li>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd 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,
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd you should disable this feature by specifying:</p>
fb77c505254b6e9c925e23e734463e87574f8f40kess EnableSendfile Off
fb77c505254b6e9c925e23e734463e87574f8f40kess </example>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>For NFS or SMB mounted files, this feature may be disabled explicitly
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd for the offending files by specifying:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <Directory "/path-to-nfs-files">
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor EnableSendfile Off
c68acc9d712af079afa2bd1a5a4aeef9a3ea573ckess </Directory>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
1b01d1ee11c612226cb3141eed4581dc179266c1rbowen<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>What the server will return to the client
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivein case of an error</description>
6b15044d54a096e6323ff1540f1a491e8de7622dsf<syntax>ErrorDocument <var>error-code</var> <var>document</var></syntax>
6b15044d54a096e6323ff1540f1a491e8de7622dsf<contextlist><context>server config</context><context>virtual host</context>
6b15044d54a096e6323ff1540f1a491e8de7622dsf</contextlist>
6b15044d54a096e6323ff1540f1a491e8de7622dsf<compatibility>Quoting syntax for text messages is different in Apache
6b15044d54a096e6323ff1540f1a491e8de7622dsf2.0</compatibility>
6b15044d54a096e6323ff1540f1a491e8de7622dsf <p>In the event of a problem or error, Apache can be configured
6b15044d54a096e6323ff1540f1a491e8de7622dsf to do one of four things,</p>
6b15044d54a096e6323ff1540f1a491e8de7622dsf <li>redirect to a local <var>URL-path</var> to handle the
6b15044d54a096e6323ff1540f1a491e8de7622dsf <p>The first option is the default, while options 2-4 are
6b15044d54a096e6323ff1540f1a491e8de7622dsf configured using the <directive>ErrorDocument</directive>
6b15044d54a096e6323ff1540f1a491e8de7622dsf directive, which is followed by the HTTP response code and a URL
6b15044d54a096e6323ff1540f1a491e8de7622dsf or a message. Apache will sometimes offer additional information
6b15044d54a096e6323ff1540f1a491e8de7622dsf <p>URLs can begin with a slash (/) for local URLs, or be a full
6b15044d54a096e6323ff1540f1a491e8de7622dsf URL which the client can resolve. Alternatively, a message can
6b15044d54a096e6323ff1540f1a491e8de7622dsf be provided to be displayed by the browser. Examples:</p>
6b15044d54a096e6323ff1540f1a491e8de7622dsf ErrorDocument 500 http://foo.example.com/cgi-bin/tester<br />
6b15044d54a096e6323ff1540f1a491e8de7622dsf ErrorDocument 403 "Sorry can't allow you access today"
6b15044d54a096e6323ff1540f1a491e8de7622dsf </example>
6b15044d54a096e6323ff1540f1a491e8de7622dsf <p>Additionally, the special value <code>default</code> can be used
6b15044d54a096e6323ff1540f1a491e8de7622dsf to specify Apache's simple hardcoded message. While not required
6b15044d54a096e6323ff1540f1a491e8de7622dsf under normal circumstances, <code>default</code> will restore
6b15044d54a096e6323ff1540f1a491e8de7622dsf Apache's simple hardcoded message for configurations that would
6b15044d54a096e6323ff1540f1a491e8de7622dsf otherwise inherit an existing <directive>ErrorDocument</directive>.</p>
6b15044d54a096e6323ff1540f1a491e8de7622dsf ErrorDocument 404 default<br />
6b15044d54a096e6323ff1540f1a491e8de7622dsf </Directory>
6b15044d54a096e6323ff1540f1a491e8de7622dsf </example>
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
6b15044d54a096e6323ff1540f1a491e8de7622dsf greater than 512 bytes, then MSIE will show the server-generated
6b15044d54a096e6323ff1540f1a491e8de7622dsf error rather than masking it. More information is available in
6b15044d54a096e6323ff1540f1a491e8de7622dsf Microsoft Knowledge Base article <a
6b15044d54a096e6323ff1540f1a491e8de7622dsf href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q294807"
6b15044d54a096e6323ff1540f1a491e8de7622dsf <p>Prior to version 2.0, messages were indicated by prefixing
6b15044d54a096e6323ff1540f1a491e8de7622dsf 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>
af18698b10b429b270551ca3a5d51a75e1c9db22brianp</contextlist>
fb77c505254b6e9c925e23e734463e87574f8f40kess <p>The <directive>ErrorLog</directive> directive sets the name of
fb77c505254b6e9c925e23e734463e87574f8f40kess the file to which the server will log any errors it encounters. If
af18698b10b429b270551ca3a5d51a75e1c9db22brianp the <var>file-path</var> is not absolute then it is assumed to be
af18698b10b429b270551ca3a5d51a75e1c9db22brianp relative to the <directive module="core">ServerRoot</directive>.</p>
003f0c9fda6664daf5092a0e42f65ede20098153slive begins with a pipe (|) then it is assumed to be a command to spawn
fb77c505254b6e9c925e23e734463e87574f8f40kess to handle the error log.</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd </example>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>Using <code>syslog</code> instead of a filename enables logging
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd via syslogd(8) if the system supports it. The default is to use
af18698b10b429b270551ca3a5d51a75e1c9db22brianp syslog facility <code>local7</code>, but you can override this by
af18698b10b429b270551ca3a5d51a75e1c9db22brianp using the <code>syslog:<var>facility</var></code> syntax where
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd <var>facility</var> can be one of the names usually documented in
13cbe1d8f52c8097cb581e7eb259693b64d41d10poirier syslog(1).</p>
13cbe1d8f52c8097cb581e7eb259693b64d41d10poirier ErrorLog syslog:user
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd href="/misc/security_tips.html#serverroot">security tips</a>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd document for details on why your security could be compromised
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd if the directory where log files are stored is writable by
fb77c505254b6e9c925e23e734463e87574f8f40kess anyone other than the user that starts the server.</p>
41ef8b3051855b802104193ee0a587515af60a37wrowe <p>When entering a file path on non-Unix platforms, care should be taken
41ef8b3051855b802104193ee0a587515af60a37wrowe to make sure that only forward slashed are used even though the platform
41ef8b3051855b802104193ee0a587515af60a37wrowe may allow the use of back slashes. In general it is a good idea to always
41ef8b3051855b802104193ee0a587515af60a37wrowe use forward slashes throughout the configuration files.</p>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<seealso><directive module="core">LogLevel</directive></seealso>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<seealso><a href="/logs.html">Apache Log Files</a></seealso>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess</directivesynopsis>
41ef8b3051855b802104193ee0a587515af60a37wrowe<directivesynopsis>
41ef8b3051855b802104193ee0a587515af60a37wrowe<description>File attributes used to create the ETag
41ef8b3051855b802104193ee0a587515af60a37wroweHTTP response header</description>
41ef8b3051855b802104193ee0a587515af60a37wrowe<contextlist><context>server config</context><context>virtual host</context>
fb77c505254b6e9c925e23e734463e87574f8f40kess<context>directory</context><context>.htaccess</context>
9c233808c898095865fcc0a2dc1cf594d0d8faf3sf</contextlist>
9c233808c898095865fcc0a2dc1cf594d0d8faf3sf The <directive>FileETag</directive> directive configures the file
9c233808c898095865fcc0a2dc1cf594d0d8faf3sf attributes that are used to create the <code>ETag</code> (entity
41ef8b3051855b802104193ee0a587515af60a37wrowe tag) response header field when the document is based on a file.
41ef8b3051855b802104193ee0a587515af60a37wrowe (The <code>ETag</code> value is used in cache management to save
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd network bandwidth.) In Apache 1.3.22 and earlier, the
41ef8b3051855b802104193ee0a587515af60a37wrowe from the file's inode, size, and last-modified time (mtime). The
41ef8b3051855b802104193ee0a587515af60a37wrowe <directive>FileETag</directive> directive allows you to choose
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen which of these -- if any -- should be used. The recognized keywords are:
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <dd>The file's i-node number will be included in the calculation</dd>
41ef8b3051855b802104193ee0a587515af60a37wrowe <dd>The date and time the file was last modified will be included</dd>
41ef8b3051855b802104193ee0a587515af60a37wrowe <dd>The number of bytes in the file will be included</dd>
9fb925624300c864fe3969a264e52aa83f3c2dd0slive <dd>All available fields will be used. This is equivalent to:
78f4d313fd5edf76dc5cfb8725e082a08cd29740jwoolley <dd>If a document is file-based, no <code>ETag</code> field will be
2025fe01de41805f6148851335693aa5ebe2faffnd included in the response</dd>
9c233808c898095865fcc0a2dc1cf594d0d8faf3sf <p>The <code>INode</code>, <code>MTime</code>, and <code>Size</code>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess keywords may be prefixed with either <code>+</code> or <code>-</code>,
9fb925624300c864fe3969a264e52aa83f3c2dd0slive which allow changes to be made to the default setting inherited
41ef8b3051855b802104193ee0a587515af60a37wrowe from a broader scope. Any keyword appearing without such a prefix
41ef8b3051855b802104193ee0a587515af60a37wrowe immediately and completely cancels the inherited setting.</p>
9c233808c898095865fcc0a2dc1cf594d0d8faf3sf <p>If a directory's configuration includes
41ef8b3051855b802104193ee0a587515af60a37wrowe <code>FileETag INode MTime Size</code>, and a
41ef8b3051855b802104193ee0a587515af60a37wrowe subdirectory's includes <code>FileETag -INode</code>,
9c233808c898095865fcc0a2dc1cf594d0d8faf3sf the setting for that subdirectory (which will be inherited by
41ef8b3051855b802104193ee0a587515af60a37wrowe any sub-subdirectories that don't override it) will be equivalent to
9fb925624300c864fe3969a264e52aa83f3c2dd0slive</directivesynopsis>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<description>Contains directives that apply to matched
313bb560bc5c323cfd40c9cad7335b4b8e060aedkessfilenames</description>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<syntax><Files <var>filename</var>> ... </Files></syntax>
41ef8b3051855b802104193ee0a587515af60a37wrowe<contextlist><context>server config</context><context>virtual host</context>
41ef8b3051855b802104193ee0a587515af60a37wrowe<context>directory</context><context>.htaccess</context>
832853bb93c1831daf24e4727c5ca0e1b1786e83lars</contextlist>
832853bb93c1831daf24e4727c5ca0e1b1786e83lars <p>The <directive type="section">Files</directive> directive
832853bb93c1831daf24e4727c5ca0e1b1786e83lars limits the scope of the enclosed directives by filename. It is comparable
af18698b10b429b270551ca3a5d51a75e1c9db22brianp to the <directive module="core" type="section">Directory</directive>
af18698b10b429b270551ca3a5d51a75e1c9db22brianp and <directive module="core" type="section">Location</directive>
af18698b10b429b270551ca3a5d51a75e1c9db22brianp directives. It should be matched with a <code></Files></code>
79c754eb51681c3389cd966753e902c429f78939trawick directive. The directives given within this section will be applied to
79c754eb51681c3389cd966753e902c429f78939trawick any object with a basename (last component of filename) matching the
79c754eb51681c3389cd966753e902c429f78939trawick specified filename. <directive type="section">Files</directive>
79c754eb51681c3389cd966753e902c429f78939trawick sections are processed in the order they appear in the
79c754eb51681c3389cd966753e902c429f78939trawick configuration file, after the <directive module="core"
79c754eb51681c3389cd966753e902c429f78939trawick <code>.htaccess</code> files are read, but before <directive
79c754eb51681c3389cd966753e902c429f78939trawick type="section" module="core">Location</directive> sections. Note
79c754eb51681c3389cd966753e902c429f78939trawick that <directive type="section">Files</directive> can be nested
79c754eb51681c3389cd966753e902c429f78939trawick module="core">Directory</directive> sections to restrict the
79c754eb51681c3389cd966753e902c429f78939trawick portion of the filesystem they apply to.</p>
79c754eb51681c3389cd966753e902c429f78939trawick <p>The <var>filename</var> argument should include a filename, or
79c754eb51681c3389cd966753e902c429f78939trawick a wild-card string, where <code>?</code> matches any single character,
79c754eb51681c3389cd966753e902c429f78939trawick and <code>*</code> matches any sequences of characters. Extended regular
79c754eb51681c3389cd966753e902c429f78939trawick expressions can also be used, with the addition of the
79c754eb51681c3389cd966753e902c429f78939trawick <Files ~ "\.(gif|jpe?g|png)$">
79c754eb51681c3389cd966753e902c429f78939trawick <p>would match most common Internet graphics formats. <directive
79c754eb51681c3389cd966753e902c429f78939trawick module="core" type="section">FilesMatch</directive> is preferred,
79c754eb51681c3389cd966753e902c429f78939trawick however.</p>
79c754eb51681c3389cd966753e902c429f78939trawick module="core">Directory</directive> and <directive type="section"
79c754eb51681c3389cd966753e902c429f78939trawick module="core">Location</directive> sections, <directive
79c754eb51681c3389cd966753e902c429f78939trawick type="section">Files</directive> sections can be used inside
79c754eb51681c3389cd966753e902c429f78939trawick <code>.htaccess</code> files. This allows users to control access to
79c754eb51681c3389cd966753e902c429f78939trawick their own files, at a file-by-file level.</p>
79c754eb51681c3389cd966753e902c429f78939trawick<seealso><a href="/sections.html">How <Directory>, <Location>
79c754eb51681c3389cd966753e902c429f78939trawick and <Files> sections work</a> for an explanation of how these
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive different sections are combined when a request is received</seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Contains directives that apply to regular-expression matched
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivefilenames</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax><FilesMatch <var>regex</var>> ... </FilesMatch></syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>directory</context><context>.htaccess</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive type="section">FilesMatch</directive> directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive limits the scope of the enclosed directives by filename, just as the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="core" type="section">Files</directive> directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive does. However, it accepts a regular expression. For example:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <FilesMatch "\.(gif|jpe?g|png)$">
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>would match most common Internet graphics formats.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<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>
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
69fba5b8aa0b0dc408f649cfdaab064ce120b05bslive<description>Forces all matching files to be served with the specified
69fba5b8aa0b0dc408f649cfdaab064ce120b05bsliveMIME content-type</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>directory</context><context>.htaccess</context>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</contextlist>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<compatibility>Moved to the core in Apache 2.0</compatibility>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive type="section" module="core">Directory</directive>, or
f7fe99050600166042c04b8e595fb75499eed7f0geoff <directive type="section" module="core">Location</directive> or
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen <directive type="section" module="core">Files</directive>
f7fe99050600166042c04b8e595fb75499eed7f0geoff section, this directive forces all matching files to be served
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen with the content type identification given by
f7fe99050600166042c04b8e595fb75499eed7f0geoff <var>MIME-type</var>. For example, if you had a directory full of
f7fe99050600166042c04b8e595fb75499eed7f0geoff GIF files, but did not want to label them all with <code>.gif</code>,
f7fe99050600166042c04b8e595fb75499eed7f0geoff you might want to use:</p>
f7fe99050600166042c04b8e595fb75499eed7f0geoff <p>Note that unlike <directive module="core">DefaultType</directive>,
f7fe99050600166042c04b8e595fb75499eed7f0geoff this directive overrides all mime-type associations, including
f7fe99050600166042c04b8e595fb75499eed7f0geoff filename extensions, that might identify the media type.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>You can override any <directive>ForceType</directive> setting
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <Location /images><br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </Location><br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive # but normal mime-type associations here:<br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive ForceType None<br />
fb77c505254b6e9c925e23e734463e87574f8f40kess </Location>
fb77c505254b6e9c925e23e734463e87574f8f40kess </example>
4f854c24127e28f7ad72ce9a39d4448aaf910fc1slive</directivesynopsis>
9b5e2c5e769dc678a1aca06df75c32022b2f1492trawick<directivesynopsis>
fb77c505254b6e9c925e23e734463e87574f8f40kess<description>Enables DNS lookups on client IP addresses</description>
69fba5b8aa0b0dc408f649cfdaab064ce120b05bslive<contextlist><context>server config</context><context>virtual host</context>
69fba5b8aa0b0dc408f649cfdaab064ce120b05bslive <p>This directive enables DNS lookups so that host names can be
69fba5b8aa0b0dc408f649cfdaab064ce120b05bslive logged (and passed to CGIs/SSIs in <code>REMOTE_HOST</code>).
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor The value <code>Double</code> refers to doing double-reverse
b5d3d68a9f683722eac7a3ca507c3e571908dfc0rbowen DNS lookup. That is, after a reverse lookup is performed, a forward
b5d3d68a9f683722eac7a3ca507c3e571908dfc0rbowen lookup is then performed on that result. At least one of the IP
b5d3d68a9f683722eac7a3ca507c3e571908dfc0rbowen addresses in the forward lookup must match the original
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen address. (In "tcpwrappers" terminology this is called
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Regardless of the setting, when <module>mod_authz_host</module> is
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive used for controlling access by hostname, a double reverse lookup
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive will be performed. This is necessary for security. Note that the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive result of this double-reverse isn't generally available unless you
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive set <code>HostnameLookups Double</code>. For example, if only
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>HostnameLookups On</code> and a request is made to an object
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess that is protected by hostname restrictions, regardless of whether
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd the double-reverse fails or not, CGIs will still be passed the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The default is <code>Off</code> in order to save the network
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive 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
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor <code>Off</code>, since DNS lookups can take considerable
c68acc9d712af079afa2bd1a5a4aeef9a3ea573ckess amounts of time. The utility <program>logresolve</program>, compiled by
fb109b84906e3ee61680aa289953c2f9e859354erbowen default to the <code>bin</code> subdirectory of your installation
fb109b84906e3ee61680aa289953c2f9e859354erbowen directory, can be used to look up host names from logged IP addresses
fb109b84906e3ee61680aa289953c2f9e859354erbowen offline.</p>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Encloses directives that will be processed only
fb109b84906e3ee61680aa289953c2f9e859354erbowenif a test is true at startup</description>
fb109b84906e3ee61680aa289953c2f9e859354erbowen<syntax><IfDefine [!]<var>parameter-name</var>> ...
fb109b84906e3ee61680aa289953c2f9e859354erbowen </IfDefine></syntax>
fb109b84906e3ee61680aa289953c2f9e859354erbowen<contextlist><context>server config</context><context>virtual host</context>
960188481b7025ac8ef7221b67af83dd27e46cd0rjung<context>directory</context><context>.htaccess</context>
960188481b7025ac8ef7221b67af83dd27e46cd0rjung</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <code><IfDefine <var>test</var>>...</IfDefine>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd </code> section is used to mark directives that are conditional. The
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd directives within an <directive type="section">IfDefine</directive>
5155e92c6100b47513159eee1b2b9914ab204a5acovener section are only processed if the <var>test</var> is true. If <var>
5155e92c6100b47513159eee1b2b9914ab204a5acovener test</var> is false, everything between the start and end markers is
5155e92c6100b47513159eee1b2b9914ab204a5acovener ignored.</p>
fb109b84906e3ee61680aa289953c2f9e859354erbowen <p>The <var>test</var> in the <directive type="section"
fb109b84906e3ee61680aa289953c2f9e859354erbowen >IfDefine</directive> section directive can be one of two forms:</p>
2bac697634d965d9d9a921a99a68b2c454c8a95dbnicholes <p>In the former case, the directives between the start and end
2bac697634d965d9d9a921a99a68b2c454c8a95dbnicholes markers are only processed if the parameter named
d950cf9262224a223e2ff5c51393708071e14b94covener <var>parameter-name</var> is defined. The second format reverses
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor the test, and only processes the directives if
2bac697634d965d9d9a921a99a68b2c454c8a95dbnicholes <var>parameter-name</var> is <strong>not</strong> defined.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <var>parameter-name</var> argument is a define as given on
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the <program>httpd</program> command line via <code>-D<var>parameter-</var>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p><directive type="section">IfDefine</directive> sections are
e302f38fd646764ce1a1e1c578d794aef514a9e5sf nest-able, which can be used to implement simple
e302f38fd646764ce1a1e1c578d794aef514a9e5sf multiple-parameter tests. Example:</p>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf httpd -DReverseProxy ...<br />
e302f38fd646764ce1a1e1c578d794aef514a9e5sf <IfDefine ReverseProxy><br />
e302f38fd646764ce1a1e1c578d794aef514a9e5sf </IfDefine>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf </example>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf</directivesynopsis>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<description>Encloses directives that are processed conditional on the
b89fea36d9c12cec3344576824f4e6798da90ad4rbowenpresence or absence of a specific module</description>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<syntax><IfModule [!]<var>module-file</var>|<var>module-identifier</var>> ...
e302f38fd646764ce1a1e1c578d794aef514a9e5sf </IfModule></syntax>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<contextlist><context>server config</context><context>virtual host</context>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf</contextlist>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<compatibility>Module identifiers are available in version 2.1 and
e302f38fd646764ce1a1e1c578d794aef514a9e5sflater.</compatibility>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf <p>The <code><IfModule <var>test</var>>...</IfModule></code>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf section is used to mark directives that are conditional on the presence of
e302f38fd646764ce1a1e1c578d794aef514a9e5sf a specific module. The directives within an <directive type="section"
e302f38fd646764ce1a1e1c578d794aef514a9e5sf >IfModule</directive> section are only processed if the <var>test</var>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf is true. If <var>test</var> is false, everything between the start and
e302f38fd646764ce1a1e1c578d794aef514a9e5sf end markers is ignored.</p>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf >IfModule</directive> section directive can be one of two forms:</p>
b5c4b00201fdc3ed11c6cc05cf3f9a7912ac0cfbsf <p>In the former case, the directives between the start and end
b5c4b00201fdc3ed11c6cc05cf3f9a7912ac0cfbsf markers are only processed if the module named <var>module</var>
b5c4b00201fdc3ed11c6cc05cf3f9a7912ac0cfbsf is included in Apache -- either compiled in or
b5c4b00201fdc3ed11c6cc05cf3f9a7912ac0cfbsf >LoadModule</directive>. The second format reverses the test,
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen and only processes the directives if <var>module</var> is
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen <p>The <var>module</var> argument can be either the module identifier or
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen the file name of the module, at the time it was compiled. For example,
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen <code>mod_rewrite.c</code> is the file name. If a module consists of
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen several source files, use the name of the file containing the string
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen <p><directive type="section">IfModule</directive> sections are
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen nest-able, which can be used to implement simple multiple-module
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen <note>This section should only be used if you need to have one
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen configuration file that works whether or not a specific module
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen is available. In normal operation, directives need not be
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen placed in <directive type="section">IfModule</directive>
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen sections.</note>
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen</directivesynopsis>
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen<directivesynopsis>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<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>
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen <p>This directive allows inclusion of other configuration files
e302f38fd646764ce1a1e1c578d794aef514a9e5sf from within the server configuration files.</p>
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen <p>Shell-style (<code>fnmatch()</code>) wildcard characters can be used to
e302f38fd646764ce1a1e1c578d794aef514a9e5sf include several files at once, in alphabetical order. In
e302f38fd646764ce1a1e1c578d794aef514a9e5sf addition, if <directive>Include</directive> points to a directory,
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen rather than a file, Apache will read all files in that directory
0b5f11662dee7135ff8dd04311a4ee6df7fe2b1crbowen and any subdirectory. But including entire directories is not
4497075b5e08b0c8ee89425a1758258ae80550fcsf recommended, because it is easy to accidentally leave temporary
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen files in a directory that can cause <program>httpd</program> to
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen <p>The file path specified may be an absolute path, or may be relative
e302f38fd646764ce1a1e1c578d794aef514a9e5sf to the <directive module="core">ServerRoot</directive> directory.</p>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf </example>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf </example>
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen <p>Running <code>apachectl configtest</code> will give you a list
e302f38fd646764ce1a1e1c578d794aef514a9e5sf of the files that are being processed during the configuration
e302f38fd646764ce1a1e1c578d794aef514a9e5sf check:</p>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf root@host# apachectl configtest<br />
e302f38fd646764ce1a1e1c578d794aef514a9e5sf Processing config file: /usr/local/apache2/conf/ssl.conf<br />
e302f38fd646764ce1a1e1c578d794aef514a9e5sf Processing config file: /usr/local/apache2/conf/vhosts/vhost1.conf<br />
e302f38fd646764ce1a1e1c578d794aef514a9e5sf Processing config file: /usr/local/apache2/conf/vhosts/vhost2.conf<br />
e302f38fd646764ce1a1e1c578d794aef514a9e5sf</directivesynopsis>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<directivesynopsis>
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen<description>Enables HTTP persistent connections</description>
b08558bf6a64f9501ad3eca34eaf4d978bd928cfsf<contextlist><context>server config</context><context>virtual host</context>
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen</contextlist>
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen <p>The Keep-Alive extension to HTTP/1.0 and the persistent
e302f38fd646764ce1a1e1c578d794aef514a9e5sf connection feature of HTTP/1.1 provide long-lived HTTP sessions
e302f38fd646764ce1a1e1c578d794aef514a9e5sf 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
9228509ac5da8374df4a5d50b7da139e7b31f8a3sf <p>For HTTP/1.0 clients, Keep-Alive connections will only be
9228509ac5da8374df4a5d50b7da139e7b31f8a3sf used if they are specifically requested by a client. In
9228509ac5da8374df4a5d50b7da139e7b31f8a3sf addition, a Keep-Alive connection with an HTTP/1.0 client can
b89fea36d9c12cec3344576824f4e6798da90ad4rbowen only be used when the length of the content is known in
9228509ac5da8374df4a5d50b7da139e7b31f8a3sf advance. This implies that dynamic content such as CGI output,
9228509ac5da8374df4a5d50b7da139e7b31f8a3sf SSI pages, and server-generated directory listings will
9228509ac5da8374df4a5d50b7da139e7b31f8a3sf generally not use Keep-Alive connections to HTTP/1.0 clients.
9228509ac5da8374df4a5d50b7da139e7b31f8a3sf For HTTP/1.1 clients, persistent connections are the default
e302f38fd646764ce1a1e1c578d794aef514a9e5sf unless otherwise specified. If the client requests it, chunked
e302f38fd646764ce1a1e1c578d794aef514a9e5sf encoding will be used in order to send content of unknown
e302f38fd646764ce1a1e1c578d794aef514a9e5sf length over persistent connections.</p>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<seealso><directive module="core">MaxKeepAliveRequests</directive></seealso>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf</directivesynopsis>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<directivesynopsis>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<description>Amount of time the server will wait for subsequent
e302f38fd646764ce1a1e1c578d794aef514a9e5sfrequests on a persistent connection</description>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<contextlist><context>server config</context><context>virtual host</context>
abdaaa23d72ef7e7ff91eab9c5581d40130680c1rbowen</contextlist>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf <p>The number of seconds Apache will wait for a subsequent
e302f38fd646764ce1a1e1c578d794aef514a9e5sf request before closing the connection. Once a request has been
abdaaa23d72ef7e7ff91eab9c5581d40130680c1rbowen received, the timeout value specified by the
abdaaa23d72ef7e7ff91eab9c5581d40130680c1rbowen <directive module="core">Timeout</directive> directive applies.</p>
abdaaa23d72ef7e7ff91eab9c5581d40130680c1rbowen <p>Setting <directive>KeepAliveTimeout</directive> to a high value
abdaaa23d72ef7e7ff91eab9c5581d40130680c1rbowen may cause performance problems in heavily loaded servers. The
abdaaa23d72ef7e7ff91eab9c5581d40130680c1rbowen higher the timeout, the more server processes will be kept
abdaaa23d72ef7e7ff91eab9c5581d40130680c1rbowen occupied waiting on connections with idle clients.</p>
abdaaa23d72ef7e7ff91eab9c5581d40130680c1rbowen</directivesynopsis>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<description>Restrict enclosed access controls to only certain HTTP
e302f38fd646764ce1a1e1c578d794aef514a9e5sfmethods</description>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<syntax><Limit <var>method</var> [<var>method</var>] ... > ...
b5c4b00201fdc3ed11c6cc05cf3f9a7912ac0cfbsf </Limit></syntax>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf<contextlist><context>server config</context><context>virtual host</context>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf</contextlist>
e302f38fd646764ce1a1e1c578d794aef514a9e5sf <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
e302f38fd646764ce1a1e1c578d794aef514a9e5sf <directive type="section">Limit</directive> section.</strong></p>
a8ee031b2224ce5473826c9d4f603681589245fawrowe <p>The purpose of the <directive type="section">Limit</directive>
a8ee031b2224ce5473826c9d4f603681589245fawrowe directive is to restrict the effect of the access controls to the
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor nominated HTTP methods. For all other methods, the access
a8ee031b2224ce5473826c9d4f603681589245fawrowe restrictions that are enclosed in the <directive
a8ee031b2224ce5473826c9d4f603681589245fawrowe type="section">Limit</directive> bracket <strong>will have no
a8ee031b2224ce5473826c9d4f603681589245fawrowe effect</strong>. The following example applies the access control
a8ee031b2224ce5473826c9d4f603681589245fawrowe only to the methods <code>POST</code>, <code>PUT</code>, and
a8ee031b2224ce5473826c9d4f603681589245fawrowe <code>DELETE</code>, leaving all other methods unprotected:</p>
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor <Limit POST PUT DELETE><br />
a8ee031b2224ce5473826c9d4f603681589245fawrowe Require valid-user<br />
a8ee031b2224ce5473826c9d4f603681589245fawrowe </Limit>
a8ee031b2224ce5473826c9d4f603681589245fawrowe <p>The method names listed can be one or more of: <code>GET</code>,
a8ee031b2224ce5473826c9d4f603681589245fawrowe <code>POST</code>, <code>PUT</code>, <code>DELETE</code>,
a8ee031b2224ce5473826c9d4f603681589245fawrowe <code>PATCH</code>, <code>PROPFIND</code>, <code>PROPPATCH</code>,
34b157732214cedcd129cd9fe7c4290757505d60minfrin <code>MKCOL</code>, <code>COPY</code>, <code>MOVE</code>,
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor <code>LOCK</code>, and <code>UNLOCK</code>. <strong>The method name is
a8ee031b2224ce5473826c9d4f603681589245fawrowe case-sensitive.</strong> If <code>GET</code> is used it will also
a8ee031b2224ce5473826c9d4f603681589245fawrowe restrict <code>HEAD</code> requests. The <code>TRACE</code> method
a8ee031b2224ce5473826c9d4f603681589245fawrowe cannot be limited.</p>
34b157732214cedcd129cd9fe7c4290757505d60minfrin module="core">LimitExcept</directive> section should always be
34b157732214cedcd129cd9fe7c4290757505d60minfrin module="core">Limit</directive> section when restricting access,
a8ee031b2224ce5473826c9d4f603681589245fawrowe module="core">LimitExcept</directive> section provides protection
a8ee031b2224ce5473826c9d4f603681589245fawrowe against arbitrary methods.</note>
003f0c9fda6664daf5092a0e42f65ede20098153slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Restrict access controls to all HTTP methods
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveexcept the named ones</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax><LimitExcept <var>method</var> [<var>method</var>] ... > ...
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </LimitExcept></syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>directory</context><context>.htaccess</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
fb77c505254b6e9c925e23e734463e87574f8f40kess <p><directive type="section">LimitExcept</directive> and
c976a7c7d20f2be319b128dd7d0b1568da224c0arbowen <code></LimitExcept></code> are used to enclose
fb77c505254b6e9c925e23e734463e87574f8f40kess a group of access control directives which will then apply to any
fb77c505254b6e9c925e23e734463e87574f8f40kess HTTP access method <strong>not</strong> listed in the arguments;
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive i.e., it is the opposite of a <directive type="section"
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd module="core">Limit</directive> section and can be used to control
530eba85dbd41b8a0fa5255d3648d1440199a661slive both standard and nonstandard/unrecognized methods. See the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive type="section">Limit</directive> for more details.</p>
530eba85dbd41b8a0fa5255d3648d1440199a661slive <LimitExcept POST GET><br />
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd Require valid-user<br />
fb77c505254b6e9c925e23e734463e87574f8f40kess </LimitExcept>
fb77c505254b6e9c925e23e734463e87574f8f40kess </example>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<description>Determine maximum number of internal redirects and nested
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cndsubrequests</description>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<syntax>LimitInternalRecursion <var>number</var> [<var>number</var>]</syntax>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<compatibility>Available in Apache 2.0.47 and later</compatibility>
0db981f8fdfb62c5149efa079f0369b73d472d04rpluem <p>An internal redirect happens, for example, when using the <directive
0db981f8fdfb62c5149efa079f0369b73d472d04rpluem module="mod_actions">Action</directive> directive, which internally
0db981f8fdfb62c5149efa079f0369b73d472d04rpluem redirects the original request to a CGI script. A subrequest is Apache's
0db981f8fdfb62c5149efa079f0369b73d472d04rpluem mechanism to find out what would happen for some URI if it were requested.
0db981f8fdfb62c5149efa079f0369b73d472d04rpluem For example, <module>mod_dir</module> uses subrequests to look for the
0db981f8fdfb62c5149efa079f0369b73d472d04rpluem files listed in the <directive module="mod_dir">DirectoryIndex</directive>
0db981f8fdfb62c5149efa079f0369b73d472d04rpluem directive.</p>
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor <p><directive>LimitInternalRecursion</directive> prevents the server
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor from crashing when entering an infinite loop of internal redirects or
a5f060e0c74a44cb8896ae794c08f94f7c9a46a7covener subrequests. Such loops are usually caused by misconfigurations.</p>
a5f060e0c74a44cb8896ae794c08f94f7c9a46a7covener <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
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <var>number</var>, it will be assigned to both limits.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive LimitInternalRecursion 5
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd </example>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
003f0c9fda6664daf5092a0e42f65ede20098153slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Restricts the total size of the HTTP request body sent
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivefrom the client</description>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess<contextlist><context>server config</context><context>virtual host</context>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess<context>directory</context><context>.htaccess</context>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive specifies the number of <var>bytes</var> from 0
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive (meaning unlimited) to 2147483647 (2GB) that are allowed in a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive request body.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive>LimitRequestBody</directive> directive allows
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the user to set a limit on the allowed size of an HTTP request
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive message body within the context in which the directive is given
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive (server, per-directory, per-file or per-location). If the client
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive request exceeds that limit, the server will return an error
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd response instead of servicing the request. The size of a normal
fb77c505254b6e9c925e23e734463e87574f8f40kess request message body will vary greatly depending on the nature of
030108b1816bcda3d925df65357feabdce83bc94slive the resource and the methods allowed on that resource. CGI scripts
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor typically use the message body for retrieving form information.
030108b1816bcda3d925df65357feabdce83bc94slive Implementations of the <code>PUT</code> method will require
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive 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
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd control over abnormal client request behavior, which may be
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd useful for avoiding some forms of denial-of-service
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess attacks.</p>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <p>If, for example, you are permitting file upload to a particular
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive location, and wish to limit the size of the uploaded file to 100K,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive you might use the following directive:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive LimitRequestBody 102400
fb77c505254b6e9c925e23e734463e87574f8f40kess </example>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Limits the number of HTTP request header fields that
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivewill be accepted from the client</description>
003f0c9fda6664daf5092a0e42f65ede20098153slive<contextlist><context>server config</context></contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <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
003f0c9fda6664daf5092a0e42f65ede20098153slive distributed).</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive>LimitRequestFields</directive> directive allows
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the server administrator to modify the limit on the number of
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess 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
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor client request might include. The number of request header fields
030108b1816bcda3d925df65357feabdce83bc94slive used by a client rarely exceeds 20, but this may vary among
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd different client implementations, often depending upon the extent
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd to which a user has configured their browser to support detailed
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd content negotiation. Optional HTTP extensions are often expressed
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd using request header fields.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive gives the server administrator greater
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive control over abnormal client request behavior, which may be
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess useful for avoiding some forms of denial-of-service attacks.
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess The value should be increased if normal clients see an error
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess response from the server that indicates too many fields were
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess sent in the request.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive LimitRequestFields 50
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Limits the size of the HTTP request header allowed from the
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveclient</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax>LimitRequestFieldsize <var>bytes</var></syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context></contextlist>
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding <p>This directive specifies the number of <var>bytes</var>
fb77c505254b6e9c925e23e734463e87574f8f40kess that will be allowed in an HTTP request header.</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>The <directive>LimitRequestFieldSize</directive> directive
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd allows the server administrator to reduce or increase the limit
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd on the allowed size of an HTTP request header field. A server
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd needs this value to be large enough to hold any one header field
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive from a normal client request. The size of a normal request header
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding field will vary greatly among different client implementations,
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding often depending upon the extent to which a user has configured
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding their browser to support detailed content negotiation. SPNEGO
7654193c1faf603feec999850322ad79e6c551bcnd authentication headers can be up to 12392 bytes.</p>
b24c77ceb4cea5ffa92536e19f0aa83608960dc4fielding <p>This directive gives the server administrator greater
c97e8972ab1f4dd167e3dc4db87daf91114009fbnd control over abnormal client request behavior, which may be
7654193c1faf603feec999850322ad79e6c551bcnd useful for avoiding some forms of denial-of-service attacks.</p>
7654193c1faf603feec999850322ad79e6c551bcnd LimitRequestFieldSize 4094
7654193c1faf603feec999850322ad79e6c551bcnd </example>
7654193c1faf603feec999850322ad79e6c551bcnd <note>Under normal conditions, the value should not be changed from
7654193c1faf603feec999850322ad79e6c551bcnd the default.</note>
c97e8972ab1f4dd167e3dc4db87daf91114009fbnd</directivesynopsis>
7654193c1faf603feec999850322ad79e6c551bcnd<directivesynopsis>
439acee10571861c670c438038a62f90a08bf137covener<description>Limit the size of the HTTP request line that will be accepted
439acee10571861c670c438038a62f90a08bf137covenerfrom the client</description>
439acee10571861c670c438038a62f90a08bf137covener<contextlist><context>server config</context></contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive sets the number of <var>bytes</var> that will be
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener allowed on the HTTP request-line.</p>
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener <p>The <directive>LimitRequestLine</directive> directive allows
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener the server administrator to reduce or increase the limit on the allowed size
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener of a client's HTTP request-line. Since the request-line consists of the
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener HTTP method, URI, and protocol version, the
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener <directive>LimitRequestLine</directive> directive places a
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener restriction on the length of a request-URI allowed for a request
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener on the server. A server needs this value to be large enough to
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener hold any of its resource names, including any information that
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener might be passed in the query part of a <code>GET</code> request.</p>
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener <p>This directive gives the server administrator greater
c3e2e664a67b1adb9b6a6b91ff161f4f562cecf6covener control over abnormal client request behavior, which may be
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor useful for avoiding some forms of denial-of-service attacks.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive LimitRequestLine 4094
fb77c505254b6e9c925e23e734463e87574f8f40kess <note>Under normal conditions, the value should not be changed from
fb77c505254b6e9c925e23e734463e87574f8f40kess the default.</note>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Limits the size of an XML-based request body</description>
9b5e2c5e769dc678a1aca06df75c32022b2f1492trawick<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>directory</context><context>.htaccess</context></contextlist>
9ed9eaf871c58d281af02e76125ceadb5060afa5nd <p>Limit (in bytes) on maximum size of an XML-based request
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive body. A value of <code>0</code> will disable any checking.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive LimitXMLRequestBody 0
fb77c505254b6e9c925e23e734463e87574f8f40kess</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Applies the enclosed directives only to matching
fb77c505254b6e9c925e23e734463e87574f8f40kessURLs</description>
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd<syntax><Location
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd <var>URL-path</var>|<var>URL</var>> ... </Location></syntax>
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd<contextlist><context>server config</context><context>virtual host</context>
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive type="section">Location</directive> directive
750d12c59545dbbac70390988de94f7e901b08f2niq limits the scope of the enclosed directives by URL. It is similar to the
750d12c59545dbbac70390988de94f7e901b08f2niq <directive type="section" module="core">Directory</directive>
750d12c59545dbbac70390988de94f7e901b08f2niq directive, and starts a subsection which is terminated with a
750d12c59545dbbac70390988de94f7e901b08f2niq type="section">Location</directive> sections are processed in the
750d12c59545dbbac70390988de94f7e901b08f2niq order they appear in the configuration file, after the <directive
750d12c59545dbbac70390988de94f7e901b08f2niq type="section" module="core">Directory</directive> sections and
750d12c59545dbbac70390988de94f7e901b08f2niq <code>.htaccess</code> files are read, and after the <directive
750d12c59545dbbac70390988de94f7e901b08f2niq type="section" module="core">Files</directive> sections.</p>
750d12c59545dbbac70390988de94f7e901b08f2niq <p><directive type="section">Location</directive> sections operate
750d12c59545dbbac70390988de94f7e901b08f2niq completely outside the filesystem. This has several consequences.
750d12c59545dbbac70390988de94f7e901b08f2niq Most importantly, <directive type="section">Location</directive>
750d12c59545dbbac70390988de94f7e901b08f2niq directives should not be used to control access to filesystem
750d12c59545dbbac70390988de94f7e901b08f2niq locations. Since several different URLs may map to the same
750d12c59545dbbac70390988de94f7e901b08f2niq filesystem location, such access controls may by circumvented.</p>
6b15044d54a096e6323ff1540f1a491e8de7622dsf <p>Use <directive type="section">Location</directive> to apply
6b15044d54a096e6323ff1540f1a491e8de7622dsf directives to content that lives outside the filesystem. For
6b15044d54a096e6323ff1540f1a491e8de7622dsf content that lives in the filesystem, use <directive
6b15044d54a096e6323ff1540f1a491e8de7622dsf type="section" module="core">Directory</directive> and <directive
6b15044d54a096e6323ff1540f1a491e8de7622dsf type="section" module="core">Files</directive>. An exception is
1a0ca5f6b566a5eb77d63f466fcf78fb388a4182igalic apply a configuration to the entire server.</p>
1a0ca5f6b566a5eb77d63f466fcf78fb388a4182igalic <p>For all origin (non-proxy) requests, the URL to be matched is a
1a0ca5f6b566a5eb77d63f466fcf78fb388a4182igalic URL-path of the form <code>/path/</code>. No scheme, hostname,
6b15044d54a096e6323ff1540f1a491e8de7622dsf port, or query string may be included. For proxy requests, the
6b15044d54a096e6323ff1540f1a491e8de7622dsf URL to be matched is of the form
6b15044d54a096e6323ff1540f1a491e8de7622dsf <code>scheme://servername/path</code>, and you must include the
6b15044d54a096e6323ff1540f1a491e8de7622dsf prefix.</p>
6b15044d54a096e6323ff1540f1a491e8de7622dsf <p>The URL may use wildcards. In a wild-card string, <code>?</code> matches
750d12c59545dbbac70390988de94f7e901b08f2niq any single character, and <code>*</code> matches any sequences of
750d12c59545dbbac70390988de94f7e901b08f2niq characters.</p>
94aba9caa9b2f7a0e95a55f51264c908b69470e2igalic <p>Extended regular
6b15044d54a096e6323ff1540f1a491e8de7622dsf expressions can also be used, with the addition of the
750d12c59545dbbac70390988de94f7e901b08f2niq <Location ~ "/(extra|special)/data">
6b15044d54a096e6323ff1540f1a491e8de7622dsf </example>
6b15044d54a096e6323ff1540f1a491e8de7622dsf <p>would match URLs that contained the substring <code>/extra/data</code>
750d12c59545dbbac70390988de94f7e901b08f2niq type="section" module="core">LocationMatch</directive> behaves
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive identical to the regex version of <directive
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd functionality is especially useful when combined with the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directive. For example, to enable status requests, but allow them
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive only from browsers at <code>foo.com</code>, you might use:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <Location /status><br />
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd SetHandler server-status<br />
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd Order Deny,Allow<br />
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd Deny from all<br />
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd </Location>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The slash character has special meaning depending on where in a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive URL it appears. People may be used to its behavior in the filesystem
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd where multiple adjacent slashes are frequently collapsed to a single
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive slash (<em>i.e.</em>, <code>/home///foo</code> is the same as
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <code>/home/foo</code>). In URL-space this is not necessarily true.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive The <directive type="section" module="core">LocationMatch</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directive and the regex version of <directive type="section"
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive >Location</directive> require you to explicitly specify multiple
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive slashes if that is your intention.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>For example, <code><LocationMatch ^/abc></code> would match
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd the request URL <code>/abc</code> but not the request URL <code>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive //abc</code>. The (non-regex) <directive type="section"
6e483e0b8aa3fa574288a7452221392a03e2b9a3noodl >Location</directive> directive behaves similarly when used for
6e483e0b8aa3fa574288a7452221392a03e2b9a3noodl proxy requests. But when (non-regex) <directive type="section"
6e483e0b8aa3fa574288a7452221392a03e2b9a3noodl >Location</directive> is used for non-proxy requests it will
6e483e0b8aa3fa574288a7452221392a03e2b9a3noodl implicitly match multiple slashes with a single slash. For example,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive if you specify <code><Location /abc/def></code> and the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive request is to <code>/abc//def</code> then it will match.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><a href="/sections.html">How <Directory>, <Location>
130d299c4b2b15be45532a176604c71fdc7bea5bnd and <Files> sections work</a> for an explanation of how these
a00429a6b3b4dbb113b6dc67cfc0507f610276e9takashi different sections are combined when a request is received</seealso>
130d299c4b2b15be45532a176604c71fdc7bea5bnd</directivesynopsis>
a00429a6b3b4dbb113b6dc67cfc0507f610276e9takashi<description>Applies the enclosed directives only to regular-expression
a00429a6b3b4dbb113b6dc67cfc0507f610276e9takashimatching URLs</description>
955d7fc3e7adb6463b7243e15c04e858718e799etakashi<syntax><LocationMatch
955d7fc3e7adb6463b7243e15c04e858718e799etakashi <var>regex</var>> ... </LocationMatch></syntax>
955d7fc3e7adb6463b7243e15c04e858718e799etakashi<contextlist><context>server config</context><context>virtual host</context>
955d7fc3e7adb6463b7243e15c04e858718e799etakashi</contextlist>
955d7fc3e7adb6463b7243e15c04e858718e799etakashi <p>The <directive type="section">LocationMatch</directive> directive
955d7fc3e7adb6463b7243e15c04e858718e799etakashi limits the scope of the enclosed directives by URL, in an identical manner
955d7fc3e7adb6463b7243e15c04e858718e799etakashi to <directive module="core" type="section">Location</directive>. However,
955d7fc3e7adb6463b7243e15c04e858718e799etakashi it takes a regular expression as an argument instead of a simple
78f97ce162b66a0dbfd7af4dcd9984f162569b04minfrin string. For example:</p>
955d7fc3e7adb6463b7243e15c04e858718e799etakashi <LocationMatch "/(extra|special)/data">
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>would match URLs that contained the substring <code>/extra/data</code>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<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>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
55d36f9b61520c2374ab463e77e8a62daa416398nd<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Controls the verbosity of the ErrorLog</description>
003f0c9fda6664daf5092a0e42f65ede20098153slive<contextlist><context>server config</context><context>virtual host</context>
55d36f9b61520c2374ab463e77e8a62daa416398nd</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p><directive>LogLevel</directive> adjusts the verbosity of the
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd messages recorded in the error logs (see <directive
fb77c505254b6e9c925e23e734463e87574f8f40kess module="core">ErrorLog</directive> directive). The following
fb77c505254b6e9c925e23e734463e87574f8f40kess <var>level</var>s are available, in order of decreasing
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd significance:</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <columnspec><column width=".2"/><column width=".3"/><column width=".5"/>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd </columnspec>
bea526116133aa3d7dabd1924bfc580b37fbf22aslive <td>"getpwuid: couldn't determine user name from uid"</td>
fb77c505254b6e9c925e23e734463e87574f8f40kess <td>"socket: Failed to get a socket, exiting child"</td>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <td>"child process 1234 did not exit, sending another
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive SIGHUP"</td>
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen <td>"httpd: caught SIGBUS, attempting to dump core in
3621f3acee323a877639a96d84891095eb07933aminfrin <td>"Server seems busy, (you may need to increase
3621f3acee323a877639a96d84891095eb07933aminfrin <p>When a particular level is specified, messages from all
3621f3acee323a877639a96d84891095eb07933aminfrin other levels of higher significance will be reported as well.
3621f3acee323a877639a96d84891095eb07933aminfrin <em>E.g.</em>, when <code>LogLevel info</code> is specified,
cf8a8738330694e60bad421fcc8361d80b0e9124minfrin then messages with log levels of <code>notice</code> and
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor recommended.</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd LogLevel notice
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>When logging to a regular file messages of the level
7b5535ed88e0f561b3bfb3330137bd804846afd4slive <code>notice</code> cannot be suppressed and thus are always
7b5535ed88e0f561b3bfb3330137bd804846afd4slive logged. However, this doesn't apply when logging is done
7b5535ed88e0f561b3bfb3330137bd804846afd4slive</directivesynopsis>
cf8a8738330694e60bad421fcc8361d80b0e9124minfrin<directivesynopsis>
3621f3acee323a877639a96d84891095eb07933aminfrin<description>Number of requests allowed on a persistent
3621f3acee323a877639a96d84891095eb07933aminfrinconnection</description>
3621f3acee323a877639a96d84891095eb07933aminfrin<syntax>MaxKeepAliveRequests <var>number</var></syntax>
cf8a8738330694e60bad421fcc8361d80b0e9124minfrin<contextlist><context>server config</context><context>virtual host</context>
3621f3acee323a877639a96d84891095eb07933aminfrin</contextlist>
cf8a8738330694e60bad421fcc8361d80b0e9124minfrin <p>The <directive>MaxKeepAliveRequests</directive> directive
3621f3acee323a877639a96d84891095eb07933aminfrin limits the number of requests allowed per connection when
3621f3acee323a877639a96d84891095eb07933aminfrin <directive module="core" >KeepAlive</directive> is on. If it is
03aa31ad82759363ba1a55589e517b16308ef635minfrin set to <code>0</code>, unlimited requests will be allowed. We
3621f3acee323a877639a96d84891095eb07933aminfrin recommend that this setting be kept to a high value for maximum
3621f3acee323a877639a96d84891095eb07933aminfrin server performance.</p>
03aa31ad82759363ba1a55589e517b16308ef635minfrin MaxKeepAliveRequests 500
3621f3acee323a877639a96d84891095eb07933aminfrin</directivesynopsis>
03aa31ad82759363ba1a55589e517b16308ef635minfrin<directivesynopsis>
03aa31ad82759363ba1a55589e517b16308ef635minfrin<description>Designates an IP address for name-virtual
03aa31ad82759363ba1a55589e517b16308ef635minfrinhosting</description>
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor<syntax>NameVirtualHost <var>addr</var>[:<var>port</var>]</syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context></contextlist>
fb77c505254b6e9c925e23e734463e87574f8f40kess <p>The <directive>NameVirtualHost</directive> directive is a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive required directive if you want to configure <a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Although <var>addr</var> can be hostname it is recommended
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive NameVirtualHost 111.22.33.44
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <p>With the <directive>NameVirtualHost</directive> directive you
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess specify the IP address on which the server will receive requests
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive for the name-based virtual hosts. This will usually be the address
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive to which your name-based virtual host names resolve. In cases
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive where a firewall or other proxy receives the requests and forwards
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive them on a different IP address to the server, you must specify the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive IP address of the physical interface on the machine which will be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive servicing the requests. If you have multiple name-based hosts on
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive multiple addresses, repeat the directive for each address.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Note, that the "main server" and any <code>_default_</code> servers
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive will <strong>never</strong> be served for a request to a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive>NameVirtualHost</directive> IP address (unless for some
891df99fdfa41fc8a486568f4d31ddf4a571258adreid reason you specify <directive>NameVirtualHost</directive> but then
891df99fdfa41fc8a486568f4d31ddf4a571258adreid don't define any <directive>VirtualHost</directive>s for that
59368b594c9b09b59ae58c7de26d2d5ce1c99a29takashi address).</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Optionally you can specify a port number on which the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive NameVirtualHost 111.22.33.44:8080
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick <p>IPv6 addresses must be enclosed in square brackets, as shown
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick in the following example:</p>
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick NameVirtualHost [fe80::a00:20ff:fea7:ccea]:8080
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen <p>To receive requests on all interfaces, you can use an argument of
9f38f3ec3e8087985d108a24ae796962fef83644takashi NameVirtualHost *
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick <note><title>Argument to <directive type="section">VirtualHost</directive>
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick directive</title>
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick type="section">VirtualHost</directive> directive must
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick exactly match the argument to the <directive
ffec3e56ff5331a2d732ec07e9d107303fed43f4covener NameVirtualHost 1.2.3.4<br />
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick <VirtualHost 1.2.3.4><br />
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick # ...<br />
98f5034c8cbf2ef025b317b3e01acae82e143b11trawick </VirtualHost><br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Configures what features are available in a particular
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivedirectory</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax>Options
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive [+|-]<var>option</var> [[+|-]<var>option</var>] ...</syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>directory</context><context>.htaccess</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <p>The <directive>Options</directive> directive controls which
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess server features are available in a particular directory.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p><var>option</var> can be set to <code>None</code>, in which
130d299c4b2b15be45532a176604c71fdc7bea5bnd case none of the extra features are enabled, or one or more of
130d299c4b2b15be45532a176604c71fdc7bea5bnd the following:</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <dd>All options except for <code>MultiViews</code>. This is the default
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd setting.</dd>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd is permitted.</dd>
4bb78e7cdd53f50240cff4ad7a97c7ed36483797slive The server will follow symbolic links in this directory.
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd <p>Even though the server follows the symlink it does <em>not</em>
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd change the pathname used to match against <directive type="section"
4bb78e7cdd53f50240cff4ad7a97c7ed36483797slive <p>Note also, that this option <strong>gets ignored</strong> if set
4bb78e7cdd53f50240cff4ad7a97c7ed36483797slive inside a <directive type="section" module="core">Location</directive>
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd section.</p>
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd Server-side includes provided by <module>mod_include</module>
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd are permitted.</dd>
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd Server-side includes are permitted, but the <code>#exec
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd cmd</code> and <code>#exec cgi</code> are disabled. It is still
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd possible to <code>#include virtual</code> CGI scripts from
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd <directive module="mod_alias">ScriptAlias</directive>ed
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd directories.</dd>
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd If a URL which maps to a directory is requested, and there
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd is no <directive module="mod_dir">DirectoryIndex</directive>
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor (<em>e.g.</em>, <code>index.html</code>) in that directory, then
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd <module>mod_autoindex</module> will return a formatted listing
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd of the directory.</dd>
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd <a href="/content-negotiation.html">Content negotiated</a>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive "MultiViews" are allowed using
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <dd>The server will only follow symbolic links for which the
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess target file or directory is owned by the same user id as the
7245e9b991db85d9d9a587fe5f4051f642ebdc3cchrisd <note><title>Note</title> This option gets ignored if
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen <p>Normally, if multiple <directive>Options</directive> could
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen apply to a directory, then the most specific one is used and
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess others are ignored; the options are not merged. (See <a
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen href="/sections.html#mergin">how sections are merged</a>.)
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive>Options</directive> directive are preceded by a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>+</code> or <code>-</code> symbol, the options are
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive merged. Any options preceded by a <code>+</code> are added to the
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen options currently in force, and any options preceded by a
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen <code>-</code> are removed from the options currently in
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen force. </p>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>For example, without any <code>+</code> and <code>-</code> symbols:</p>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen Options Indexes FollowSymLinks<br />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </Directory><br />
03e0a375c2435102fb2b51e34cccff52acbfddcdnd Options Includes<br />
03e0a375c2435102fb2b51e34cccff52acbfddcdnd </Directory>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd </example>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd <code>/web/docs/spec</code> directory. However if the second
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen <directive>Options</directive> directive uses the <code>+</code> and
03e0a375c2435102fb2b51e34cccff52acbfddcdnd Options Indexes FollowSymLinks<br />
03e0a375c2435102fb2b51e34cccff52acbfddcdnd </Directory><br />
03e0a375c2435102fb2b51e34cccff52acbfddcdnd Options +Includes -Indexes<br />
03e0a375c2435102fb2b51e34cccff52acbfddcdnd </Directory>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd </example>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd <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>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The default in the absence of any other settings is
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Selects which authenticated users can access
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivea resource</description>
003f0c9fda6664daf5092a0e42f65ede20098153slive<syntax>Require <var>entity-name</var> [<var>entity-name</var>] ...</syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>directory</context><context>.htaccess</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
6fad623c3cc52b4a84d4d36538f6eed886f49f98covener <p>This directive selects which authenticated users can access
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive a resource. The allowed syntaxes are:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <dt><code>Require user <var>userid</var> [<var>userid</var>]
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <dd>Only the named users can access the resource.</dd>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <dt><code>Require group <var>group-name</var> [<var>group-name</var>]
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <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
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen as <directive module="mod_authn_file">AuthUserFile</directive>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen and <directive module="mod_authz_groupfile">AuthGroupFile</directive> (to
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess define users and groups) in order to work correctly. Example:</p>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen AuthType Basic<br />
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd AuthName "Restricted Resource"<br />
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor Require group admin
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen <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
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive place the <directive>Require</directive> statement into a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="core" type="section">Limit</directive>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess section.</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<seealso><directive module="core">Satisfy</directive></seealso>
e0ef044feba0082771091af42798cada5bb1f4fcrbowen</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Limits the CPU consumption of processes launched
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveby Apache children</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax>RLimitCPU <var>seconds</var>|max [<var>seconds</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
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
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the server is running as <code>root</code>, or in the initial startup
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This applies to processes forked off from Apache children
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive servicing requests, not the Apache children themselves. This
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive includes CGI scripts and SSI exec commands, but not any
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen processes forked off from the Apache parent such as piped
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen <p>CPU resource limits are expressed in seconds per
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd process.</p>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<seealso><directive module="core">RLimitMEM</directive></seealso>
2f505ba07f89ba6a175d6ceae67fb273c4eb0993covener<seealso><directive module="core">RLimitNPROC</directive></seealso>
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor</directivesynopsis>
ffec3e56ff5331a2d732ec07e9d107303fed43f4covener<directivesynopsis>
611f7fd8a0a5ee4a29eeed79dfd8bf6faaa3c613covener<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>
ae134ecc8faf4e6a8eb68e1c3724506771442a46rbowen <p>Takes 1 or 2 parameters. The first parameter sets the soft
e0ef044feba0082771091af42798cada5bb1f4fcrbowen 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
72580dbc2a55511f13f377063725b9f143b20826stoddard be set to the maximum allowed by the operating system
72580dbc2a55511f13f377063725b9f143b20826stoddard configuration. Raising the maximum resource limit requires that
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the server is running as <code>root</code>, or in the initial startup
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess phase.</p>
72580dbc2a55511f13f377063725b9f143b20826stoddard <p>This applies to processes forked off from Apache children
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor servicing requests, not the Apache children themselves. This
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor includes CGI scripts and SSI exec commands, but not any
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor processes forked off from the Apache parent such as piped
72580dbc2a55511f13f377063725b9f143b20826stoddard <p>Memory resource limits are expressed in bytes per
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive process.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">RLimitCPU</directive></seealso>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<seealso><directive module="core">RLimitNPROC</directive></seealso>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen</directivesynopsis>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<directivesynopsis>
ef8e89e090461194ecadd31e8796a2c51e0531a2kess<description>Limits the number of processes that can be launched by
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowenprocesses launched by Apache children</description>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<syntax>RLimitNPROC <var>number</var>|max [<var>number</var>|max]</syntax>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<default>Unset; uses operating system defaults</default>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<contextlist><context>server config</context><context>virtual host</context>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<context>directory</context><context>.htaccess</context></contextlist>
ffec3e56ff5331a2d732ec07e9d107303fed43f4covener <p>Takes 1 or 2 parameters. The first parameter sets the soft
611f7fd8a0a5ee4a29eeed79dfd8bf6faaa3c613covener 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
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
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>This applies to processes forked off from Apache children
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive servicing requests, not the Apache children themselves. This
e0ef044feba0082771091af42798cada5bb1f4fcrbowen includes CGI scripts and SSI exec commands, but not any
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive processes forked off from the Apache parent such as piped
72580dbc2a55511f13f377063725b9f143b20826stoddard <p>Process limits control the number of processes per user.</p>
72580dbc2a55511f13f377063725b9f143b20826stoddard <p>If CGI processes are <strong>not</strong> running
72580dbc2a55511f13f377063725b9f143b20826stoddard under user ids other than the web server user id, this directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive will limit the number of processes that the server itself can
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive 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>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<directivesynopsis>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<description>Interaction between host-level access control and
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowenuser authentication</description>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<contextlist><context>directory</context><context>.htaccess</context>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen</contextlist>
611f7fd8a0a5ee4a29eeed79dfd8bf6faaa3c613covener<compatibility>Influenced by <directive module="core" type="section"
031bbbc0d1189b07330e38d0c126820a9ab7795egryzortype="section">LimitExcept</directive> in version 2.0.51 and
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjimlater</compatibility>
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
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive 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
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess passes the address access restriction <em>and</em> enters a valid
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive username and password. With the <code>Any</code> option the client will be
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele granted access if they either pass the host restriction or enter a
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele valid username and password. This can be used to password restrict
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele an area, but to let clients from particular addresses in without
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive prompting for a password.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>For example, if you wanted to let people on your network have
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive unrestricted access to a portion of your website, but require that
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen people outside of your network provide a password, you could use a
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen configuration similar to the following:</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd Require valid-user<br />
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen Allow from 192.168.1<br />
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen Satisfy Any
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Since version 2.0.51 <directive>Satisfy</directive> directives can
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive be restricted to particular methods by <directive module="core"
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive type="section">Limit</directive> and <directive module="core" type="section"
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <seealso><directive module="mod_authz_host">Allow</directive></seealso>
fb77c505254b6e9c925e23e734463e87574f8f40kess <seealso><directive module="core">Require</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Technique for locating the interpreter for CGI
6b64034fa2a644ba291c484c0c01c7df5b8d982ckessscripts</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax>ScriptInterpreterSource Registry|Registry-Strict|Script</syntax>
7852e17fb37b2a02ccdcab107f2c7f5fd41fd201nd<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>directory</context><context>.htaccess</context></contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<compatibility>Win32 only;
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveoption <code>Registry-Strict</code> is available in Apache 2.0 and
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivelater</compatibility>
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive <p>This directive is used to control how Apache finds the
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive interpreter used to run CGI scripts. The default setting is
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive <code>Script</code>. This causes Apache to use the interpreter pointed to
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive by the shebang line (first line, starting with <code>#!</code>) in the
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive script. On Win32 systems this line usually looks like:</p>
d950cf9262224a223e2ff5c51393708071e14b94covener <p>or, if <code>perl</code> is in the <code>PATH</code>, simply:</p>
d950cf9262224a223e2ff5c51393708071e14b94covener <p>Setting <code>ScriptInterpreterSource Registry</code> will
d950cf9262224a223e2ff5c51393708071e14b94covener cause the Windows Registry tree <code>HKEY_CLASSES_ROOT</code> to be
d950cf9262224a223e2ff5c51393708071e14b94covener searched using the script file extension (e.g., <code>.pl</code>) as a
e4e60c2f7ba8f12b687f588b89e413842e9f2d76igalic search key. The command defined by the registry subkey
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor <code>Shell\ExecCGI\Command</code> or, if it does not exist, by the subkey
d950cf9262224a223e2ff5c51393708071e14b94covener <code>Shell\Open\Command</code> is used to open the script file. If the
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor registry keys cannot be found, Apache falls back to the behavior of the
d950cf9262224a223e2ff5c51393708071e14b94covener <p>Be careful when using <code>ScriptInterpreterSource
e4e60c2f7ba8f12b687f588b89e413842e9f2d76igalic module="mod_alias">ScriptAlias</directive>'ed directories, because
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor Apache will try to execute <strong>every</strong> file within this
d950cf9262224a223e2ff5c51393708071e14b94covener directory. The <code>Registry</code> setting may cause undesired
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor program calls on files which are typically not executed. For
e4e60c2f7ba8f12b687f588b89e413842e9f2d76igalic example, the default open command on <code>.htm</code> files on
d950cf9262224a223e2ff5c51393708071e14b94covener 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
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive <p>The option <code>Registry-Strict</code> which is new in Apache
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive 2.0 does the same thing as <code>Registry</code> but uses only the
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive <code>ExecCGI</code> key is not a common one. It must be
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive configured manually in the windows registry and hence prevents
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive accidental program calls on your system.</p>
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
beb923bec9bff2b49ce5027df2fe944e2b74e28brederpj<description>Email address that the server includes in error
beb923bec9bff2b49ce5027df2fe944e2b74e28brederpjmessages sent to the client</description>
dc223428958ad9ff05011545bcdda000887b93e5slive<syntax>ServerAdmin <var>email-address</var>|<var>URL</var></syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
fb77c505254b6e9c925e23e734463e87574f8f40kess <p>The <directive>ServerAdmin</directive> sets the contact address
d8c44cd75cf575fe51319280c12445109e878523noodl that the server includes in any error messages it returns to the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive client. If the <code>httpd</code> doesn't recognize the supplied argument
030108b1816bcda3d925df65357feabdce83bc94slive as an URL, it
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor assumes, that it's an <var>email-address</var> and prepends it with
37742b630743e470b94618ecb3560fbd82e50b59rbowen <code>mailto:</code> in hyperlink targets. However, it's recommended to
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd actually use an email address, since there are a lot of CGI scripts that
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd make that assumption. If you want to use an URL, it should point to another
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd server under your control. Otherwise users may not be able to contact you in
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd case of errors.</p>
fb77c505254b6e9c925e23e734463e87574f8f40kess <p>It may be worth setting up a dedicated address for this, e.g.</p>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess ServerAdmin www-admin@foo.example.com
37742b630743e470b94618ecb3560fbd82e50b59rbowen <p>as users do not always mention that they are talking about the
37742b630743e470b94618ecb3560fbd82e50b59rbowen server!</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
e8811b6d38f756b325446ded5d96857d13856511takashi<description>Alternate names for a host used when matching requests
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cndto name-virtual hosts</description>
130d299c4b2b15be45532a176604c71fdc7bea5bnd<syntax>ServerAlias <var>hostname</var> [<var>hostname</var>] ...</syntax>
130d299c4b2b15be45532a176604c71fdc7bea5bnd<contextlist><context>virtual host</context></contextlist>
ca908c21f63a71c5efa7d32bd2cfafe9a42ba1fbrbowen <p>The <directive>ServerAlias</directive> directive sets the
130d299c4b2b15be45532a176604c71fdc7bea5bnd alternate names for a host, for use with <a
130d299c4b2b15be45532a176604c71fdc7bea5bnd href="/vhosts/name-based.html">name-based virtual hosts</a>.</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <VirtualHost *><br />
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd # ...<br />
05201775eaa6b363b8a119c8aea5db246b967591yoshiki </VirtualHost>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd </example>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<seealso><a href="/vhosts/">Apache Virtual Host documentation</a></seealso>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</directivesynopsis>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<description>Hostname and port that the server uses to identify
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnditself</description>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<syntax>ServerName <var>fully-qualified-domain-name</var>[:<var>port</var>]</syntax>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<contextlist><context>server config</context><context>virtual host</context>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</contextlist>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<compatibility>In version 2.0, this
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd directive supersedes the functionality of the <directive>Port</directive>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd directive from version 1.3.</compatibility>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <p>The <directive>ServerName</directive> directive sets the hostname and
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess port that the server uses to identify itself. This is used when
37742b630743e470b94618ecb3560fbd82e50b59rbowen creating redirection URLs. For example, if the name of the
37742b630743e470b94618ecb3560fbd82e50b59rbowen machine hosting the web server is <code>simple.example.com</code>,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive but the machine also has the DNS alias <code>www.example.com</code>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive and you wish the web server to be so identified, the following
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directive should be used:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive ServerName www.example.com:80
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>If no <directive>ServerName</directive> is specified, then the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive server attempts to deduce the hostname by performing a reverse
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive lookup on the IP address. If no port is specified in the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive>ServerName</directive>, then the server will use the port
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive from the incoming
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess request. For optimal reliability and predictability, you should
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess 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
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="core">UseCanonicalName</directive> directive for
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess settings which determine whether self-referential URL's (e.g., by the
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess specified port, or to the port number given in the client's request.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><a href="/dns-caveats.html">Issues Regarding DNS and
7fbd7281d06cec1918aa370214df77c572f871a9sf<seealso><directive module="core">UseCanonicalName</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">NameVirtualHost</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">ServerAlias</directive></seealso>
7fbd7281d06cec1918aa370214df77c572f871a9sf</directivesynopsis>
7fbd7281d06cec1918aa370214df77c572f871a9sf<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Legacy URL pathname for a name-based virtual host that
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveis accessed by an incompatible browser</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>virtual host</context></contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive>ServerPath</directive> directive sets the legacy
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive URL pathname for a host, for use with <a
1597043cec6ad37fa4154bf09b0fccdabed1a239slive<seealso><a href="/vhosts/">Apache Virtual Host documentation</a></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Base directory for the server installation</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context></contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive>ServerRoot</directive> directive sets the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directory in which the server lives. Typically it will contain the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive subdirectories <code>conf/</code> and <code>logs/</code>. Relative
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive paths in other configuration directives (such as <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_so">LoadModule</directive>, for example) are taken as
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive relative to this directory.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><a href="/misc/security_tips.html#serverroot">the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive security tips</a> for information on how to properly set
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive permissions on the <directive>ServerRoot</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Configures the footer on server-generated documents</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<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>
7fbd7281d06cec1918aa370214df77c572f871a9sf <p>This directive controls whether <code>Server</code> response
7fbd7281d06cec1918aa370214df77c572f871a9sf header field which is sent back to clients includes a
7fbd7281d06cec1918aa370214df77c572f871a9sf description of the generic OS-type of the server as well as
7fbd7281d06cec1918aa370214df77c572f871a9sf information about compiled-in modules.</p>
7fbd7281d06cec1918aa370214df77c572f871a9sf <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>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<compatibility>Moved into the core in Apache 2.0</compatibility>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>When placed into an <code>.htaccess</code> file or a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive type="section" module="core">Directory</directive> or
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive type="section" module="core">Location</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive section, this directive forces all matching files to be parsed
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive through the <a href="/handler.html">handler</a> given by
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen <var>handler-name</var>. For example, if you had a directory you
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen wanted to be parsed entirely as imagemap rule files, regardless
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen of extension, you might put the following into an
8b052d682204371decc64f942aede5ef1da98955erikabele SetHandler imap-file
8b052d682204371decc64f942aede5ef1da98955erikabele <p>Another example: if you wanted to have the server display a
8b052d682204371decc64f942aede5ef1da98955erikabele status report whenever a URL of
8b052d682204371decc64f942aede5ef1da98955erikabele <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>
7fbd7281d06cec1918aa370214df77c572f871a9sf<seealso><directive module="mod_mime">AddHandler</directive></seealso>
7fbd7281d06cec1918aa370214df77c572f871a9sf</directivesynopsis>
7fbd7281d06cec1918aa370214df77c572f871a9sf<directivesynopsis>
7fbd7281d06cec1918aa370214df77c572f871a9sf<description>Sets the filters that will process client requests and POST
7fbd7281d06cec1918aa370214df77c572f871a9sfinput</description>
7fbd7281d06cec1918aa370214df77c572f871a9sf<syntax>SetInputFilter <var>filter</var>[;<var>filter</var>...]</syntax>
7fbd7281d06cec1918aa370214df77c572f871a9sf<contextlist><context>server config</context><context>virtual host</context>
7fbd7281d06cec1918aa370214df77c572f871a9sf</contextlist>
7fbd7281d06cec1918aa370214df77c572f871a9sf <p>The <directive>SetInputFilter</directive> directive sets the
7fbd7281d06cec1918aa370214df77c572f871a9sf filter or filters which will process client requests and POST
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive input when they are received by the server. This is in addition to
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive any filters defined elsewhere, including the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="mod_mime">AddInputFilter</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directive.</p>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <p>If more than one filter is specified, they must be separated
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive by semicolons in the order in which they should process the
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd content.</p>
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele<seealso><a href="/filter.html">Filters</a> documentation</seealso>
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Sets the filters that will process responses from the
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveserver</description>
fb77c505254b6e9c925e23e734463e87574f8f40kess<syntax>SetOutputFilter <var>filter</var>[;<var>filter</var>...]</syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>directory</context><context>.htaccess</context>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen</contextlist>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>The <directive>SetOutputFilter</directive> directive sets the filters
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd which will process responses from the server before they are
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive sent to the client. This is in addition to any filters defined
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive elsewhere, including the
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <directive module="mod_mime">AddOutputFilter</directive>
6beba165aeced2ca77a6f1593ee08c47a32099efcovener directive.</p>
6beba165aeced2ca77a6f1593ee08c47a32099efcovener <p>For example, the following configuration will process all files
6beba165aeced2ca77a6f1593ee08c47a32099efcovener in the <code>/www/data/</code> directory for server-side
7a975d0413ba303546b7619e4785cb641f7f09fdcovener includes.</p>
6beba165aeced2ca77a6f1593ee08c47a32099efcovener SetOutputFilter INCLUDES<br />
6beba165aeced2ca77a6f1593ee08c47a32099efcovener </Directory>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <p>If more than one filter is specified, they must be separated
6beba165aeced2ca77a6f1593ee08c47a32099efcovener by semicolons in the order in which they should process the
7a975d0413ba303546b7619e4785cb641f7f09fdcovener content.</p>
7a975d0413ba303546b7619e4785cb641f7f09fdcovener<seealso><a href="/filter.html">Filters</a> documentation</seealso>
7a975d0413ba303546b7619e4785cb641f7f09fdcovener</directivesynopsis>
7a975d0413ba303546b7619e4785cb641f7f09fdcovener<directivesynopsis>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim<description>Amount of time the server will wait for
7a975d0413ba303546b7619e4785cb641f7f09fdcovenercertain events before failing a request</description>
7a975d0413ba303546b7619e4785cb641f7f09fdcovener<contextlist><context>server config</context></contextlist>
7a975d0413ba303546b7619e4785cb641f7f09fdcovener <p>The <directive>TimeOut</directive> directive currently defines
7a975d0413ba303546b7619e4785cb641f7f09fdcovener the amount of time Apache will wait for three things:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <li>The total amount of time it takes to receive a GET
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim request.</li>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <li>The amount of time between receipt of TCP packets on a
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim POST or PUT request.</li>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <li>The amount of time between ACKs on transmissions of TCP
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim packets in responses.</li>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <p>We plan on making these separately configurable at some point
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim 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
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim necessary in most situations. It is not set any lower by
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim default because there may still be odd places in the code where
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim the timer is not reset when a packet is sent. </p>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim</directivesynopsis>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim<directivesynopsis>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim<description>Configures how the server determines its own name and
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjimport</description>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim<contextlist><context>server config</context><context>virtual host</context>
f7acc4b00a8bf92fea10fce6ac09aa57eafec0ecjim <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>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick they may be broken by this option. The client is essentially free
a0fed3e26656887c8458aa1081d516d08ced3c84trawick to give whatever value they want as a hostname. But if the CGI is
a0fed3e26656887c8458aa1081d516d08ced3c84trawick only using <code>SERVER_NAME</code> to construct self-referential URLs
a0fed3e26656887c8458aa1081d516d08ced3c84trawick then it should be just fine.</p>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick<seealso><directive module="core">ServerName</directive></seealso>
88d86cfadffe2275a3dfb67a4d7bdc018630b661rbowen<seealso><directive module="mpm_common">Listen</directive></seealso>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick</directivesynopsis>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick<description>Contains directives that apply only to a specific
a0fed3e26656887c8458aa1081d516d08ced3c84trawickhostname or IP address</description>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick<syntax><VirtualHost
a0fed3e26656887c8458aa1081d516d08ced3c84trawick <var>addr</var>[:<var>port</var>] [<var>addr</var>[:<var>port</var>]]
a0fed3e26656887c8458aa1081d516d08ced3c84trawick ...> ... </VirtualHost></syntax>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick<contextlist><context>server config</context></contextlist>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick <p><directive type="section">VirtualHost</directive> and
a0fed3e26656887c8458aa1081d516d08ced3c84trawick <code></VirtualHost></code> are used to enclose a group of
a0fed3e26656887c8458aa1081d516d08ced3c84trawick directives that will apply only to a particular virtual host. Any
a0fed3e26656887c8458aa1081d516d08ced3c84trawick directive that is allowed in a virtual host context may be
a0fed3e26656887c8458aa1081d516d08ced3c84trawick used. When the server receives a request for a document on a
a0fed3e26656887c8458aa1081d516d08ced3c84trawick particular virtual host, it uses the configuration directives
a0fed3e26656887c8458aa1081d516d08ced3c84trawick enclosed in the <directive type="section">VirtualHost</directive>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick <li>A fully qualified domain name for the IP address of the
a0fed3e26656887c8458aa1081d516d08ced3c84trawick virtual host;</li>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick <li>The character <code>*</code>, which is used only in combination with
a0fed3e26656887c8458aa1081d516d08ced3c84trawick <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>
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor <VirtualHost 10.1.2.3><br />
a0fed3e26656887c8458aa1081d516d08ced3c84trawick ServerAdmin webmaster@host.foo.com<br />
a0fed3e26656887c8458aa1081d516d08ced3c84trawick </VirtualHost>
bf0e7f6393e91c0a7c15cb0d889a4238c973dc2etrawick <p>IPv6 addresses must be specified in square brackets because
bf0e7f6393e91c0a7c15cb0d889a4238c973dc2etrawick the optional port number could not be determined otherwise. An
bf0e7f6393e91c0a7c15cb0d889a4238c973dc2etrawick IPv6 example is shown below:</p>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick <VirtualHost [fe80::a00:20ff:fea7:ccea]><br />
a0fed3e26656887c8458aa1081d516d08ced3c84trawick ServerAdmin webmaster@host.example.com<br />
bf0e7f6393e91c0a7c15cb0d889a4238c973dc2etrawick </VirtualHost>
bf0e7f6393e91c0a7c15cb0d889a4238c973dc2etrawick <p>Each Virtual Host must correspond to a different IP address,
bf0e7f6393e91c0a7c15cb0d889a4238c973dc2etrawick different port number or a different host name for the server,
bf0e7f6393e91c0a7c15cb0d889a4238c973dc2etrawick 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
a0fed3e26656887c8458aa1081d516d08ced3c84trawick <strong>not</strong> affect what addresses Apache listens on. You
a0fed3e26656887c8458aa1081d516d08ced3c84trawick may need to ensure that Apache is listening on the correct addresses
a0fed3e26656887c8458aa1081d516d08ced3c84trawick using <directive module="mpm_common">Listen</directive>.</p>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick <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
a0fed3e26656887c8458aa1081d516d08ced3c84trawick 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.
a0fed3e26656887c8458aa1081d516d08ced3c84trawick See the <a href="/vhosts/name-based.html">name-based virtual hosting</a>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick documentation for further details.)</p>
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor <p>You can specify a <code>:port</code> to change the port that is
a0fed3e26656887c8458aa1081d516d08ced3c84trawick matched. If unspecified then it defaults to the same port as the
a0fed3e26656887c8458aa1081d516d08ced3c84trawick most recent <directive module="mpm_common">Listen</directive>
a0fed3e26656887c8458aa1081d516d08ced3c84trawick 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 log files 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>
031bbbc0d1189b07330e38d0c126820a9ab7795egryzor</directivesynopsis>
215694531f7d868b906df96e22a80e6a1d2326a6lgentis</modulesynopsis>