204 No Content
The HTTP 204 No Content success status response code
indicates that a request has succeeded, but that the client doesn't need to navigate away
from its current page.
This might be used, for example, when implementing "save and continue editing" functionality for a wiki site.
In this case a PUT request would be used to save the page, and the 204 No Content response
would be sent to indicate that the editor should not be replaced by some other page.
A 204 response is cacheable by default (an ETag header is included in such a response).
Status
204 No ContentSpecifications
| Specification | Title |
|---|---|
| RFC 7231, section 6.3.5: 204 No Content | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
Browser compatibility
BCD tables only load in the browser
The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.
Compatibility notes
- Although this status code is intended to describe a response with no body, servers
may erroneously include data following the headers. The protocol allows user agents to
vary in how they process such responses (discussion regarding this
specification text can be found here). This is observable in persistent
connections, where the invalid body may include a distinct response to a subsequent
request.
Apple Safari rejects any such data. Google Chrome and Microsoft Edge discard up to four invalid bytes preceding a valid response. Firefox tolerates in excess of a kilobyte of invalid data preceding a valid response.