HTTP 100 Continue vs 201 Created
HTTP 100 (Continue) is a 1xx Informational response, while 201 (Created) is a 2xx Success response. 100 indicates that the server has received the request headers and the client should proceed to send the request body. This lets the client know it can continue with the request or abort if the headers were rejected. In contrast, 201 means that the request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
Description
The server has received the request headers and the client should proceed to send the request body. This lets the client know it can continue with the request or abort if the headers were rejected.
When You See It
When a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.
How to Fix
This is an interim response — no fix needed. The client should continue sending the request body.
Description
The request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
When You See It
After successfully creating a new user, post, order, or other resource via a REST API.
How to Fix
No fix needed. Check the Location header for the URL of the new resource.
Key Differences
100 is a 1xx Informational response, while 201 is a 2xx Success response.
HTTP 100: The server has received the request headers and the client should proceed to send the request body. This lets the client know it can continue with the request or abort if the headers were rejected.
HTTP 201: The request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
You encounter 100 when when a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.
You encounter 201 when after successfully creating a new user, post, order, or other resource via a REST API.
When to Use Which
For 100 (Continue): This is an interim response — no fix needed. The client should continue sending the request body. For 201 (Created): No fix needed. Check the Location header for the URL of the new resource.