From: pcs Date: Fri, 18 Apr 1997 21:55:11 +0000 (+0000) Subject: Explain Satisfy directive. X-Git-Tag: APACHE_1_2b9~41 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=d982446ed0e4bf7c4f82bce8e8e79f2cba8b6cf8;p=apache Explain Satisfy directive. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@77931 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html index e04f1f82ae..0ac24a310e 100644 --- a/docs/manual/mod/core.html +++ b/docs/manual/mod/core.html @@ -1060,12 +1060,22 @@ See also RLimitMEM or RLimitCPU

Satisfy

Syntax: Satisfy 'any' or 'all'
+Default: Satisy all
Context: server config, virtual host, directory, .htaccess
Status: core
Compatibility: Satisfy is only available in Apache 1.2 and later

-Access policy if both allow and require used. The parameter can be either -'all' or 'any'. +Access policy if both allow and require used. The parameter can be +either 'all' or 'any'. This directive is only useful +if access to a particular area is being restricted by both +username/password and client host address. In this case the +default behavior ("all") is to require that the client passes the +address access restriction and enters a valid username and +password. With the "any" option the client will be granted access if +they either pass the host restriction or enter a valid username and +password. This can be used to password restrict an area, but to let +clients from particular addresses in without prompting for a password. +