204 No Content

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

Browser compatibility

No compatibility data found. Please contribute data for "204 No Content" to the MDN compatibility data repository.

See also

Document Tags and Contributors

 Contributors to this page: fscholz, teoli
 Last updated by: fscholz,