Technology and engineering · 2017
RFC 8188: Encrypted Content-Encoding for HTTP
by M. Thomson
This memo introduces a content coding for HTTP that allows message payloads to be encrypted.
Anyone can see what's on the shelves. Open a book with a free account, and stay in touch with its book club.
- First published
- 2017
- Status
- Proposed Standard
- Pages
- 16
- Copyright
- ✓ Free to read · Copied in full, as published
Where it comes from
RFC Editor · IETF Datatracker · IETF Trust Legal Provisions
Copied in full and unchanged from the RFC Editor, with the RFC's own notices. © IETF Trust and the persons identified as the document authors. The IETF Trust allows copying and distributing an RFC in full and without modification, so Micwyn shows it exactly as published and makes no study guide, audio or other version of it.
Discuss a passage
Select any passage in the reader and press Discuss to talk about it in public.
Ask Micwyn about this book
Try asking
If you like this one
RFC 5573: Asynchronous Channels for the Blocks Extensible Exchange Protocol (BEEP)RFC 8291: Message Encryption for Web PushRFC 8448: Example Handshake Traces for TLS 1.3RFC 8449: Record Size Limit Extension for TLSRFC 8833: Application-Layer Protocol Negotiation (ALPN) for WebRTCRFC 8999: Version-Independent Properties of QUICRFC 9287: Greasing the QUIC BitFive Weeks in a BalloonRecords of a Family of EngineersMen of Invention and Industry