An Encoding Parameter for HTTP Basic Authentication
draft-reschke-basicauth-enc-08

 
Document
Type Replaced Internet-Draft (httpauth WG)
Last updated 2013-06-10 (latest revision 2013-05-08)
Replaced by draft-ietf-httpauth-basicauth-enc, draft-ietf-httpauth-basicauth-update
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream
WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG
IESG state Replaced by draft-ietf-httpauth-basicauth-enc, draft-ietf-httpauth-basicauth-update
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
//www.ietf.org/archive/id/draft-reschke-basicauth-enc-08.txt

Abstract

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 the non-ASCII 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.

Authors

Julian Reschke (julian.reschke@greenbytes.de)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)