W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2010

Fwd: I-D Action:draft-reschke-basicauth-enc-00.txt

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 11 Aug 2010 16:55:40 +0200
Message-ID: <4C62B9EC.6050001@gmx.de>
To: HTTP Working Group <ietf-http-wg@w3.org>
FYI: a *very* modest proposal to fix the I18N issue in Basic 
Authentication (just that, nothing else).

Best regards, Julian

-------- Original Message --------
Subject: I-D Action:draft-reschke-basicauth-enc-00.txt
Date: Wed, 11 Aug 2010 07:30:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
Reply-To: internet-drafts@ietf.org
To: i-d-announce@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts 

	Title           : An Encoding Parameter for HTTP Basic Authentication
	Author(s)       : J. Reschke
	Filename        : draft-reschke-basicauth-enc-00.txt
	Pages           : 6
	Date            : 2010-08-11

The "Basic" authentication scheme defined in RFC 2617 does not
properly define how to treat non-ASCII characters.  This has lead to
a situation where user agent implementations disagree, and servers
make different assumptions based on the locales they are running in.
There is little interoperability for characters in the ISO-8859-1
character set, and even less interoperability for any characters
beyond that.

This document defines a backwards-compatible extension to "Basic",
specifying the server's character encoding expectation, using a new
authentication scheme parameter.

A URL for this Internet-Draft is:

Internet-Drafts are also available by anonymous FTP at:

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the

Received on Wednesday, 11 August 2010 14:56:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:54 UTC