RFC 8297: An HTTP Status Code for Indicating Hints
In plain English — editorial summary, not part of the RFC
This memo introduces an informational HTTP status code that can be used to convey hints that help a client make preparations for processing the final response.
Document record
- Document ID
- RFC8297
- Published
- December 2017
- Authors
- K. Oku
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8291Message Encryption for Web PushCurrent
November 2017
- RFC 8171Transparent Interconnection of Lots of Links (TRILL): Edge Directory Assistance MechanismsCurrent
June 2017
- RFC 8030Generic Event Delivery Using HTTP PushCurrent
December 2016
- RFC 8599Push Notification with the Session Initiation Protocol (SIP)Current
May 2019
- RFC 8765DNS Push NotificationsCurrent
June 2020
- RFC 7067Directory Assistance Problem and High-Level Design ProposalCurrent
November 2013
- RFC 8303On the Usage of Transport Features Provided by IETF Transport ProtocolsCurrent
February 2018
- RFC 8304Transport Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP-Lite)Current
February 2018
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?