The HTTP Status Code 205 means that the server successfully processed the client's request, and the server asks that the client reset its document view, and that is not returning any content.
Frequently Asked Questions
What does HTTP 205 Reset Content mean?
HTTP 205 is a 2xx success status code meaning the server successfully processed the request and is instructing the client to reset its document view. Unlike other success codes, 205 carries an explicit directive: the client must clear or refresh its current UI state. No content is returned in the response body.
When does a server return a 205 status code?
A server returns 205 most commonly after a form submission completes successfully and the form fields should be cleared so the user can enter new data. It is designed for data-entry workflows where the client is expected to reset its state between submissions. Outside of that pattern, 205 is rarely used in modern web development.
What is the difference between HTTP 205 and 204?
Both 204 No Content and 205 Reset Content indicate success without returning a response body, but they differ in what they ask the client to do next. A 204 tells the client to continue as-is and take no further action, while a 205 explicitly instructs the client to reset or clear the current document view. If you want a silent background success with no UI change, use 204; if you want the client to wipe its state, use 205.
Does a 205 response include a body?
No. The server must not generate content in a 205 response. RFC 7231 specifies that a 205 response must not include a message body. Any Content-Length header, if present, must be set to 0, and Transfer-Encoding must not be present. The response ends after the headers.
How do browsers handle a 205 response?
Browser handling of 205 is inconsistent in practice. The spec expects the client to reset the document view, but browsers do not automatically clear form fields on receiving a 205. In modern applications, the reset logic is typically implemented in JavaScript on the client side rather than relied upon as a native browser behavior.
How does HTTP 205 differ from HTTP 200?
HTTP 200 OK is the standard success response and typically returns content in the response body. HTTP 205 Reset Content also signals success but returns no body and additionally instructs the client to reset its view. Use 200 when you want to return data to the client; use 205 when the action succeeded, no data needs to be returned, and the client UI should be cleared.
