204 No Content success status response code indicates that the request has succeed, but that the client doesn't need to go away from its current page. A 204 response is cacheable by default. An
ETag header is included in such a response.
The common use case is to return
204 as a result of a
PUT request, updating a resource, without changing the current content of the page displayed to the user. If the resource is created,
Created is returned instead. If the page should be changed to the newly updated page, the
200 should be used instead.
204 No Content
|RFC 7231, section 6.3.5: 204 No Content||Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content|
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.
|Feature||Android||Chrome for Android||Edge Mobile||Firefox for Android||IE Mobile||Opera Mobile||Safari Mobile|