datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

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

Document type: Replaced Internet-Draft (httpauth WG)
Document stream: IETF
Last updated: 2013-06-10 (latest revision 2013-05-08)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html
IETF State: Adopted by a WG
Consensus: Unknown
Document shepherd: No shepherd assigned
IESG State: Replaced by draft-ietf-httpauth-basicauth-enc
Responsible AD: (None)
Send notices to: No addresses provided
Email Authors | IPR Disclosures | References | Referenced By | Check nits | History feed | Search Mailing Lists

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-reschke-basicauth-enc

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)