[11642] in www-talk@info.cern.ch
RE: cgi authorization
daemon@ATHENA.MIT.EDU (Igor Clark)
Wed Jun 21 10:54:23 2000
Date: Wed, 21 Jun 2000 05:12:13 -0400 (EDT)
Old-X-Envelope-From: www-talk-request@tux.w3.org Wed Jun 21 05:12:11 2000
From: Igor Clark <igor.clark@forefrontconsulting.co.uk>
To: Fish <fish@infidels.org>
Cc: www-talk@w3.org
In-Reply-To: <000001bfdb0f$8cff57c0$0200a8c0@PROTEVA>
Message-Id: <Pine.LNX.4.21.0006210952520.11894-100000@fevah.pixelpark.co.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Old-X-Envelope-To: www-talk
Resent-From: gerald@w3.org
Resent-To: www-talk@w3.org
Hi
> Apparently, according to RFC2616, the 401 response you received should have
> included a "WWW-Authenticate:" header. This header contains the challenge. The
> response to the challenge would, it seems, be entered in the "Authorization:"
> header on a subsequent request.
This is right. The header you have to supply is
Authorization: <username:password>
(without the < and >). As I understand it, the username/password pair
must be base-64 encoded.
Igor.
--
<?> Internet applications consulting & development
<e> igor@forefrontconsulting.co.uk
<m> +44 (0)79 6715 5849
