configuring.html.en revision 81785f72c9d133aef57ad6b02f248345d90239aa
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
This file is generated from xml source: DO NOT EDIT
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-->
<title>Configuration Files - Apache HTTP Server</title>
<link href="/style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
<link href="/style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
<body id="manual-page"><div id="page-header">
<p class="menu"><a href="/mod/">Modules</a> | <a href="/mod/directives.html">Directives</a> | <a href="/faq/">FAQ</a> | <a href="/glossary.html">Glossary</a> | <a href="/sitemap.html">Sitemap</a></p>
<p class="apache">Apache HTTP Server Version 2.3</p>
<div id="path">
<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="./">Version 2.3</a></div><div id="page-content"><div id="preamble"><h1>Configuration Files</h1>
<div class="toplang">
<p><span>Available Languages: </span><a href="/de/configuring.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> |
</div>
<p>This document describes the files used to configure the Apache
HTTP server.</p>
</div>
<div id="quickview"><ul id="toc"><li><img alt="" src="/images/down.gif" /> <a href="#main">Main Configuration Files</a></li>
<li><img alt="" src="/images/down.gif" /> <a href="#syntax">Syntax of the Configuration Files</a></li>
</ul></div>
<div class="section">
<h2><a name="main" id="main">Main Configuration Files</a></h2>
<table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="/mod/mod_mime.html">mod_mime</a></code></li></ul></td><td><ul><li><code class="directive"><a href="/mod/core.html#ifdefine"><IfDefine></a></code></li><li><code class="directive"><a href="/mod/core.html#include">Include</a></code></li><li><code class="directive"><a href="/mod/mod_mime.html#typesconfig">TypesConfig</a></code></li></ul></td></tr></table>
configuration files. The main configuration file is usually called
compile-time, but may be overridden with the <code>-f</code>
command line flag. In addition, other configuration files may be
directive, and wildcards can be used to include many configuration
files. Any directive may be placed in any of these configuration
files. Changes to the main configuration files are only
recognized by Apache when it is started or restarted.</p>
<p>The server also reads a file containing mime document types;
the filename is set by the <code class="directive"><a href="/mod/mod_mime.html#typesconfig">TypesConfig</a></code> directive,
<div class="section">
<h2><a name="syntax" id="syntax">Syntax of the Configuration Files</a></h2>
<p>Apache configuration files contain one directive per line.
The back-slash "\" may be used as the last character on a line
to indicate that the directive continues onto the next line.
There must be no other characters or white space between the
back-slash and the end of the line.</p>
<p>Directives in the configuration files are case-insensitive,
but arguments to directives are often case sensitive. Lines
that begin with the hash character "#" are considered
comments, and are ignored. Comments may <strong>not</strong> be
included on a line after a configuration directive. Blank lines
and white space occurring before a directive are ignored, so
you may indent directives for clarity.</p>
<p>The maximum length of a line in the configuration file,
after joining any continued lines and removing leading and
trailing white space, is 8192 characters.</p>
<p>You can check your configuration files for syntax errors
without starting the server by using <code>apachectl
configtest</code> or the <code>-t</code> command line
option.</p>
<div class="section">
<h2><a name="modules" id="modules">Modules</a></h2>
<table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="/mod/mod_so.html">mod_so</a></code></li></ul></td><td><ul><li><code class="directive"><a href="/mod/core.html#ifmodule"><IfModule></a></code></li><li><code class="directive"><a href="/mod/mod_so.html#loadmodule">LoadModule</a></code></li></ul></td></tr></table>
<p>Apache is a modular server. This implies that only the most
basic functionality is included in the core server. Extended
features are available through <a href="mod/">modules</a> which can be loaded
included in the server at compile-time. If the server is
modules, then modules can be compiled separately and added at
any time using the <code class="directive"><a href="/mod/mod_so.html#loadmodule">LoadModule</a></code>
directive.
Otherwise, Apache must be recompiled to add or remove modules.
Configuration directives may be included conditional on a
presence of a particular module by enclosing them in an <code class="directive"><a href="/mod/core.html#ifmodule"><IfModule></a></code> block.</p>
<p>To see which modules are currently compiled into the server,
you can use the <code>-l</code> command line option.</p>
<div class="section">
<h2><a name="scope" id="scope">Scope of Directives</a></h2>
<table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td /><td><ul><li><code class="directive"><a href="/mod/core.html#directory"><Directory></a></code></li><li><code class="directive"><a href="/mod/core.html#directorymatch"><DirectoryMatch></a></code></li><li><code class="directive"><a href="/mod/core.html#files"><Files></a></code></li><li><code class="directive"><a href="/mod/core.html#filesmatch"><FilesMatch></a></code></li><li><code class="directive"><a href="/mod/core.html#location"><Location></a></code></li><li><code class="directive"><a href="/mod/core.html#locationmatch"><LocationMatch></a></code></li><li><code class="directive"><a href="/mod/core.html#virtualhost"><VirtualHost></a></code></li></ul></td></tr></table>
<p>Directives placed in the main configuration files apply to
the entire server. If you wish to change the configuration for
only a part of the server, you can scope your directives by
placing them in <code class="directive"><a href="/mod/core.html#directory"><Directory></a></code>, <code class="directive"><a href="/mod/core.html#directorymatch"><DirectoryMatch></a></code>, <code class="directive"><a href="/mod/core.html#files"><Files></a></code>, <code class="directive"><a href="/mod/core.html#filesmatch"><FilesMatch></a></code>, <code class="directive"><a href="/mod/core.html#location"><Location></a></code>, and <code class="directive"><a href="/mod/core.html#locationmatch"><LocationMatch></a></code>
sections. These sections limit the application of the
directives which they enclose to particular filesystem
locations or URLs. They can also be nested, allowing for very
fine grained configuration.</p>
<p>Apache has the capability to serve many different websites
simultaneously. This is called <a href="vhosts/">Virtual
Hosting</a>. Directives can also be scoped by placing them
sections, so that they will only apply to requests for a
particular website.</p>
<p>Although most directives can be placed in any of these
sections, some directives do not make sense in some contexts.
For example, directives controlling process creation can only
be placed in the main server context. To find which directives
can be placed in which sections, check the <a href="mod/directive-dict.html#Context">Context</a> of the
directive. For further information, we provide details on <a href="sections.html">How Directory, Location and Files sections
work</a>.</p>
<div class="section">
<h2><a name="htaccess" id="htaccess">.htaccess Files</a></h2>
<table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td /><td><ul><li><code class="directive"><a href="/mod/core.html#accessfilename">AccessFileName</a></code></li><li><code class="directive"><a href="/mod/core.html#allowoverride">AllowOverride</a></code></li></ul></td></tr></table>
<p>Apache allows for decentralized management of configuration
via special files placed inside the web tree. The special files
are usually called <code>.htaccess</code>, but any name can be
specified in the <code class="directive"><a href="/mod/core.html#accessfilename">AccessFileName</a></code>
directive. Directives placed in <code>.htaccess</code> files
apply to the directory where you place the file, and all
sub-directories. The <code>.htaccess</code> files follow the
same syntax as the main configuration files. Since
<code>.htaccess</code> files are read on every request, changes
made in these files take immediate effect.</p>
<p>To find which directives can be placed in
<code>.htaccess</code> files, check the <a href="mod/directive-dict.html#Context">Context</a> of the
directive. The server administrator further controls what
directives may be placed in <code>.htaccess</code> files by
configuring the <code class="directive"><a href="/mod/core.html#allowoverride">AllowOverride</a></code>
directive in the main configuration files.</p>
<p>For more information on <code>.htaccess</code> files, see
</div></div>
<div class="bottomlang">
<p><span>Available Languages: </span><a href="/de/configuring.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> |
</div><div id="footer">
<p class="apache">Copyright 2009 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
<p class="menu"><a href="/mod/">Modules</a> | <a href="/mod/directives.html">Directives</a> | <a href="/faq/">FAQ</a> | <a href="/glossary.html">Glossary</a> | <a href="/sitemap.html">Sitemap</a></p></div>
</body></html>