Upgrading to SASL Within HTTP/1.1
draft-burdis-http-sasl-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Keith Burdis | ||
| Last updated | 2001-03-05 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
This document describes how to use the Upgrade mechanism in HTTP/1.1 to initiate an SASL session over an existing TCP connection, performing authentication using a negotiated SASL mechanism and then tunnelling subsequent HTTP messages over this protected connection. It is based on RFC 2817 which describes how to upgrade to TLS from within HTTP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)