Success
204 No Content
The request succeeded and there is deliberately nothing to send back. Common for DELETE calls, form submissions handled in the background and analytics beacons.
Common causes
- Normal API behaviour.
- Occasionally seen when a caching layer strips a body it should have kept.
How to fix it
- Only a problem if you expected content. Check whether a proxy or CDN rule is emptying the response.
See what a site actually returns
Run a live check and read the real status code, headers and timings.
Other status codes
200 OK
201 Created
206 Partial Content
301 Moved Permanently
302 Found
303 See Other
304 Not Modified
307 Temporary Redirect
308 Permanent Redirect
400 Bad Request
401 Unauthorized
403 Forbidden
404 Not Found
405 Method Not Allowed
408 Request Timeout
410 Gone
413 Payload Too Large
418 I'm a Teapot
429 Too Many Requests
451 Unavailable For Legal Reasons
500 Internal Server Error
501 Not Implemented
502 Bad Gateway
503 Service Unavailable
504 Gateway Timeout
507 Insufficient Storage
508 Loop Detected
521 Web Server Is Down
522 Connection Timed Out
523 Origin Is Unreachable
525 SSL Handshake Failed