Encrypted Content-Encoding for HTTP

Document Type Replaced Internet-Draft (individual)
Author Martin Thomson 
Last updated 2015-10-19
Replaces draft-nottingham-http-encryption-encoding
Replaced by RFC 8188
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
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
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This memo introduces a content-coding for HTTP that allows message payloads to be encrypted.


Martin Thomson (martin.thomson@gmail.com)

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