What 103 means
An early, interim response that carries hints, usually Link headers saying “you’ll need this stylesheet and font”. The browser can start loading them while the server is still building the real page.
When servers send it
When a server or CDN knows which resources a page needs before the page itself is ready, for example while waiting for a database. The final response, usually 200, follows on the same request.
Why you might see it
- A CDN with Early Hints turned on, replaying the
Linkheaders it saw on earlier responses. - An application that sends 103 deliberately before slow work.
Using it as a developer
- Only hint what the page will definitely use. Hints for unused files waste bandwidth.
- Browsers act on
preloadandpreconnecthints in 103 responses. Chrome, for example, only does so over HTTP/2 and HTTP/3. - Old clients and some proxies mishandle interim responses over HTTP/1.1, which is why many servers only send 103 over HTTP/2 or later.
If you’re visiting a website
- Nothing. It just makes pages load a little faster.
Related codes
- 100 Continue: The server has the request headers and the client should go ahead and send the body.
- 200 OK: The request worked and the response contains the result.
- 304 Not Modified: Your cached copy is still up to date, so use that.
Where it’s defined
103 Early Hints is defined in RFC 8297, section 2. It’s a 1xx code, the informational class: the request was received and is still being processed.
Other 1xx codes
100 Continue · 101 Switching Protocols
Or search them all in the HTTP status code list.