An Encoding Mechanism for HTTP Digest Authentication
draft-ietf-httpauth-digest-encoding-02
| Document | Type |
Replaced Internet-Draft
(httpauth WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Rifaat Shekh-Yusef | ||
| Last updated | 2014-01-13 (Latest revision 2013-07-07) | ||
| Replaced by | RFC 7616 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-httpauth-digest | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
RFC2617 does not define how to treat Unicode characters [UNICODE] outside the ASCII range [RFC20] with the "Digest" scheme. This document defines an extension to the "Digest" scheme, and a mechanism that enables the client and server to negotiate their support for the UTF-8 [RFC3629] character encoding scheme.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)