From 8be30dd5eec98384a0fbccb8c5dbb58dce126513 Mon Sep 17 00:00:00 2001 From: Joshua Slive Date: Tue, 29 Nov 2005 18:22:43 +0000 Subject: [PATCH] Merge r349776 from trunk: Fix a mixed-up module reference and document (carefully) how to turn off require in a subdirectory. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@349779 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/core.xml | 33 ++++++++++++++++++++++++++++++++- 1 file changed, 32 insertions(+), 1 deletion(-) diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml index 4e663fb6920..0da8fdf2d77 100644 --- a/docs/manual/mod/core.xml +++ b/docs/manual/mod/core.xml @@ -2394,7 +2394,7 @@ a resource

This directive selects which authenticated users can access a resource. The restrictions are processed by authorization modules. Some of the allowed syntaxes provided by - mod_authz_owner and + mod_authz_user and mod_authz_groupfile are:

@@ -2437,6 +2437,37 @@ a resource place the Require statement into a Limit section.

+ +

If Require is used together with + the Allow or + Deny directives, + then the interaction of these restrictions is controlled by + the Satisfy directive.

+ + Removing controls in subdirectories +

The following example shows how to use the Satisfy directive to disable access + controls in a subdirectory of a protected directory. This + technique should be used with caution, because it will also + disable any access controls imposed by + mod_authz_host.

+ + <Directory /path/to/protected/>
+ + Require user david
+
+ </Directory>
+ <Directory /path/to/protected/unprotected>
+ + # All access controls and authentication are disabled
+ # in this directory
+ Satisfy Any
+ Allow from all
+
+ </Directory>
+
+
+ Authentication, Authorization, -- 2.47.2