📄 sections.html.en
字号:
<?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"><html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --><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="./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.2</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.2</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鏰is"> fr </a> |<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黵k鏴"> tr </a></p></div> <p>Directives in the <a href="configuring.html">configuration files</a> may apply to theentire server, or they may be restricted to apply only to particulardirectories, files, hosts, or URLs. This document describes how touse configuration section containers or <code>.htaccess</code> filesto 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="#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><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><table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="./mod/core.html">core</a></code></li><li><code class="module"><a href="./mod/mod_version.html">mod_version</a></code></li><li><code class="module"><a href="./mod/mod_proxy.html">mod_proxy</a></code></li></ul></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#ifdefine"><IfDefine></a></code></li><li><code class="directive"><a href="./mod/core.html#ifmodule"><IfModule></a></code></li><li><code class="directive"><a href="./mod/mod_version.html#ifversion"><IfVersion></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/mod_proxy.html#proxy"><Proxy></a></code></li><li><code class="directive"><a href="./mod/mod_proxy.html#proxymatch"><ProxyMatch></a></code></li><li><code class="directive"><a href="./mod/core.html#virtualhost"><VirtualHost></a></code></li></ul></td></tr></table><p>There are two basic types of containers. Most containers areevaluated for each request. The enclosed directives are applied onlyfor those requests that match the containers. The <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<code class="directive"><a href="./mod/mod_version.html#ifversion"><IfVersion></a></code>containers, on the other hand, are evaluated only at server startupand restart. If their conditions are true at startup, then theenclosed directives will apply to all requests. If the conditions arenot true, the enclosed directives will be ignored.</p><p>The <code class="directive"><a href="./mod/core.html#ifdefine"><IfDefine></a></code> directiveencloses directives that will only be applied if an appropriateparameter is defined on the <code class="program"><a href="./programs/httpd.html">httpd</a></code> command line. For example,with the following configuration, all requests will be redirectedto 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 /></IfDefine></code></p></div><p>The <code class="directive"><a href="./mod/core.html#ifmodule"><IfModule></a></code>directive is very similar, except it encloses directives that willonly be applied if a particular module is available in the server.The module must either be statically compiled in the server, or itmust be dynamically compiled and its <code class="directive"><a href="./mod/mod_so.html#loadmodule">LoadModule</a></code> line must be earlier in theconfiguration file. This directive should only be used if you needyour configuration file to work whether or not certain modules areinstalled. It should not be used to enclose directives that you wantto work all the time, because it can suppress useful error messagesabout 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 beapplied 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 /></IfModule></code></p></div><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 willonly be applied if a particular version of the server is executing. Thismodule is designed for the use in test suites and large networks which have todeal 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><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<code class="directive"><a href="./mod/mod_version.html#ifversion"><IfVersion></a></code>can apply negative conditions by preceding their test with "!".Also, these sections can be nested to achieve more complexrestrictions.</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><p>The most commonly used configuration section containers are theones that change the configuration of particular places in thefilesystem or webspace. First, it is important to understand thedifference between the two. The filesystem is the view of your disksas seen by your operating system. For example, in a default install,Apache resides at <code>/usr/local/apache2</code> in the Unixfilesystem or <code>"c:/Program Files/Apache Group/Apache2"</code> inthe Windows filesystem. (Note that forward slashes should always beused as the path separator in Apache, even for Windows.) In contrast,the webspace is the view of your site as delivered by the web serverand seen by the client. So the path <code>/dir/</code> in thewebspace corresponds to the path<code>/usr/local/apache2/htdocs/dir/</code> in the filesystem of adefault Apache install on Unix. The webspace need not map directly tothe filesystem, since webpages may be generated dynamicallyfrom databases or other locations.</p><h3><a name="filesystem" id="filesystem">Filesystem Containers</a></h3><p>The <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code>and <code class="directive"><a href="./mod/core.html#files"><Files></a></code>directives, along with their <a class="glossarylink" href="./glossary.html#regex" title="see glossary">regex</a>counterparts, apply directives toparts of the filesystem. Directives enclosed in a <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> section apply tothe named filesystem directory and all subdirectories of thatdirectory. The same effect can be obtained using <a href="howto/htaccess.html">.htaccess files</a>. For example, in thefollowing 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 /></Directory></code></p></div><p>Directives enclosed in a <code class="directive"><a href="./mod/core.html#files"><Files></a></code> section apply to any file withthe specified name, regardless of what directory it lies in.So for example, the following configuration directives will,when placed in the main section of the configuration file,deny access to any file named <code>private.html</code> regardlessof where it is found.</p><div class="example"><p><code><Files private.html><br />Order allow,deny<br />Deny from all<br /></Files></code></p></div><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<code class="directive"><a href="./mod/core.html#directory"><Directory></a></code> sectionscan be combined. For example, the following configuration will denyaccess to <code>/var/web/dir1/private.html</code>,<code>/var/web/dir1/subdir2/private.html</code>,<code>/var/web/dir1/subdir3/private.html</code>, and any other instanceof <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 /></Directory></code></p></div><h3><a name="webspace" id="webspace">Webspace Containers</a></h3><p>The <code class="directive"><a href="./mod/core.html#location"><Location></a></code>directive and its <a class="glossarylink" href="./glossary.html#regex" title="see glossary">regex</a> counterpart, on theother hand, change theconfiguration for content in the webspace. For example, the followingconfiguration prevents access to any URL-path that begins in /private.In particular, it will apply to requests for<code>http://yoursite.example.com/private</code>,<code>http://yoursite.example.com/private123</code>, and<code>http://yoursite.example.com/private/dir/file.html</code> as wellas 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><p>The <code class="directive"><a href="./mod/core.html#location"><Location></a></code>directive need not have anything to do with the filesystem.For example, the following example shows how to map a particularURL to an internal Apache handler provided by <code class="module"><a href="./mod/mod_status.html">mod_status</a></code>.No file called <code>server-status</code> needs to exist in thefilesystem.</p><div class="example"><p><code><Location /server-status><br />SetHandler server-status<br /></Location></code></p></div><h3><a name="wildcards" id="wildcards">Wildcards and Regular Expressions</a></h3><p>The <code class="directive"><a href="./mod/core.html#directory"><Directory></a></code>,<code class="directive"><a href="./mod/core.html#files"><Files></a></code>, and<code class="directive"><a href="./mod/core.html#location"><Location></a></code>directives can each use shell-style wildcard characters as in<code>fnmatch</code> from the C standard library. The character "*"matches any sequence of characters, "?" matches any single character,and "[<em>seq</em>]" matches any character in <em>seq</em>. The "/"character will not be matched by any wildcard; it must be specifiedexplicitly.</p><p>If even more flexible matching is required, eachcontainer has a regular expression (regex) counterpart <code class="directive"><a href="./mod/core.html#directorymatch"><DirectoryMatch></a></code>, <code class="directive"><a href="./mod/core.html#filesmatch"><FilesMatch></a></code>, and <code class="directive"><a href="./mod/core.html#locationmatch"><LocationMatch></a></code> that allowperl-compatible<a class="glossarylink" href="./glossary.html#regex" title="see glossary">regular expressions</a>to be used in choosing the matches. But see the section below onconfiguration merging to find out how using regex sections will changehow directives are applied.</p><p>A non-regex wildcard section that changes the configuration ofall user directories could look as follows:</p><div class="example"><p><code><Directory /home/*/public_html><br />Options Indexes<br />⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -