AuthName somedomain<br>
AuthUserFile /web/users<br>
AuthGroupFile /web/groups<br>
-Limit <GET POST><br>
+<Limit GET POST><br>
require group admin<br>
</Limit>
</code></blockquote>
<A name="satisfy"><h2>Satisfy</h2></A>
<!--%plaintext <?INDEX {\tt Satisfy} directive> -->
-<strong>Syntax:</strong><br>
+<strong>Syntax:</strong> Satisfy <em>'any' or 'all'</em><br>
<strong>Context:</strong> server config, virtual host, directory, .htaccess<br>
<strong>Status:</strong> core<br>
<strong>Compatibility:</strong> Satisfy is only available in Apache 1.2 and later<p>
+Access policy if both allow and require used. The parameter can be either
+<em>'all'</em> or <em>'any'</em>.
+
<p><hr>
<A name="sendbuffersize"><h2>SendBufferSize</h2></A>
<strong>Compatibility:</strong> ServerPath is only available in Apache
1.1 and later.<p>
-The ServerAlias directive sets the legacy URL pathname for a host, for
+The ServerPath directive sets the legacy URL pathname for a host, for
use with <a href="../host.html">Host-header based virtual hosts</a>.
<hr>
The ServerRoot directive sets the directory in which the server lives.
Typically it will contain the subdirectories <code>conf/</code> and
<code>logs/</code>. Relative paths for other configuration files are taken
-as relative to this directory.<p><hr>
+as relative to this directory.<br>
+See also <a href="../invoking.html">the <code>-d</code> option to httpd</a>.<p><hr>
<A name="servertype"><h2>ServerType directive</h2></A>
<!--%plaintext <?INDEX {\tt ServerType} directive> -->
<strong>Syntax:</strong> <VirtualHost <em>addr</em>[:<em>port</em>]> ...
</VirtualHost> <br>
<strong>Context:</strong> server config<br>
-<strong>Status:</strong> Core. <p>
+<strong>Status:</strong> Core.<br>
+<strong>Compatibility:</strong> Non-IP address-based Virtual Hosting is
+only available in Apache 1.2 and later.<p>
<VirtualHost> and </VirtualHost> are used to enclose a group of
directives which will apply only to a particular virtual host.
</VirtualHost>
</code></blockquote>
-Currently, each VirtualHost must correspond to a different IP address for
-the server, so the server machine must be configured to accept IP packets for
-multiple addresses. If the machine does not have multiple network interfaces,
-then this can be accomplished with the <code>ifconfig alias</code> command
-(if your OS supports it), or with kernel patches like
-<A HREF="../misc/vif-info.html">VIF</A> (for SunOS(TM) 4.1.x).<p>
-
+Each VirtualHost must correspond to a different IP address or a
+different host name for the server, in the latter case the server
+machine must be configured to accept IP packets for multiple
+addresses. (If the machine does not have multiple network interfaces,
+then this can be accomplished with the <code>ifconfig alias</code>
+command (if your OS supports it), or with kernel patches like <A
+HREF="../misc/vif-info.html">VIF</A> (for SunOS(TM) 4.1.x)).<p>
<p><strong>See also:</strong>
<A HREF="../virtual-host.html">Information on Virtual Hosts.
Regular expressions have the same syntax as those found in the
Unix egrep command.
-<DT>( <I>test_condition</I> )<DD>true if <I>test_condition</I> is true
-<DT>! <I>test_condition</I><DD>true if <I>test_condition</I> is false
- <I>test_condition1</I> and <I>test_condition2</I> are true
-<DT><I>test_condition1</I> && <I>test_condition2</I><DD>true if both
- <I>test_condition1</I> and <I>test_condition2</I> are true
-<DT><I>test_condition1</I> || <I>test_condition2</I><DD>true if either
- <I>test_condition1</I> or <I>test_condition2</I> is true
+<DT>( <I>test_condition</I> )
+ <DD>true if <I>test_condition</I> is true
+<DT>! <I>test_condition</I>
+ <DD>true if <I>test_condition</I> is false
+<DT><I>test_condition1</I> && <I>test_condition2</I>
+ <DD>true if both <I>test_condition1</I> and <I>test_condition2</I> are true
+<DT><I>test_condition1</I> || <I>test_condition2</I>
+ <DD>true if either <I>test_condition1</I> or <I>test_condition2</I> is true
</DL>
<P> "<I>=</I>" and "</I>!=</I>" bind more tightly than "<I>&&</I>" and "<I>||</I>".