HTTP 2xx
204 No Content
The request succeeded but there is no content to return.
What causes it
- A successful DELETE, or a PUT that returns no body.
How to fix it
Expected. No action needed.
Example response
A typical raw HTTP response a client receives for a 204, with the headers this code is defined around.
HTTP/1.1 204 No ContentRelated codes
200Common
OKThe request succeeded. This is the normal response for a healthy page or API.201
CreatedThe request succeeded and a new resource was created as a result.202
AcceptedThe request was accepted for processing, but the processing has not finished. Common for async or queued work.206
Partial ContentThe server is delivering only part of the resource, in response to a Range request.Know before your visitors do.
Sentinel checks your site around the clock from multiple regions and alerts you the moment it starts returning a 2xx error, so you can fix it before it costs you.