HTTP 100 Continue — What It Means
What HTTP status code 100 Continue means, when servers return it, and how to handle it correctly.
Published September 22, 2026
HTTP 100 Continue is an interim response telling the client that the request headers were accepted and it should go ahead and send the body.
What it means
Clients send 'Expect: 100-continue' before a large upload so the server can reject it early (wrong auth or size) without wasting bandwidth sending the body.
Common causes: Large POST or PUT bodies; Clients using Expect: 100-continue; Proxies forwarding the handshake.
On the wire
Practical examples
Test it from the shell
curl -i https://example.com/path # look for HTTP 100Handling 100 in code or config
curl -H 'Expect: 100-continue' -T big.bin https://example.com/uploadHow to fix it
Let the HTTP library handle it automatically; Disable Expect: 100-continue if a proxy mishandles it; Check server and proxy support.
1. Reproduce: curl -i <url>
2. Confirm the status is 100
3. Apply the fix above and re-testCommon mistakes
- Treating this as an error when it is a normal part of HTTP.
- Disable Expect: 100-continue if a proxy mishandles it
- Ignoring the response headers that explain the details.
Key takeaways
- 100 means Continue.
- HTTP 100 Continue is an interim response telling the client that the request headers were accepted and it should go ahead and send the body.
- Read the response headers and logs for the exact cause.
FAQ
Do I need to handle 100 manually?
No. HTTP clients and servers process it transparently; the final response is what you see.
Is 100 a client or server error?
It is a success status code, in the 1xx class.