Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 97465 invoked from network); 15 Jun 2006 14:57:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Jun 2006 14:57:45 -0000 Received: (qmail 45898 invoked by uid 500); 15 Jun 2006 14:57:32 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 45852 invoked by uid 500); 15 Jun 2006 14:57:32 -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 45821 invoked by uid 99); 15 Jun 2006 14:57:31 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jun 2006 07:57:31 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [207.155.252.219] (HELO warrior.cnchost.com) (207.155.252.219) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jun 2006 07:57:30 -0700 Received: from [192.168.0.21] (c-24-15-193-17.hsd1.il.comcast.net [24.15.193.17]) by warrior.cnchost.com (ConcentricHost(2.54) Relay) with ESMTP id 4BDAA21D3 for ; Thu, 15 Jun 2006 10:56:51 -0400 (EDT) Message-ID: <44917532.6020104@rowe-clan.net> Date: Thu, 15 Jun 2006 09:56:50 -0500 From: "William A. Rowe, Jr." User-Agent: Mozilla Thunderbird 1.0.8-1.1.fc4 (X11/20060501) X-Accept-Language: en-us, en MIME-Version: 1.0 To: users@httpd.apache.org References: <877j3i4hcj.fsf@newsguy.com> In-Reply-To: <877j3i4hcj.fsf@newsguy.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] Password protect... no user required X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N reader@newsguy.com wrote: > > What doesn't appear to be explained is how to get around the incoming > browser user having to know a username and it is a real username on > server. > > There is some discussion of setting your own usernames but still it > would seem to require an incoming browser to supply both a username > and a password. Uhm, perhaps because the RFC calls for a username and password to be sent. It isn't either/or. --------------------------------------------------------------------- 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