HTTP 205 Reset Content
HTTP 205 Reset Content means the request succeeded and the server is asking the client to reset the document view that caused the request to be sent. In practice, this means the client should clear the form that was submitted. Like 204, there is no response body. Unlike 204, 205 actively requests a UI reset rather than just acknowledging completion.
Quick reference
| Code | 205 |
|---|---|
| Name | Reset Content |
| Category | 2xx Success |
| Specification | RFC 9110 §15.3.6 |
| IANA status | Assigned |
| Cacheable | No — not cacheable |
| Client action | Reset the current form or document view. No response body is included. |
| In-depth guide | HTTP 205 full guide → |
What HTTP 205 means
RFC 9110 defines 205 as indicating that the server has fulfilled the request and desires that the user agent reset the document view, which caused the request to be sent, to its original state as received from the origin server. The response must not include a payload body.
205 is designed for interactive web applications where submitting a form should result in that form being cleared and ready for the next entry. An example: a user submits a feedback form, the server processes it and returns 205, and the browser clears the form fields so the user can submit another entry without manually clearing the fields.
The key distinction from 204 No Content: 204 says "success, do nothing with the UI." 205 says "success, reset the UI to its initial state." In browser behavior, 204 leaves the current page as-is. 205 triggers a form reset equivalent to clicking a reset button on the form.
Browser behavior
Browser handling of 205 is inconsistent in practice. The HTML specification does not have explicit instructions for how browsers should handle 205 responses to form submissions. Some browsers reset the form fields; others treat 205 the same as 204 and do nothing. Single-page applications typically ignore the status code and implement their own form reset logic in JavaScript after receiving a success response.
For reliable form reset behavior in modern web applications, implement the reset in JavaScript explicitly after a successful API response, rather than relying on browser 205 handling. Return 204 from the API and handle the form state in the client.
205 vs 204
FAQ
What does HTTP 205 Reset Content mean?
HTTP 205 means the request succeeded and the server wants the client to reset its current view — typically clearing a form. There is no response body.
How is 205 different from 204?
204 means success with nothing to return. 205 means success and please reset the form or view. In practice, browser support for the reset behavior is inconsistent, so most modern applications use 204 and handle UI reset in JavaScript.
Should I use 205 in my API?
Only if your API consumers are traditional browsers that reliably implement the reset behavior. For REST APIs consumed by JavaScript clients, use 204 and handle the form reset in client code.
Can a 205 response include a body?
No. RFC 9110 forbids a payload body with 205, the same as 204.
Related resources
On this site: HTTP 205 Reset Content — full guide · HTTP 204 No Content · HTTP 200 OK · All 2xx success codes
Standards: RFC 9110 §15.3.6 · IANA HTTP Status Code Registry · MDN Web Docs: 205