<title>Configuration Sections - 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" />
-<link href="./style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" />
+<link href="./style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="./style/css/prettify.css" />
+<script src="./style/scripts/prettify.js" type="text/javascript">
+</script>
+
<link href="./images/favicon.ico" rel="shortcut icon" /></head>
<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>
+<p class="menu"><a href="./mod/">Modules</a> | <a href="./mod/directives.html">Directives</a> | <a href="
http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="./glossary.html">Glossary</a> | <a href="./sitemap.html">Sitemap</a></p>
+<p class="apache">Apache HTTP Server Version 2.5</p>
<img alt="" src="./images/feather.gif" /></div>
<div class="up"><a href="./"><img title="<-" alt="<-" src="./images/left.gif" /></a></div>
<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 Sections</h1>
+<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.
5</a></div><div id="page-content"><div id="preamble"><h1>Configuration Sections</h1>
<div class="toplang">
<p><span>Available Languages: </span><a href="./en/sections.html" title="English"> en </a> |
<a href="./fr/sections.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
to change the scope of other configuration directives.</p>
</div>
<div id="quickview"><ul id="toc"><li><img alt="" src="./images/down.gif" /> <a href="#types">Types of Configuration Section Containers</a></li>
-<li><img alt="" src="./images/down.gif" /> <a href="#file-and-web">Filesystem and Webspace</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#file-and-web">Filesystem, Webspace, and Boolean Expressions</a></li>
<li><img alt="" src="./images/down.gif" /> <a href="#virtualhost">Virtual Hosts</a></li>
<li><img alt="" src="./images/down.gif" /> <a href="#proxy">Proxy</a></li>
<li><img alt="" src="./images/down.gif" /> <a href="#whatwhere">What Directives are Allowed?</a></li>
-<li><img alt="" src="./images/down.gif" /> <a href="#mergin">How the sections are merged</a></li>
-</ul></div>
+<li><img alt="" src="./images/down.gif" /> <a href="#merging">How the sections are merged</a></li>
+</ul><ul class="seealso"><li><a href="#comments_section">Comments</a></li></ul></div>
<div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
<div class="section">
<h2><a name="types" id="types">Types of Configuration Section Containers</a></h2>
to another site only if the server is started using
<code>httpd -DClosedForNow</code>:</p>
-<div class="example"><p><code>
-<IfDefine ClosedForNow><br />
-Redirect / http://otherserver.example.com/<br />
+<pre class="prettyprint lang-config">
+<IfDefine ClosedForNow>
+ Redirect / http://otherserver.example.com/
</IfDefine>
-</code></p></div>
+</pre>
+
<p>The <code class="directive"><a href="./mod/core.html#ifmodule"><IfModule></a></code>
directive is very similar, except it encloses directives that will
to work all the time, because it can suppress useful error messages
about missing modules.</p>
-<p>In the following example, the <code class="directive"><a href="./mod/mod_mime_magic.html#mimemagicfiles">MimeMagicFiles</a></code> directive will be
+<p>In the following example, the <code class="directive"><a href="./mod/mod_mime_magic.html#mimemagicfile">MimeMagicFile</a></code> directive will be
applied only if <code class="module"><a href="./mod/mod_mime_magic.html">mod_mime_magic</a></code> is available.</p>
-<div class="example"><p><code>
-<IfModule mod_mime_magic.c><br />
-MimeMagicFile conf/magic<br />
+<pre class="prettyprint lang-config">
+<IfModule mod_mime_magic.c>
+ MimeMagicFile conf/magic
</IfModule>
-</code></p></div>
+</pre>
+
<p>The <code class="directive"><a href="./mod/mod_version.html#ifversion"><IfVersion></a></code>
directive is very similar to <code class="directive"><a href="./mod/core.html#ifdefine"><IfDefine></a></code> and <code class="directive"><a href="./mod/core.html#ifmodule"><IfModule></a></code>, except it encloses directives that will
module is designed for the use in test suites and large networks which have to
deal with different httpd versions and different configurations.</p>
-<div class="example"><p><code>
- <IfVersion >= 2.1><br />
- <span class="indent">
- # this happens only in versions greater or<br />
- # equal 2.1.0.<br />
- </span>
- </IfVersion>
-</code></p></div>
+<pre class="prettyprint lang-config">
+<IfVersion >= 2.4>
+ # this happens only in versions greater or
+ # equal 2.4.0.
+</IfVersion>
+</pre>
+
<p><code class="directive"><a href="./mod/core.html#ifdefine"><IfDefine></a></code>,
<code class="directive"><a href="./mod/core.html#ifmodule"><IfModule></a></code>, and the
restrictions.</p>
</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
<div class="section">
-<h2><a name="file-and-web" id="file-and-web">Filesystem and Webspace</a></h2>
+<h2><a name="file-and-web" id="file-and-web">Filesystem, Webspace, and Boolean Expressions</a></h2>
<p>The most commonly used configuration section containers are the
ones that change the configuration of particular places in the
counterparts, apply directives to
parts of the filesystem. Directives enclosed in a <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> section apply to
the named filesystem directory and all subdirectories of that
-directory. The same effect can be obtained using <a href="howto/htaccess.html">.htaccess files</a>. For example, in the
+directory (as well as the files in those directories).
+The same effect can be obtained using <a href="howto/htaccess.html">.htaccess files</a>. For example, in the
following configuration, directory indexes will be enabled for the
<code>/var/web/dir1</code> directory and all subdirectories.</p>
-<div class="example"><p><code>
-<Directory /var/web/dir1><br />
-Options +Indexes<br />
+<pre class="prettyprint lang-config">
+<Directory /var/web/dir1>
+ Options +Indexes
</Directory>
-</code></p></div>
+</pre>
+
<p>Directives enclosed in a <code class="directive"><a href="./mod/core.html#files"><Files></a></code> section apply to any file with
the specified name, regardless of what directory it lies in.
deny access to any file named <code>private.html</code> regardless
of where it is found.</p>
-<div class="example"><p><code>
-<Files private.html><br />
-Order allow,deny<br />
-Deny from all<br />
+<pre class="prettyprint lang-config">
+<Files private.html>
+ Require all denied
</Files>
-</code></p></div>
+</pre>
+
<p>To address files found in a particular part of the filesystem, the
<code class="directive"><a href="./mod/core.html#files"><Files></a></code> and
of <code>private.html</code> found under the <code>/var/web/dir1/</code>
directory.</p>
-<div class="example"><p><code>
-<Directory /var/web/dir1><br />
-<Files private.html><br />
-Order allow,deny<br />
-Deny from all<br />
-</Files><br />
+<pre class="prettyprint lang-config">
+<Directory /var/web/dir1>
+ <Files private.html>
+ Require all denied
+ </Files>
</Directory>
-</code></p></div>
+</pre>
+
<h3><a name="webspace" id="webspace">Webspace Containers</a></h3>
<code>http://yoursite.example.com/private/dir/file.html</code> as well
as any other requests starting with the <code>/private</code> string.</p>
-<div class="example"><p><code>
-<Location /private><br />
-Order Allow,Deny<br />
-Deny from all<br />
-</Location>
-</code></p></div>
+<pre class="prettyprint lang-config">
+<LocationMatch ^/private>
+ Require all denied
+</LocationMatch>
+</pre>
+
<p>The <code class="directive"><a href="./mod/core.html#location"><Location></a></code>
directive need not have anything to do with the filesystem.
No file called <code>server-status</code> needs to exist in the
filesystem.</p>
-<div class="example"><p><code>
-<Location /server-status><br />
-SetHandler server-status<br />
+<pre class="prettyprint lang-config">
+<Location /server-status>
+ SetHandler server-status
</Location>
-</code></p></div>
+</pre>
+
<h3><a name="overlapping-webspace" id="overlapping-webspace">Overlapping Webspace</a></h3>
-In order to have two overlapping URLs one has to consider the order in which
+<p>In order to have two overlapping URLs one has to consider the order in which
certain sections or directives are evaluated. For
-<code class="directive"><a href="./mod/core.html#location"><Location></a></code> this would be:
-<div class="example"><p><code>
-<Location /foo><br />
-</Location><br />
-<Location /foo/bar><br />
+<code class="directive"><a href="./mod/core.html#location"><Location></a></code> this would be:</p>
+<pre class="prettyprint lang-config">
+<Location /foo>
+</Location>
+<Location /foo/bar>
</Location>
-</code></p></div>
-<code class="directive"><a href="./mod/core.html#alias"><Alias></a></code>es on the other hand,
-are mapped vice-versa:
-<div class="example"><p><code>
-Alias /foo/bar /srv/www/uncommon/bar<br />
-Alias /foo /srv/www/common/foo<br />
-</code></p></div>
-The same is true for the <code class="directive"><a href="./mod/mod_proxy.html#proxypass">ProxyPass</a></code>
-directives:
-<div class="example"><p><code>
+</pre>
+
+<p><code class="directive"><a href="./mod/mod_alias.html#alias"><Alias></a></code>es on the other hand,
+are mapped vice-versa:</p>
+<pre class="prettyprint lang-config">
+Alias /foo/bar /srv/www/uncommon/bar
+Alias /foo /srv/www/common/foo
+</pre>
+
+<p>The same is true for the <code class="directive"><a href="./mod/mod_proxy.html#proxypass">ProxyPass</a></code>
+directives:</p>
+<pre class="prettyprint lang-config">
ProxyPass /special-area http://special.example.com smax=5 max=10
ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid nofailover=On
-</code></p></div>
-
+</pre>
+
+
<h3><a name="wildcards" id="wildcards">Wildcards and Regular Expressions</a></h3>
<p>A non-regex wildcard section that changes the configuration of
all user directories could look as follows:</p>
-<div class="example"><p><code>
-<Directory /home/*/public_html><br />
-Options Indexes<br />
+<pre class="prettyprint lang-config">
+<Directory /home/*/public_html>
+ Options Indexes
</Directory>
-</code></p></div>
+</pre>
+
<p>Using regex sections, we can deny access to many types of image files
at once:</p>
-<div class="example"><p><code>
-<FilesMatch \.(?i:gif|jpe?g|png)$><br />
-Order allow,deny<br />
-Deny from all<br />
+<pre class="prettyprint lang-config">
+<FilesMatch \.(?i:gif|jpe?g|png)$>
+ Require all denied
</FilesMatch>
-</code></p></div>
+</pre>
+
+
+
+
+<h3><a name="expressions" id="expressions">Boolean expressions</a></h3>
+<p>The <code class="directive"><a href="./mod/core.html#if"><If></a></code>
+directive change the configuration depending on a condition which can be
+expressed by a boolean expression. For example, the following configuration
+denies access if the HTTP Referer header does not start with
+"http://www.example.com/".</p>
+<pre class="prettyprint lang-config">
+<If "!(%{HTTP_REFERER} -strmatch 'http://www.example.com/*')">
+ Require all denied
+</If>
+</pre>
+
location, allowing your restrictions to be circumvented.
For example, consider the following configuration:</p>
-<div class="example"><p><code>
-<Location /dir/><br />
-Order allow,deny<br />
-Deny from all<br />
+<pre class="prettyprint lang-config">
+<Location /dir/>
+ Require all denied
</Location>
-</code></p></div>
+</pre>
+
<p>This works fine if the request is for
<code>http://yoursite.example.com/dir/</code>. But what if you are on
to all requests regardless of the specific URL.</p>
+<h3><a name="nesting" id="nesting">Nesting of sections</a></h3>
+
+<p>Some section types can be nested inside other section types. One the one
+hand, <code class="directive"><a href="./mod/core.html#files"><Files></a></code> can be used
+inside <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code>. On
+the other hand, <code class="directive"><a href="./mod/core.html#if"><If></a></code> can
+be used inside <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code>,
+<code class="directive"><a href="./mod/core.html#location"><Location></a></code>, and <code class="directive"><a href="./mod/core.html#files"><Files></a></code> sections. The regex
+counterparts of the named section behave identically.</p>
+
+<p>Nested sections are merged after non-nested sections of the same type.</p>
+
+
+
</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
<div class="section">
<h2><a name="virtualhost" id="virtualhost">Virtual Hosts</a></h2>
to sites accessed through <code class="module"><a href="./mod/mod_proxy.html">mod_proxy</a></code>'s proxy server
that match the specified URL. For example, the following configuration
will prevent the proxy server from being used to access the
-<code>cnn.com</code> website.</p>
+<code>www.example.com</code> website.</p>
-<div class="example"><p><code>
-<Proxy http://cnn.com/*><br />
-Order allow,deny<br />
-Deny from all<br />
+<pre class="prettyprint lang-config">
+<Proxy http://www.example.com/*>
+ Require all granted
</Proxy>
-</code></p></div>
+</pre>
+
</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
<div class="section">
<h2><a name="whatwhere" id="whatwhere">What Directives are Allowed?</a></h2>
<p>To find out what directives are allowed in what types of
configuration sections, check the <a href="mod/directive-dict.html#Context">Context</a> of the directive.
-Everything that is allowed in
+Everything that is allowed in
<code class="directive"><a href="./mod/core.html#directory"><Directory></a></code>
sections is also syntactically allowed in
<code class="directive"><a href="./mod/core.html#directorymatch"><DirectoryMatch></a></code>,
</ul>
</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
<div class="section">
-<h2><a name="mergin" id="mergin">How the sections are merged</a></h2>
+<h2><a name="merging" id="merging">How the sections are merged</a></h2>
<p>The configuration sections are applied in a very particular order.
Since this can have important effects on how configuration directives
<li><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> done simultaneously</li>
+
+ <li><code class="directive"><a href="./mod/core.html#if"><If></a></code>
+ </li>
+
</ol>
<p>Apart from <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code>, each group is processed in
container takes the place of the <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> container in the processing
order.</p>
- <p>Later sections override earlier ones.</p>
+ <p>Later sections override earlier ones, however each module is responsible
+ for interpreting what form this override takes. A later configuration section
+ with directives from a given module might cause a conceptual "merge" of some
+ directives, all directives, or a complete replacement of the modules
+ configuration with the module defaults and directives explicitly listed in
+ the later context.</p>
<div class="note"><h3>Technical Note</h3>
There is actually a
this example will be applied in the order A > B > C > D >
E.</p>
-<div class="example"><p><code>
-<Location /><br />
-E<br />
-</Location><br />
-<br />
-<Files f.html><br />
-D<br />
-</Files><br />
-<br />
-<VirtualHost *><br />
-<Directory /a/b><br />
-B<br />
-</Directory><br />
-</VirtualHost><br />
-<br />
-<DirectoryMatch "^.*b$"><br />
-C<br />
-</DirectoryMatch><br />
-<br />
-<Directory /a/b><br />
-A<br />
-</Directory><br />
-<br />
-</code></p></div>
+<pre class="prettyprint lang-config">
+<Location />
+ E
+</Location>
+
+<Files f.html>
+ D
+</Files>
+
+<VirtualHost *>
+<Directory /a/b>
+ B
+</Directory>
+</VirtualHost>
+
+<DirectoryMatch "^.*b$">
+ C
+</DirectoryMatch>
+
+<Directory /a/b>
+ A
+</Directory>
+
+</pre>
+
<p>For a more concrete example, consider the following. Regardless of
any access restrictions placed in <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> sections, the <code class="directive"><a href="./mod/core.html#location"><Location></a></code> section will be
evaluated last and will allow unrestricted access to the server. In
other words, order of merging is important, so be careful!</p>
-<div class="example"><p><code>
-<Location /><br />
-Order deny,allow<br />
-Allow from all<br />
-</Location><br />
-<br />
-# Woops! This <Directory> section will have no effect<br />
-<Directory /><br />
-Order allow,deny<br />
-Allow from all<br />
-Deny from badguy.example.com<br />
+<pre class="prettyprint lang-config">
+<Location />
+ Require all granted
+</Location>
+
+# Woops! This <Directory> section will have no effect
+<Directory />
+ <RequireAll>
+ Require all granted
+ Require not host badguy.example.com
+ </RequireAll>
</Directory>
-</code></p></div>
+</pre>
+
<a href="./ja/sections.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
<a href="./ko/sections.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> |
<a href="./tr/sections.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p>
-</div><div id="footer">
-<p class="apache">Copyright 2010 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>
+</div><div class="top"><a href="#page-header"><img src="./images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our <a href="http://httpd.apache.org/lists.html">mailing lists</a>.</div>
+<script type="text/javascript"><!--//--><![CDATA[//><!--
+var comments_shortname = 'httpd';
+var comments_identifier = 'http://httpd.apache.org/docs/trunk/sections.html';
+(function(w, d) {
+ if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
+ d.write('<div id="comments_thread"><\/div>');
+ var s = d.createElement('script');
+ s.type = 'text/javascript';
+ s.async = true;
+ s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
+ (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
+ }
+ else {
+ d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
+ }
+})(window, document);
+//--><!]]></script></div><div id="footer">
+<p class="apache">Copyright 2012 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="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="./glossary.html">Glossary</a> | <a href="./sitemap.html">Sitemap</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
+if (typeof(prettyPrint) !== 'undefined') {
+ prettyPrint();
+}
+//--><!]]></script>
</body></html>
\ No newline at end of file
projects / apache / blobdiff