Encrypted Content-Encoding for HTTP
draft-thomson-http-encryption-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Martin Thomson | ||
| Last updated | 2015-10-19 | ||
| Replaces | draft-nottingham-http-encryption-encoding | ||
| Replaced by | RFC 8188 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-httpbis-encryption-encoding | |
| 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 memo introduces a content-coding for HTTP that allows message payloads to be encrypted.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)