204 No Content

Estimated reading: 1 minute 690 views

A status response that indicates a request was successful, but the client doesn’t need to or will not navigate away from it’s current page.

This can occur if a link, or action, has a ‘save and continue editing’ function like for a wiki or blog. This also can occur if there is an empty link.

The user should confirm the action they are requesting to determine if the response is appropriate to the request. If not then server support may need to be contacted.

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).


204 No Content


Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
# status.204