100 Continue
The server got the request headers and has not rejected them, so the client should go ahead and send the request body.
What 100 Continue means
100 Continue is an interim response. It tells the client that the server has read the request headers and is happy for the body to follow.
Clients ask for it by sending Expect: 100-continue before uploading a large body. If the server would refuse the request anyway (for example with 401 or 413), it can say so before any data is wasted.
Browsers rarely send Expect: 100-continue, so you mostly meet this code with curl and HTTP client libraries.
Headers that go with it
Expect
Example response
HTTP/1.1 100 ContinueHow to check for a 100 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 === 100) {
console.log(res.status, res.statusText);
}Python
import requests
res = requests.get("https://example.com/")
if res.status_code == 100:
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 == 100 {
fmt.Println(res.Status)
}Specification
100 Continue is defined in RFC 9110, section 15.2.1.
Related status codes
- 417
The server cannot meet the requirement in the request's Expect header, which is almost always Expect: 100-continue.
- 101
The server agrees to switch to the different protocol the client asked for in its Upgrade header, such as WebSocket.
- 103
An interim response that sends Link headers early so the browser can preload CSS, fonts or scripts while the server builds the page.