RFC 9729: The Concealed HTTP Authentication Scheme
In plain English — editorial summary, not part of the RFC
Most HTTP authentication schemes are probeable in the sense that it is possible for an unauthenticated client to probe whether an origin serves resources that require authentication. It is possible for an origin to hide the fact that it requires authentication by not generating Unauthorized status codes; however, that only works with non-cryptographic authentication schemes: cryptographic signatures require a fresh nonce to be signed. Prior to this document, there was no existing way for the origin to share such a nonce without exposing the fact that it serves resources that require authentication. This document defines a new non-probeable cryptographic authentication scheme.
Document record
- Document ID
- RFC9729
- Published
- February 2025
- Authors
- D. Schinazi; D. Oliver; J. Hoyland
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9484Proxying IP in HTTPCurrent
October 2023
- RFC 9298Proxying UDP in HTTPUpdated
August 2022
- RFC 9297HTTP Datagrams and the Capsule ProtocolCurrent
August 2022
- RFC 9000QUIC: A UDP-Based Multiplexed and Secure TransportCurrent
May 2021
- RFC 8999Version-Independent Properties of QUICUpdated
May 2021
- RFC 9019A Firmware Update Architecture for Internet of ThingsCurrent
April 2021
- RFC 8994An Autonomic Control Plane (ACP)Current
May 2021
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
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?