Visual RFC.
ALL RFCs / RFC 8297
Read the RFC ↗
RFC 8297 / EARLY PREPARATION

Prepare while the final response is pending

01

HTTP 103 Early Hints lets a server send likely response fields before it finishes preparing the final answer. A client can start useful work sooner.

RFC 8297 · § 1EXAMPLE
4 / 4
Prepare while the final response is pendingA fictional client sends GET page to the origin. The origin sends informational103 with a style preload Link while the final page is pending. The client optionally sends a separate style resource GET to a same-origin asset endpoint; this is not a pushed body inside103. Finally the origin returns200 and the page body, completing the original request. The chosen preload is speculative, not mandatory and not proof of a speedup.Prepare early; keep the original request pendingClientOriginHTTP/1.1 200 OKActual final fields + page bodyOriginal request completes nowPreload work might or might not help
04
Process the eventual final response.

The final response completes the original request. The hint was only preparation; it did not guarantee this status, these fields or a performance benefit.

Source for this drawing: RFC 8297 · Read RFC section 1 ↗

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
New to this? Start hereA quick picture + helpful background

A message needs an address.

Think of a packet as a small addressed envelope. Devices pass it onward; transport protocols decide what delivery promises an application gets.

Helpful first, if these ideas are unfamiliar

These pictures are analogies to help you learn. The linked RFC explains the actual rules.

Terms in this drawing
Informational response
An interim 1xx response sent before the final response; it does not finish this request.
Speculative
Work begun before knowing it will be needed; it can turn out to be unnecessary.
Preload
A link relation hinting that a resource may be useful soon. Actual client resource policy still applies.
Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

KEY POINT

An early hint does not complete the original request.

  • The 103 response is informational: the original request still needs its final response.
  • A client can speculatively evaluate a Link field with rel=preload and start fetching the resource while it waits. This is an optimization, not mandatory fetching.
  • Hints differ from server push: in this example the client chooses to send an ordinary asset request. No asset body is pushed inside the 103.
DETAILS

The server may be waiting for upstream work or a database result. The illustration uses fictional HTTP/1.1 message labels and a same-origin style resource, but does not claim browser/network traces or a measured speedup. The immutable December 2017 memo says Experimental; current RFC Editor metadata lists Proposed Standard. It is not a new HTTP version.

Read the RFC section ↗

All chapters in RFC 8297

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗