- Home
- Tools
- Developer Tools
- HTTP Status Codes
- 100 Continue
100 Continue
An interim reply: the server has read the request headers and tells the client to go ahead and send the body.
- Class
- 1xx Informational. An interim answer: the request has arrived and the final response is still to come.
- Defined in
- RFC 9110
What it looks like
PUT /upload HTTP/1.1 Content-Length: 104857600 Expect: 100-continue HTTP/1.1 100 Continue
When a server sends it
Only when the client asked for it. A client that is about to send a large body can put Expect: 100-continue in its headers and wait. The server looks at the headers alone and answers 100 Continue if it is willing to take the body, or a final status such as 401 or 413 if it is not. An upload that would have been refused is then never sent.
What to do with it
Nothing, in most cases. HTTP libraries deal with it on their own, and the final response follows on the same connection.
The curl command adds the Expect header by itself for larger uploads. When a server or a proxy on the way doesn't answer it, curl waits a second and sends the body anyway. Its option -H "Expect:" switches the header off.
Not to be confused with
| 417 Expectation Failed | The server can't or won't deal with the Expect header at all. |
|---|---|
| 103 Early Hints | Also an interim reply, but about what the browser can load in advance. |
All codes are on the list of HTTP status codes, which can be searched by number and by word.