103 Early Hints
An interim response that sends Link headers early so the browser can preload CSS, fonts or scripts while the server builds the page.
What 103 Early Hints means
Defined in RFC 8297. While the server is still working on the final response (querying a database, rendering HTML), it can send 103 with headers like Link: </style.css>; rel=preload so the browser starts fetching those files sooner.
The hints are only hints. The final response still has to send its own headers, and clients that do not understand 103 are expected to ignore it and wait for the real answer.
Headers that go with it
Link
Example response
HTTP/1.1 103 Early HintsHow to check for a 103 response
cURL
# Print only the status code
curl -s -o /dev/null -w "%{http_code}\n" https://example.com/JavaScript (Node.js)
const res = await fetch("https://example.com/");
if (res.status === 103) {
console.log(res.status, res.statusText);
}Python
import requests
res = requests.get("https://example.com/")
if res.status_code == 103:
print(res.status_code, res.reason)Go
res, err := http.Get("https://example.com/")
if err != nil {
log.Fatal(err)
}
defer res.Body.Close()
if res.StatusCode == 103 {
fmt.Println(res.Status)
}Specification
103 Early Hints is defined in RFC 8297.
Related status codes
- 200
The request worked. The response body holds the result, such as the page, file or JSON data the client asked for.
- 100
The server got the request headers and has not rejected them, so the client should go ahead and send the request body.
- 304
The cached copy is still valid, so the server sends no body and the client loads the resource from its own cache.