Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 20734 invoked from network); 6 Feb 2007 19:54:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Feb 2007 19:54:53 -0000 Received: (qmail 50402 invoked by uid 500); 6 Feb 2007 19:54:51 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 50092 invoked by uid 500); 6 Feb 2007 19:54:50 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 50075 invoked by uid 99); 6 Feb 2007 19:54:50 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Feb 2007 11:54:50 -0800 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=MAILTO_TO_SPAM_ADDR,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of jslive@gmail.com designates 66.249.82.226 as permitted sender) Received: from [66.249.82.226] (HELO wx-out-0506.google.com) (66.249.82.226) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Feb 2007 11:54:40 -0800 Received: by wx-out-0506.google.com with SMTP id t13so1860543wxc for ; Tue, 06 Feb 2007 11:54:19 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=JAEAmCGkx53tSOOnSkq6O+EWDWRtWGveqKDuI5BNyRTQlOX3AgpY5PwPN2dm25LwFpOSL/dNX74Fb8PRp0jSAgBWIGclDDpPv++LELjVf7A0HT62E8VC46hBfJl/uALvf047tvWb/h6eEIPzz9qehhJm2WffUa5GD7m3X+sK0m0= Received: by 10.70.38.9 with SMTP id l9mr15223087wxl.1170791659741; Tue, 06 Feb 2007 11:54:19 -0800 (PST) Received: by 10.70.20.20 with HTTP; Tue, 6 Feb 2007 11:54:19 -0800 (PST) Message-ID: Date: Tue, 6 Feb 2007 14:54:19 -0500 From: "Joshua Slive" Sender: jslive@gmail.com To: users@httpd.apache.org In-Reply-To: <3e9f0ea0702061132k30d6fa03rb86b64171cb8a6d5@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3e9f0ea0702061035s45d83713p8602571bc4d2ffd9@mail.gmail.com> <3e9f0ea0702061043h36078215h50cc5340a12c700e@mail.gmail.com> <3e9f0ea0702061132k30d6fa03rb86b64171cb8a6d5@mail.gmail.com> X-Google-Sender-Auth: 2a6d4342d9e3c941 X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] Defining IPs in one place On 2/6/07, Liz Kim wrote: > It would be ideal to keep the protections on /A/* as they are, while > updating the protection on /A. > However, it seems that adding "Satisfy any" on /A is disabling the > protections on directories under /A. > For example, /A/B now needs to satisfy any of /A's list of IP's, /A's > password or /A/B's password. No, /A/B will not be affected at all by /A's password if you define a new set of auth directives for /A/B. The Allow/Deny/Satisfy directive, however, will carry over unless you override them in /A/B. > > The only solution I see is to define independent protections on /A and /A/* > For example, /A would "Satisfy any" with a list of IP's and a password. > /A/B would "Satisfy all" with the list of the same IP's a different > password. You should not need to relist the Allow/Deny directives in /A/B. The will be inherited from /A. Just put "Satisfy All" in /A/B along with whatever new password you want. Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org