Skip to the content

103 Early Hints

An interim reply with Link headers, sent ahead of the real response so the browser can start loading what the page will need.

Class
1xx Informational. An interim answer: the request has arrived and the final response is still to come.
Defined in
RFC 8297

What it looks like

HTTP/1.1 103 Early Hints
Link: </style.css>; rel=preload; as=style
Link: <https://cdn.example.com>; rel=preconnect

HTTP/1.1 200 OK
Content-Type: text/html

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

When a server sends it

While the server is still putting the page together, running queries and rendering a template, it often knows already which stylesheet, script or font the page will ask for. It sends those as Link headers in a 103, and the real response, a 200 for example, follows when it is ready.

What to do with it

Nothing has to be done with the 103 itself. Browsers that support it start preloading, or open connections to the servers that are named. A client that doesn't know the code ignores it.

If you run the site: it only helps when the server needs noticeable time to produce the page, and most browsers only accept early hints over HTTP/2 and HTTP/3, on the request for the page itself. The hints have to match what the final response really uses, or the browser fetches files for nothing.

Not to be confused with

100 ContinueAlso interim, but about the request body: the client may send it.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12