204 No Content

What it means

Common for DELETE requests and for saves where the client does not need data back.

Common causes

• An update or delete succeeded with nothing to return.

How to fix it

1. No fix needed. Do not expect a body when parsing a 204 response.

Example response

HTTP/1.1 204 No Content
ETag: "v3"

Worked example

A DELETE request succeeds and returns 204 No Content. The client can remove the item from its current view, but it should not attempt to parse a response body because this status has none. For a successful update, the client can rely on the status and any returned headers, then refresh the resource later if it needs a representation.

How to read this response

1. Find the status line in your browser's Network panel, API client, or server access log.
2. Read the response body and headers shown above; headers such as Location, Allow, Retry-After, and WWW-Authenticate explain the next step.
3. Use the code's class to orient your diagnosis: informational, successful, redirected, request-related, or server-side.

How to check a status code

Enter a URL in the HTTP Status Checker to see its status code, every redirect hop, and response time. For redirect-heavy pages, the Website Speed Test shows how much time redirects add.

Frequently asked questions

What it means: HTTP 204

204 No Content: The request succeeded and there is no response body.

Common causes: 204

An update or delete succeeded with nothing to return.

How to fix it: HTTP 204

No fix needed. Do not expect a body when parsing a 204 response.

Tools