core.xml revision bbc62a0c1ee4c8cd36759bfe0ba5af84ddea2780
530eba85dbd41b8a0fa5255d3648d1440199a661slive<!DOCTYPE modulesynopsis SYSTEM "/style/modulesynopsis.dtd">
e942c741056732f50da2074b36fe59805d370650slive<?xml-stylesheet type="text/xsl" href="/style/manual.en.xsl"?>
5f5d1b4cc970b7f06ff8ef6526128e9a27303d88nd<!-- $LastChangedRevision$ -->
08cb74ca432a8c24e39f17dedce527e6a47b8001jerenkrantz Licensed to the Apache Software Foundation (ASF) under one or more
08cb74ca432a8c24e39f17dedce527e6a47b8001jerenkrantz contributor license agreements. See the NOTICE file distributed with
d5d794fc2f4cc9ca6d6da17cfa2cdcd8d244bacdnd this work for additional information regarding copyright ownership.
d5d794fc2f4cc9ca6d6da17cfa2cdcd8d244bacdnd The ASF licenses this file to You under the Apache License, Version 2.0
d5d794fc2f4cc9ca6d6da17cfa2cdcd8d244bacdnd (the "License"); you may not use this file except in compliance with
d5d794fc2f4cc9ca6d6da17cfa2cdcd8d244bacdnd the License. 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>Configures optimizations for a Protocol's Listener Sockets</description>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna<syntax>AcceptFilter <var>protocol</var> <var>accept_filter</var></syntax>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna<contextlist><context>server config</context></contextlist>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna <p>This directive enables operating system specific optimizations for a
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna listening socket by the <directive>Protocol</directive> type.
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna The basic premise is for the kernel to not send a socket to the server
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna process until either data is received or an entire HTTP Request is buffered.
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna Only <a href="http://www.freebsd.org/cgi/man.cgi?query=accept_filter&sektion=9">
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna FreeBSD's Accept Filters</a>, Linux's more primitive
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna <code>TCP_DEFER_ACCEPT</code>, and Windows' optimized AcceptEx()
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna are currently supported.</p>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna <p>Using <code>none</code> for an argument will disable any accept filters
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna for that protocol. This is useful for protocols that require a server
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna send data first, such as <code>ftp:</code> or <code>nntp</code>:</p>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna AcceptFilter nntp none
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna </highlight>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna <p>The default protocol names are <code>https</code> for port 443
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna and <code>http</code> for all other ports. To specify another protocol
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna is being used with a listening port, add the <var>protocol</var>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna argument to the <directive module="mpm_common">Listen</directive>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna directive.</p>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquernaAcceptFilter http httpready
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquernaAcceptFilter https dataready
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna </highlight>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna <p>The <code>httpready</code> accept filter buffers entire HTTP requests at
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna the kernel level. Once an entire request is received, the kernel then
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna sends it to the server. See the
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna <a href="http://www.freebsd.org/cgi/man.cgi?query=accf_http&sektion=9">
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna accf_http(9)</a> man page for more details. Since HTTPS requests are
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna encrypted only the <a href="http://www.freebsd.org/cgi/man.cgi?query=accf_data&sektion=9">
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquernaAcceptFilter http data
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquernaAcceptFilter https data
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna </highlight>
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna <p>Linux's <code>TCP_DEFER_ACCEPT</code> does not support buffering http
7e8f5c6496b3825b6b128e2aacc4b1b09d28553dpquerna requests. Any value besides <code>none</code> will enable
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>TCP_DEFER_ACCEPT</code> on that listener. For more details
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive see the Linux
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <a href="http://homepages.cwi.nl/~aeb/linux/man2html/man7/tcp.7.html">
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveAcceptFilter http data
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabeleAcceptFilter https data
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Window's mpm_winnt interprets the AcceptFilter to toggle the AcceptEx()
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive API, and does not support http protocol buffering. There are two values
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive which utilize the Windows AcceptEx() API and will recycle network
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive sockets between connections. <code>data</code> waits until data has
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive been transmitted as documented above, and the initial data buffer and
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive network endpoint addresses are all retrieved from the single AcceptEx()
fb77c505254b6e9c925e23e734463e87574f8f40kess invocation. <code>connect</code> will use the AcceptEx() API, also
fb77c505254b6e9c925e23e734463e87574f8f40kess retrieve the network endpoint addresses, but like <code>none</code>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the <code>connect</code> option does not wait for the initial data
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive transmission.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>On Windows, <code>none</code> uses accept() rather than AcceptEx()
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive and will not recycle sockets between connections. This is useful for
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive network adapters with broken driver support, as well as some virtual
fb77c505254b6e9c925e23e734463e87574f8f40kess network providers such as vpn drivers, or spam, virus or spyware
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive filters.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">Protocol</directive></seealso>
fb77c505254b6e9c925e23e734463e87574f8f40kess</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Resources accept trailing pathname information</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>virtual host</context><context>directory</context>
fb77c505254b6e9c925e23e734463e87574f8f40kess <p>This directive controls whether requests that contain trailing
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess pathname information that follows an actual filename (or
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive non-existent file in an existing directory) will be accepted or
fb77c505254b6e9c925e23e734463e87574f8f40kess rejected. The trailing pathname information can be made
fb77c505254b6e9c925e23e734463e87574f8f40kess available to scripts in the <code>PATH_INFO</code> environment
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive variable.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>For example, assume the location <code>/test/</code> points to
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive a directory that contains only the single file
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The three possible arguments for the
130d299c4b2b15be45532a176604c71fdc7bea5bnd <dt><code>Off</code></dt><dd>A request will only be accepted if it
130d299c4b2b15be45532a176604c71fdc7bea5bnd maps to a literal path that exists. Therefore a request with
130d299c4b2b15be45532a176604c71fdc7bea5bnd trailing pathname information after the true filename such as
130d299c4b2b15be45532a176604c71fdc7bea5bnd <code>/test/here.html/more</code> in the above example will return
ef8e89e090461194ecadd31e8796a2c51e0531a2kess a 404 NOT FOUND error.</dd>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <dt><code>On</code></dt><dd>A request will be accepted if a
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd leading path component maps to a file that exists. The above
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd example <code>/test/here.html/more</code> will be accepted if
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>/test/here.html</code> maps to a valid file.</dd>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <dt><code>Default</code></dt><dd>The treatment of requests with
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive trailing pathname information is determined by the <a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive href="/handler.html">handler</a> responsible for the request.
003f0c9fda6664daf5092a0e42f65ede20098153slive The core handler for normal files defaults to rejecting
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <code>PATH_INFO</code> requests. Handlers that serve scripts, such as <a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive href="mod_isapi.html">isapi-handler</a>, generally accept
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <p>The primary purpose of the <code>AcceptPathInfo</code>
003f0c9fda6664daf5092a0e42f65ede20098153slive directive is to allow you to override the handler's choice of
003f0c9fda6664daf5092a0e42f65ede20098153slive accepting or rejecting <code>PATH_INFO</code>. This override is required,
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess for example, when you use a <a href="/filter.html">filter</a>, such
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess as <a href="mod_include.html">INCLUDES</a>, to generate content
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive based on <code>PATH_INFO</code>. The core handler would usually reject
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd the request, so you can use the following configuration to enable
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd such a script:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<Files "mypaths.shtml">
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Options +Includes
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive SetOutputFilter INCLUDES
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive AcceptPathInfo On
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</Files>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
130d299c4b2b15be45532a176604c71fdc7bea5bnd</directivesynopsis>
130d299c4b2b15be45532a176604c71fdc7bea5bnd<directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<description>Name of the distributed configuration file</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax>AccessFileName <var>filename</var> [<var>filename</var>] ...</syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
1a3f62ca37273a15a06bb94a61d3c6fcf4bf38c9rbowen</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>While processing a request the server looks for
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the first existing configuration file from this list of names in
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding every directory of the path to the document, if distributed
684f2a9a422185adda0692a1203c5ad6687fc5c5nd configuration files are <a href="#allowoverride">enabled for that
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <highlight language="config">AccessFileName .acl</highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>before returning the document
003f0c9fda6664daf5092a0e42f65ede20098153slive <code>/usr/local/web/index.html</code>, the server will read
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>/usr/local/.acl</code> and <code>/usr/local/web/.acl</code>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding for directives, unless they have been disabled with</p>
684f2a9a422185adda0692a1203c5ad6687fc5c5nd<Directory />
a8ce9095d102e43fecb81093a132b90b9a227f78kess AllowOverride None
684f2a9a422185adda0692a1203c5ad6687fc5c5nd</Directory>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding </highlight>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding<seealso><directive module="core">AllowOverride</directive></seealso>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding<seealso><a href="/configuring.html">Configuration Files</a></seealso>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding<seealso><a href="/howto/htaccess.html">.htaccess Files</a></seealso>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<description>Default charset parameter to be added when a response
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cndcontent-type is <code>text/plain</code> or <code>text/html</code></description>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding<syntax>AddDefaultCharset On|Off|<var>charset</var></syntax>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding<context>virtual host</context><context>directory</context>
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding <p>This directive specifies a default value for the media type
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding charset parameter (the name of a character encoding) to be added
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding 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
843a03fe0b138a4c1f64cb90a014e9417ac30691fielding any charset specified in the body of the response via a <code>META</code>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive element, though the exact behavior is often dependent on the user's client
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive configuration. A setting of <code>AddDefaultCharset Off</code>
58699879a562774640b95e9eedfd891f336e38c2nd disables this functionality. <code>AddDefaultCharset On</code> enables
58699879a562774640b95e9eedfd891f336e38c2nd a default charset of <code>iso-8859-1</code>. Any other value is assumed
58699879a562774640b95e9eedfd891f336e38c2nd to be the <var>charset</var> to be used, which should be one of the
fb77c505254b6e9c925e23e734463e87574f8f40kess <a href="http://www.iana.org/assignments/character-sets">IANA registered
fb77c505254b6e9c925e23e734463e87574f8f40kess charset values</a> for use in Internet media types (MIME types).
58699879a562774640b95e9eedfd891f336e38c2nd For example:</p>
58699879a562774640b95e9eedfd891f336e38c2nd <highlight language="config">AddDefaultCharset utf-8</highlight>
58699879a562774640b95e9eedfd891f336e38c2nd <p><directive>AddDefaultCharset</directive> should only be used when all
58699879a562774640b95e9eedfd891f336e38c2nd of the text resources to which it applies are known to be in that
58699879a562774640b95e9eedfd891f336e38c2nd character encoding and it is too inconvenient to label their charset
58699879a562774640b95e9eedfd891f336e38c2nd individually. One such example is to add the charset parameter
58699879a562774640b95e9eedfd891f336e38c2nd to resources containing generated content, such as legacy CGI
c14037646789087319802aaada2e8534ccab0158slive scripts, that might be vulnerable to cross-site scripting attacks
58699879a562774640b95e9eedfd891f336e38c2nd due to user-provided data being included in the output. Note, however,
fb77c505254b6e9c925e23e734463e87574f8f40kess that a better solution is to just fix (or delete) those scripts, since
fb77c505254b6e9c925e23e734463e87574f8f40kess setting a default charset does not protect users that have enabled
fb77c505254b6e9c925e23e734463e87574f8f40kess the "auto-detect character encoding" feature on their browser.</p>
fb77c505254b6e9c925e23e734463e87574f8f40kess<seealso><directive module="mod_mime">AddCharset</directive></seealso>
58699879a562774640b95e9eedfd891f336e38c2nd</directivesynopsis>
58699879a562774640b95e9eedfd891f336e38c2nd<directivesynopsis>
58699879a562774640b95e9eedfd891f336e38c2nd<description>Determines whether encoded path separators in URLs are allowed to
6b64034fa2a644ba291c484c0c01c7df5b8d982ckessbe passed through</description>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess<contextlist><context>server config</context><context>virtual host</context>
58699879a562774640b95e9eedfd891f336e38c2nd</contextlist>
58699879a562774640b95e9eedfd891f336e38c2nd<compatibility>
fb77c505254b6e9c925e23e734463e87574f8f40kessNoDecode option available in 2.3.12 and later.</compatibility>
58699879a562774640b95e9eedfd891f336e38c2nd <p>The <directive>AllowEncodedSlashes</directive> directive allows URLs
58699879a562774640b95e9eedfd891f336e38c2nd which contain encoded path separators (<code>%2F</code> for <code>/</code>
58699879a562774640b95e9eedfd891f336e38c2nd and additionally <code>%5C</code> for <code>\</code> on according systems)
58699879a562774640b95e9eedfd891f336e38c2nd to be used in the path info.</p>
58699879a562774640b95e9eedfd891f336e38c2nd <p>With the default value, <code>Off</code>, such URLs are refused
58699879a562774640b95e9eedfd891f336e38c2nd with a 404 (Not found) error.</p>
58699879a562774640b95e9eedfd891f336e38c2nd <p>With the value <code>On</code>, such URLs are accepted, and encoded
58699879a562774640b95e9eedfd891f336e38c2nd slashes are decoded like all other encoded characters.</p>
4a7affccb2f1f5b94cab395e1bf3825aed715ebcnd <p>With the value <code>NoDecode</code>, such URLs are accepted, but
9b5e2c5e769dc678a1aca06df75c32022b2f1492trawick encoded slashes are not decoded but left in their encoded state.</p>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess <p>Turning <directive>AllowEncodedSlashes</directive> <code>On</code> is
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess mostly useful when used in conjunction with <code>PATH_INFO</code>.</p>
4a7affccb2f1f5b94cab395e1bf3825aed715ebcnd <p>If encoded slashes are needed in path info, use of <code>NoDecode</code> is
9b5e2c5e769dc678a1aca06df75c32022b2f1492trawick strongly recommended as a security measure. Allowing slashes
4a7affccb2f1f5b94cab395e1bf3825aed715ebcnd to be decoded could potentially allow unsafe paths.</p>
4a7affccb2f1f5b94cab395e1bf3825aed715ebcnd<seealso><directive module="core">AcceptPathInfo</directive></seealso>
ec9b02c6869b75575ada34c800672162833a2c06nd</directivesynopsis>
58699879a562774640b95e9eedfd891f336e38c2nd<directivesynopsis>
58699879a562774640b95e9eedfd891f336e38c2nd<description>Types of directives that are allowed in
58699879a562774640b95e9eedfd891f336e38c2nd<default>AllowOverride None (2.3.9 and later), AllowOverride All (2.3.8 and earlier)</default>
77ead9e0262e4f08ec336d1a65b2edef7705c839nd <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>
77ead9e0262e4f08ec336d1a65b2edef7705c839nd <directive type="section" module="core">Directory</directive>
77ead9e0262e4f08ec336d1a65b2edef7705c839nd 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.
77ead9e0262e4f08ec336d1a65b2edef7705c839nd <p>When this directive is set to <code>None</code> and <directive
77ead9e0262e4f08ec336d1a65b2edef7705c839nd <code>None</code> <a href="#accessfilename">.htaccess</a> files are
77ead9e0262e4f08ec336d1a65b2edef7705c839nd completely ignored. In this case, the server will not even attempt
9b5e2c5e769dc678a1aca06df75c32022b2f1492trawick to read <code>.htaccess</code> files in the filesystem.</p>
77ead9e0262e4f08ec336d1a65b2edef7705c839nd <p>When this directive is set to <code>All</code>, then any
77ead9e0262e4f08ec336d1a65b2edef7705c839nd directive which has the .htaccess <a
77ead9e0262e4f08ec336d1a65b2edef7705c839nd href="directive-dict.html#Context">Context</a> is allowed in
77ead9e0262e4f08ec336d1a65b2edef7705c839nd <p>The <var>directive-type</var> can be one of the following
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive groupings of directives.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Allow use of the authorization directives (<directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="mod_authn_dbm">AuthDBMUserFile</directive>,
fb77c505254b6e9c925e23e734463e87574f8f40kess <directive module="mod_authz_groupfile">AuthGroupFile</directive>,
fb77c505254b6e9c925e23e734463e87574f8f40kess <directive module="mod_authn_core">AuthName</directive>,
fb77c505254b6e9c925e23e734463e87574f8f40kess <directive module="mod_authn_core">AuthType</directive>, <directive
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess module="mod_authn_file">AuthUserFile</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_authz_core">Require</directive>, <em>etc.</em>).</dd>
b12b918ae6baf9c5762ed61b7393d0e2198378c0nd Allow use of the directives controlling document types
10673857794a4b3d9568ca2d983722a87ed352f1rbowen <directive module="mod_negotiation">LanguagePriority</directive>,
fb77c505254b6e9c925e23e734463e87574f8f40kess <directive module="core">SetOutputFilter</directive>, and
fb77c505254b6e9c925e23e734463e87574f8f40kess <module>mod_mime</module> Add* and Remove* directives),
fb77c505254b6e9c925e23e734463e87574f8f40kess document meta data (<directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_headers">RequestHeader</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_setenvif">SetEnvIf</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_setenvif">SetEnvIfNoCase</directive>, <directive
fb77c505254b6e9c925e23e734463e87574f8f40kess module="mod_setenvif">BrowserMatch</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_usertrack">CookieExpires</directive>, <directive
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd module="mod_usertrack">CookieDomain</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_usertrack">CookieStyle</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_usertrack">CookieTracking</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_rewrite">RewriteEngine</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_rewrite">RewriteOptions</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_rewrite">RewriteBase</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_rewrite">RewriteCond</directive>, <directive
1f53e295ebd19aed1767d12da7abfab9936c148cjerenkrantz <module>mod_alias</module> directives (<directive
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess module="mod_alias">RedirectTemp</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="mod_alias">RedirectPermanent</directive>, <directive
1f53e295ebd19aed1767d12da7abfab9936c148cjerenkrantz module="mod_alias">RedirectMatch</directive>), and
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="mod_actions">Action</directive> from
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Allow use of the directives controlling directory indexing
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive (<directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="mod_autoindex">AddIcon</directive>, <directive
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <directive module="mod_autoindex">AddIconByType</directive>,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="mod_autoindex">DefaultIcon</directive>, <directive
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem module="mod_dir">DirectoryIndex</directive>, , <directive
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem module="mod_dir">FallbackResource</directive>,<a href="mod_autoindex.html#indexoptions.fancyindexing"
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem module="mod_autoindex">HeaderName</directive>, <directive
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem module="mod_autoindex">IndexIgnore</directive>, <directive
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem module="mod_autoindex">IndexOptions</directive>, <directive
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem Allow use of the directives controlling host access (<directive
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem module="mod_access_compat">Allow</directive>, <directive
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem module="mod_access_compat">Deny</directive> and <directive
5528d1a30ae8560e2d7a96d734ffe31500dc6113rpluem<!-- TODO - Update this for 2.4 syntax -->
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Allow use of AllowOverride option to treat syntax errors in
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive .htaccess as non-fatal: instead of causing an Internal Server
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Error, disallowed or unrecognised directives will be ignored
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive and a warning logged:
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <li><strong>Nonfatal=Override</strong> treats directives
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive forbidden by AllowOverride as non-fatal.</li>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <li><strong>Nonfatal=Unknown</strong> treats unknown directives
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive as non-fatal. This covers typos and directives implemented
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive by a module that's not present.</li>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <li><strong>Nonfatal=All</strong> treats both the above as non-fatal.</li>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Note that a syntax error in a valid directive will still cause
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive an internal server error.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Nonfatal errors may have security implications for .htaccess users.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive For example, if AllowOverride disallows AuthConfig, users'
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive configuration designed to restrict access to a site will be disabled.
103a93c625bcde1a6a7a5155b64dcda36f612180pquerna Allow use of the directives controlling specific directory
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive features (<directive module="core">Options</directive> and
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="mod_include">XBitHack</directive>).
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive An equal sign may be given followed by a comma (but no spaces)
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive separated lists of options that may be set using the <directive
f23fb63b05f89f47d7a3099491f2c68dcce432e9kess <p>Even though the list of options that may be used in .htaccess files
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive can be limited with this directive, as long as any <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="core">Options</directive> directive is allowed any
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive other inherited option can be disabled by using the non-relative
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive syntax. In other words, this mechanism cannot force a specific option
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd to remain <em>set</em> while allowing any others to be set.
b12b918ae6baf9c5762ed61b7393d0e2198378c0nd AllowOverride Options=Indexes,MultiViews
b12b918ae6baf9c5762ed61b7393d0e2198378c0nd </example>
54bcd0e21a5c79158afd3b78bf707a493a5fb33crbowen <highlight language="config">AllowOverride AuthConfig Indexes</highlight>
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 <note><p>For security and performance reasons, do not set
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <code>AllowOverride</code> to anything other than <code>None</code>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive in your <code><Directory /></code> block. Instead, find (or
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive create) the <code><Directory></code> block that refers to the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directory where you're actually planning to place a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">AccessFileName</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">AllowOverrideList</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>
9ed9eaf871c58d281af02e76125ceadb5060afa5nd<description>Individual directives that are allowed in
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>When the server finds an <code>.htaccess</code> file (as
1c9f7cdf2e1bc8313e559a96638c3c36e3143791yoshiki specified by <directive module="core">AccessFileName</directive>)
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive it needs to know which directives declared in that file can override
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive earlier configuration directives.</p>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <note><title>Only available in <Directory> sections</title>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive>AllowOverrideList</directive> is valid only in
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive type="section" module="core">Directory</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive sections specified without regular expressions, not in <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive type="section" module="core">Location</directive>, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="core" type="section">DirectoryMatch</directive> or
003f0c9fda6664daf5092a0e42f65ede20098153slive <directive type="section" module="core">Files</directive> sections.
530eba85dbd41b8a0fa5255d3648d1440199a661slive <p>When this directive is set to <code>None</code> and <directive
530eba85dbd41b8a0fa5255d3648d1440199a661slive module="core">AllowOverride</directive> is set to <code>None</code>,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive then <a href="#accessfilename">.htaccess</a> files are completely
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive ignored. In this case, the server will not even attempt to read
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveAllowOverride None
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveAllowOverrideList Redirect RedirectMatch
9ed9eaf871c58d281af02e76125ceadb5060afa5nd </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>In the example above only the <code>Redirect</code> and
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>RedirectMatch</code> directives are allowed. All others will
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive cause an internal server error.</p>
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholesAllowOverride AuthConfig
fb77c505254b6e9c925e23e734463e87574f8f40kessAllowOverrideList CookieTracking CookieName
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes </highlight>
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes <p>In the example above <directive module="core">AllowOverride
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes </directive> grants permission to the <code>AuthConfig</code>
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes directive grouping and <directive>AllowOverrideList</directive> grants
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes permission to only two directives from the <code>FileInfo</code> directive
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes grouping. All others will cause an internal server error.</p>
fb77c505254b6e9c925e23e734463e87574f8f40kess<seealso><directive module="core">AccessFileName</directive></seealso>
fb77c505254b6e9c925e23e734463e87574f8f40kess<seealso><directive module="core">AllowOverride</directive></seealso>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<seealso><a href="/configuring.html">Configuration Files</a></seealso>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<seealso><a href="/howto/htaccess.html">.htaccess Files</a></seealso>
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes</directivesynopsis>
4c7bdb15764021d39e486adb7bc2166d3f683773bnicholes<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Technique for locating the interpreter for CGI
313bb560bc5c323cfd40c9cad7335b4b8e060aedkessscripts</description>
fb77c505254b6e9c925e23e734463e87574f8f40kess<syntax>CGIMapExtension <var>cgi-path</var> <var>.extension</var></syntax>
fb77c505254b6e9c925e23e734463e87574f8f40kess<contextlist><context>directory</context><context>.htaccess</context>
fb77c505254b6e9c925e23e734463e87574f8f40kess</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive is used to control how Apache httpd finds the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive interpreter used to run CGI scripts. For example, setting
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive cause all CGI script files with a <code>.foo</code> extension to
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive be passed to the FOO interpreter.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Enables the generation of <code>Content-MD5</code> HTTP Response
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveheaders</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>directory</context><context>.htaccess</context>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive enables the generation of
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>Content-MD5</code> headers as defined in RFC1864
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive respectively RFC2616.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>MD5 is an algorithm for computing a "message digest"
fb77c505254b6e9c925e23e734463e87574f8f40kess (sometimes called "fingerprint") of arbitrary-length data, with
fb77c505254b6e9c925e23e734463e87574f8f40kess a high degree of confidence that any alterations in the data
fb77c505254b6e9c925e23e734463e87574f8f40kess will be reflected in alterations in the message digest.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <code>Content-MD5</code> header provides an end-to-end
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive message integrity check (MIC) of the entity-body. A proxy or
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive client may check this header for detecting accidental
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive modification of the entity-body in transit. Example header:</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd Content-MD5: AuLb7Dp1rqtRtxz2m9kRpA==
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Note that this can cause performance problems on your server
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive since the message digest is computed on every request (the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive values are not cached).</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p><code>Content-MD5</code> is only sent for documents served
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive by the <module>core</module>, and not by any module. For example,
c14037646789087319802aaada2e8534ccab0158slive SSI documents, output from CGI scripts, and byte range responses
c14037646789087319802aaada2e8534ccab0158slive do not have this header.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<description>Base directory for the server run-time files</description>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<syntax>DefaultRuntimeDir <var>directory-path</var></syntax>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<default>DefaultRuntimeDir DEFAULT_REL_RUNTIMEDIR (logs/)</default>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<contextlist><context>server config</context></contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive>DefaultRuntimeDir</directive> directive sets the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directory in which the server will create various run-time files
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess (shared memory, locks, etc.). If set as a relative path, the full path
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive will be relative to <directive>ServerRoot</directive>.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveDefaultRuntimeDir scratch/
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The default location of <directive>DefaultRuntimeDir</directive> may be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive modified by changing the <code>DEFAULT_REL_RUNTIMEDIR</code> #define
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive at build time.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Note: <directive>ServerRoot</directive> should be specified before this
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directive is used, otherwise the default value of <directive>ServerRoot</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive would be used to set the base directory.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><a href="/misc/security_tips.html#serverroot">the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive security tips</a> for information on how to properly set
003f0c9fda6664daf5092a0e42f65ede20098153slive permissions on the <directive>ServerRoot</directive></seealso>
003f0c9fda6664daf5092a0e42f65ede20098153slive</directivesynopsis>
003f0c9fda6664daf5092a0e42f65ede20098153slive<directivesynopsis>
fb77c505254b6e9c925e23e734463e87574f8f40kess<description>This directive has no effect other than to emit warnings
fb77c505254b6e9c925e23e734463e87574f8f40kessif the value is not <code>none</code>. In prior versions, DefaultType
fb77c505254b6e9c925e23e734463e87574f8f40kesswould specify a default media type to assign to response content for
003f0c9fda6664daf5092a0e42f65ede20098153slivewhich no other media type configuration could be found.
003f0c9fda6664daf5092a0e42f65ede20098153slive</description>
003f0c9fda6664daf5092a0e42f65ede20098153slive<syntax>DefaultType <var>media-type|none</var></syntax>
130d299c4b2b15be45532a176604c71fdc7bea5bnd<contextlist><context>server config</context><context>virtual host</context>
130d299c4b2b15be45532a176604c71fdc7bea5bnd</contextlist>
130d299c4b2b15be45532a176604c71fdc7bea5bnd<compatibility>All choices except <code>none</code> are DISABLED for 2.3.x and later.
130d299c4b2b15be45532a176604c71fdc7bea5bnd</compatibility>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>This directive has been disabled. For backwards compatibility
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd of configuration files, it may be specified with the value
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <code>none</code>, meaning no default media type. For example:</p>
fb77c505254b6e9c925e23e734463e87574f8f40kess <highlight language="config">DefaultType None</highlight>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd httpd-2.2.7 and later.</p>
030108b1816bcda3d925df65357feabdce83bc94slive <directive module="mod_mime">AddType</directive> to configure media
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive type assignments via file extensions, or the
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <directive module="core">ForceType</directive> directive to configure
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd the media type for specific resources. Otherwise, the server will
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd send the response without a Content-Type header field and the
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd recipient may attempt to guess the media type.</p>
fb77c505254b6e9c925e23e734463e87574f8f40kess</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess<syntax>Define <var>parameter-name</var> [<var>parameter-value</var>]</syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>In its one parameter form, <directive>Define</directive> is equivalent
130d299c4b2b15be45532a176604c71fdc7bea5bnd to passing the <code>-D</code> argument to <program>httpd</program>. It
130d299c4b2b15be45532a176604c71fdc7bea5bnd can be used to toggle the use of
130d299c4b2b15be45532a176604c71fdc7bea5bnd <directive module="core" type="section">IfDefine</directive> sections
130d299c4b2b15be45532a176604c71fdc7bea5bnd without needing to alter <code>-D</code> arguments in any startup
130d299c4b2b15be45532a176604c71fdc7bea5bnd scripts.</p>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>In addition to that, if the second parameter is given, a config variable
130d299c4b2b15be45532a176604c71fdc7bea5bnd is set to this value. The variable can be used in the configuration using
130d299c4b2b15be45532a176604c71fdc7bea5bnd the <code>${VAR}</code> syntax. The variable is always globally defined
130d299c4b2b15be45532a176604c71fdc7bea5bnd and not limited to the scope of the surrounding config section.</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<IfDefine TEST>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd Define servername test.example.com
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</IfDefine>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<IfDefine !TEST>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Define servername www.example.com
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</IfDefine>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Variable names may not contain colon ":" characters, to avoid clashes
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess with <directive module="mod_rewrite">RewriteMap</directive>'s syntax.</p>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Enclose a group of directives that apply only to the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivenamed file-system directory, sub-directories, and their contents.</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive... </Directory></syntax>
130d299c4b2b15be45532a176604c71fdc7bea5bnd<contextlist><context>server config</context><context>virtual host</context>
130d299c4b2b15be45532a176604c71fdc7bea5bnd</contextlist>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <code></Directory></code> are used to enclose a group of
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd directives that will apply only to the named directory,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive sub-directories of that directory, and the files within the respective
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess directories. Any directive that is allowed
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess in a directory context may be used. <var>Directory-path</var> is
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess either the full path to a directory, or a wild-card string using
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess Unix shell-style matching. In a wild-card string, <code>?</code> matches
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess any single character, and <code>*</code> matches any sequences of
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess 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>
130d299c4b2b15be45532a176604c71fdc7bea5bnd Options Indexes FollowSymLinks
130d299c4b2b15be45532a176604c71fdc7bea5bnd</Directory>
130d299c4b2b15be45532a176604c71fdc7bea5bnd </highlight>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>Be careful with the <var>directory-path</var> arguments:
130d299c4b2b15be45532a176604c71fdc7bea5bnd They have to literally match the filesystem path which Apache httpd uses
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd 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
fb77c505254b6e9c925e23e734463e87574f8f40kess expressions</glossary> can also be used, with the addition of the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<Directory ~ "^/www/[0-9]{3}">
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess</Directory>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess</highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>would match directories in <code>/www/</code> that consisted of
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive three numbers.</p>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess match the directory (or one of its parents) containing a document,
15ba1801088da1aad6d20609cf3f7b0b1eefce8aslive then the directives are applied in the order of shortest match
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive first, interspersed with the directives from the <a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<Directory />
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive AllowOverride None
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</Directory>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<Directory "/home">
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive AllowOverride FileInfo
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</Directory>
030108b1816bcda3d925df65357feabdce83bc94slive </highlight>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>for access to the document <code>/home/web/dir/doc.html</code>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd the steps are:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <li>Apply directive <code>AllowOverride FileInfo</code> (for
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>/home/.htaccess</code>, <code>/home/web/.htaccess</code> and
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <code>/home/web/dir/.htaccess</code> in that order.</li>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Regular expressions are not considered until after all of the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive normal sections have been applied. Then all of the regular
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive expressions are tested in the order they appeared in the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive configuration file. For example, with</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<Directory ~ "abc$">
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive # ... directives here ...
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</Directory>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>the regular expression section won't be considered until after
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd all normal <directive type="section">Directory</directive>s and
fb77c505254b6e9c925e23e734463e87574f8f40kess <code>.htaccess</code> files have been applied. Then the regular
fb77c505254b6e9c925e23e734463e87574f8f40kess expression will match on <code>/home/abc/public_html/abc</code> and
fb77c505254b6e9c925e23e734463e87574f8f40kess the corresponding <directive type="section">Directory</directive> will
fb77c505254b6e9c925e23e734463e87574f8f40kess be applied.</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <code><Directory /></code> is to permit all access.
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd This means that Apache httpd will serve any file mapped from an URL. It is
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd recommended that you change this with a block such
c68acc9d712af079afa2bd1a5a4aeef9a3ea573ckess<Directory />
c68acc9d712af079afa2bd1a5a4aeef9a3ea573ckess Require all denied
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</Directory>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive href="/misc/security_tips.html">Security Tips</a> page for more
af18698b10b429b270551ca3a5d51a75e1c9db22brianp <p>The directory sections occur in the <code>httpd.conf</code> file.
af18698b10b429b270551ca3a5d51a75e1c9db22brianp <directive type="section">Directory</directive> directives
003f0c9fda6664daf5092a0e42f65ede20098153slive cannot nest, and cannot appear in a <directive module="core"
fb77c505254b6e9c925e23e734463e87574f8f40kess type="section">Limit</directive> or <directive module="core"
af18698b10b429b270551ca3a5d51a75e1c9db22brianp<seealso><a href="/sections.html">How <Directory>,
af18698b10b429b270551ca3a5d51a75e1c9db22brianp <Location> and <Files> sections work</a> for an
003f0c9fda6664daf5092a0e42f65ede20098153slive explanation of how these different sections are combined when a
af18698b10b429b270551ca3a5d51a75e1c9db22brianp request is received</seealso>
af18698b10b429b270551ca3a5d51a75e1c9db22brianp</directivesynopsis>
fb77c505254b6e9c925e23e734463e87574f8f40kess<description>Enclose directives that apply to
fb77c505254b6e9c925e23e734463e87574f8f40kessthe contents of file-system directories matching a regular expression.</description>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd... </DirectoryMatch></syntax>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<contextlist><context>server config</context><context>virtual host</context>
af18698b10b429b270551ca3a5d51a75e1c9db22brianp</contextlist>
af18698b10b429b270551ca3a5d51a75e1c9db22brianp <p><directive type="section">DirectoryMatch</directive> and
af18698b10b429b270551ca3a5d51a75e1c9db22brianp <code></DirectoryMatch></code> are used to enclose a group
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd of directives which will apply only to the named directory (and the files within),
af18698b10b429b270551ca3a5d51a75e1c9db22brianp the same as <directive module="core" type="section">Directory</directive>.
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd However, it takes as an argument a
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd <glossary ref="regex">regular expression</glossary>. For example:</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<DirectoryMatch "^/www/(.+/)?[0-9]{3}">
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</DirectoryMatch>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</highlight>
fb77c505254b6e9c925e23e734463e87574f8f40kess <p>would match directories in <code>/www/</code> that consisted of three
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd numbers.</p>
41ef8b3051855b802104193ee0a587515af60a37wrowe Prior to 2.3.9, this directive implicitly applied to sub-directories
41ef8b3051855b802104193ee0a587515af60a37wrowe (like <directive module="core" type="section">Directory</directive>) and
41ef8b3051855b802104193ee0a587515af60a37wrowe could not match the end of line symbol ($). In 2.3.9 and later,
41ef8b3051855b802104193ee0a587515af60a37wrowe only directories that match the expression are affected by the enclosed
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess directives.
41ef8b3051855b802104193ee0a587515af60a37wrowe This directive applies to requests for directories that may or may
41ef8b3051855b802104193ee0a587515af60a37wrowe not end in a trailing slash, so expressions that are anchored to the
41ef8b3051855b802104193ee0a587515af60a37wrowe end of line ($) must be written with care.
41ef8b3051855b802104193ee0a587515af60a37wrowe <p>From 2.4.8 onwards, named groups and backreferences are captured and
41ef8b3051855b802104193ee0a587515af60a37wrowe written to the environment with the corresponding name prefixed with
fb77c505254b6e9c925e23e734463e87574f8f40kess "MATCH_" and in upper case. This allows elements of paths to be referenced
fb77c505254b6e9c925e23e734463e87574f8f40kess from within <a href="/expr.html">expressions</a> and modules like
41ef8b3051855b802104193ee0a587515af60a37wrowe <module>mod_rewrite</module>. In order to prevent confusion, numbered
41ef8b3051855b802104193ee0a587515af60a37wrowe (unnamed) backreferences are ignored. Use named groups instead.</p>
9fb925624300c864fe3969a264e52aa83f3c2dd0slive<DirectoryMatch ^/var/www/combined/(?<sitename>[^/]+)>
41ef8b3051855b802104193ee0a587515af60a37wrowe require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
41ef8b3051855b802104193ee0a587515af60a37wrowe</DirectoryMatch>
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd</highlight>
41ef8b3051855b802104193ee0a587515af60a37wrowe<seealso><directive type="section" module="core">Directory</directive> for
41ef8b3051855b802104193ee0a587515af60a37wrowea description of how regular expressions are mixed in with normal
41ef8b3051855b802104193ee0a587515af60a37wrowe<directive type="section">Directory</directive>s</seealso>
41ef8b3051855b802104193ee0a587515af60a37wrowehref="/sections.html">How <Directory>, <Location> and
9b5e2c5e769dc678a1aca06df75c32022b2f1492trawick<Files> sections work</a> for an explanation of how these different
6b64034fa2a644ba291c484c0c01c7df5b8d982ckesssections are combined when a request is received</seealso>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess</directivesynopsis>
41ef8b3051855b802104193ee0a587515af60a37wrowe<directivesynopsis>
41ef8b3051855b802104193ee0a587515af60a37wrowe<description>Directory that forms the main document tree visible
41ef8b3051855b802104193ee0a587515af60a37wrowefrom the web</description>
9fb925624300c864fe3969a264e52aa83f3c2dd0slive<syntax>DocumentRoot <var>directory-path</var></syntax>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<default>DocumentRoot /usr/local/apache/htdocs</default>
78f4d313fd5edf76dc5cfb8725e082a08cd29740jwoolley<contextlist><context>server config</context><context>virtual host</context>
78f4d313fd5edf76dc5cfb8725e082a08cd29740jwoolley</contextlist>
9fb925624300c864fe3969a264e52aa83f3c2dd0slive <p>This directive sets the directory from which <program>httpd</program>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess will serve files. Unless matched by a directive like <directive
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess module="mod_alias">Alias</directive>, the server appends the
9fb925624300c864fe3969a264e52aa83f3c2dd0slive path from the requested URL to the document root to make the
41ef8b3051855b802104193ee0a587515af60a37wrowe path to the document. Example:</p>
41ef8b3051855b802104193ee0a587515af60a37wrowe <highlight language="config">DocumentRoot "/usr/web"</highlight>
41ef8b3051855b802104193ee0a587515af60a37wrowe <p>then an access to
41ef8b3051855b802104193ee0a587515af60a37wrowe <code>http://my.example.com/index.html</code> refers to
fb77c505254b6e9c925e23e734463e87574f8f40kess <code>/usr/web/index.html</code>. If the <var>directory-path</var> is
41ef8b3051855b802104193ee0a587515af60a37wrowe not absolute then it is assumed to be relative to the <directive
9fb925624300c864fe3969a264e52aa83f3c2dd0slive <p>The <directive>DocumentRoot</directive> should be specified without
41ef8b3051855b802104193ee0a587515af60a37wrowe a trailing slash.</p>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<seealso><a href="/urlmapping.html#documentroot">Mapping URLs to Filesystem
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess</directivesynopsis>
af18698b10b429b270551ca3a5d51a75e1c9db22brianp<description>Contains directives that apply only if the condition of a
af18698b10b429b270551ca3a5d51a75e1c9db22brianpprevious <directive type="section" module="core">If</directive> or
af18698b10b429b270551ca3a5d51a75e1c9db22brianp<directive type="section" module="core">ElseIf</directive> section is not
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivesatisfied by a request at runtime</description>
003f0c9fda6664daf5092a0e42f65ede20098153slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>directory</context><context>.htaccess</context>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive type="section">Else</directive> applies the enclosed
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directives if and only if the most recent
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive in the same scope has not been applied.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive For example: In </p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<If "-z req('Host')">
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<Else>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</Else>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p> The <directive type="section">If</directive> would match HTTP/1.0
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive type="section">Else</directive> would match requests
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive type="section" module="core">If</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive type="section" module="core">ElseIf</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><a href="/sections.html">How <Directory>, <Location>,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <Files> sections work</a> for an explanation of how these
69fba5b8aa0b0dc408f649cfdaab064ce120b05bslive different sections are combined when a request is received.
69fba5b8aa0b0dc408f649cfdaab064ce120b05bslive <directive type="section">Else</directive> are applied last.</seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<description>Contains directives that apply only if a condition is satisfied
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cndby a request at runtime while the condition of a previous
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directive type="section">ElseIf</directive> section is not
f7fe99050600166042c04b8e595fb75499eed7f0geoffsatisfied</description>
f7fe99050600166042c04b8e595fb75499eed7f0geoff<syntax><ElseIf <var>expression</var>> ... </ElseIf></syntax>
f7fe99050600166042c04b8e595fb75499eed7f0geoff<contextlist><context>server config</context><context>virtual host</context>
f7fe99050600166042c04b8e595fb75499eed7f0geoff<context>directory</context><context>.htaccess</context>
f7fe99050600166042c04b8e595fb75499eed7f0geoff</contextlist>
f7fe99050600166042c04b8e595fb75499eed7f0geoff <p>The <directive type="section">ElseIf</directive> applies the enclosed
f7fe99050600166042c04b8e595fb75499eed7f0geoff directives if and only if both the given condition evaluates to true and
f7fe99050600166042c04b8e595fb75499eed7f0geoff the most recent <directive type="section">If</directive> or
f7fe99050600166042c04b8e595fb75499eed7f0geoff <directive type="section">ElseIf</directive> section in the same scope has
f7fe99050600166042c04b8e595fb75499eed7f0geoff not been applied. For example: In </p>
fb77c505254b6e9c925e23e734463e87574f8f40kess</If>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<ElseIf "-R '10.0.0.0/8'">
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</ElseIf>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<Else>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</Else>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive type="section">ElseIf</directive> would match if
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the remote address of a request belongs to the subnet 10.0.0.0/8 but
fb77c505254b6e9c925e23e734463e87574f8f40kess<seealso><a href="/expr.html">Expressions in Apache HTTP Server</a>,
fb77c505254b6e9c925e23e734463e87574f8f40kessfor a complete reference and more examples.</seealso>
fb77c505254b6e9c925e23e734463e87574f8f40kess<seealso><directive type="section" module="core">If</directive></seealso>
4f854c24127e28f7ad72ce9a39d4448aaf910fc1slive<seealso><directive type="section" module="core">Else</directive></seealso>
4f854c24127e28f7ad72ce9a39d4448aaf910fc1slive<seealso><a href="/sections.html">How <Directory>, <Location>,
4f854c24127e28f7ad72ce9a39d4448aaf910fc1slive <Files> sections work</a> for an explanation of how these
9b5e2c5e769dc678a1aca06df75c32022b2f1492trawick different sections are combined when a request is received.
4f854c24127e28f7ad72ce9a39d4448aaf910fc1slive <directive type="section">Else</directive> are applied last.</seealso>
69fba5b8aa0b0dc408f649cfdaab064ce120b05bslive</directivesynopsis>
69fba5b8aa0b0dc408f649cfdaab064ce120b05bslive<directivesynopsis>
69fba5b8aa0b0dc408f649cfdaab064ce120b05bslive<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>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive controls whether the <program>httpd</program> may use
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive memory-mapping if it needs to read the contents of a file during
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive delivery. By default, when the handling of a request requires
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess access to the data within a file -- for example, when delivering a
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd server-parsed file using <module>mod_include</module> -- Apache httpd
3209c0009829fcf63b6213fb9c43d534f7906006slive memory-maps the file if the OS supports it.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This memory-mapping sometimes yields a performance improvement.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive But in some environments, it is better to disable the memory-mapping
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive to prevent operational problems:</p>
c68acc9d712af079afa2bd1a5a4aeef9a3ea573ckess <li>On some multiprocessor systems, memory-mapping can reduce the
fb109b84906e3ee61680aa289953c2f9e859354erbowen <li>Deleting or truncating a file while <program>httpd</program>
fb109b84906e3ee61680aa289953c2f9e859354erbowen has it memory-mapped can cause <program>httpd</program> to
fb109b84906e3ee61680aa289953c2f9e859354erbowen crash with a segmentation fault.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>For server configurations that are vulnerable to these problems,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive you should disable memory-mapping of delivered files by specifying:</p>
fb109b84906e3ee61680aa289953c2f9e859354erbowen <highlight language="config">EnableMMAP Off</highlight>
fb109b84906e3ee61680aa289953c2f9e859354erbowen <p>For NFS mounted files, this feature may be disabled explicitly for
fb109b84906e3ee61680aa289953c2f9e859354erbowen the offending files by specifying:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<Directory "/path-to-nfs-files">
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd EnableMMAP Off
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</Directory>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
fb109b84906e3ee61680aa289953c2f9e859354erbowen</directivesynopsis>
fb109b84906e3ee61680aa289953c2f9e859354erbowen<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Use the kernel sendfile support to deliver files to the client</description>
9b5e2c5e769dc678a1aca06df75c32022b2f1492trawick<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>directory</context><context>.htaccess</context>
2bac697634d965d9d9a921a99a68b2c454c8a95dbnicholes</contextlist>
2bac697634d965d9d9a921a99a68b2c454c8a95dbnicholes<compatibility>Default changed to Off in
2bac697634d965d9d9a921a99a68b2c454c8a95dbnicholesversion 2.3.9.</compatibility>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive controls whether <program>httpd</program> may use the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive sendfile support from the kernel to transmit file contents to the client.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive By default, when the handling of a request requires no access
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive to the data within a file -- for example, when delivering a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive static file -- Apache httpd uses sendfile to deliver the file contents
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive without ever reading the file if the OS supports it.</p>
003f0c9fda6664daf5092a0e42f65ede20098153slive <p>This sendfile mechanism avoids separate read and send operations,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive and buffer allocations. But on some platforms or within some
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd filesystems, it is better to disable this feature to avoid
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele operational problems:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <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
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive offloading bugs on certain networking cards when using IPv6.</li>
fb77c505254b6e9c925e23e734463e87574f8f40kess <li>On Linux on Itanium, <code>sendfile</code> may be unable to handle
fb77c505254b6e9c925e23e734463e87574f8f40kess files over 2GB in size.</li>
fb77c505254b6e9c925e23e734463e87574f8f40kess module="core">DocumentRoot</directive> (e.g., NFS, SMB, CIFS, FUSE),
fb77c505254b6e9c925e23e734463e87574f8f40kess the kernel may be unable to serve the network file through
fb77c505254b6e9c925e23e734463e87574f8f40kess its own cache.</li>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>For server configurations that are not vulnerable to these problems,
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd you may enable this feature by specifying:</p>
530eba85dbd41b8a0fa5255d3648d1440199a661slive <highlight language="config">EnableSendfile On</highlight>
530eba85dbd41b8a0fa5255d3648d1440199a661slive <p>For network mounted files, this feature may be disabled explicitly
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive for the offending files by specifying:</p>
530eba85dbd41b8a0fa5255d3648d1440199a661slive<Directory "/path-to-nfs-files">
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd EnableSendfile Off
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</Directory>
530eba85dbd41b8a0fa5255d3648d1440199a661slive </highlight>
fb77c505254b6e9c925e23e734463e87574f8f40kess <p>Please note that the per-directory and .htaccess configuration
fb77c505254b6e9c925e23e734463e87574f8f40kess of <directive>EnableSendfile</directive> is not supported by
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd Only global definition of <directive>EnableSendfile</directive>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd is taken into account by the module.
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<description>Abort configuration parsing with a custom error message</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>directory</context><context>.htaccess</context>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>If an error can be detected within the configuration, this
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directive can be used to generate a custom error message, and halt
003f0c9fda6664daf5092a0e42f65ede20098153slive configuration parsing. The typical use is for reporting required
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive modules which are missing from the configuration.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive# ensure that mod_include is loaded
003f0c9fda6664daf5092a0e42f65ede20098153slive<IfModule !include_module>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Error "mod_include is required by mod_foo. Load it with LoadModule."
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</IfModule>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess# ensure that exactly one of SSL,NOSSL is defined
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess<IfDefine SSL>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess<IfDefine NOSSL>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess Error "Both SSL and NOSSL are defined. Define only one of them."
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess</IfDefine>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess</IfDefine>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<IfDefine !SSL>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<IfDefine !NOSSL>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Error "Either SSL or NOSSL must be defined."
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</IfDefine>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</IfDefine>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
fb77c505254b6e9c925e23e734463e87574f8f40kess<description>What the server will return to the client
030108b1816bcda3d925df65357feabdce83bc94slivein case of an error</description>
030108b1816bcda3d925df65357feabdce83bc94slive<syntax>ErrorDocument <var>error-code</var> <var>document</var></syntax>
030108b1816bcda3d925df65357feabdce83bc94slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>directory</context><context>.htaccess</context>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</contextlist>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>In the event of a problem or error, Apache httpd can be configured
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess to do one of four things,</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <li>internally redirect to a local <var>URL-path</var> to handle the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <li>redirect to an external <var>URL</var> to handle the
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <p>The first option is the default, while options 2-4 are
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive configured using the <directive>ErrorDocument</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directive, which is followed by the HTTP response code and a URL
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive or a message. Apache httpd will sometimes offer additional information
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>URLs can begin with a slash (/) for local web-paths (relative
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd to the <directive module="core">DocumentRoot</directive>), or be a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive full URL which the client can resolve. Alternatively, a message
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive can be provided to be displayed by the browser. Examples:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveErrorDocument 500 http://foo.example.com/cgi-bin/tester
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveErrorDocument 401 /subscription_info.html
6b64034fa2a644ba291c484c0c01c7df5b8d982ckessErrorDocument 403 "Sorry can't allow you access today"
6b64034fa2a644ba291c484c0c01c7df5b8d982ckessErrorDocument 403 Forbidden!
030108b1816bcda3d925df65357feabdce83bc94slive </highlight>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>Additionally, the special value <code>default</code> can be used
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd to specify Apache httpd's simple hardcoded message. While not required
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd under normal circumstances, <code>default</code> will restore
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd Apache httpd's simple hardcoded message for configurations that would
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive otherwise inherit an existing <directive>ErrorDocument</directive>.</p>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess ErrorDocument 404 default
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</Directory>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Note that when you specify an <directive>ErrorDocument</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive that points to a remote URL (ie. anything with a method such as
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>http</code> in front of it), Apache HTTP Server will send a redirect to the
c97e8972ab1f4dd167e3dc4db87daf91114009fbnd client to tell it where to find the document, even if the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive document ends up being on the same server. This has several
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive implications, the most important being that the client will not
003f0c9fda6664daf5092a0e42f65ede20098153slive receive the original error status code, but instead will
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive receive a redirect status code. This in turn can confuse web
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive robots and other clients which try to determine if a URL is
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive valid using the status code. In addition, if you use a remote
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive URL in an <code>ErrorDocument 401</code>, the client will not
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive know to prompt the user for a password since it will not
fb77c505254b6e9c925e23e734463e87574f8f40kess receive the 401 status code. Therefore, <strong>if you use an
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>ErrorDocument 401</code> directive then it must refer to a local
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>Microsoft Internet Explorer (MSIE) will by default ignore
fb77c505254b6e9c925e23e734463e87574f8f40kess server-generated error messages when they are "too small" and substitute
fb77c505254b6e9c925e23e734463e87574f8f40kess its own "friendly" error messages. The size threshold varies depending on
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd the type of error, but in general, if you make your error document
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd greater than 512 bytes, then MSIE will show the server-generated
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd error rather than masking it. More information is available in
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd Microsoft Knowledge Base article <a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q294807"
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Although most error messages can be overridden, there are certain
7654193c1faf603feec999850322ad79e6c551bcnd circumstances where the internal messages are used regardless of the
7654193c1faf603feec999850322ad79e6c551bcnd setting of <directive module="core">ErrorDocument</directive>. In
c97e8972ab1f4dd167e3dc4db87daf91114009fbnd particular, if a malformed request is detected, normal request processing
7654193c1faf603feec999850322ad79e6c551bcnd will be immediately halted and the internal error message returned.
7654193c1faf603feec999850322ad79e6c551bcnd This is necessary to guard against security problems caused by
7654193c1faf603feec999850322ad79e6c551bcnd bad requests.</p>
7654193c1faf603feec999850322ad79e6c551bcnd <p>If you are using mod_proxy, you may wish to enable
7654193c1faf603feec999850322ad79e6c551bcnd <directive module="mod_proxy">ProxyErrorOverride</directive> so that you can provide
7654193c1faf603feec999850322ad79e6c551bcnd custom error messages on behalf of your Origin servers. If you don't enable ProxyErrorOverride,
7654193c1faf603feec999850322ad79e6c551bcnd Apache httpd will not generate custom error documents for proxied content.</p>
c97e8972ab1f4dd167e3dc4db87daf91114009fbnd</directivesynopsis>
7654193c1faf603feec999850322ad79e6c551bcnd<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Location where the server will log errors</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax> ErrorLog <var>file-path</var>|syslog[:<var>facility</var>]</syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<default>ErrorLog logs/error_log (Unix) ErrorLog logs/error.log (Windows and OS/2)</default>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
fb77c505254b6e9c925e23e734463e87574f8f40kess <p>The <directive>ErrorLog</directive> directive sets the name of
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the file to which the server will log any errors it encounters. If
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the <var>file-path</var> is not absolute then it is assumed to be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive relative to the <directive module="core">ServerRoot</directive>.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <highlight language="config">ErrorLog "/var/log/httpd/error_log"</highlight>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess begins with a pipe character "<code>|</code>" then it is assumed to be a
9b5e2c5e769dc678a1aca06df75c32022b2f1492trawick command to spawn to handle the error log.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <highlight language="config">ErrorLog "|/usr/local/bin/httpd_errors"</highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>See the notes on <a href="/logs.html#piped">piped logs</a> for
9ed9eaf871c58d281af02e76125ceadb5060afa5nd more information.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Using <code>syslog</code> instead of a filename enables logging
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive via syslogd(8) if the system supports it and if <module>mod_syslog</module>
fb77c505254b6e9c925e23e734463e87574f8f40kess is loaded. The default is to use syslog facility <code>local7</code>,
fb77c505254b6e9c925e23e734463e87574f8f40kess but you can override this by using the <code>syslog:<var>facility</var></code>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive syntax where <var>facility</var> can be one of the names usually documented in
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive syslog(1). The facility is effectively global, and if it is changed
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive in individual virtual hosts, the final facility specified affects the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive entire server.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <highlight language="config">ErrorLog syslog:user</highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Additional modules can provide their own ErrorLog providers. The syntax
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd href="/misc/security_tips.html#serverroot">security tips</a>
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd document for details on why your security could be compromised
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd if the directory where log files are stored is writable by
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive anyone other than the user that starts the server.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>When entering a file path on non-Unix platforms, care should be taken
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive to make sure that only forward slashes are used even though the platform
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive may allow the use of back slashes. In general it is a good idea to always
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive use forward slashes throughout the configuration files.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">LogLevel</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><a href="/logs.html">Apache HTTP Server Log Files</a></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
003f0c9fda6664daf5092a0e42f65ede20098153slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Format specification for error log entries</description>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<syntax> ErrorLogFormat [connection|request] <var>format</var></syntax>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<contextlist><context>server config</context><context>virtual host</context>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</contextlist>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p><directive>ErrorLogFormat</directive> allows to specify what
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive supplementary information is logged in the error log in addition to the
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd actual log message.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive#Simple example
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cndErrorLogFormat "[%t] [%l] [pid %P] %F: %E: [client %a] %M"
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Specifying <code>connection</code> or <code>request</code> as first
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive parameter allows to specify additional formats, causing additional
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive information to be logged when the first message is logged for a specific
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive connection or request, respectively. This additional information is only
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd logged once per connection/request. If a connection or request is processed
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive without causing any log message, the additional information is not logged
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd either.</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>It can happen that some format string items do not produce output. For
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd example, the Referer header is only present if the log message is
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd associated to a request and the log message happens at a time when the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Referer header has already been read from the client. If no output is
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive produced, the default behavior is to delete everything from the preceding
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive space character to the next space character. This means the log line is
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive implicitly divided into fields on non-whitespace to whitespace transitions.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive If a format string item does not produce output, the whole field is
130d299c4b2b15be45532a176604c71fdc7bea5bnd omitted. For example, if the remote address <code>%a</code> in the log
130d299c4b2b15be45532a176604c71fdc7bea5bnd format <code>[%t] [%l] [%a] %M </code> is not available, the surrounding
130d299c4b2b15be45532a176604c71fdc7bea5bnd brackets are not logged either. Space characters can be escaped with a
130d299c4b2b15be45532a176604c71fdc7bea5bnd backslash to prevent them from delimiting a field. The combination '% '
130d299c4b2b15be45532a176604c71fdc7bea5bnd (percent space) is a zero-width field delimiter that does not produce any
130d299c4b2b15be45532a176604c71fdc7bea5bnd output.</p>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>The above behavior can be changed by adding modifiers to the format
130d299c4b2b15be45532a176604c71fdc7bea5bnd string item. A <code>-</code> (minus) modifier causes a minus to be logged if the
130d299c4b2b15be45532a176604c71fdc7bea5bnd respective item does not produce any output. In once-per-connection/request
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd formats, it is also possible to use the <code>+</code> (plus) modifier. If an
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive item with the plus modifier does not produce any output, the whole line is
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive omitted.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>A number as modifier can be used to assign a log severity level to a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive format item. The item will only be logged if the severity of the log
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive message is not higher than the specified log severity level. The number can
a04a96aae08a62f2d9d5833b3313a9751fa3f680yoshiki range from 1 (alert) over 4 (warn) and 7 (debug) to 15 (trace8).</p>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <p>For example, here's what would happen if you added modifiers to
55d36f9b61520c2374ab463e77e8a62daa416398nd <columnspec><column width=".3"/><column width=".7"/></columnspec>
fb77c505254b6e9c925e23e734463e87574f8f40kess <td>Logs a <code>-</code> if <code>Referer</code> is not set.</td>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <td>Omits the entire line if <code>Referer</code> is not set.</td>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <td>Logs the <code>Referer</code> only if the log message severity
55d36f9b61520c2374ab463e77e8a62daa416398nd is higher than 4.</td>
55d36f9b61520c2374ab463e77e8a62daa416398nd <p>Some format string items accept additional parameters in braces.</p>
55d36f9b61520c2374ab463e77e8a62daa416398nd <columnspec><column width=".2"/><column width=".8"/></columnspec>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <tr><th>Format String</th> <th>Description</th></tr>
bea526116133aa3d7dabd1924bfc580b37fbf22aslive <td>Client IP address and port of the request</td></tr>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <td>Underlying peer IP address and port of the connection (see the
bea526116133aa3d7dabd1924bfc580b37fbf22aslive <td>Request environment variable <em>name</em></td></tr>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <td>Source file name and line number of the log call</td></tr>
7b5535ed88e0f561b3bfb3330137bd804846afd4slive <td>Number of keep-alive requests on this connection</td></tr>
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd <td>Log ID of the connection if used in connection scope, empty otherwise</td></tr>
7b5535ed88e0f561b3bfb3330137bd804846afd4slive <td>System unique thread ID of current thread (the same ID as
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd displayed by e.g. <code>top</code>; currently Linux only)</td></tr>
7b5535ed88e0f561b3bfb3330137bd804846afd4slive <td>The current time in compact ISO 8601 format, including
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <td>The canonical <directive module="core">ServerName</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <td>The server name of the server serving the request according to the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="core" >UseCanonicalName</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The log ID format <code>%L</code> produces a unique id for a connection
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive or request. This can be used to correlate which log lines belong to the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive same connection or request, which request happens on which connection.
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <module>mod_log_config</module>, to allow to correlate access log entries
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess with error log lines. If <module>mod_unique_id</module> is loaded, its
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive unique id will be used as log ID for requests.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive#Example (default format for threaded MPMs)
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveErrorLogFormat "[%{u}t] [%-m:%l] [pid %P:tid %T] %7F: %E: [client\ %a] %M% ,\ referer\ %{Referer}i"
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive [Thu May 12 08:28:57.652118 2011] [core:error] [pid 8777:tid 4326490112] [client ::1:58619] File does not exist: /usr/local/apache2/htdocs/favicon.ico
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Notice that, as discussed above, some fields are omitted
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive entirely because they are not defined.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive#Example (similar to the 2.2.x format)
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveErrorLogFormat "[%t] [%l] %7F: %E: [client\ %a] %M% ,\ referer\ %{Referer}i"
003f0c9fda6664daf5092a0e42f65ede20098153slive </highlight>
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabeleErrorLogFormat "[%{uc}t] [%-m:%-l] [R:%L] [C:%{C}L] %7F: %E: %M"
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabeleErrorLogFormat request "[%{uc}t] [R:%L] Request %k on C:%{c}L pid:%P tid:%T"
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveErrorLogFormat request "[%{uc}t] [R:%L] UA:'%+{User-Agent}i'"
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveErrorLogFormat request "[%{uc}t] [R:%L] Referer:'%+{Referer}i'"
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveErrorLogFormat connection "[%{uc}t] [C:%{c}L] local\ %a remote\ %A"
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">ErrorLog</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">LogLevel</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><a href="/logs.html">Apache HTTP Server Log Files</a></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Keep track of extended status information for each
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliverequest</description>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<contextlist><context>server config</context></contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This option tracks additional data per worker about the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive currently executing request, and a utilization summary; you
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive can see these variables during runtime by configuring
003f0c9fda6664daf5092a0e42f65ede20098153slive <module>mod_status</module>. Note that other modules may
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive rely on this scoreboard.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This setting applies to the entire server, and cannot be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive enabled or disabled on a virtualhost-by-virtualhost basis.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive The collection of extended status information can slow down
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the server. Also note that this setting cannot be changed
130d299c4b2b15be45532a176604c71fdc7bea5bnd during a graceful restart.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Note that loading <module>mod_status</module> will change
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the default behavior to ExtendedStatus On, while other
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess third party modules may do the same. Such modules rely on
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess collecting detailed information about the state of all workers.
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess The default is changed by <module>mod_status</module> beginning
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess with version 2.3.6; the previous default was always Off.</p>
130d299c4b2b15be45532a176604c71fdc7bea5bnd</directivesynopsis>
130d299c4b2b15be45532a176604c71fdc7bea5bnd<directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<description>File attributes used to create the ETag
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cndHTTP response header for static files</description>
6c5c651b0b97607b8c8b4965c1385c67699f217fnd<contextlist><context>server config</context><context>virtual host</context>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</contextlist>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<compatibility>The default used to be "INode MTime Size" in 2.3.14 and
6c5c651b0b97607b8c8b4965c1385c67699f217fndearlier.</compatibility>
4bb78e7cdd53f50240cff4ad7a97c7ed36483797slive The <directive>FileETag</directive> directive configures the file
4bb78e7cdd53f50240cff4ad7a97c7ed36483797slive attributes that are used to create the <code>ETag</code> (entity
4bb78e7cdd53f50240cff4ad7a97c7ed36483797slive tag) response header field when the document is based on a static file.
4bb78e7cdd53f50240cff4ad7a97c7ed36483797slive (The <code>ETag</code> value is used in cache management to save
4bb78e7cdd53f50240cff4ad7a97c7ed36483797slive network bandwidth.) The
4bb78e7cdd53f50240cff4ad7a97c7ed36483797slive <directive>FileETag</directive> directive allows you to choose
4bb78e7cdd53f50240cff4ad7a97c7ed36483797slive which of these -- if any -- should be used. The recognized keywords are:
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <dd>The file's i-node number will be included in the calculation</dd>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <dd>The date and time the file was last modified will be included</dd>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <dd>The number of bytes in the file will be included</dd>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <dd>All available fields will be used. This is equivalent to:
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <highlight language="config">FileETag INode MTime Size</highlight></dd>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <dd>If a document is file-based, no <code>ETag</code> field will be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive included in the response</dd>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen <p>The <code>INode</code>, <code>MTime</code>, and <code>Size</code>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess keywords may be prefixed with either <code>+</code> or <code>-</code>,
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen which allow changes to be made to the default setting inherited
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive from a broader scope. Any keyword appearing without such a prefix
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive immediately and completely cancels the inherited setting.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>If a directory's configuration includes
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen <code>FileETag INode MTime Size</code>, and a
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen subdirectory's includes <code>FileETag -INode</code>,
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen the setting for that subdirectory (which will be inherited by
130d299c4b2b15be45532a176604c71fdc7bea5bnd any sub-subdirectories that don't override it) will be equivalent to
130d299c4b2b15be45532a176604c71fdc7bea5bnd Do not change the default for directories or locations that have WebDAV
130d299c4b2b15be45532a176604c71fdc7bea5bnd enabled and use <module>mod_dav_fs</module> as a storage provider.
7ef9b6763ad87846cf83c3f71467f43e349d080aerikabele <module>mod_dav_fs</module> uses <code>MTime Size</code>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen as a fixed format for <code>ETag</code> comparisons on conditional requests.
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen These conditional requests will break if the <code>ETag</code> format is
03e0a375c2435102fb2b51e34cccff52acbfddcdnd An ETag is not generated for responses parsed by <module>mod_include</module>,
03e0a375c2435102fb2b51e34cccff52acbfddcdnd since the response entity can change without a change of the INode, MTime, or Size
03e0a375c2435102fb2b51e34cccff52acbfddcdnd of the static file with embedded SSI directives.
03e0a375c2435102fb2b51e34cccff52acbfddcdnd</directivesynopsis>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd<description>Contains directives that apply to matched
03e0a375c2435102fb2b51e34cccff52acbfddcdndfilenames</description>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd<syntax><Files <var>filename</var>> ... </Files></syntax>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd<contextlist><context>server config</context><context>virtual host</context>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd</contextlist>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd <p>The <directive type="section">Files</directive> directive
03e0a375c2435102fb2b51e34cccff52acbfddcdnd limits the scope of the enclosed directives by filename. It is comparable
03e0a375c2435102fb2b51e34cccff52acbfddcdnd to the <directive module="core" type="section">Directory</directive>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd and <directive module="core" type="section">Location</directive>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd directives. It should be matched with a <code></Files></code>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd directive. The directives given within this section will be applied to
03e0a375c2435102fb2b51e34cccff52acbfddcdnd any object with a basename (last component of filename) matching the
03e0a375c2435102fb2b51e34cccff52acbfddcdnd specified filename. <directive type="section">Files</directive>
03e0a375c2435102fb2b51e34cccff52acbfddcdnd sections are processed in the order they appear in the
03e0a375c2435102fb2b51e34cccff52acbfddcdnd <code>.htaccess</code> files are read, but before <directive
03e0a375c2435102fb2b51e34cccff52acbfddcdnd type="section" module="core">Location</directive> sections. Note
03e0a375c2435102fb2b51e34cccff52acbfddcdnd that <directive type="section">Files</directive> can be nested
03e0a375c2435102fb2b51e34cccff52acbfddcdnd module="core">Directory</directive> sections to restrict the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive portion of the filesystem they apply to.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <var>filename</var> argument should include a filename, or
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive a wild-card string, where <code>?</code> matches any single character,
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd and <code>*</code> matches any sequences of characters.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<Files "cat.html">
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive # Insert stuff that applies to cat.html here
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</Files>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<Files "?at.*">
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive # This would apply to cat.html, bat.html, hat.php and so on.
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</Files>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive can also be used, with the addition of the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<Files ~ "\.(gif|jpe?g|png)$">
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</Files>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</highlight>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <p>would match most common Internet graphics formats. <directive
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess module="core" type="section">FilesMatch</directive> is preferred,
fb77c505254b6e9c925e23e734463e87574f8f40kess however.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="core">Directory</directive> and <directive type="section"
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="core">Location</directive> sections, <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive type="section">Files</directive> sections can be used inside
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>.htaccess</code> files. This allows users to control access to
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen their own files, at a file-by-file level.</p>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<seealso><a href="/sections.html">How <Directory>, <Location>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen and <Files> sections work</a> for an explanation of how these
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen different sections are combined when a request is received</seealso>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</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>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<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
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <directive module="core" type="section">Files</directive> directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive does. However, it accepts a <glossary ref="regex">regular
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<FilesMatch "\.(gif|jpe?g|png)$">
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</FilesMatch>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>would match most common Internet graphics formats.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>From 2.4.8 onwards, named groups and backreferences are captured and
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive written to the environment with the corresponding name prefixed with
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive "MATCH_" and in upper case. This allows elements of files to be referenced
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive from within <a href="/expr.html">expressions</a> and modules like
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <module>mod_rewrite</module>. In order to prevent confusion, numbered
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive (unnamed) backreferences are ignored. Use named groups instead.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<FilesMatch ^(?<sitename>[^/]+)>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen</FilesMatch>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen</highlight>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<seealso><a href="/sections.html">How <Directory>, <Location>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen and <Files> sections work</a> for an explanation of how these
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen different sections are combined when a request is received</seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Forces all matching files to be served with the specified
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivemedia type in the HTTP Content-Type header field</description>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<contextlist><context>directory</context><context>.htaccess</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
72580dbc2a55511f13f377063725b9f143b20826stoddard <p>When placed into an <code>.htaccess</code> file or a
72580dbc2a55511f13f377063725b9f143b20826stoddard <directive type="section" module="core">Directory</directive>, or
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive type="section" module="core">Location</directive> or
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <directive type="section" module="core">Files</directive>
72580dbc2a55511f13f377063725b9f143b20826stoddard section, this directive forces all matching files to be served
72580dbc2a55511f13f377063725b9f143b20826stoddard with the content type identification given by
72580dbc2a55511f13f377063725b9f143b20826stoddard <var>media-type</var>. For example, if you had a directory full of
72580dbc2a55511f13f377063725b9f143b20826stoddard GIF files, but did not want to label them all with <code>.gif</code>,
72580dbc2a55511f13f377063725b9f143b20826stoddard you might want to use:</p>
56d7eed7205462540aec7202cd82d9f5516fc537kess <highlight language="config">ForceType image/gif</highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Note that this directive overrides other indirect media type
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive associations defined in mime.types or via the
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen <p>You can also override more general
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<Location /images>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen</Location>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive# but normal mime-type associations here:
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive ForceType None
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</Location>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive primarily overrides the content types generated for
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd static files served out of the filesystem. For resources other than
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive static files, where the generator of the response typically specifies
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive a Content-Type, this directive has no effect.</p>
72580dbc2a55511f13f377063725b9f143b20826stoddard</directivesynopsis>
72580dbc2a55511f13f377063725b9f143b20826stoddard<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Directory to write gmon.out profiling data to. </description>
72580dbc2a55511f13f377063725b9f143b20826stoddard<syntax>GprofDir <var>/tmp/gprof/</var>|<var>/tmp/gprof/</var>%</syntax>
72580dbc2a55511f13f377063725b9f143b20826stoddard<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>When the server has been compiled with gprof profiling support,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive>GprofDir</directive> causes <code>gmon.out</code> files to
fb77c505254b6e9c925e23e734463e87574f8f40kess be written to the specified directory when the process exits. If the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive argument ends with a percent symbol ('%'), subdirectories are created
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive for each process id.</p>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen <p>This directive currently only works with the <module>prefork</module>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen</directivesynopsis>
ef8e89e090461194ecadd31e8796a2c51e0531a2kess<directivesynopsis>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<description>Enables DNS lookups on client IP addresses</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive enables DNS lookups so that host names can be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive logged (and passed to CGIs/SSIs in <code>REMOTE_HOST</code>).
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess The value <code>Double</code> refers to doing double-reverse
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive DNS lookup. That is, after a reverse lookup is performed, a forward
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele lookup is then performed on that result. At least one of the IP
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele addresses in the forward lookup must match the original
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele 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
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen will be performed. This is necessary for security. Note that the
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen result of this double-reverse isn't generally available unless you
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen set <code>HostnameLookups Double</code>. For example, if only
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen <code>HostnameLookups On</code> and a request is made to an object
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd that is protected by hostname restrictions, regardless of whether
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen the double-reverse fails or not, CGIs will still be passed the
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen single-reverse result in <code>REMOTE_HOST</code>.</p>
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
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>Off</code>, since DNS lookups can take considerable
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive amounts of time. The utility <program>logresolve</program>, compiled by
fb77c505254b6e9c925e23e734463e87574f8f40kess default to the <code>bin</code> subdirectory of your installation
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directory, can be used to look up host names from logged IP addresses
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive offline.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive href="mod_authz_host.html#reqhost">hostname-based Require
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess directives</a>, a hostname lookup will be performed regardless of
7852e17fb37b2a02ccdcab107f2c7f5fd41fd201nd</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Contains directives that apply only if a condition is
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivesatisfied by a request at runtime</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax><If <var>expression</var>> ... </If></syntax>
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive<contextlist><context>server config</context><context>virtual host</context>
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive<context>directory</context><context>.htaccess</context>
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive</contextlist>
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive <p>The <directive type="section">If</directive> directive
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive evaluates an expression at runtime, and applies the enclosed
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive directives if and only if the expression evaluates to true.
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive For example:</p>
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive <highlight language="config"><If "-z req('Host')"></highlight>
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive <p>would match HTTP/1.0 requests without a <var>Host:</var> header.
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive Expressions may contain various shell-like operators for string
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive comparison (<code>=</code>, <code>!=</code>, <code><</code>, ...),
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive integer comparison (<code>-eq</code>, <code>-ne</code>, ...),
234c8b28171d7e12b3c1f85b60fabd7c908a9c37slive and others (<code>-n</code>, <code>-z</code>, <code>-f</code>, ...).
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive It is also possible to use regular expressions, </p>
dc223428958ad9ff05011545bcdda000887b93e5slive <highlight language="config"><If "%{QUERY_STRING} =~ /(delete|commit)=.*?elem/"></highlight>
dc223428958ad9ff05011545bcdda000887b93e5slive <p>shell-like pattern matches and many other operations. These operations
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive can be done on request headers (<code>req</code>), environment variables
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive (<code>env</code>), and a large number of other properties. The full
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive documentation is available in <a href="/expr.html">Expressions in
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Only directives that support the <a href="directive-dict.html#Context"
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive >directory context</a> can be used within this configuration section.</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<seealso><a href="/expr.html">Expressions in Apache HTTP Server</a>,
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cndfor a complete reference and more examples.</seealso>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<seealso><directive type="section" module="core">ElseIf</directive></seealso>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<seealso><directive type="section" module="core">Else</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><a href="/sections.html">How <Directory>, <Location>,
fb77c505254b6e9c925e23e734463e87574f8f40kess <Files> sections work</a> for an explanation of how these
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess different sections are combined when a request is received.
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <directive type="section">Else</directive> are applied last.</seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Encloses directives that will be processed only
fb77c505254b6e9c925e23e734463e87574f8f40kessif a test is true at startup</description>
130d299c4b2b15be45532a176604c71fdc7bea5bnd </IfDefine></syntax>
130d299c4b2b15be45532a176604c71fdc7bea5bnd<contextlist><context>server config</context><context>virtual host</context>
130d299c4b2b15be45532a176604c71fdc7bea5bnd</contextlist>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>The <code><IfDefine <var>test</var>>...</IfDefine>
130d299c4b2b15be45532a176604c71fdc7bea5bnd </code> section is used to mark directives that are conditional. The
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd directives within an <directive type="section">IfDefine</directive>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd section are only processed if the <var>test</var> is true. If <var>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd test</var> is false, everything between the start and end markers is
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd ignored.</p>
05201775eaa6b363b8a119c8aea5db246b967591yoshiki >IfDefine</directive> section directive can be one of two forms:</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>In the former case, the directives between the start and end
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd markers are only processed if the parameter named
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <var>parameter-name</var> is defined. The second format reverses
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd the test, and only processes the directives if
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <var>parameter-name</var> is <strong>not</strong> defined.</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>The <var>parameter-name</var> argument is a define as given on the
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <program>httpd</program> command line via <code>-D<var>parameter</var>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd </code> at the time the server was started or by the <directive
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <p><directive type="section">IfDefine</directive> sections are
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess nest-able, which can be used to implement simple
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive multiple-parameter tests. Example:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <example>httpd -DReverseProxy -DUseCache -DMemCache ...</example>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<IfDefine ReverseProxy>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive LoadModule proxy_http_module modules/mod_proxy_http.so
8490b2f9f6469d5089163f6dd303d9a81f8e908ctrawick <IfDefine UseCache>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <IfDefine MemCache>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </IfDefine>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <IfDefine !MemCache>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess </IfDefine>
030108b1816bcda3d925df65357feabdce83bc94slive </IfDefine>
030108b1816bcda3d925df65357feabdce83bc94slive</IfDefine>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<description>Encloses directives that are processed conditional on the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivepresence or absence of a specific module</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax><IfModule [!]<var>module-file</var>|<var>module-identifier</var>> ...
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess </IfModule></syntax>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<contextlist><context>server config</context><context>virtual host</context>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<context>directory</context><context>.htaccess</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <code><IfModule <var>test</var>>...</IfModule></code>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd section is used to mark directives that are conditional on the presence of
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive a specific module. The directives within an <directive type="section"
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive >IfModule</directive> section are only processed if the <var>test</var>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive is true. If <var>test</var> is false, everything between the start and
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive end markers is ignored.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <var>test</var> in the <directive type="section"
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive >IfModule</directive> section directive can be one of two forms:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>In the former case, the directives between the start and end
530eba85dbd41b8a0fa5255d3648d1440199a661slive markers are only processed if the module named <var>module</var>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive is included in Apache httpd -- either compiled in or
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive >LoadModule</directive>. The second format reverses the test,
530eba85dbd41b8a0fa5255d3648d1440199a661slive and only processes the directives if <var>module</var> is
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <var>module</var> argument can be either the module identifier or
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the file name of the module, at the time it was compiled. For example,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>mod_rewrite.c</code> is the file name. If a module consists of
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive several source files, use the name of the file containing the string
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p><directive type="section">IfModule</directive> sections are
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive nest-able, which can be used to implement simple multiple-module
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <note>This section should only be used if you need to have one
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive configuration file that works whether or not a specific module
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive is available. In normal operation, directives need not be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive placed in <directive type="section">IfModule</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive sections.</note>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Includes other configuration files from within
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivethe server configuration files</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax>Include <var>file-path</var>|<var>directory-path</var>|<var>wildcard</var></syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<compatibility>Directory
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivewildcard matching available in 2.3.6 and later</compatibility>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive allows inclusion of other configuration files
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive from within the server configuration files.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Shell-style (<code>fnmatch()</code>) wildcard characters can be used
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive in the filename or directory parts of the path to include several files
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive at once, in alphabetical order. In addition, if
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive>Include</directive> points to a directory, rather than a file,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Apache httpd will read all files in that directory and any subdirectory.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive However, including entire directories is not recommended, because it is
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive easy to accidentally leave temporary files in a directory that can cause
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <program>httpd</program> to fail. Instead, we encourage you to use the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive wildcard syntax shown below, to include files that match a particular
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive pattern, such as *.conf, for example.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive module="core">Include</directive> directive will
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <strong>fail with an error</strong> if a wildcard expression does not
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive match any file. The <directive module="core">IncludeOptional</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directive can be used if non-matching wildcards should be ignored.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The file path specified may be an absolute path, or may be relative
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive to the <directive module="core">ServerRoot</directive> directory.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Wildcards may be included in the directory or file portion of the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive path. This example will fail if there is no subdirectory in conf/vhosts
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive that contains at least one *.conf file:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <highlight language="config">Include conf/vhosts/*/*.conf</highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Alternatively, the following command will just be ignored in case of
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive missing files or directories:</p>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen <highlight language="config">IncludeOptional conf/vhosts/*/*.conf</highlight>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<seealso><directive module="core">IncludeOptional</directive></seealso>
8b052d682204371decc64f942aede5ef1da98955erikabele</directivesynopsis>
8b052d682204371decc64f942aede5ef1da98955erikabele<directivesynopsis>
8b052d682204371decc64f942aede5ef1da98955erikabele<description>Includes other configuration files from within
8b052d682204371decc64f942aede5ef1da98955erikabelethe server configuration files</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax>IncludeOptional <var>file-path</var>|<var>directory-path</var>|<var>wildcard</var></syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<compatibility>Available in 2.3.6 and later</compatibility>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>This directive allows inclusion of other configuration files
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive from within the server configuration files. It works identically to the
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele <directive module="core">Include</directive> directive, with the
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele exception that if wildcards do not match any file or directory, the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="core">IncludeOptional</directive> directive will be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive silently ignored instead of causing an error.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">Include</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<directivesynopsis>
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<description>Enables HTTP persistent connections</description>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The Keep-Alive extension to HTTP/1.0 and the persistent
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive connection feature of HTTP/1.1 provide long-lived HTTP sessions
003f0c9fda6664daf5092a0e42f65ede20098153slive which allow multiple requests to be sent over the same TCP
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive connection. In some cases this has been shown to result in an
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd almost 50% speedup in latency times for HTML documents with
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive many images. To enable Keep-Alive connections, set
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>For HTTP/1.0 clients, Keep-Alive connections will only be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive used if they are specifically requested by a client. In
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive addition, a Keep-Alive connection with an HTTP/1.0 client can
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive only be used when the length of the content is known in
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd advance. This implies that dynamic content such as CGI output,
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd SSI pages, and server-generated directory listings will
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive generally not use Keep-Alive connections to HTTP/1.0 clients.
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd For HTTP/1.1 clients, persistent connections are the default
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd unless otherwise specified. If the client requests it, chunked
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd encoding will be used in order to send content of unknown
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive length over persistent connections.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>When a client uses a Keep-Alive connection it will be counted
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive as a single "request" for the <directive module="mpm_common"
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive >MaxConnectionsPerChild</directive> directive, regardless
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive of how many requests are sent using the connection.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">MaxKeepAliveRequests</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<directivesynopsis>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<description>Amount of time the server will wait for subsequent
9b5e2c5e769dc678a1aca06df75c32022b2f1492trawickrequests on a persistent connection</description>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<contextlist><context>server config</context><context>virtual host</context>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess</contextlist>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>The number of seconds Apache httpd will wait for a subsequent
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive request before closing the connection. By adding a postfix of ms the
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd timeout can be also set in milliseconds. Once a request has been
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd received, the timeout value specified by the
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <directive module="core">Timeout</directive> directive applies.</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>Setting <directive>KeepAliveTimeout</directive> to a high value
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd may cause performance problems in heavily loaded servers. The
fb77c505254b6e9c925e23e734463e87574f8f40kess higher the timeout, the more server processes will be kept
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd occupied waiting on connections with idle clients.</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>In a name-based virtual host context, the value of the first
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive defined virtual host best matching the local IP and port will be used.</p>
fb77c505254b6e9c925e23e734463e87574f8f40kess</directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<description>Restrict enclosed access controls to only certain HTTP
52bb691f8e13e9d0b55fcc214018ee85846fa87frbowenmethods</description>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<syntax><Limit <var>method</var> [<var>method</var>] ... > ...
fb77c505254b6e9c925e23e734463e87574f8f40kess </Limit></syntax>
fb77c505254b6e9c925e23e734463e87574f8f40kess<contextlist><context>directory</context><context>.htaccess</context>
27303c8bb552a8a5fc859feb735d686fc59f59a1yoshiki</contextlist>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>Access controls are normally effective for
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <strong>all</strong> access methods, and this is the usual
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd desired behavior. <strong>In the general case, access control
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd directives should not be placed within a
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <directive type="section">Limit</directive> section.</strong></p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>The purpose of the <directive type="section">Limit</directive>
3386d67e54f92fdf6a3ffc5f7f8081eed6c44badslive directive is to restrict the effect of the access controls to the
3386d67e54f92fdf6a3ffc5f7f8081eed6c44badslive nominated HTTP methods. For all other methods, the access
05201775eaa6b363b8a119c8aea5db246b967591yoshiki restrictions that are enclosed in the <directive
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen type="section">Limit</directive> bracket <strong>will have no
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen effect</strong>. The following example applies the access control
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive only to the methods <code>POST</code>, <code>PUT</code>, and
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>DELETE</code>, leaving all other methods unprotected:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<Limit POST PUT DELETE>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Require valid-user
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</Limit>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The method names listed can be one or more of: <code>GET</code>,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>POST</code>, <code>PUT</code>, <code>DELETE</code>,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>PATCH</code>, <code>PROPFIND</code>, <code>PROPPATCH</code>,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>MKCOL</code>, <code>COPY</code>, <code>MOVE</code>,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>LOCK</code>, and <code>UNLOCK</code>. <strong>The method name is
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive case-sensitive.</strong> If <code>GET</code> is used it will also
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive restrict <code>HEAD</code> requests. The <code>TRACE</code> method
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="core">LimitExcept</directive> section should always be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive used in preference to a <directive type="section">Limit</directive>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess section when restricting access, since a <directive type="section"
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="core">LimitExcept</directive> section provides protection
fb77c505254b6e9c925e23e734463e87574f8f40kess against arbitrary methods.</note>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive type="section">Limit</directive> and
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <directive type="section" module="core">LimitExcept</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directives may be nested. In this case, each successive level of
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive type="section">Limit</directive> or <directive
13e5182a0c199ecc7a73db97b6448a544e940868slive type="section" module="core">LimitExcept</directive> directives must
13e5182a0c199ecc7a73db97b6448a544e940868slive further restrict the set of methods to which access controls apply.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive type="section">LimitExcept</directive> directives with
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the <directive module="mod_authz_core">Require</directive> directive,
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd note that the first <directive module="mod_authz_core">Require</directive>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd to succeed authorizes the request, regardless of the presence of other
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <directive module="mod_authz_core">Require</directive> directives.</note>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>For example, given the following configuration, all users will
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <code>Require group editors</code> directive will be ignored
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd in all cases:</p>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<LimitExcept GET>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Require valid-user
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</LimitExcept>
13e5182a0c199ecc7a73db97b6448a544e940868slive<Limit POST>
13e5182a0c199ecc7a73db97b6448a544e940868slive Require group editors
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</Limit>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
13e5182a0c199ecc7a73db97b6448a544e940868slive<description>Restrict access controls to all HTTP methods
b00583f8e126bbb00b06dcf06af06c9d07978701kessexcept the named ones</description>
13e5182a0c199ecc7a73db97b6448a544e940868slive<syntax><LimitExcept <var>method</var> [<var>method</var>] ... > ...
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </LimitExcept></syntax>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess<contextlist><context>directory</context><context>.htaccess</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
13e5182a0c199ecc7a73db97b6448a544e940868slive <p><directive type="section">LimitExcept</directive> and
13e5182a0c199ecc7a73db97b6448a544e940868slive a group of access control directives which will then apply to any
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive HTTP access method <strong>not</strong> listed in the arguments;
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess i.e., it is the opposite of a <directive type="section"
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="core">Limit</directive> section and can be used to control
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive both standard and nonstandard/unrecognized methods. See the
13e5182a0c199ecc7a73db97b6448a544e940868slive type="section">Limit</directive> for more details.</p>
13e5182a0c199ecc7a73db97b6448a544e940868slive<LimitExcept POST GET>
13e5182a0c199ecc7a73db97b6448a544e940868slive Require valid-user
13e5182a0c199ecc7a73db97b6448a544e940868slive</LimitExcept>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
13e5182a0c199ecc7a73db97b6448a544e940868slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
13e5182a0c199ecc7a73db97b6448a544e940868slive<description>Determine maximum number of internal redirects and nested
13e5182a0c199ecc7a73db97b6448a544e940868slivesubrequests</description>
13e5182a0c199ecc7a73db97b6448a544e940868slive<syntax>LimitInternalRecursion <var>number</var> [<var>number</var>]</syntax>
13e5182a0c199ecc7a73db97b6448a544e940868slive<contextlist><context>server config</context><context>virtual host</context>
13e5182a0c199ecc7a73db97b6448a544e940868slive</contextlist>
13e5182a0c199ecc7a73db97b6448a544e940868slive <p>An internal redirect happens, for example, when using the <directive
13e5182a0c199ecc7a73db97b6448a544e940868slive module="mod_actions">Action</directive> directive, which internally
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive redirects the original request to a CGI script. A subrequest is Apache httpd's
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive mechanism to find out what would happen for some URI if it were requested.
3b9c7ec844aa240622a33735d1b9cbac4232e268rbowen For example, <module>mod_dir</module> uses subrequests to look for the
3b9c7ec844aa240622a33735d1b9cbac4232e268rbowen files listed in the <directive module="mod_dir">DirectoryIndex</directive>
3b9c7ec844aa240622a33735d1b9cbac4232e268rbowen directive.</p>
3b9c7ec844aa240622a33735d1b9cbac4232e268rbowen <p><directive>LimitInternalRecursion</directive> prevents the server
3b9c7ec844aa240622a33735d1b9cbac4232e268rbowen from crashing when entering an infinite loop of internal redirects or
fb77c505254b6e9c925e23e734463e87574f8f40kess subrequests. Such loops are usually caused by misconfigurations.</p>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>The directive stores two different limits, which are evaluated on
130d299c4b2b15be45532a176604c71fdc7bea5bnd per-request basis. The first <var>number</var> is the maximum number of
130d299c4b2b15be45532a176604c71fdc7bea5bnd internal redirects, that may follow each other. The second <var>number</var>
130d299c4b2b15be45532a176604c71fdc7bea5bnd determines, how deep subrequests may be nested. If you specify only one
130d299c4b2b15be45532a176604c71fdc7bea5bnd <var>number</var>, it will be assigned to both limits.</p>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <highlight language="config">LimitInternalRecursion 5</highlight>
130d299c4b2b15be45532a176604c71fdc7bea5bnd</directivesynopsis>
130d299c4b2b15be45532a176604c71fdc7bea5bnd<directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<description>Restricts the total size of the HTTP request body sent
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivefrom the client</description>
fb77c505254b6e9c925e23e734463e87574f8f40kess<contextlist><context>server config</context><context>virtual host</context>
fb77c505254b6e9c925e23e734463e87574f8f40kess<context>directory</context><context>.htaccess</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>This directive specifies the number of <var>bytes</var> from 0
130d299c4b2b15be45532a176604c71fdc7bea5bnd (meaning unlimited) to 2147483647 (2GB) that are allowed in a
130d299c4b2b15be45532a176604c71fdc7bea5bnd request body. See the note below for the limited applicability
130d299c4b2b15be45532a176604c71fdc7bea5bnd to proxy requests.</p>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>The <directive>LimitRequestBody</directive> directive allows
130d299c4b2b15be45532a176604c71fdc7bea5bnd the user to set a limit on the allowed size of an HTTP request
130d299c4b2b15be45532a176604c71fdc7bea5bnd message body within the context in which the directive is given
130d299c4b2b15be45532a176604c71fdc7bea5bnd (server, per-directory, per-file or per-location). If the client
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd request exceeds that limit, the server will return an error
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd response instead of servicing the request. The size of a normal
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive request message body will vary greatly depending on the nature of
fb77c505254b6e9c925e23e734463e87574f8f40kess the resource and the methods allowed on that resource. CGI scripts
fb77c505254b6e9c925e23e734463e87574f8f40kess typically use the message body for retrieving form information.
fb77c505254b6e9c925e23e734463e87574f8f40kess Implementations of the <code>PUT</code> method will require
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess a value at least as large as any representation that the server
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess wishes to accept for that resource.</p>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <p>This directive gives the server administrator greater
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess control over abnormal client request behavior, which may be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive useful for avoiding some forms of denial-of-service
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive attacks.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <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 <highlight language="config">LimitRequestBody 102400</highlight>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <note><p>For a full description of how this directive is interpreted by
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd proxy requests, see the <module>mod_proxy</module> documentation.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Limits the number of HTTP request header fields that
ef8e89e090461194ecadd31e8796a2c51e0531a2kesswill be accepted from the client</description>
ef8e89e090461194ecadd31e8796a2c51e0531a2kess<contextlist><context>server config</context><context>virtual host</context></contextlist>
ef8e89e090461194ecadd31e8796a2c51e0531a2kess <p><var>Number</var> is an integer from 0 (meaning unlimited) to
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess 32767. The default value is defined by the compile-time
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive constant <code>DEFAULT_LIMIT_REQUEST_FIELDS</code> (100 as
ef8e89e090461194ecadd31e8796a2c51e0531a2kess distributed).</p>
ef8e89e090461194ecadd31e8796a2c51e0531a2kess <p>The <directive>LimitRequestFields</directive> directive allows
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the server administrator to modify the limit on the number of
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive request header fields allowed in an HTTP request. A server needs
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive this value to be larger than the number of fields that a normal
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive client request might include. The number of request header fields
9ed9eaf871c58d281af02e76125ceadb5060afa5nd used by a client rarely exceeds 20, but this may vary among
9ed9eaf871c58d281af02e76125ceadb5060afa5nd different client implementations, often depending upon the extent
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive to which a user has configured their browser to support detailed
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive content negotiation. Optional HTTP extensions are often expressed
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd using request header fields.</p>
15e56959c3c6ae729207d91e13d08a022522661derikabele <p>This directive gives the server administrator greater
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive control over abnormal client request behavior, which may be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive useful for avoiding some forms of denial-of-service attacks.
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd The value should be increased if normal clients see an error
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd response from the server that indicates too many fields were
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive sent in the request.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <highlight language="config">LimitRequestFields 50</highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p> When name-based virtual hosting is used, the value for this
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directive is taken from the default (first-listed) virtual host for the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive local IP and port combination.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
ef8e89e090461194ecadd31e8796a2c51e0531a2kess<description>Limits the size of the HTTP request header allowed from the
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveclient</description>
530eba85dbd41b8a0fa5255d3648d1440199a661slive<syntax>LimitRequestFieldSize <var>bytes</var></syntax>
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele<contextlist><context>server config</context><context>virtual host</context></contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive specifies the number of <var>bytes</var>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive that will be allowed in an HTTP request header.</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>The <directive>LimitRequestFieldSize</directive> directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive allows the server administrator to set the limit
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive on the allowed size of an HTTP request header field. A server
ef8e89e090461194ecadd31e8796a2c51e0531a2kess 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
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive field will vary greatly among different client implementations,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive often depending upon the extent to which a user has configured
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive their browser to support detailed content negotiation. SPNEGO
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive authentication headers can be up to 12392 bytes.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive gives the server administrator greater
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive control over abnormal client request behavior, which may be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive useful for avoiding some forms of denial-of-service attacks.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <highlight language="config">LimitRequestFieldSize 4094</highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <note>Under normal conditions, the value should not be changed from
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the default.</note>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p> When name-based virtual hosting is used, the value for this
ef8e89e090461194ecadd31e8796a2c51e0531a2kess directive is taken from the default (first-listed) virtual host best
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive matching the current IP address and port combination.</p>
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Limit the size of the HTTP request line that will be accepted
80c4526970a11f37c0f8e3b82afdf03902dac3f3slivefrom the client</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context></contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive sets the number of <var>bytes</var> that will be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive allowed on the HTTP request-line.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive>LimitRequestLine</directive> directive allows
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the server administrator to set the limit on the allowed size
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive of a client's HTTP request-line. Since the request-line consists of the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive HTTP method, URI, and protocol version, the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive>LimitRequestLine</directive> directive places a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive restriction on the length of a request-URI allowed for a request
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive on the server. A server needs this value to be large enough to
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive hold any of its resource names, including any information that
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive might be passed in the query part of a <code>GET</code> request.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This directive gives the server administrator greater
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive control over abnormal client request behavior, which may be
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive useful for avoiding some forms of denial-of-service attacks.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <highlight language="config">LimitRequestLine 4094</highlight>
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele <note>Under normal conditions, the value should not be changed from
18b4b0fd6056093002ddef488636bf5ebe415ef0erikabele the default. Also, you can't set this higher than 8190 without
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive modifying the source and rebuilding.</note>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p> When name-based virtual hosting is used, the value for this
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directive is taken from the default (first-listed) virtual host best
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive matching the current IP address and port combination.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Limits the size of an XML-based request body</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<context>directory</context><context>.htaccess</context></contextlist>
9b5e2c5e769dc678a1aca06df75c32022b2f1492trawick <p>Limit (in bytes) on maximum size of an XML-based request
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess body. A value of <code>0</code> will disable any checking.</p>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <highlight language="config">LimitXMLRequestBody 0</highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Applies the enclosed directives only to matching
fb77c505254b6e9c925e23e734463e87574f8f40kessURLs</description>
003f0c9fda6664daf5092a0e42f65ede20098153slive<syntax><Location
fb77c505254b6e9c925e23e734463e87574f8f40kess <var>URL-path</var>|<var>URL</var>> ... </Location></syntax>
fb77c505254b6e9c925e23e734463e87574f8f40kess<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
521d38e84f603f3c8cdd15807fc3f8eb9e188b34nd <p>The <directive type="section">Location</directive> directive
521d38e84f603f3c8cdd15807fc3f8eb9e188b34nd limits the scope of the enclosed directives by URL. It is similar to the
521d38e84f603f3c8cdd15807fc3f8eb9e188b34nd <directive type="section" module="core">Directory</directive>
521d38e84f603f3c8cdd15807fc3f8eb9e188b34nd directive, and starts a subsection which is terminated with a
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive type="section">Location</directive> sections are processed in the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive order they appear in the configuration file, after the <directive
9ed9eaf871c58d281af02e76125ceadb5060afa5nd type="section" module="core">Directory</directive> sections and
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>.htaccess</code> files are read, and after the <directive
fb77c505254b6e9c925e23e734463e87574f8f40kess type="section" module="core">Files</directive> sections.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p><directive type="section">Location</directive> sections operate
fb77c505254b6e9c925e23e734463e87574f8f40kess completely outside the filesystem. This has several consequences.
fb77c505254b6e9c925e23e734463e87574f8f40kess Most importantly, <directive type="section">Location</directive>
fb77c505254b6e9c925e23e734463e87574f8f40kess directives should not be used to control access to filesystem
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive locations. Since several different URLs may map to the same
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive filesystem location, such access controls may by circumvented.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The enclosed directives will be applied to the request if the path component
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen of the URL meets <em>any</em> of the following criteria:
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen <li>The specified location matches exactly the path component of the URL.
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen <li>The specified location, which ends in a forward slash, is a prefix
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen of the path component of the URL (treated as a context root).
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <li>The specified location, with the addition of a trailing slash, is a
fb77c505254b6e9c925e23e734463e87574f8f40kess prefix of the path component of the URL (also treated as a context root).
521d38e84f603f3c8cdd15807fc3f8eb9e188b34nd In the example below, where no trailing slash is used, requests to
521d38e84f603f3c8cdd15807fc3f8eb9e188b34nd /private1, /private1/ and /private1/file.txt will have the enclosed
521d38e84f603f3c8cdd15807fc3f8eb9e188b34nd directives applied, but /private1other would not.
d3f27ec18dfa6283e852aa98253212edafaa0e2brbowen<Location /private1>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</Location>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
fb77c505254b6e9c925e23e734463e87574f8f40kess In the example below, where a trailing slash is used, requests to
003f0c9fda6664daf5092a0e42f65ede20098153slive /private2/ and /private2/file.txt will have the enclosed
fb77c505254b6e9c925e23e734463e87574f8f40kess directives applied, but /private2 and /private2other would not.
18831446030f4eda7e0563c92a896ccfdb6eb1d7slive</Location>
ef8e89e090461194ecadd31e8796a2c51e0531a2kess </highlight>
4cafc94e99922f00654e1779d30c2cccf5278c4fkess <p>Use <directive type="section">Location</directive> to apply
4cafc94e99922f00654e1779d30c2cccf5278c4fkess directives to content that lives outside the filesystem. For
4cafc94e99922f00654e1779d30c2cccf5278c4fkess content that lives in the filesystem, use <directive
4cafc94e99922f00654e1779d30c2cccf5278c4fkess type="section" module="core">Directory</directive> and <directive
4cafc94e99922f00654e1779d30c2cccf5278c4fkess type="section" module="core">Files</directive>. An exception is
4cafc94e99922f00654e1779d30c2cccf5278c4fkess <code><Location /></code>, which is an easy way to
4cafc94e99922f00654e1779d30c2cccf5278c4fkess apply a configuration to the entire server.</p>
27303c8bb552a8a5fc859feb735d686fc59f59a1yoshiki <p>For all origin (non-proxy) requests, the URL to be matched is a
4cafc94e99922f00654e1779d30c2cccf5278c4fkess URL-path of the form <code>/path/</code>. <em>No scheme, hostname,
4cafc94e99922f00654e1779d30c2cccf5278c4fkess port, or query string may be included.</em> For proxy requests, the
4cafc94e99922f00654e1779d30c2cccf5278c4fkess URL to be matched is of the form
4cafc94e99922f00654e1779d30c2cccf5278c4fkess <code>scheme://servername/path</code>, and you must include the
fb77c505254b6e9c925e23e734463e87574f8f40kess prefix.</p>
4cafc94e99922f00654e1779d30c2cccf5278c4fkess <p>The URL may use wildcards. In a wild-card string, <code>?</code> matches
4cafc94e99922f00654e1779d30c2cccf5278c4fkess any single character, and <code>*</code> matches any sequences of
4cafc94e99922f00654e1779d30c2cccf5278c4fkess characters. Neither wildcard character matches a / in the URL-path.</p>
96a8ac87abbb04c2a925f7fde5eb12bf1d1f4bc3slive <p><glossary ref="regex">Regular expressions</glossary>
96a8ac87abbb04c2a925f7fde5eb12bf1d1f4bc3slive can also be used, with the addition of the <code>~</code>
6452eaa76913f6ba732f88cfce6d4f8bf142482bkess character. For example:</p>
96a8ac87abbb04c2a925f7fde5eb12bf1d1f4bc3slive<Location ~ "/(extra|special)/data">
96a8ac87abbb04c2a925f7fde5eb12bf1d1f4bc3slive</Location>
96a8ac87abbb04c2a925f7fde5eb12bf1d1f4bc3slive</highlight>
96a8ac87abbb04c2a925f7fde5eb12bf1d1f4bc3slive <p>would match URLs that contained the substring <code>/extra/data</code>
96a8ac87abbb04c2a925f7fde5eb12bf1d1f4bc3slive or <code>/special/data</code>. The directive <directive
96a8ac87abbb04c2a925f7fde5eb12bf1d1f4bc3slive type="section" module="core">LocationMatch</directive> behaves
96a8ac87abbb04c2a925f7fde5eb12bf1d1f4bc3slive identical to the regex version of <directive
96a8ac87abbb04c2a925f7fde5eb12bf1d1f4bc3slive type="section">Location</directive>, and is preferred, for the
96a8ac87abbb04c2a925f7fde5eb12bf1d1f4bc3slive simple reason that <code>~</code> is hard to distinguish from
96a8ac87abbb04c2a925f7fde5eb12bf1d1f4bc3slive functionality is especially useful when combined with the
96a8ac87abbb04c2a925f7fde5eb12bf1d1f4bc3slive directive. For example, to enable status requests, but allow them
96a8ac87abbb04c2a925f7fde5eb12bf1d1f4bc3slive only from browsers at <code>example.com</code>, you might use:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<Location /status>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive SetHandler server-status
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Require host example.com
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</Location>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
2e5e2673cb64d3e4d445d911c6f61ac171020725nd <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
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive where multiple adjacent slashes are frequently collapsed to a single
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive slash (<em>i.e.</em>, <code>/home///foo</code> is the same as
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <code>/home/foo</code>). In URL-space this is not necessarily true.
2e5e2673cb64d3e4d445d911c6f61ac171020725nd The <directive type="section" module="core">LocationMatch</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directive and the regex version of <directive type="section"
733738e83a9b0113476e3f67992c2278d61ee4dakess >Location</directive> require you to explicitly specify multiple
733738e83a9b0113476e3f67992c2278d61ee4dakess slashes if that is your intention.</p>
2e5e2673cb64d3e4d445d911c6f61ac171020725nd <p>For example, <code><LocationMatch ^/abc></code> would match
2e5e2673cb64d3e4d445d911c6f61ac171020725nd the request URL <code>/abc</code> but not the request URL <code>
2e5e2673cb64d3e4d445d911c6f61ac171020725nd >Location</directive> directive behaves similarly when used for
2e5e2673cb64d3e4d445d911c6f61ac171020725nd proxy requests. But when (non-regex) <directive type="section"
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive >Location</directive> is used for non-proxy requests it will
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd implicitly match multiple slashes with a single slash. For example,
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd if you specify <code><Location /abc/def></code> and the
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd request is to <code>/abc//def</code> then it will match.</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>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">LocationMatch</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Applies the enclosed directives only to regular-expression
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cndmatching URLs</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax><LocationMatch
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <var>regex</var>> ... </LocationMatch></syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive type="section">LocationMatch</directive> directive
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd limits the scope of the enclosed directives by URL, in an identical manner
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd to <directive module="core" type="section">Location</directive>. However,
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd it takes a <glossary ref="regex">regular expression</glossary>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd as an argument instead of a simple string. For example:</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<LocationMatch "/(extra|special)/data">
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</LocationMatch>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>would match URLs that contained the substring <code>/extra/data</code>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>From 2.4.8 onwards, named groups and backreferences are captured and
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd written to the environment with the corresponding name prefixed with
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive "MATCH_" and in upper case. This allows elements of URLs to be referenced
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive from within <a href="/expr.html">expressions</a> and modules like
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <module>mod_rewrite</module>. In order to prevent confusion, numbered
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive (unnamed) backreferences are ignored. Use named groups instead.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<LocationMatch ^/combined/(?<sitename>[^/]+)>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</LocationMatch>
fb77c505254b6e9c925e23e734463e87574f8f40kess</highlight>
9b5e2c5e769dc678a1aca06df75c32022b2f1492trawick<seealso><a href="/sections.html">How <Directory>, <Location>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive and <Files> sections work</a> for an explanation of how these
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive different sections are combined when a request is received</seealso>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Controls the verbosity of the ErrorLog</description>
fb77c505254b6e9c925e23e734463e87574f8f40kess<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<compatibility>Per-module and per-directory configuration is available in
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Apache HTTP Server 2.3.6 and later</compatibility>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p><directive>LogLevel</directive> adjusts the verbosity of the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive messages recorded in the error logs (see <directive
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module="core">ErrorLog</directive> directive). The following
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <var>level</var>s are available, in order of decreasing
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive significance:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <columnspec><column width=".2"/><column width=".3"/><column width=".5"/>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </columnspec>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <td>"getpwuid: couldn't determine user name from uid"</td>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <td>"socket: Failed to get a socket, exiting child"</td>
58e56a1d61ae176cc5ecb7c4863881736947d8b8rbowen <td>"child process 1234 did not exit, sending another
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd SIGHUP"</td>
ef8e89e090461194ecadd31e8796a2c51e0531a2kess <td>"httpd: caught SIGBUS, attempting to dump core in
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <td>"Server seems busy, (you may need to increase
23b36269d124e7a6aaa5221891f7ae2ef3eeb158jerenkrantz <td>"proxy: CONNECT: sending the CONNECT request to the remote proxy"</td>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <td>"read from buffered SSL brigade, mode 0, 17 bytes"</td>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <td>"map lookup FAILED: map=rewritemap key=keyname"</td>
1a1cf0ee9229ee29e5750b25dd94dbb9b04072cfianh <td>"| 0000: 02 23 44 30 13 40 ac 34 df 3d bf 9a 19 49 39 15 |"</td>
530eba85dbd41b8a0fa5255d3648d1440199a661slive <td>Trace messages, dumping large amounts of data</td>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <td>"| 0000: 02 23 44 30 13 40 ac 34 df 3d bf 9a 19 49 39 15 |"</td>
530eba85dbd41b8a0fa5255d3648d1440199a661slive <p>When a particular level is specified, messages from all
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive other levels of higher significance will be reported as well.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <em>E.g.</em>, when <code>LogLevel info</code> is specified,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive then messages with log levels of <code>notice</code> and
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive recommended.</p>
23b36269d124e7a6aaa5221891f7ae2ef3eeb158jerenkrantz <highlight language="config">LogLevel notice</highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>When logging to a regular file messages of the level
f35c904c3b359610a46e94fbb4ba8495b2338521slive <code>notice</code> cannot be suppressed and thus are always
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive logged. However, this doesn't apply when logging is done
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>Specifying a level without a module name will reset the level
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive for all modules to that level. Specifying a level with a module
fb77c505254b6e9c925e23e734463e87574f8f40kess name will set the level for that module only. It is possible to
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive use the module source file name, the module identifier, or the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive module identifier with the trailing <code>_module</code> omitted
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive as module specification. This means the following three specifications
003f0c9fda6664daf5092a0e42f65ede20098153slive are equivalent:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveLogLevel info ssl:warn
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveLogLevel info mod_ssl.c:warn
313bb560bc5c323cfd40c9cad7335b4b8e060aedkessLogLevel info ssl_module:warn
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>It is also possible to change the level per directory:</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveLogLevel info
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd LogLevel debug
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</Directory>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Per directory loglevel configuration only affects messages that are
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive logged after the request has been parsed and that are associated with
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the request. Log messages which are associated with the server or
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess the connection are not affected. The latter can be influenced by the
db1b819ff8966e3c6a5ca03c59a8ae06c2cecc9frbowen <directive module="core">LogLevelOverride</directive> directive,
130d299c4b2b15be45532a176604c71fdc7bea5bnd<seealso><directive module="core">ErrorLog</directive></seealso>
130d299c4b2b15be45532a176604c71fdc7bea5bnd<seealso><directive module="core">ErrorLogFormat</directive></seealso>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<seealso><directive module="core">LogLevelOverride</directive></seealso>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<seealso><a href="/logs.html">Apache HTTP Server Log Files</a></seealso>
c97e8972ab1f4dd167e3dc4db87daf91114009fbnd</directivesynopsis>
c97e8972ab1f4dd167e3dc4db87daf91114009fbnd<directivesynopsis>
9f1dd1339447bf4b291682cd94bf9f28bc2685e0niq<description>Override the verbosity of the ErrorLog for certain clients</description>
9f1dd1339447bf4b291682cd94bf9f28bc2685e0niq<syntax>LogLevel <var>ipaddress</var>[/<var>prefixlen</var>]
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive [<var>module</var>:]<var>level</var> [<var>module</var>:<var>level</var>] ...
db1b819ff8966e3c6a5ca03c59a8ae06c2cecc9frbowen<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<compatibility>Available in Apache HTTP Server 2.5.0 and later</compatibility>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p><directive>LogLevelOverride</directive> adjusts the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="core">LogLevel</directive> for requests coming from
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd certain client IP addresses.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive This allows to enable verbose logging only for certain test clients.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive The IP address is checked at a very early state in the connection
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive processing. Therefore, <directive>LogLevelOverride</directive> allows to
003f0c9fda6664daf5092a0e42f65ede20098153slive change the log level for things like the SSL handshake which happen before
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive a <directive module="core">LogLevel</directive> directive in an
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive type="section" module="core">If</directive> container would
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive be evaluated.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p><directive>LogLevelOverride</directive> accepts either a single
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive IP-address or a CIDR IP-address/len subnet specification.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive For the syntax of the loglevel specification, see the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="core">LogLevel</directive> directive.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>For requests that match a <directive>LogLevelOverride</directive>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directive, per-directory specifications of
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="core">LogLevel</directive> are ignored.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive LogLevelOverride 192.0.2.7 ssl:trace8
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive </highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="core">LogLevelOverride</directive> only affects
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive log messages that are associated with the request or the connection.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive Log messages which are associated with the server not affected.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<seealso><directive module="core">LogLevel</directive></seealso>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Number of requests allowed on a persistent
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveconnection</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax>MaxKeepAliveRequests <var>number</var></syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd</contextlist>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>The <directive>MaxKeepAliveRequests</directive> directive
130d299c4b2b15be45532a176604c71fdc7bea5bnd limits the number of requests allowed per connection when
130d299c4b2b15be45532a176604c71fdc7bea5bnd <directive module="core" >KeepAlive</directive> is on. If it is
130d299c4b2b15be45532a176604c71fdc7bea5bnd set to <code>0</code>, unlimited requests will be allowed. We
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd recommend that this setting be kept to a high value for maximum
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive server performance.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <highlight language="config">MaxKeepAliveRequests 500</highlight>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
003f0c9fda6664daf5092a0e42f65ede20098153slive<description>Number of ranges allowed before returning the complete
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveresource </description>
6b64034fa2a644ba291c484c0c01c7df5b8d982ckess<syntax>MaxRanges default | unlimited | none | <var>number-of-ranges</var></syntax>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<contextlist><context>server config</context><context>virtual host</context>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<compatibility>Available in Apache HTTP Server 2.3.15 and later</compatibility>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive limits the number of HTTP ranges the server is willing to
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive return to the client. If more ranges than permitted are requested,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the complete resource is returned instead.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <dd>Limits the number of ranges to a compile-time default of 200.</dd>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <dd>The server does not limit the number of ranges it is
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive willing to satisfy.</dd>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <dd>A positive number representing the maximum number of ranges the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive server is willing to satisfy.</dd>
b00fe3c3354db01001b8eddfd9b88441380f837dwrowe</directivesynopsis>
12099dff89f3135d53929f4f1bdb42c7d044d928nd<directivesynopsis>
b00fe3c3354db01001b8eddfd9b88441380f837dwrowe <description>Number of overlapping ranges (eg: <code>100-200,150-300</code>) allowed before returning the complete
12099dff89f3135d53929f4f1bdb42c7d044d928nd resource </description>
cb646158ff2c192d4325a10a280e5006d191db8awrowe <syntax>MaxRangeOverlaps default | unlimited | none | <var>number-of-ranges</var></syntax>
b00fe3c3354db01001b8eddfd9b88441380f837dwrowe <contextlist><context>server config</context><context>virtual host</context>
12099dff89f3135d53929f4f1bdb42c7d044d928nd </contextlist>
12099dff89f3135d53929f4f1bdb42c7d044d928nd <compatibility>Available in Apache HTTP Server 2.3.15 and later</compatibility>
12099dff89f3135d53929f4f1bdb42c7d044d928nd limits the number of overlapping HTTP ranges the server is willing to
b00fe3c3354db01001b8eddfd9b88441380f837dwrowe return to the client. If more overlapping ranges than permitted are requested,
b00fe3c3354db01001b8eddfd9b88441380f837dwrowe the complete resource is returned instead.</p>
12099dff89f3135d53929f4f1bdb42c7d044d928nd <dd>Limits the number of overlapping ranges to a compile-time default of 20.</dd>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <dd>The server does not limit the number of overlapping ranges it is
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive willing to satisfy.</dd>
fb77c505254b6e9c925e23e734463e87574f8f40kess <dd>A positive number representing the maximum number of overlapping ranges the
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim server is willing to satisfy.</dd>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd<directivesynopsis>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <description>Number of range reversals (eg: <code>100-200,50-70</code>) allowed before returning the complete
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd resource </description>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <syntax>MaxRangeReversals default | unlimited | none | <var>number-of-ranges</var></syntax>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <contextlist><context>server config</context><context>virtual host</context>
fb77c505254b6e9c925e23e734463e87574f8f40kess </contextlist>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <compatibility>Available in Apache HTTP Server 2.3.15 and later</compatibility>
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <p>The <directive>MaxRangeReversals</directive> directive
3c6c63407f1855ddfc45ac69b69a2a9bf15135e6rbowen limits the number of HTTP Range reversals the server is willing to
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess return to the client. If more ranges reversals than permitted are requested,
3c6c63407f1855ddfc45ac69b69a2a9bf15135e6rbowen the complete resource is returned instead.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <dd>Limits the number of range reversals to a compile-time default of 20.</dd>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <dd>The server does not limit the number of range reversals it is
3c6c63407f1855ddfc45ac69b69a2a9bf15135e6rbowen willing to satisfy.</dd>
3c6c63407f1855ddfc45ac69b69a2a9bf15135e6rbowen <dd>A positive number representing the maximum number of range reversals the
fb77c505254b6e9c925e23e734463e87574f8f40kess server is willing to satisfy.</dd>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive</directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<directivesynopsis>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<description>Configures mutex mechanism and lock file directory for all
80c4526970a11f37c0f8e3b82afdf03902dac3f3sliveor specified mutexes</description>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive<syntax>Mutex <var>mechanism</var> [default|<var>mutex-name</var>] ... [OmitPID]</syntax>
130d299c4b2b15be45532a176604c71fdc7bea5bnd<contextlist><context>server config</context></contextlist>
130d299c4b2b15be45532a176604c71fdc7bea5bnd<compatibility>Available in Apache HTTP Server 2.3.4 and later</compatibility>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The <directive>Mutex</directive> directive sets the mechanism,
130d299c4b2b15be45532a176604c71fdc7bea5bnd and optionally the lock file location, that httpd and modules use
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive to serialize access to resources. Specify <code>default</code> as
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim the first argument to change the settings for all mutexes; specify
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim a mutex name (see table below) as the first argument to override
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim defaults only for that mutex.</p>
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim <p>The <directive>Mutex</directive> directive is typically used in
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim the following exceptional situations:</p>
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim <li>change the mutex mechanism when the default mechanism selected
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim by <glossary>APR</glossary> has a functional or performance
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim problem</li>
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim <li>change the directory used by file-based mutexes when the
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim default directory does not support locking</li>
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim <p>This directive only configures mutexes which have been registered
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim with the core server using the <code>ap_mutex_register()</code> API.
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim All modules bundled with httpd support the <directive>Mutex</directive>
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim directive, but third-party modules may not. Consult the documentation
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim of the third-party module, which must indicate the mutex name(s) which
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim can be configured if this directive is supported.</p>
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim <p>The following mutex <em>mechanisms</em> are available:</p>
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim <p>This selects the default locking implementation, as determined by
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim <glossary>APR</glossary>. The default locking implementation can
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim be displayed by running <program>httpd</program> with the
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim <p>This effectively disables the mutex, and is only allowed for a
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim mutex if the module indicates that it is a valid choice. Consult the
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim <p>This is a mutex variant based on a Posix semaphore.</p>
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim <p>The semaphore ownership is not recovered if a thread in the process
a38b5f73e7f0f3b8726fb47d27b145f37036ead0jim holding the mutex segfaults, resulting in a hang of the web server.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This is a mutex variant based on a SystemV IPC semaphore.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>It is possible to "leak" SysV semaphores if processes crash
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive before the semaphore is removed.</p>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>The semaphore API allows for a denial of service attack by any
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd CGIs running under the same uid as the webserver (<em>i.e.</em>,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive all CGIs, unless you use something like <program>suexec</program>
a23acbbd61b9565caecea9931b6bcdf0b6228cbbslive <p>This selects the "best" available semaphore implementation, choosing
a23acbbd61b9565caecea9931b6bcdf0b6228cbbslive between Posix and SystemV IPC semaphores, in that order.</p></li>
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>This is a mutex variant based on cross-process Posix thread
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd mutexes.</p>
a23acbbd61b9565caecea9931b6bcdf0b6228cbbslive <p>On most systems, if a child process terminates abnormally while
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive holding a mutex that uses this implementation, the server will deadlock
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive and stop responding to requests. When this occurs, the server will
a23acbbd61b9565caecea9931b6bcdf0b6228cbbslive require a manual restart to recover.</p>
a23acbbd61b9565caecea9931b6bcdf0b6228cbbslive <p>Solaris is a notable exception as it provides a mechanism which
fb77c505254b6e9c925e23e734463e87574f8f40kess usually allows the mutex to be recovered after a child process
a23acbbd61b9565caecea9931b6bcdf0b6228cbbslive terminates abnormally while holding a mutex.</p>
a23acbbd61b9565caecea9931b6bcdf0b6228cbbslive <p>If your system implements the
a23acbbd61b9565caecea9931b6bcdf0b6228cbbslive <code>pthread_mutexattr_setrobust_np()</code> function, you may be able
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>This is a mutex variant where a physical (lock-)file and the
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>When multiple mutexes based on this mechanism are used within
130d299c4b2b15be45532a176604c71fdc7bea5bnd multi-threaded, multi-process environments, deadlock errors (EDEADLK)
130d299c4b2b15be45532a176604c71fdc7bea5bnd can be reported for valid mutex operations if <code>fcntl()</code>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd is not thread-aware, such as on Solaris.</p>
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd <p>This is similar to the <code>fcntl:/path/to/mutex</code> method
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd with the exception that the <code>flock()</code> function is used to
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>This selects the "best" available file locking implementation,
130d299c4b2b15be45532a176604c71fdc7bea5bnd choosing between <code>fcntl</code> and <code>flock</code>, in that
130d299c4b2b15be45532a176604c71fdc7bea5bnd <p>Most mechanisms are only available on selected platforms, where the
130d299c4b2b15be45532a176604c71fdc7bea5bnd underlying platform and <glossary>APR</glossary> support it. Mechanisms
a7f40ca49262952d6dd69d021cf5b0c2b452ae4cnd which aren't available on all platforms are <em>posixsem</em>,
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess <em>sysvsem</em>, <em>sem</em>, <em>pthread</em>, <em>fcntl</em>,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <p>With the file-based mechanisms <em>fcntl</em> and <em>flock</em>,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive the path, if provided, is a directory where the lock file will be created.
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive The default directory is httpd's run-time file directory,
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive <directive module="core">DefaultRuntimeDir</directive>. If a relative
313bb560bc5c323cfd40c9cad7335b4b8e060aedkess path is provided, it is relative to
a23acbbd61b9565caecea9931b6bcdf0b6228cbbslive <directive module="core">DefaultRuntimeDir</directive>. Always use a local
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive disk filesystem for <code>/path/to/mutex</code> and never a directory residing
130d299c4b2b15be45532a176604c71fdc7bea5bnd on a NFS- or AFS-filesystem. The basename of the file will be the mutex
130d299c4b2b15be45532a176604c71fdc7bea5bnd type, an optional instance string provided by the module, and unless the
fb77c505254b6e9c925e23e734463e87574f8f40kess <code>OmitPID</code> keyword is specified, the process id of the httpd
130d299c4b2b15be45532a176604c71fdc7bea5bnd parent process will be appended to to make the file name unique, avoiding
130d299c4b2b15be45532a176604c71fdc7bea5bnd conflicts when multiple httpd instances share a lock file directory. For
130d299c4b2b15be45532a176604c71fdc7bea5bnd example, if the mutex name is <code>mpm-accept</code> and the lock file
130d299c4b2b15be45532a176604c71fdc7bea5bnd directory is <code>/var/httpd/locks</code>, the lock file name for the
a23acbbd61b9565caecea9931b6bcdf0b6228cbbslive httpd instance with parent process id 12345 would be
fb77c505254b6e9c925e23e734463e87574f8f40kess <p>It is best to <em>avoid</em> putting mutex files in a world-writable
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive directory such as <code>/var/tmp</code> because someone could create
a23acbbd61b9565caecea9931b6bcdf0b6228cbbslive a denial of service attack and prevent the server from starting by
a23acbbd61b9565caecea9931b6bcdf0b6228cbbslive creating a lockfile with the same name as the one the server will try
506ccad87840d0f348a9b9560b711f0a8398ce6aslive to create.</p>
a23acbbd61b9565caecea9931b6bcdf0b6228cbbslive <p>The following table documents the names of mutexes used by httpd
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive and bundled modules.</p>
130d299c4b2b15be45532a176604c71fdc7bea5bnd <td><module>prefork</module> and <module>worker</module> MPMs</td>
9b5e2c5e769dc678a1aca06df75c32022b2f1492trawick <td>incoming connections, to avoid the thundering herd problem;
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive for more information, refer to the
80c4526970a11f37c0f8e3b82afdf03902dac3f3slive documentation</td>
<p>You only need to set the protocol if you are running on non-standard ports, otherwise <code>http</code> is assumed for port 80 and <code>https</code> for port 443.</p>
<p>For example, if you are running <code>https</code> on a non-standard port, specify the protocol explicitly:</p>
<p>You can also specify the protocol using the <directive module="mpm_common">Listen</directive> directive.</p>
ServerName server.example.com
ServerAlias server server2.example.com server2
ServerAlias *.example.com
<syntax>ServerName [<var>scheme</var>://]<var>fully-qualified-domain-name</var>[:<var>port</var>]</syntax>
settings which determine whether self-referential URLs (e.g., by the
httpd: Could not reliably determine the server's fully qualified domain name, using rocinante.local for ServerName
href="http://wiki.apache.org/httpd/FAQ#Why_does_Apache_ask_for_my_password_twice_before_serving_a_file.3F">
ServerName host.example.com
ServerName host.example.com