W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2012

Re: paramname in draft-reschke-basicauth-enc-04

From: Stefan Eissing <stefan.eissing@greenbytes.de>
Date: Sun, 5 Feb 2012 14:16:57 +0100
Cc: "Julian Reschke" <julian.reschke@gmx.de>, "Bjoern Hoehrmann" <derhoermi@gmx.net>, Martin J. Dürst <duerst@it.aoyama.ac.jp>, "HTTP Working Group" <ietf-http-wg@w3.org>
Message-Id: <D07DD322-C80B-40A8-B70E-13944E03EE94@greenbytes.de>
To: "Anne van Kesteren" <annevk@opera.com>
For "basic" that would be reasonable. Is this also intended to work
for Digest or NTLM? 

If so, it would be useful for legacy systems that have stored password
hashes in other encodings to announce the encoding they need. (If I remember
implementation of digest and ntlm correctly)

//Stefan

Am 05.02.2012 um 12:56 schrieb Anne van Kesteren:

> On Sat, 04 Feb 2012 12:55:26 +0100, Julian Reschke <julian.reschke@gmx.de> wrote:
>> Now there's not a lot we can do about people not reading specs, but how about:
>> 
>>   WWW-Authenticate: Basic realm="something", accept-charset="UTF-8"
> 
> Works for me. It only accepts "UTF-8" (case-insensitive) as value right?
> 
> 
> -- 
> Anne van Kesteren
> http://annevankesteren.nl/
> 

<green/>bytes GmbH
Hafenweg 16, 48155 Münster, Germany
Phone: +49 251 2807760. Amtsgericht Münster: HRB5782
Received on Sunday, 5 February 2012 13:17:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:54 GMT