RFC 8942: HTTP Client Hints
In plain English — editorial summary, not part of the RFC
HTTP defines proactive content negotiation to allow servers to select the appropriate response for a given request, based upon the user agent's characteristics, as expressed in request headers. In practice, user agents are often unwilling to send those request headers, because it is not clear whether they will be used, and sending them impacts both performance and privacy. This document defines an Accept-CH response header that servers can use to advertise their use of request headers for proactive content negotiation, along with a set of guidelines for the creation of such headers, colloquially known as "Client Hints."
Document record
- Document ID
- RFC8942
- Published
- February 2021
- Authors
- I. Grigorik; Y. Weiss
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- wit
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8941Structured Field Values for HTTPObsoleted
February 2021
- RFC 8961Requirements for Time-Based Loss DetectionCurrent
November 2020
- RFC 8923A Minimal Set of Transport Services for End SystemsCurrent
October 2020
- RFC 8922A Survey of the Interaction between Security Protocols and Transport ServicesCurrent
October 2020
- RFC 8974Extended Tokens and Stateless Clients in the Constrained Application Protocol (CoAP)Current
January 2021
- RFC 8985The RACK-TLP Loss Detection Algorithm for TCPCurrent
February 2021
- RFC 8899Packetization Layer Path MTU Discovery for Datagram TransportsCurrent
September 2020
- RFC 8888RTP Control Protocol (RTCP) Feedback for Congestion ControlCurrent
January 2021
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?