Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 2355 invoked from network); 6 Feb 2007 19:10:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Feb 2007 19:10:51 -0000 Received: (qmail 57990 invoked by uid 500); 6 Feb 2007 19:10:46 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 57975 invoked by uid 500); 6 Feb 2007 19:10:45 -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 57964 invoked by uid 99); 6 Feb 2007 19:10:45 -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:10:45 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,PLING_QUERY,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of lizkim270@gmail.com designates 66.249.92.168 as permitted sender) Received: from [66.249.92.168] (HELO ug-out-1314.google.com) (66.249.92.168) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Feb 2007 11:10:36 -0800 Received: by ug-out-1314.google.com with SMTP id 75so1715204ugb for ; Tue, 06 Feb 2007 11:10:15 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=MiPE5EImGe9r99f8pXYeGUuIeytfSvnBg/MbuPaary1zPFRV+UFYYMb2zqHo5H2vIh/mpSSuBXKyWCDOKtOUascUzm1WVpbT6OKuFrL6KF2K3YQvfyHVJa6oX+VdrOVupLoSCwIrqDxDgs5xwbnj2TmpAa4Z8YQ7E0R3MDcA5Ic= Received: by 10.78.139.1 with SMTP id m1mr1864669hud.1170789014698; Tue, 06 Feb 2007 11:10:14 -0800 (PST) Received: by 10.78.35.7 with HTTP; Tue, 6 Feb 2007 11:10:14 -0800 (PST) Message-ID: <3e9f0ea0702061110p41f49650nba322639b62f0715@mail.gmail.com> Date: Tue, 6 Feb 2007 11:10:14 -0800 From: "Liz Kim" To: users@httpd.apache.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_7300_1997177.1170789014651" References: <3e9f0ea0702061007p17440c52r6958f9370f828eb0@mail.gmail.com> <3e9f0ea0702061031x6639f06aw6a9eebcde9748a0c@mail.gmail.com> <3e9f0ea0702061041i59e8141cy35a89c1c1f3352e9@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] Satisfy any?! ------=_Part_7300_1997177.1170789014651 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Ah.. Ok so pretty much what I am trying to do == impossible! Thanks for being so patient! :) On 2/6/07, Joshua Slive wrote: > > On 2/6/07, Liz Kim wrote: > > Just to clearing things: > > There cant be two separate passwords for the following two URLs? > > http://someurl/A > > http://someurl/A/B > > You keep changing your question ;-) > > Yes, there can be two separate passwords: one that you get if you > request http://.../A and one for http://.../A/B. Earlier you asked "I > would like to the client to able to view B by entering in two > passwords". The answer to that remains no. Each URL can only be > protected by a single password. http://.../A and http://.../A/B are > different URLs. > > So if the client goes first to /A and then to /A/B, they will get two > different login prompts if you protect with different auth directives. > But if they go directly to /A/B they will only get a single login > prompt. > > 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 > > ------=_Part_7300_1997177.1170789014651 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Ah.. Ok so pretty much
what I am trying to do == impossible!
Thanks for being so patient! :)

On 2/6/07, Joshua Slive < joshua@slive.ca> wrote:
On 2/6/07, Liz Kim < lizkim270@gmail.com> wrote:
> Just to clearing things:
> There cant be two separate passwords for the following two URLs?
> http://someurl/A
> http://someurl/A/B

You keep changing your question ;-)

Yes, there can be two separate passwords: one that you get if you
request http://.../A and one for http://.../A/B.  Earlier you asked "I
would like to the client to able to view B by entering in two
passwords".  The answer to that remains no.  Each URL can only be
protected by a single password.  http://.../A and http://.../A/B are
different URLs.

So if the client goes first to /A and then to /A/B, they will get two
different login prompts if you protect with different auth directives.
But if they go directly to /A/B they will only get a single login
prompt.

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: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


------=_Part_7300_1997177.1170789014651--