The HTTP 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, 201
Created
is returned instead. If the page should be changed to the newly updated page, the 200
should be used instead.
204 No Content
Specification | Title |
---|---|
RFC 7231, section 6.3.5: 204 No Content | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
Feature | Chrome | Edge | Firefox | Internet Explorer | Opera | Safari | Servo |
---|---|---|---|---|---|---|---|
Basic Support | (Yes) | (Yes) | (Yes) | (Yes) | (Yes) | (Yes) | (Yes) |
Feature | Android | Chrome for Android | Edge Mobile | Firefox for Android | IE Mobile | Opera Mobile | Safari Mobile |
---|---|---|---|---|---|---|---|
Basic Support | (Yes) | (Yes) | (Yes) | (Yes) | (Yes) | (Yes) | (Yes) |
© 2005–2017 Mozilla Developer Network and individual contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/204