Free tools

HTTP 204 No Content

The request succeeded and there is no body. Free reference, no signup.

204 No Content

MeaningThe request succeeded and there is no body.
WhenA delete, update, or save finished and the server has nothing to return.
CausesDELETE and some PUT or POST handlers.
FixNo fix. Clients should not try to parse a body.
RetryDo not retry unless the action is idempotent.
Alert?No. An empty success is still a success.

Runs in your browser. Nothing you enter is stored.

Most 204s are not an incident

An empty success is still a success.

curl -sS -X POST https://api.trigv.com/v1/events \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $TRIGV_API_KEY" \
  -d '{"channel":"ops","title":"HTTP 204","level":"warning"}'
Get an API key All status codes

How to use it

  1. Read what 204 means before changing a retry loop.
  2. Check the common causes against the response body and the server log.
  3. Follow the retry note. Retrying a 400 with the same body will fail again.
  4. Alert only in the cases the verdict describes.

About this tool

HTTP 204 No Content means The request succeeded and there is no body. Servers send it when A delete, update, or save finished and the server has nothing to return.

Common causes: DELETE and some PUT or POST handlers. The practical fix is: No fix. Clients should not try to parse a body.

Retry: Do not retry unless the action is idempotent.

Alert on it? No. An empty success is still a success.

Trigv is a push for the moment a status starts mattering, not a log of every response. If the code is one you should hear about, the snippet posts a single event with level error or warning. The status page itself does not call your API.

Questions

What is HTTP 204?

The request succeeded and there is no body.

Should the client retry?

Do not retry unless the action is idempotent.

Should I alert on it?

No. An empty success is still a success.

How is this different from reading the spec?

The page adds a plain retry note and an alert verdict for people running the service, not only for people parsing the response.

200 OK The request succeeded. 201 Created The request succeeded and created a resource. 202 Accepted The server accepted the request and will finish it later. Cron Job Alert Script Wrap a command so a failed, slow, or finished cron job sends a Trigv alert.