mirror of
https://github.com/apache/httpd.git
synced 2026-01-06 09:01:14 +03:00
core.xml: revert turns to <pre>formatted examples and use
<indent> elements update transformations of core.html.en and quickreference.html.en (due to the mod_rewrite.xml fix) git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@97146 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
André Malo
@@ -118,12 +118,15 @@ available</td></tr><tr><th><a href="module-dict.html#Status">Status:
|
||||
request, so you can use the following configuration to enable
|
||||
such a script:</p>
|
||||
|
||||
<div class="example"><pre>
|
||||
<Files "mypaths.shtml">
|
||||
Options +Includes
|
||||
SetOutputFilter INCLUDES
|
||||
AcceptPathInfo on
|
||||
</Files></pre></div>
|
||||
<div class="example"><p><code>
|
||||
<Files "mypaths.shtml"><br />
|
||||
<span class="indent">
|
||||
Options +Includes<br />
|
||||
SetOutputFilter INCLUDES<br />
|
||||
AcceptPathInfo on<br />
|
||||
</span>
|
||||
</Files>
|
||||
</code></p></div>
|
||||
|
||||
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="directive-section"><h2><a name="AccessFileName" id="AccessFileName">AccessFileName</a> <a name="accessfilename" id="accessfilename">Directive</a></h2><table class="directive"><tr><th><a href="directive-dict.html#Description">Description:
|
||||
</a></th><td>Name of the distributed configuration file</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:
|
||||
@@ -148,10 +151,13 @@ available</td></tr><tr><th><a href="module-dict.html#Status">Status:
|
||||
<code>/usr/local/.acl</code> and <code>/usr/local/web/.acl</code>
|
||||
for directives, unless they have been disabled with</p>
|
||||
|
||||
<div class="example"><pre>
|
||||
<Directory />
|
||||
AllowOverride None
|
||||
</Directory></pre></div>
|
||||
<div class="example"><p><code>
|
||||
<Directory /><br />
|
||||
<span class="indent">
|
||||
AllowOverride None<br />
|
||||
</span>
|
||||
</Directory>
|
||||
</code></p></div>
|
||||
<h3>See also</h3><ul><li><code class="directive"><a href="#allowoverride">AllowOverride</a></code></li><li><a href="../configuring.html">Configuration Files</a></li><li><a href="../howto/htaccess.html">.htaccess Files</a></li></ul></div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="directive-section"><h2><a name="AddDefaultCharset" id="AddDefaultCharset">AddDefaultCharset</a> <a name="adddefaultcharset" id="adddefaultcharset">Directive</a></h2><table class="directive"><tr><th><a href="directive-dict.html#Description">Description:
|
||||
</a></th><td>Default character set to be added for a
|
||||
response without an explicit character set</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:
|
||||
@@ -388,10 +394,13 @@ named file-system directory and sub-directories</td></tr><tr><th><a href="direct
|
||||
<code>/home/user/public_html</code>, but <code><Directory
|
||||
/home/*/public_html></code> will match. Example:</p>
|
||||
|
||||
<div class="example"><pre>
|
||||
<Directory /usr/local/httpd/htdocs>
|
||||
Options Indexes FollowSymLinks
|
||||
</Directory></pre></div>
|
||||
<div class="example"><p><code>
|
||||
<Directory /usr/local/httpd/htdocs><br />
|
||||
<span class="indent">
|
||||
Options Indexes FollowSymLinks<br />
|
||||
</span>
|
||||
</Directory>
|
||||
</code></p></div>
|
||||
|
||||
<div class="note">
|
||||
<p>Be careful with the <var>directory-path</var> arguments:
|
||||
@@ -419,14 +428,19 @@ named file-system directory and sub-directories</td></tr><tr><th><a href="direct
|
||||
first, interspersed with the directives from the <a href="#accessfilename">.htaccess</a> files. For example,
|
||||
with</p>
|
||||
|
||||
<div class="example"><pre>
|
||||
<Directory />
|
||||
AllowOverride None
|
||||
</Directory>
|
||||
|
||||
<Directory /home/>
|
||||
AllowOverride FileInfo
|
||||
</Directory></pre></div>
|
||||
<div class="example"><p><code>
|
||||
<Directory /><br />
|
||||
<span class="indent">
|
||||
AllowOverride None<br />
|
||||
</span>
|
||||
</Directory><br />
|
||||
<br />
|
||||
<Directory /home/><br />
|
||||
<span class="indent">
|
||||
AllowOverride FileInfo<br />
|
||||
</span>
|
||||
</Directory>
|
||||
</code></p></div>
|
||||
|
||||
<p>for access to the document <code>/home/web/dir/doc.html</code>
|
||||
the steps are:</p>
|
||||
@@ -447,10 +461,13 @@ named file-system directory and sub-directories</td></tr><tr><th><a href="direct
|
||||
expressions are tested in the order they appeared in the
|
||||
configuration file. For example, with</p>
|
||||
|
||||
<div class="example"><pre>
|
||||
<Directory ~ abc$>
|
||||
# ... directives here ...
|
||||
</Directory></pre></div>
|
||||
<div class="example"><p><code>
|
||||
<Directory ~ abc$><br />
|
||||
<span class="indent">
|
||||
# ... directives here ...<br />
|
||||
</span>
|
||||
</Directory>
|
||||
</code></p></div>
|
||||
|
||||
<p>The regular expression section won't be considered until after
|
||||
all normal <Directory>s and <code>.htaccess</code> files
|
||||
@@ -463,11 +480,14 @@ named file-system directory and sub-directories</td></tr><tr><th><a href="direct
|
||||
recommended that you change this with a block such
|
||||
as</strong></p>
|
||||
|
||||
<div class="example"><pre>
|
||||
<Directory />
|
||||
Order Deny,Allow
|
||||
Deny from All
|
||||
</Directory></pre></div>
|
||||
<div class="example"><p><code>
|
||||
<Directory /><br />
|
||||
<span class="indent">
|
||||
Order Deny,Allow<br />
|
||||
Deny from All<br />
|
||||
</span>
|
||||
</Directory>
|
||||
</code></p></div>
|
||||
|
||||
<p><strong>and then override this for directories you
|
||||
<em>want</em> accessible. See the <a href="../misc/security_tips.html">Security Tips</a> page for more
|
||||
@@ -888,14 +908,17 @@ if a test is true at startup</td></tr><tr><th><a href="directive-dict.html#Synta
|
||||
nest-able, which can be used to implement simple
|
||||
multiple-parameter tests. Example:</p>
|
||||
|
||||
<div class="example"><pre>
|
||||
$ httpd -DReverseProxy ...
|
||||
|
||||
# httpd.conf
|
||||
<IfDefine ReverseProxy>
|
||||
LoadModule rewrite_module modules/mod_rewrite.so
|
||||
LoadModule proxy_module modules/libproxy.so
|
||||
</IfDefine></pre></div>
|
||||
<div class="example"><p><code>
|
||||
httpd -DReverseProxy ...<br />
|
||||
<br />
|
||||
# httpd.conf<br />
|
||||
<IfDefine ReverseProxy><br />
|
||||
<span class="indent">
|
||||
LoadModule rewrite_module modules/mod_rewrite.so<br />
|
||||
LoadModule proxy_module modules/libproxy.so<br />
|
||||
</span>
|
||||
</IfDefine>
|
||||
</code></p></div>
|
||||
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="directive-section"><h2><a name="IfModule" id="IfModule"><IfModule></a> <a name="ifmodule" id="ifmodule">Directive</a></h2><table class="directive"><tr><th><a href="directive-dict.html#Description">Description:
|
||||
</a></th><td>Encloses directives that are processed conditional on the
|
||||
presence or absence of a specific module</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:
|
||||
@@ -1049,7 +1072,7 @@ methods</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:
|
||||
<strong>all</strong> access methods, and this is the usual
|
||||
desired behavior. <strong>In the general case, access control
|
||||
directives should not be placed within a
|
||||
<code class="directive"><limit></code> section.</strong></p>
|
||||
<code class="directive"><Limit></code> section.</strong></p>
|
||||
|
||||
<p>The purpose of the <code class="directive"><Limit></code>
|
||||
directive is to restrict the effect of the access controls to the
|
||||
@@ -1059,10 +1082,13 @@ methods</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:
|
||||
example applies the access control only to the methods POST, PUT,
|
||||
and DELETE, leaving all other methods unprotected:</p>
|
||||
|
||||
<div class="example"><pre>
|
||||
<Limit POST PUT DELETE>
|
||||
Require valid-user
|
||||
</Limit></pre></div>
|
||||
<div class="example"><p><code>
|
||||
<Limit POST PUT DELETE><br />
|
||||
<span class="indent">
|
||||
Require valid-user<br />
|
||||
</span>
|
||||
</Limit>
|
||||
</code></p></div>
|
||||
|
||||
<p>The method names listed can be one or more of: <code>GET</code>,
|
||||
<code>POST</code>, <code>PUT</code>, <code>DELETE</code>,
|
||||
@@ -1091,10 +1117,13 @@ except the named ones</td></tr><tr><th><a href="directive-dict.html#Syntax">Synt
|
||||
|
||||
<p>For example:</p>
|
||||
|
||||
<div class="example"><pre>
|
||||
<LimitExcept POST GET>
|
||||
Require valid-user
|
||||
<LimitExcept></pre></div>
|
||||
<div class="example"><p><code>
|
||||
<LimitExcept POST GET><br />
|
||||
<span class="indent">
|
||||
Require valid-user<br />
|
||||
</span>
|
||||
<LimitExcept>
|
||||
</code></p></div>
|
||||
|
||||
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="directive-section"><h2><a name="LimitRequestBody" id="LimitRequestBody">LimitRequestBody</a> <a name="limitrequestbody" id="limitrequestbody">Directive</a></h2><table class="directive"><tr><th><a href="directive-dict.html#Description">Description:
|
||||
</a></th><td>Restricts the total size of the HTTP request body sent
|
||||
@@ -1315,13 +1344,16 @@ URLs</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:
|
||||
directive. For example, to enable status requests, but allow them
|
||||
only from browsers at foo.com, you might use:</p>
|
||||
|
||||
<div class="example"><pre>
|
||||
<Location /status>
|
||||
SetHandler server-status
|
||||
Order Deny,Allow
|
||||
Deny from all
|
||||
Allow from .foo.com
|
||||
</Location></pre></div>
|
||||
<div class="example"><p><code>
|
||||
<Location /status><br />
|
||||
<span class="indent">
|
||||
SetHandler server-status<br />
|
||||
Order Deny,Allow<br />
|
||||
Deny from all<br />
|
||||
Allow from .foo.com<br />
|
||||
</span>
|
||||
</Location>
|
||||
</code></p></div>
|
||||
|
||||
<div class="note"><h3>Note about / (slash)</h3>
|
||||
<p>The slash character has special meaning depending on where in a
|
||||
@@ -1644,27 +1676,37 @@ directory</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:
|
||||
|
||||
<p>For example, without any + and - symbols:</p>
|
||||
|
||||
<div class="example"><pre>
|
||||
<Directory /web/docs>
|
||||
Options Indexes FollowSymLinks
|
||||
</Directory>
|
||||
|
||||
<Directory /web/docs/spec>
|
||||
Options Includes
|
||||
</Directory></pre></div>
|
||||
<div class="example"><p><code>
|
||||
<Directory /web/docs><br />
|
||||
<span class="indent">
|
||||
Options Indexes FollowSymLinks<br />
|
||||
</span>
|
||||
</Directory><br />
|
||||
<br />
|
||||
<Directory /web/docs/spec><br />
|
||||
<span class="indent">
|
||||
Options Includes<br />
|
||||
</span>
|
||||
</Directory>
|
||||
</code></p></div>
|
||||
|
||||
<p>then only <code>Includes</code> will be set for the
|
||||
/web/docs/spec directory. However if the second
|
||||
<code class="directive">Options</code> directive uses the + and - symbols:</p>
|
||||
|
||||
<div class="example"><pre>
|
||||
<Directory /web/docs>
|
||||
Options Indexes FollowSymLinks
|
||||
</Directory>
|
||||
|
||||
<Directory /web/docs/spec>
|
||||
Options +Includes -Indexes
|
||||
</Directory></pre></div>
|
||||
<div class="example"><p><code>
|
||||
<Directory /web/docs><br />
|
||||
<span class="indent">
|
||||
Options Indexes FollowSymLinks<br />
|
||||
</span>
|
||||
</Directory><br />
|
||||
<br />
|
||||
<Directory /web/docs/spec><br />
|
||||
<span class="indent">
|
||||
Options +Includes -Indexes<br />
|
||||
</span>
|
||||
</Directory>
|
||||
</code></p></div>
|
||||
|
||||
<p>then the options <code>FollowSymLinks</code> and
|
||||
<code>Includes</code> are set for the /web/docs/spec directory.</p>
|
||||
@@ -2067,7 +2109,9 @@ handler</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:
|
||||
|
||||
<div class="example"><p><code>
|
||||
<Location /status><br />
|
||||
SetHandler server-status<br />
|
||||
<span class="indent">
|
||||
SetHandler server-status<br />
|
||||
</span>
|
||||
</Location>
|
||||
</code></p></div>
|
||||
<h3>See also</h3><ul><li><code class="directive"><a href="../mod/mod_mime.html#addhandler">AddHandler</a></code></li></ul></div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="directive-section"><h2><a name="SetInputFilter" id="SetInputFilter">SetInputFilter</a> <a name="setinputfilter" id="setinputfilter">Directive</a></h2><table class="directive"><tr><th><a href="directive-dict.html#Description">Description:
|
||||
@@ -2107,10 +2151,13 @@ server</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:
|
||||
in the <code>/www/data/</code> directory for server-side
|
||||
includes.</p>
|
||||
|
||||
<div class="example"><pre>
|
||||
<Directory /www/data/>
|
||||
SetOutputFilter INCLUDES
|
||||
</Directory></pre></div>
|
||||
<div class="example"><p><code>
|
||||
<Directory /www/data/><br />
|
||||
<span class="indent">
|
||||
SetOutputFilter INCLUDES<br />
|
||||
</span>
|
||||
</Directory>
|
||||
</code></p></div>
|
||||
|
||||
<p>If more than one filter is specified, they must be separated
|
||||
by semicolons in the order in which they should process the
|
||||
@@ -2189,12 +2236,13 @@ port</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:
|
||||
reverse DNS lookup on the server IP address that the client
|
||||
connected to in order to work out self-referential URLs.</p>
|
||||
|
||||
<p><strong>Warning:</strong> if CGIs make assumptions about the
|
||||
values of <code>SERVER_NAME</code> they may be broken by this
|
||||
option. The client is essentially free to give whatever value
|
||||
they want as a hostname. But if the CGI is only using
|
||||
<code>SERVER_NAME</code> to construct self-referential URLs
|
||||
<div class="warning"><h3>Warning:</h3>
|
||||
<p>If CGIs make assumptions about the values of <code>SERVER_NAME</code>
|
||||
they may be broken by this option. The client is essentially free
|
||||
to give whatever value they want as a hostname. But if the CGI is
|
||||
only using <code>SERVER_NAME</code> to construct self-referential URLs
|
||||
then it should be just fine.</p>
|
||||
</div>
|
||||
<h3>See also</h3><ul><li><code class="directive"><a href="#servername">ServerName</a></code></li><li><code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code></li></ul></div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="directive-section"><h2><a name="VirtualHost" id="VirtualHost"><VirtualHost></a> <a name="virtualhost" id="virtualhost">Directive</a></h2><table class="directive"><tr><th><a href="directive-dict.html#Description">Description:
|
||||
</a></th><td>Contains directives that apply only to a specific
|
||||
hostname or IP address</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:
|
||||
@@ -2228,11 +2276,13 @@ hostname or IP address</td></tr><tr><th><a href="directive-dict.html#Syntax">Syn
|
||||
|
||||
<div class="example"><h3>Example</h3><p><code>
|
||||
<VirtualHost 10.1.2.3><br />
|
||||
ServerAdmin webmaster@host.foo.com<br />
|
||||
DocumentRoot /www/docs/host.foo.com<br />
|
||||
ServerName host.foo.com<br />
|
||||
ErrorLog logs/host.foo.com-error_log<br />
|
||||
TransferLog logs/host.foo.com-access_log<br />
|
||||
<span class="indent">
|
||||
ServerAdmin webmaster@host.foo.com<br />
|
||||
DocumentRoot /www/docs/host.foo.com<br />
|
||||
ServerName host.foo.com<br />
|
||||
ErrorLog logs/host.foo.com-error_log<br />
|
||||
TransferLog logs/host.foo.com-access_log<br />
|
||||
</span>
|
||||
</VirtualHost>
|
||||
</code></p></div>
|
||||
|
||||
@@ -2243,11 +2293,13 @@ hostname or IP address</td></tr><tr><th><a href="directive-dict.html#Syntax">Syn
|
||||
|
||||
<div class="example"><p><code>
|
||||
<VirtualHost [fe80::a00:20ff:fea7:ccea]><br />
|
||||
ServerAdmin webmaster@host.example.com<br />
|
||||
DocumentRoot /www/docs/host.example.com<br />
|
||||
ServerName host.example.com<br />
|
||||
ErrorLog logs/host.example.com-error_log<br />
|
||||
TransferLog logs/host.example.com-access_log<br />
|
||||
<span class="indent">
|
||||
ServerAdmin webmaster@host.example.com<br />
|
||||
DocumentRoot /www/docs/host.example.com<br />
|
||||
ServerName host.example.com<br />
|
||||
ErrorLog logs/host.example.com-error_log<br />
|
||||
TransferLog logs/host.example.com-access_log<br />
|
||||
</span>
|
||||
</VirtualHost>
|
||||
</code></p></div>
|
||||
|
||||
@@ -2259,6 +2311,13 @@ hostname or IP address</td></tr><tr><th><a href="directive-dict.html#Syntax">Syn
|
||||
accomplished with the <code>ifconfig alias</code> command (if
|
||||
your OS supports it).</p>
|
||||
|
||||
<div class="note"><h3>Note</h3>
|
||||
<p>The use of <code class="directive"><VirtualHost></code> does
|
||||
<strong>not</strong> affect what addresses Apache listens on. You
|
||||
may need to ensure that Apache is listening on the correct addresses
|
||||
using <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>.</p>
|
||||
</div>
|
||||
|
||||
<p>When using IP-based virtual hosting, the special name
|
||||
<code>_default_</code> can be specified in
|
||||
which case this virtual host will match any IP address that is
|
||||
@@ -2277,14 +2336,12 @@ hostname or IP address</td></tr><tr><th><a href="directive-dict.html#Syntax">Syn
|
||||
to match all ports on that address. (This is recommended when used
|
||||
with <code>_default_</code>.)</p>
|
||||
|
||||
<p><strong>SECURITY</strong>: See the <a href="../misc/security_tips.html">security tips</a> document
|
||||
for details on why your security could be compromised if the
|
||||
<div class="warning"><h3>Security</h3>
|
||||
<p>See the <a href="../misc/security_tips.html">security tips</a>
|
||||
document for details on why your security could be compromised if the
|
||||
directory where logfiles are stored is writable by anyone other
|
||||
than the user that starts the server.</p>
|
||||
|
||||
<p><strong>NOTE</strong>: The use of <code class="directive"><VirtualHost></code> does <strong>not</strong>
|
||||
affect what addresses Apache listens on. You may need to ensure
|
||||
that Apache is listening on the correct addresses using <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>.</p>
|
||||
</div>
|
||||
<h3>See also</h3><ul><li><a href="../vhosts/">Apache Virtual Host documentation</a></li><li><a href="../dns-caveats.html">Warnings about DNS and
|
||||
Apache</a></li><li><a href="../bind.html">Setting
|
||||
which addresses and ports Apache uses</a></li><li><a href="../sections.html">How
|
||||
|
||||
@@ -67,12 +67,14 @@ available</description>
|
||||
request, so you can use the following configuration to enable
|
||||
such a script:</p>
|
||||
|
||||
<example><pre>
|
||||
<Files "mypaths.shtml">
|
||||
Options +Includes
|
||||
SetOutputFilter INCLUDES
|
||||
AcceptPathInfo on
|
||||
</Files></pre>
|
||||
<example>
|
||||
<Files "mypaths.shtml"><br />
|
||||
<indent>
|
||||
Options +Includes<br />
|
||||
SetOutputFilter INCLUDES<br />
|
||||
AcceptPathInfo on<br />
|
||||
</indent>
|
||||
</Files>
|
||||
</example>
|
||||
|
||||
</usage>
|
||||
@@ -103,10 +105,12 @@ available</description>
|
||||
<code>/usr/local/.acl</code> and <code>/usr/local/web/.acl</code>
|
||||
for directives, unless they have been disabled with</p>
|
||||
|
||||
<example><pre>
|
||||
<Directory />
|
||||
AllowOverride None
|
||||
</Directory></pre>
|
||||
<example>
|
||||
<Directory /><br />
|
||||
<indent>
|
||||
AllowOverride None<br />
|
||||
</indent>
|
||||
</Directory>
|
||||
</example>
|
||||
</usage>
|
||||
<seealso><directive module="core">AllowOverride</directive></seealso>
|
||||
@@ -424,10 +428,12 @@ named file-system directory and sub-directories</description>
|
||||
<code>/home/user/public_html</code>, but <code><Directory
|
||||
/home/*/public_html></code> will match. Example:</p>
|
||||
|
||||
<example><pre>
|
||||
<Directory /usr/local/httpd/htdocs>
|
||||
Options Indexes FollowSymLinks
|
||||
</Directory></pre>
|
||||
<example>
|
||||
<Directory /usr/local/httpd/htdocs><br />
|
||||
<indent>
|
||||
Options Indexes FollowSymLinks<br />
|
||||
</indent>
|
||||
</Directory>
|
||||
</example>
|
||||
|
||||
<note>
|
||||
@@ -457,14 +463,18 @@ named file-system directory and sub-directories</description>
|
||||
href="#accessfilename">.htaccess</a> files. For example,
|
||||
with</p>
|
||||
|
||||
<example><pre>
|
||||
<Directory />
|
||||
AllowOverride None
|
||||
</Directory>
|
||||
|
||||
<Directory /home/>
|
||||
AllowOverride FileInfo
|
||||
</Directory></pre>
|
||||
<example>
|
||||
<Directory /><br />
|
||||
<indent>
|
||||
AllowOverride None<br />
|
||||
</indent>
|
||||
</Directory><br />
|
||||
<br />
|
||||
<Directory /home/><br />
|
||||
<indent>
|
||||
AllowOverride FileInfo<br />
|
||||
</indent>
|
||||
</Directory>
|
||||
</example>
|
||||
|
||||
<p>for access to the document <code>/home/web/dir/doc.html</code>
|
||||
@@ -486,10 +496,12 @@ named file-system directory and sub-directories</description>
|
||||
expressions are tested in the order they appeared in the
|
||||
configuration file. For example, with</p>
|
||||
|
||||
<example><pre>
|
||||
<Directory ~ abc$>
|
||||
# ... directives here ...
|
||||
</Directory></pre>
|
||||
<example>
|
||||
<Directory ~ abc$><br />
|
||||
<indent>
|
||||
# ... directives here ...<br />
|
||||
</indent>
|
||||
</Directory>
|
||||
</example>
|
||||
|
||||
<p>The regular expression section won't be considered until after
|
||||
@@ -503,11 +515,13 @@ named file-system directory and sub-directories</description>
|
||||
recommended that you change this with a block such
|
||||
as</strong></p>
|
||||
|
||||
<example><pre>
|
||||
<Directory />
|
||||
Order Deny,Allow
|
||||
Deny from All
|
||||
</Directory></pre>
|
||||
<example>
|
||||
<Directory /><br />
|
||||
<indent>
|
||||
Order Deny,Allow<br />
|
||||
Deny from All<br />
|
||||
</indent>
|
||||
</Directory>
|
||||
</example>
|
||||
|
||||
<p><strong>and then override this for directories you
|
||||
@@ -1024,14 +1038,16 @@ if a test is true at startup</description>
|
||||
nest-able, which can be used to implement simple
|
||||
multiple-parameter tests. Example:</p>
|
||||
|
||||
<example><pre>
|
||||
$ httpd -DReverseProxy ...
|
||||
|
||||
# httpd.conf
|
||||
<IfDefine ReverseProxy>
|
||||
LoadModule rewrite_module modules/mod_rewrite.so
|
||||
LoadModule proxy_module modules/libproxy.so
|
||||
</IfDefine></pre>
|
||||
<example>
|
||||
httpd -DReverseProxy ...<br />
|
||||
<br />
|
||||
# httpd.conf<br />
|
||||
<IfDefine ReverseProxy><br />
|
||||
<indent>
|
||||
LoadModule rewrite_module modules/mod_rewrite.so<br />
|
||||
LoadModule proxy_module modules/libproxy.so<br />
|
||||
</indent>
|
||||
</IfDefine>
|
||||
</example>
|
||||
</usage>
|
||||
</directivesynopsis>
|
||||
@@ -1221,7 +1237,7 @@ methods</description>
|
||||
<strong>all</strong> access methods, and this is the usual
|
||||
desired behavior. <strong>In the general case, access control
|
||||
directives should not be placed within a
|
||||
<directive type="section">limit</directive> section.</strong></p>
|
||||
<directive type="section">Limit</directive> section.</strong></p>
|
||||
|
||||
<p>The purpose of the <directive type="section">Limit</directive>
|
||||
directive is to restrict the effect of the access controls to the
|
||||
@@ -1231,10 +1247,12 @@ methods</description>
|
||||
example applies the access control only to the methods POST, PUT,
|
||||
and DELETE, leaving all other methods unprotected:</p>
|
||||
|
||||
<example><pre>
|
||||
<Limit POST PUT DELETE>
|
||||
Require valid-user
|
||||
</Limit></pre>
|
||||
<example>
|
||||
<Limit POST PUT DELETE><br />
|
||||
<indent>
|
||||
Require valid-user<br />
|
||||
</indent>
|
||||
</Limit>
|
||||
</example>
|
||||
|
||||
<p>The method names listed can be one or more of: <code>GET</code>,
|
||||
@@ -1272,10 +1290,12 @@ except the named ones</description>
|
||||
|
||||
<p>For example:</p>
|
||||
|
||||
<example><pre>
|
||||
<LimitExcept POST GET>
|
||||
Require valid-user
|
||||
<LimitExcept></pre>
|
||||
<example>
|
||||
<LimitExcept POST GET><br />
|
||||
<indent>
|
||||
Require valid-user<br />
|
||||
</indent>
|
||||
<LimitExcept>
|
||||
</example>
|
||||
|
||||
</usage>
|
||||
@@ -1528,13 +1548,15 @@ URLs</description>
|
||||
directive. For example, to enable status requests, but allow them
|
||||
only from browsers at foo.com, you might use:</p>
|
||||
|
||||
<example><pre>
|
||||
<Location /status>
|
||||
SetHandler server-status
|
||||
Order Deny,Allow
|
||||
Deny from all
|
||||
Allow from .foo.com
|
||||
</Location></pre>
|
||||
<example>
|
||||
<Location /status><br />
|
||||
<indent>
|
||||
SetHandler server-status<br />
|
||||
Order Deny,Allow<br />
|
||||
Deny from all<br />
|
||||
Allow from .foo.com<br />
|
||||
</indent>
|
||||
</Location>
|
||||
</example>
|
||||
|
||||
<note><title>Note about / (slash)</title>
|
||||
@@ -1897,28 +1919,36 @@ directory</description>
|
||||
|
||||
<p>For example, without any + and - symbols:</p>
|
||||
|
||||
<example><pre>
|
||||
<Directory /web/docs>
|
||||
Options Indexes FollowSymLinks
|
||||
</Directory>
|
||||
|
||||
<Directory /web/docs/spec>
|
||||
Options Includes
|
||||
</Directory></pre>
|
||||
<example>
|
||||
<Directory /web/docs><br />
|
||||
<indent>
|
||||
Options Indexes FollowSymLinks<br />
|
||||
</indent>
|
||||
</Directory><br />
|
||||
<br />
|
||||
<Directory /web/docs/spec><br />
|
||||
<indent>
|
||||
Options Includes<br />
|
||||
</indent>
|
||||
</Directory>
|
||||
</example>
|
||||
|
||||
<p>then only <code>Includes</code> will be set for the
|
||||
/web/docs/spec directory. However if the second
|
||||
<directive>Options</directive> directive uses the + and - symbols:</p>
|
||||
|
||||
<example><pre>
|
||||
<Directory /web/docs>
|
||||
Options Indexes FollowSymLinks
|
||||
</Directory>
|
||||
|
||||
<Directory /web/docs/spec>
|
||||
Options +Includes -Indexes
|
||||
</Directory></pre>
|
||||
<example>
|
||||
<Directory /web/docs><br />
|
||||
<indent>
|
||||
Options Indexes FollowSymLinks<br />
|
||||
</indent>
|
||||
</Directory><br />
|
||||
<br />
|
||||
<Directory /web/docs/spec><br />
|
||||
<indent>
|
||||
Options +Includes -Indexes<br />
|
||||
</indent>
|
||||
</Directory>
|
||||
</example>
|
||||
|
||||
<p>then the options <code>FollowSymLinks</code> and
|
||||
@@ -2420,7 +2450,9 @@ handler</description>
|
||||
|
||||
<example>
|
||||
<Location /status><br />
|
||||
SetHandler server-status<br />
|
||||
<indent>
|
||||
SetHandler server-status<br />
|
||||
</indent>
|
||||
</Location>
|
||||
</example>
|
||||
</usage>
|
||||
@@ -2476,10 +2508,12 @@ server</description>
|
||||
in the <code>/www/data/</code> directory for server-side
|
||||
includes.</p>
|
||||
|
||||
<example><pre>
|
||||
<Directory /www/data/>
|
||||
SetOutputFilter INCLUDES
|
||||
</Directory></pre>
|
||||
<example>
|
||||
<Directory /www/data/><br />
|
||||
<indent>
|
||||
SetOutputFilter INCLUDES<br />
|
||||
</indent>
|
||||
</Directory>
|
||||
</example>
|
||||
|
||||
<p>If more than one filter is specified, they must be separated
|
||||
@@ -2571,12 +2605,13 @@ port</description>
|
||||
reverse DNS lookup on the server IP address that the client
|
||||
connected to in order to work out self-referential URLs.</p>
|
||||
|
||||
<p><strong>Warning:</strong> if CGIs make assumptions about the
|
||||
values of <code>SERVER_NAME</code> they may be broken by this
|
||||
option. The client is essentially free to give whatever value
|
||||
they want as a hostname. But if the CGI is only using
|
||||
<code>SERVER_NAME</code> to construct self-referential URLs
|
||||
<note type="warning"><title>Warning:</title>
|
||||
<p>If CGIs make assumptions about the values of <code>SERVER_NAME</code>
|
||||
they may be broken by this option. The client is essentially free
|
||||
to give whatever value they want as a hostname. But if the CGI is
|
||||
only using <code>SERVER_NAME</code> to construct self-referential URLs
|
||||
then it should be just fine.</p>
|
||||
</note>
|
||||
</usage>
|
||||
<seealso><directive module="core">ServerName</directive></seealso>
|
||||
<seealso><directive module="mpm_common">Listen</directive></seealso>
|
||||
@@ -2616,11 +2651,13 @@ hostname or IP address</description>
|
||||
|
||||
<example><title>Example</title>
|
||||
<VirtualHost 10.1.2.3><br />
|
||||
ServerAdmin webmaster@host.foo.com<br />
|
||||
DocumentRoot /www/docs/host.foo.com<br />
|
||||
ServerName host.foo.com<br />
|
||||
ErrorLog logs/host.foo.com-error_log<br />
|
||||
TransferLog logs/host.foo.com-access_log<br />
|
||||
<indent>
|
||||
ServerAdmin webmaster@host.foo.com<br />
|
||||
DocumentRoot /www/docs/host.foo.com<br />
|
||||
ServerName host.foo.com<br />
|
||||
ErrorLog logs/host.foo.com-error_log<br />
|
||||
TransferLog logs/host.foo.com-access_log<br />
|
||||
</indent>
|
||||
</VirtualHost>
|
||||
</example>
|
||||
|
||||
@@ -2631,11 +2668,13 @@ hostname or IP address</description>
|
||||
|
||||
<example>
|
||||
<VirtualHost [fe80::a00:20ff:fea7:ccea]><br />
|
||||
ServerAdmin webmaster@host.example.com<br />
|
||||
DocumentRoot /www/docs/host.example.com<br />
|
||||
ServerName host.example.com<br />
|
||||
ErrorLog logs/host.example.com-error_log<br />
|
||||
TransferLog logs/host.example.com-access_log<br />
|
||||
<indent>
|
||||
ServerAdmin webmaster@host.example.com<br />
|
||||
DocumentRoot /www/docs/host.example.com<br />
|
||||
ServerName host.example.com<br />
|
||||
ErrorLog logs/host.example.com-error_log<br />
|
||||
TransferLog logs/host.example.com-access_log<br />
|
||||
</indent>
|
||||
</VirtualHost>
|
||||
</example>
|
||||
|
||||
@@ -2647,6 +2686,13 @@ hostname or IP address</description>
|
||||
accomplished with the <code>ifconfig alias</code> command (if
|
||||
your OS supports it).</p>
|
||||
|
||||
<note><title>Note</title>
|
||||
<p>The use of <directive type="section">VirtualHost</directive> does
|
||||
<strong>not</strong> affect what addresses Apache listens on. You
|
||||
may need to ensure that Apache is listening on the correct addresses
|
||||
using <directive module="mpm_common">Listen</directive>.</p>
|
||||
</note>
|
||||
|
||||
<p>When using IP-based virtual hosting, the special name
|
||||
<code>_default_</code> can be specified in
|
||||
which case this virtual host will match any IP address that is
|
||||
@@ -2667,17 +2713,12 @@ hostname or IP address</description>
|
||||
to match all ports on that address. (This is recommended when used
|
||||
with <code>_default_</code>.)</p>
|
||||
|
||||
<p><strong>SECURITY</strong>: See the <a
|
||||
href="../misc/security_tips.html">security tips</a> document
|
||||
for details on why your security could be compromised if the
|
||||
<note type="warning"><title>Security</title>
|
||||
<p>See the <a href="../misc/security_tips.html">security tips</a>
|
||||
document for details on why your security could be compromised if the
|
||||
directory where logfiles are stored is writable by anyone other
|
||||
than the user that starts the server.</p>
|
||||
|
||||
<p><strong>NOTE</strong>: The use of <directive
|
||||
type="section">VirtualHost</directive> does <strong>not</strong>
|
||||
affect what addresses Apache listens on. You may need to ensure
|
||||
that Apache is listening on the correct addresses using <directive
|
||||
module="mpm_common">Listen</directive>.</p>
|
||||
</note>
|
||||
</usage>
|
||||
<seealso><a href="../vhosts/">Apache Virtual Host documentation</a></seealso>
|
||||
<seealso><a href="../dns-caveats.html">Warnings about DNS and
|
||||
|
||||
@@ -457,7 +457,7 @@ a resource</td></tr>
|
||||
synchronization</td></tr>
|
||||
<tr class="odd"><td><a href="mod_rewrite.html#rewritelog">RewriteLog <em>file-path</em></a></td><td /><td>sv</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Sets the name of the file used for logging rewrite engine
|
||||
processing</td></tr>
|
||||
<tr><td><a href="mod_rewrite.html#rewriteloglevel">RewriteLogLevel <em>Level</em></a></td><td /><td>sv</td><td>E</td></tr><tr><td class="descr" colspan="4">Sets the verbosity of the log file used by the rewrite
|
||||
<tr><td><a href="mod_rewrite.html#rewriteloglevel">RewriteLogLevel <em>Level</em></a></td><td> 0 </td><td>sv</td><td>E</td></tr><tr><td class="descr" colspan="4">Sets the verbosity of the log file used by the rewrite
|
||||
engine</td></tr>
|
||||
<tr class="odd"><td><a href="mod_rewrite.html#rewritemap">RewriteMap <em>MapName</em> <em>MapType</em>:<em>MapSource</em>
|
||||
</a></td><td /><td>sv</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Defines a mapping function for key-lookup</td></tr>
|
||||
|
||||
Reference in New Issue
Block a user