Thanks Joshua.. Following your explanation.. It seems like I was mistaken. When I did "Satisfy All" on /A/B it seems like it is checking All of the IP check and the Password check that was applied to /A and the password on /A/B.... Is there a way to keep /A "Satisfy any" and /A/B to inherit whatever /A had AND specific protections for /A/B? I would like to the client to able to view B by entering in two passwords (one for /A's protection and another for /A/B) when they're not on an allowed IP?
Thanks!! On 2/6/07, Joshua Slive <[EMAIL PROTECTED]> wrote:
On 2/6/07, Liz Kim <[EMAIL PROTECTED]> wrote: > How does "Satisfy any" effect the lower directories? > > I have a directory /A and /A/B and /A/B/C. > /A allows certain IPs > /A/B asks for password > /A/B/C asks for password > > I want to add the option "Satisfy any" on /A by prompting the client for a > password when hes not on the allowed IP. > When I do so, the password protection on B gets disabled... > So then I add "Satisfy all" on B on top of the "Satisfy any" on A then it > works OK even the protection on C is working Ok > although I have not added the "Satisfy all" on C... I don't understand what problem you are trying to address. It seems you have everything working as you want by using Satisfy All in /A/B If you are just curious about why it works: Satisfy, as with most apache directives, applies to the directory it is in and all child directories. So by applying it to /A you also apply it to /A/B and /A/B/C. By applying Satisfy All to /A/B you also apply it to /A/B/C. Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
