RFC 9458: Oblivious HTTP
In plain English — editorial summary, not part of the RFC
This document describes Oblivious HTTP, a protocol for forwarding encrypted HTTP messages. Oblivious HTTP allows a client to make multiple requests to an origin server without that server being able to link those requests to the client or to identify the requests as having come from the same client, while placing only limited trust in the nodes used to forward the messages.
Document record
- Document ID
- RFC9458
- Published
- January 2024
- Authors
- M. Thomson; C. A. Wood
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 40
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8828WebRTC IP Address Handling RequirementsCurrent
January 2021
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
- RFC 9464Internet Key Exchange Protocol Version 2 (IKEv2) Configuration for Encrypted DNSCurrent
November 2023
- RFC 9781A Concise Binary Object Representation (CBOR) Tag for Unprotected CBOR Web Token Claims Sets (UCCS)Current
May 2025
- RFC 9788Header Protection for Cryptographically Protected EmailCurrent
August 2025
- RFC 8446The Transport Layer Security (TLS) Protocol Version 1.3Obsoleted
August 2018
- RFC 7170Tunnel Extensible Authentication Protocol (TEAP) Version 1Obsoleted
May 2014
- RFC 7029Extensible Authentication Protocol (EAP) Mutual Cryptographic BindingCurrent
October 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?