RFC 8188: Encrypted Content-Encoding for HTTP

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

Read RFC 8188 on the RFC Editor

Outgoing relationships (15 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 3629: UTF-8, a transformation format of ISO 10646
Normative reference — RFC 7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
Normative reference — RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
Normative reference — RFC 5869: HMAC-based Extract-and-Expand Key Derivation Function (HKDF)
Normative reference — RFC 5116: An Interface and Algorithms for Authenticated Encryption
Informative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Informative reference — RFC 4648: The Base16, Base32, and Base64 Data Encodings
Informative reference — RFC 5652: Cryptographic Message Syntax (CMS)
Informative reference — RFC 4880: OpenPGP Message Format
Informative reference — RFC 7235: Hypertext Transfer Protocol (HTTP/1.1): Authentication
Informative reference — RFC 7516: JSON Web Encryption (JWE)
Informative reference — RFC 7540: Hypertext Transfer Protocol Version 2 (HTTP/2)
Informative reference — RFC 7233: Hypertext Transfer Protocol (HTTP/1.1): Range Requests

Incoming relationships (2 related RFCs)

Normatively referenced by — RFC 8291: Message Encryption for Web Push
Informatively referenced by — RFC 9530: Digest Fields