HTTP 100 Continue

The server has the request headers and the client should go ahead and send the body.

Continue

1xx InformationalStandardRFC 9110, section 15.2.1

The server has the request headers and the client should go ahead and send the body.

Example response
HTTP/1.1 100 Continue

HTTP/1.1 201 Created
Location: /uploads/7f3c
Content-Length: 0

What 100 means

The server has read the request headers, is happy with them, and is waiting for the body. It’s an interim response: the real status (such as 200 or 413) follows once the body has been sent.

When servers send it

Only when the client asks for it with Expect: 100-continue. Clients do that before a large upload, so the server can reject it (with 401 or 413, say) before any bytes of the body are wasted.

Why you might see it

  • A client such as curl sending Expect: 100-continue before a large POST or PUT. curl does this by default for larger uploads.
  • A .NET HttpClient or similar library with the expect-continue behaviour turned on.

Using it as a developer

  • Nothing to fix: it’s working as designed. Your HTTP library handles it and gives you the final status.
  • If uploads stall for about a second, the server may not support 100-continue and the client is waiting before sending anyway. Turn it off with curl -H "Expect:", or the equivalent setting in your client.
  • Servers can reject early by sending the final status straight away instead of 100.

If you’re visiting a website

  • Nothing. You won’t normally see this code in a browser.

Related codes

  • 101 Switching Protocols: The server is switching to the protocol the client asked for in its Upgrade header, usually WebSocket.
  • 103 Early Hints: An early heads-up with Link headers, so the browser can start loading CSS and fonts while the server prepares the real response.
  • 413 Content Too Large: The request body, such as an upload, is bigger than the server will accept.
  • 417 Expectation Failed: The server can’t meet the Expect header in the request.

Where it’s defined

100 Continue is defined in RFC 9110, section 15.2.1. It’s a 1xx code, the informational class: the request was received and is still being processed.

Other 1xx codes

101 Switching Protocols · 103 Early Hints

Or search them all in the HTTP status code list.

Questions people ask

What does HTTP 100 Continue mean?
The server has the request headers and the client should go ahead and send the body.
Why does curl send Expect: 100-continue?
For larger request bodies, curl asks the server first, so it doesn’t upload megabytes only to be told no. If the server never answers, curl waits about a second and sends the body anyway. Add -H "Expect:" to turn it off.
Is 100 Continue the final response?
No. It’s an interim response. The client sends the body and then gets the real status, such as 200, 201 or 413.
↑↓ move↵ openesc close