core.html revision 2724768e1047c3c6d547805ef7310837656daaf8
f79d43bbe70a01454049b77d6f15f6369744959eStéphane Graber<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano BGCOLOR="#FFFFFF"
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano TEXT="#000000"
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano LINK="#0000FF"
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano VLINK="#000080"
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano ALINK="#FF0000"
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--#include virtual="header.html" -->
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThese configuration parameters control the core Apache features, and are
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoalways available.
99e4008cad9e959b683c6f48411fcf15a92be3b5Michel Normand<li><A HREF="#allowoverride">AllowOverride</A>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<li><A HREF="#directorymatch"><DirectoryMatch></A>
d5cf438682963ac84c3617941032ba623d4ac9b2Michel Normand<li><A HREF="#identitycheck">IdentityCheck</A>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<li><A HREF="#keepalivetimeout">KeepAliveTimeout</A>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<li><A HREF="#locationmatch"><LocationMatch></A>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<li><A HREF="#maxkeepaliverequests">MaxKeepAliveRequests</a>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<li><A HREF="#maxrequestsperchild">MaxRequestsPerChild</A>
6a22713f648be8bd21297f57d9b631eb4c537ffeDaniel Lezcano<li><A HREF="#resourceconfig">ResourceConfig</A>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<h2><A name="accessconfig">AccessConfig directive</A></h2>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt AccessConfig} directive> -->
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Syntax:</strong> AccessConfig <em>filename</em><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Default:</strong> <code>AccessConfig conf/access.conf</code><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Context:</strong> server config, virtual host<br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThe server will read this file for more directives after reading the
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<A HREF="#resourceconfig">ResourceConfig</A> file. <em>Filename</em> is
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanorelative to the <A HREF="#serverroot">ServerRoot</A>.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThis feature can be disabled using:
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<blockquote><code>AccessConfig /dev/null</code></blockquote>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoHistorically, this file only contained
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand<A HREF="#directory"><Directory></A> sections; in fact it can now
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanocontain any server directive allowed in the <em>server config</em> context.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<h2><A name="accessfilename">AccessFileName directive</A></h2>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt AccessFileName} directive> -->
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Syntax:</strong> AccessFileName <em>filename filename ...</em><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Default:</strong> <code>AccessFileName .htaccess</code><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Context:</strong> server config, virtual host<br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Compatibility:</strong> AccessFileName can accept more than one filename only in Apache 1.3 and later<p>
0478642a4349846ab8e76e318909886e795df92dFilippo GiunchediWhen returning a document to the client the server looks for the first existing
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoaccess control file from this list of names in every directory of the path to
0478642a4349846ab8e76e318909886e795df92dFilippo Giunchedithe document, if access control files are enabled for that directory.
0478642a4349846ab8e76e318909886e795df92dFilippo Giunchedi<blockquote><code>AccessFileName .acl</code></blockquote>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanobefore returning the document /usr/local/web/index.html, the
0478642a4349846ab8e76e318909886e795df92dFilippo Giunchediserver will read /.acl, /usr/.acl, /usr/local/.acl and /usr/local/web/.acl
0478642a4349846ab8e76e318909886e795df92dFilippo Giunchedifor directives, unless they have been disabled with
0478642a4349846ab8e76e318909886e795df92dFilippo Giunchedi<Directory /><br>
0478642a4349846ab8e76e318909886e795df92dFilippo GiunchediAllowOverride None<br>
0478642a4349846ab8e76e318909886e795df92dFilippo Giunchedi</Directory></code></blockquote><p><hr>
0478642a4349846ab8e76e318909886e795df92dFilippo Giunchedi<h2><A name="addmodule">AddModule directive</A></h2>
0478642a4349846ab8e76e318909886e795df92dFilippo Giunchedi<!--%plaintext <?INDEX {\tt AddModule} directive> -->
6a22713f648be8bd21297f57d9b631eb4c537ffeDaniel Lezcano<strong>Syntax:</strong> AddModule <em>module module ...</em><br>
6a22713f648be8bd21297f57d9b631eb4c537ffeDaniel Lezcano<strong>Compatibility:</strong> AddModule is only available in Apache 1.2 and later<p>
6a22713f648be8bd21297f57d9b631eb4c537ffeDaniel LezcanoThe server can have modules compiled in which are not actively in use.
6a22713f648be8bd21297f57d9b631eb4c537ffeDaniel LezcanoThis directive can be used to enable the use of those modules. The
6a22713f648be8bd21297f57d9b631eb4c537ffeDaniel Lezcanoserver comes with a pre-loaded list of active modules; this list can
6a22713f648be8bd21297f57d9b631eb4c537ffeDaniel Lezcanobe cleared with the <A HREF="#clearmodulelist">ClearModuleList</A>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<h2><A name="allowoverride">AllowOverride directive</A></h2>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt AllowOverride} directive> -->
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Syntax:</strong> AllowOverride <em>override override ...</em><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Default:</strong> <code>AllowOverride All</code><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoWhen the server finds an .htaccess file (as specified by
0d9f8e188c1c4832e4f6b9de646478947ae86877Daniel Lezcano<A HREF="#accessfilename">AccessFileName</A>) it needs to know which
0d9f8e188c1c4832e4f6b9de646478947ae86877Daniel Lezcanodirectives declared in that file can override earlier access information.<p>
6a22713f648be8bd21297f57d9b631eb4c537ffeDaniel Lezcano<em>Override</em> can be set to <code>None</code>, in which case the server
6a22713f648be8bd21297f57d9b631eb4c537ffeDaniel Lezcanowill not read the file, <code>All</code> in which case the server will
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoallow all the directives, or one or more of the following:
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<dt>AuthConfig
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt AuthConfig} override> -->
0d9f8e188c1c4832e4f6b9de646478947ae86877Daniel LezcanoAllow use of the authorization directives
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano(<A HREF="mod_auth_dbm.html#authdbmgroupfile">AuthDBMGroupFile</A>,
0d9f8e188c1c4832e4f6b9de646478947ae86877Daniel Lezcano<A HREF="mod_auth_dbm.html#authdbmuserfile">AuthDBMUserFile</A>,
0d9f8e188c1c4832e4f6b9de646478947ae86877Daniel Lezcano<A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A>,
0d9f8e188c1c4832e4f6b9de646478947ae86877Daniel Lezcano<A HREF="#authname">AuthName</A>, <A HREF="#authtype">AuthType</A>,
0d9f8e188c1c4832e4f6b9de646478947ae86877Daniel Lezcano<A HREF="mod_auth.html#authuserfile">AuthUserFile</A>,
0d9f8e188c1c4832e4f6b9de646478947ae86877Daniel Lezcano<!--%plaintext <?INDEX {\tt FileInfo} override> -->
0d9f8e188c1c4832e4f6b9de646478947ae86877Daniel LezcanoAllow use of the directives controlling document types
0d9f8e188c1c4832e4f6b9de646478947ae86877Daniel Lezcano(<A HREF="mod_mime.html#addencoding">AddEncoding</A>,
0d9f8e188c1c4832e4f6b9de646478947ae86877Daniel Lezcano<A HREF="mod_mime.html#addlanguage">AddLanguage</A>,
0d9f8e188c1c4832e4f6b9de646478947ae86877Daniel Lezcano<A HREF="mod_negotiation.html#languagepriority">LanguagePriority</A>, etc.).
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt Indexes} override> -->
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoAllow use of the directives controlling directory indexing
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano(<A HREF="mod_autoindex.html#adddescription">AddDescription</A>,
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand<A HREF="mod_autoindex.html#addiconbyencoding">AddIconByEncoding</A>,
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand<A HREF="mod_autoindex.html#addiconbytype">AddIconByType</A>,
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand<A HREF="mod_autoindex.html#defaulticon">DefaultIcon</A>,
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand<A HREF="mod_autoindex.html#directoryindex">DirectoryIndex</A>,
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand<A HREF="mod_autoindex.html#fancyindexing">FancyIndexing</A>,
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand<A HREF="mod_autoindex.html#headername">HeaderName</A>,
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand<A HREF="mod_autoindex.html#indexignore">IndexIgnore</A>,
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<A HREF="mod_autoindex.html#indexoptions">IndexOptions</A>,
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<A HREF="mod_autoindex.html#readmename">ReadmeName</A>, etc.).
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt Limit} override> -->
b6d441f289eb03a1a6fe0662a14c26ecc852be21dlezcanoAllow use of the directives controlling host access (allow, deny and order).
b6d441f289eb03a1a6fe0662a14c26ecc852be21dlezcano<!--%plaintext <?INDEX {\tt Options} override> -->
b6d441f289eb03a1a6fe0662a14c26ecc852be21dlezcanoAllow use of the directives controlling specific directory features
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt AuthName} directive> -->
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Syntax:</strong> AuthName <em>auth-domain</em><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThis directive sets the name of the authorization realm for a directory.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThis realm is given to the client so that the user knows which username and
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanopassword to send.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoIt must be accompanied by <A HREF="#authtype">AuthType</A> and
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<A HREF="#require">require</A> directives, and directives such as
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<A HREF="mod_auth.html#authuserfile">AuthUserFile</A> and
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> to work.<p><hr>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt AuthType} directive> -->
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThis directive selects the type of user authentication for a directory.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt Basic} authentication scheme> -->
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoIt must be accompanied by <A HREF="#authname">AuthName</A> and
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<A HREF="#require">require</A> directives, and directives such as
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<A HREF="mod_auth.html#authuserfile">AuthUserFile</A> and
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<A HREF="mod_auth.html#authgroupfile">AuthGroupFile</A> to work.<p><hr>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<h2><A name="bindaddress">BindAddress directive</A></h2>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt BindAddress} directive> -->
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Syntax:</strong> BindAddress <em>saddr</em><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Default:</strong> <code>BindAddress *</code><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoA Unix® http server can either listen for connections to every
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoIP address of the server machine, or just one IP address of the server
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<li>An IP address
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<li>A fully-qualified Internet domain name
f79d43bbe70a01454049b77d6f15f6369744959eStéphane GraberIf the value is *, then the server will listen for connections on
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoevery IP address, otherwise it will only listen on the IP address
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanospecified. <p>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThis option can be used as an alternative method for supporting
c159cb963868d4646cf415abb064d8fd4b6ee848Daniel Lezcano<A HREF="/virtual-host.html">virtual hosts</A> instead of using
c159cb963868d4646cf415abb064d8fd4b6ee848Daniel Lezcano<A HREF="#virtualhost"><VirtualHost></A> sections.
c159cb963868d4646cf415abb064d8fd4b6ee848Daniel Lezcano<a href="/dns-caveats.html">DNS Issues</a><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<a href="/bind.html">Setting which addresses and ports Apache uses</a></p>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<h2><A name="clearmodulelist">ClearModuleList directive</A></h2>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt ClearModuleList} directive> -->
b6d441f289eb03a1a6fe0662a14c26ecc852be21dlezcano<strong>Compatibility:</strong> ClearModuleList is only available in Apache 1.2 and later<p>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThe server comes with a built-in list of active modules. This
b6d441f289eb03a1a6fe0662a14c26ecc852be21dlezcanodirective clears the list. It is assumed that the list will then be
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanore-populated using the <A HREF="#addmodule">AddModule</A> directive.<p><hr>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<h2><A name="defaulttype">DefaultType directive</A></h2>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt DefaultType} directive> -->
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Syntax:</strong> DefaultType <em>mime-type</em><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Default:</strong> <code>DefaultType text/html</code><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Context:</strong> server config, virtual host, directory, .htaccess<br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThere will be times when the server is asked to provide a document
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanowhose type cannot be determined by its MIME types mappings.<p>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThe server must inform the client of the content-type of the document, so in
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanothe event of an unknown type it uses the <CODE>DefaultType</CODE>. For
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<blockquote><code>DefaultType image/gif</code></blockquote>
aa8d013ec5b09cd1cd904173d6234ef126eb2126Peter Simonswould be appropriate for a directory which contained many gif images
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<h2><A name="directory"><Directory> directive</A></h2>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt Directory} section directive> -->
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Syntax:</strong> <Directory <em>directory</em>> ... </Directory> <br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Context:</strong> server config, virtual host<br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<Directory> and </Directory> are used to enclose a group of
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanodirectives which will apply only to the named directory and sub-directories
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoof that directory. Any directive which is allowed in a directory
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanocontext may be used. <em>Directory</em> is either the full path to a directory,
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoor a wild-card string. In a wild-card string, `?' matches any single character,
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoand `*' matches any sequences of characters. Example:
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano Options Indexes FollowSymLinks
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano </Directory>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoExtended regular expressions can also be used, with the addition of the
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano <Directory ~ "^/www/.*/[0-9]{3}">
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanowould match directories in /www/ that consisted of three numbers. In
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoApache 1.3 and later, it is reccomended to use
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<a href="#directorymatch"><DirectoryMatch></a> instead.<p>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<p>If multiple directory sections match the directory (or its parents) containing
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoa document, then the directives are applied in the order of shortest match
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanofirst, interspersed with the directives from the
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<A HREF="#accessfilename">.htaccess</A> files. For example, with
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<Directory /><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoAllowOverride None<br>
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand<Directory /home/*><br>
a941cc0bf6c215079f56d68930370dcd8c6002afMichel NormandAllowOverride FileInfo<br>
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normandfor access to the document <code>/home/web/dir/doc.html</code> the
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand<li>Apply directive <code>AllowOverride None</code> (disabling
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<li>Apply directive <code>AllowOverride FileInfo</code> (for directory
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<li>Apply any FileInfo directives in <code>/home/web/.htaccess</code>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoNote that the default Apache access for <Directory /> is
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<SAMP>Allow from All</SAMP>. This means that Apache will serve any file
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanomapped from an URL. It is recommended that you change this with a block
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand <Directory />
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand Order Deny,Allow
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand Deny from All
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand </Directory>
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normandand then override this for directories you <EM>want</EM> accessible.
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand>Security Tips</A>
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normandpage for more details.
a941cc0bf6c215079f56d68930370dcd8c6002afMichel NormandThe directory sections typically occur in the access.conf file, but they
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normandmay appear in any configuration file. <Directory> directives cannot
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normandnest, and cannot appear in a <A HREF="#limit"><Limit></A> section.
f79d43bbe70a01454049b77d6f15f6369744959eStéphane Graber<h2><A name="directorymatch"><DirectoryMatch></A></h2>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Syntax:</strong> <DirectoryMatch <em>regex</em>> ... </DirectoryMatch> <br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Context:</strong> server config, virtual host<br>
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand<strong>Compatibility:</strong> Available in Apache 1.3 and later
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<p><DirectoryMatch> and </DirectoryMatch> are used to enclose a group of
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normanddirectives which will apply only to the named directory and sub-directories
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoof that directory, the same as <a
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanohref="#directory"><Directory></a>. However, it takes as an
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoargument a regular expression. For example:</p>
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand <DirectoryMatch "^/www/.*/[0-9]{3}">
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand<p>would match directories in /www/ that consisted of three numbers.</p>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<h2><A NAME="documentroot">DocumentRoot directive</A></h2>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt DocumentRoot} directive> -->
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Syntax:</strong> DocumentRoot <em>directory-filename</em><br>
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand<strong>Context:</strong> server config, virtual host<br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThis directive sets the directory from which httpd will serve files.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoUnless matched by a directive like Alias, the server appends the path
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanofrom the requested URL to the document root to make the path to the
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanodocument. Example:
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<blockquote><code>DocumentRoot /usr/web</code></blockquote>
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normandthen an access to <code>http://www.my.host.com/index.html</code> refers
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<P>There appears to be a bug in mod_dir which causes problems when the
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoDocumentRoot has a trailing slash (i.e. "DocumentRoot /usr/web/") so
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normandplease avoid that.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<h2><A name="errordocument">ErrorDocument directive</A></h2>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt ErrorDocument} directive> -->
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Syntax:</strong> ErrorDocument <em>error-code document</em><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Context</strong> server config, virtual host, directory, .htaccess<br>
b0a33c1eb65d2c87e886c740a0dadd8ad5f8d87ddlezcano<strong>Compatibility:</strong> The directory and .htaccess contexts
b0a33c1eb65d2c87e886c740a0dadd8ad5f8d87ddlezcanoare only available in Apache 1.1 and later.<p>
b0a33c1eb65d2c87e886c740a0dadd8ad5f8d87ddlezcanoIn the event of a problem or error, Apache can be configured to do
b0a33c1eb65d2c87e886c740a0dadd8ad5f8d87ddlezcanoone of four things,
b0a33c1eb65d2c87e886c740a0dadd8ad5f8d87ddlezcano<LI>output a simple hardcoded error message
b0a33c1eb65d2c87e886c740a0dadd8ad5f8d87ddlezcano<LI>output a customized message
b0a33c1eb65d2c87e886c740a0dadd8ad5f8d87ddlezcano<LI>redirect to a local URL to handle the problem/error
b0a33c1eb65d2c87e886c740a0dadd8ad5f8d87ddlezcano<LI>redirect to an external URL to handle the problem/error
b0a33c1eb65d2c87e886c740a0dadd8ad5f8d87ddlezcano<P>The first option is the default, while options 2-4 are configured
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanousing the <CODE>ErrorDocument</CODE> directive, which is followed by
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normandthe HTTP response code and a message or URL.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<P><em>Messages</em> in this context begin with a single quote
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano(<code>"</code>), which does not form part of the message itself.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoApache will sometimes offer additional information regarding the
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<P>URLs can begin with a slash (/) for local URLs, or be a full
f79d43bbe70a01454049b77d6f15f6369744959eStéphane GraberURL which the client can resolve. Examples:
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoErrorDocument 500 http://foo.example.com/cgi-bin/tester<br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoErrorDocument 403 "Sorry can't allow you access today
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<P>Note that when you specify an <CODE>ErrorDocument</CODE> that
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanopoints to a remote URL (ie. anything with a method such as "http" in
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanofront of it) Apache will send a redirect to the client to tell it
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanowhere to find the document, even if the document ends up being
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoon the same server.. This has several implications, the
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanomost important being that <STRONG>if you use an "ErrorDocument 401"
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanodirective then it must refer to a local document.</STRONG> This results
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanofrom the nature of the HTTP basic authentication scheme.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<P>See Also: <A HREF="/custom-error.html">documentation of customizable
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand<h2><A name="errorlog">ErrorLog directive</A></h2>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt ErrorLog} directive> -->
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Syntax:</strong> ErrorLog <em>filename</em><br>
c159cb963868d4646cf415abb064d8fd4b6ee848Daniel Lezcano<strong>Default:</strong> <code>ErrorLog logs/error_log</code><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Context:</strong> server config, virtual host<br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThe error log directive sets the name of the file to which the server will log
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoany errors it encounters. If the filename does not begin with a slash (/)
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanothen it is assumed to be relative to the <A HREF="#serverroot">ServerRoot</A>.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<blockquote><code>ErrorLog /dev/null</code></blockquote>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThis effectively turns off error logging.<p>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoSECURITY: See the <A HREF="/misc/security_tips.html">security tips</A>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanodocument for details on why your security could be compromised if
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanothe directory where logfiles are stored is writable by anyone other
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanothan the user that starts the server.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<h2><A name="files"><Files> directive</A></h2>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Syntax:</strong> <Files <em>filename</em>>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano... </Files><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Context:</strong> server config, virtual host, htaccess<br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Compatibility:</strong> only available in Apache
c159cb963868d4646cf415abb064d8fd4b6ee848Daniel Lezcano1.2 and above.<p>
c159cb963868d4646cf415abb064d8fd4b6ee848Daniel Lezcano<p>The <Files> directive provides for access control by
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanofilename. It is comparable to the <a
c159cb963868d4646cf415abb064d8fd4b6ee848Daniel Lezcanohref="#directory"><Directory></a> directive and
c159cb963868d4646cf415abb064d8fd4b6ee848Daniel Lezcano<a href="#location"><Location></a> directives. It
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoshould be matched with a </Files> directive. Directives that
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoapply to the filename given should be listed
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanowithin. <code><Files></code> sections are processed in the
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoorder they appear in the configuration file, after the
b6d441f289eb03a1a6fe0662a14c26ecc852be21dlezcano<Directory> sections and <code>.htaccess</code> files are
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoread, but before <Location> sections.</p>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<p>The <em>filename</em> argument should include a filename, or a
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanowild-card string, where `?' matches any single character, and `*' matches any
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanosequences of characters. Extended regular expressions can also be used,
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanowith the addition of
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano <Files ~ "\.(gif|jpe?g|png)$">
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanowould match most common Internet graphics formats. In Apache 1.3 and
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanolater, <a href="#filesmatch"><FilesMatch></a> is perferred,
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanohref="#directory"><code><Directory></code></a> and <a
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanohref="#location"><code><Location></code></a> sections,
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<code><Files></code> sections can be used inside .htaccess
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanofiles. This allows users to control access to their own files, at a
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanofile-by-file level. When used in an .htaccess file, if the
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<em>filename</em> does not begin with a <code>/</code> character,
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanothe directory being applied will be prefixed automatically.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<h2><A name="filesmatch"><FilesMatch></A></h2>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Syntax:</strong> <FilesMatch <em>regex</em>>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano... </Files><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Context:</strong> server config, virtual host, htaccess<br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Compatibility:</strong> only available in Apache
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano1.3 and above.<p>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<p>The <FilesMatch> directive provides for access control by
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanofilename, just as the <a href="#files"><Files></a> directive
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanodoes. However, it accepts a regular expression. For example:</p>
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normand <FilesMatch "\.(gif|jpe?g|png)$">
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<p>would match most common Internet graphics formats.</p>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt Group} directive> -->
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Syntax:</strong> Group <em>unix-group</em><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Default:</strong> <code>Group #-1</code><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Context:</strong> server config, virtual host<br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThe Group directive sets the group under which the server will answer requests.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoIn order to use this directive, the stand-alone server must be run initially
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<dt>A group name
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<dd>Refers to the given group by name.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<dt># followed by a group number.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<dd>Refers to a group by its number.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoIt is recommended that you set up a new group specifically for running the
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoserver. Some admins use user <code>nobody</code>, but this is not always
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanopossible or desirable.<p>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoNote: if you start the server as a non-root user, it will fail to change
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoto the specified group, and will instead continue to run as the group of the
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanooriginal user. <p>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoSpecial note: Use of this directive in <VirtualHost> requires a
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoproperly configured <A HREF="/suexec.html">suEXEC wrapper</A>.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoWhen used inside a <VirtualHost> in this manner, only the group
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanothat CGIs are run as is affected. Non-CGI requests are still processed
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoas the group specified in the main Group directive.<p>
aa8d013ec5b09cd1cd904173d6234ef126eb2126Peter SimonsSECURITY: See <A HREF="#user">User</A> for a discussion of the security
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<h2><A name="hostnamelookups">HostNameLookups directive</A></h2>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt HostNameLookups} directive> -->
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Syntax:</strong> HostNameLookups <em>on | off | double</em><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Default:</strong> <code>HostNameLookups off</code><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Context:</strong> server config, virtual host<br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Compatibility:</strong> <code>double</code> available only in Apache
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano1.3 and above.<br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Compatibility:</strong> Default was <code>on</code> prior to Apache
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThis directive enables DNS lookups so that host names can be logged (and
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThe value <code>double</code> refers to doing double-reverse DNS.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThat is, after a reverse lookup is performed, a forward lookup is then
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoperformed on that result. At least one of the ip addresses in the forward
a941cc0bf6c215079f56d68930370dcd8c6002afMichel Normandlookup must match the original address. (In "tcpwrappers" terminology
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoRegardless of the setting, when <a href="mod_access.html">mod_access</a>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanois used for controlling access by hostname, a double reverse lookup
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanowill be performed. This is necessary for security. Note that the
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoresult of this double-reverse isn't generally available unless
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoyou set <code>HostnameLookups double</code>. For example, if only
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<code>HostnameLookups on</code> and a request is made to an object that
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanois protected by hostname restrictions, regardless of whether the
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanodouble-reverse fails or not, CGIs will still be passed the single-reverse
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThe default for this directive was previously <code>on</code> in
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoversions of Apache prior to 1.3. It was changed to <code>off</code>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoin order to save the network traffic for those sites that don't truly
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoneed the reverse lookups done. It is also better for the end users
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanobecause they don't have to suffer the extra latency that a lookup
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoHeavily loaded sites should leave this directive <code>off</code>, since DNS
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanolookups can take considerable amounts of time. The utility <i>logresolve</i>,
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoprovided in the <i>/support</i> directory, can be used to look up host names
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<h2><A name="identitycheck">IdentityCheck directive</A></h2>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<!--%plaintext <?INDEX {\tt IdentityCheck} directive> -->
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Syntax:</strong> IdentityCheck <em>boolean</em><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Default:</strong> <code>IdentityCheck off</code><br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<strong>Context:</strong> server config, virtual host<br>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThis directive enables RFC1413-compliant logging of the remote user name
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanofor each connection, where the client machine runs identd or something similar.
99e4008cad9e959b683c6f48411fcf15a92be3b5Michel NormandThis information is logged in the access log. <em>Boolean</em> is either
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoThe information should not be trusted in any way except for rudimentary usage
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanotracking.<p>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoNote that this can cause serious latency problems accessing your server
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanosince every request requires one of these lookups to be performed. When
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanofirewalls are involved each lookup might possibly fail and add 30 seconds
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoof latency to each hit. So in general this is not very useful on public
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcanoservers accessible from the Internet.
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<H2><A NAME="ifmodule"><IfModule> directive</A></H2>
f1d8791c17f7e0f131de20d7bbc8836b992bd4dbdlezcano<b>Syntax:</b> <IfModule [!]<i>module-name</i>> <i>...</i>
href="mod_mime.html#sethandler">SetHandler</a></code> directive. For example, to enable status requests, but allow them only
from browsers at foo.com, you might use:
allow from .foo.com
below 1024 are reserved for system use, i.e. regular (non-root) users cannot
might work with some 1.x installations, but won't work with all of
speed high latency (i.e. 100ms or so, such as transcontinental
It may be worth setting up a dedicated address for this, e.g.
<!--#include virtual="footer.html" -->