HTTP 204 No Content

Success code, RFC 9110, section 15.3.5

What it means

The request worked and there is intentionally nothing to send back. The response has headers but no body.

A real response

This is the request and the answer our test server gave when we asked it to return 204.

GET /c/204 HTTP/1.1
Host: example.com

HTTP/1.1 204 No Content
Date: Sat, 14 Nov 2026 10:00:00 GMT
Content-Type: text/html; charset=utf-8

If you run the site

Use 204 for a save or delete where the page stays as it is. A 204 response must not have a body. Do not use 204 on a normal page: a browser that receives it stays on the current page and shows nothing new, which people take for a broken link.

If you are a visitor

Nothing to fix. If clicking a link did nothing, the link may be answering 204 on purpose or by mistake.

A common mistake

Returning 204 for a GET of a page, so the browser does not navigate.

Registered in the IANA HTTP Status Code Registry as No Content, defined in RFC 9110, section 15.3.5.

This is an independent guide. It is not connected with the IETF, IANA, any browser maker or any company named here. Meanings were checked against the RFC texts on 14 November 2026. Responses shown were recorded on 14 November 2026 from a small test server on the author's own computer.