205
Success
205 Reset Content: Clearing the View After a Successful Request
✦ The Golden Answer: The 205 Reset Content status code is a success response that tells the client to reset the document view — typically clearing form fields, resetting the UI state, or refreshing the current view. It is particularly useful after form submissions to prevent double‑submission and give users a clean slate.
When to Use 205 Reset Content
- After POST form submissions – when you want to clear the form and show a success message.
- After PUT/PATCH updates – when the UI should revert to a default state.
- In single‑page applications (SPAs) – to reset the local state without reloading the page.
- After completing a multi‑step wizard – to return to the initial step.
Example Flow: Form Submission
| Step | Direction | HTTP Message |
|---|---|---|
| 1 | Client → Server | POST /api/contact HTTP/1.1 |
| 2 | Server → Client | HTTP/1.1 205 Reset Content |
| 3 | Client (browser) | Clears the form fields, resets the view, and optionally displays a success toast. |
Required Headers
Like 204, a 205 response must have:
Content-Length: 0– no response body.- No
Content-Typeheader (or omitted). - Optionally, you can include
Cache-Controlor other metadata headers, but they are not required.
HTTP/1.1 205 Reset Content
Content-Length: 0
How Browsers Handle 205
Modern browsers interpret 205 as:
- A successful response with no body.
- A signal to reset the current document view.
- For forms, this usually means clearing all input fields, checkboxes, and textareas.
- No page reload or navigation occurs — the user stays on the same page.
Difference Between 204 and 205
| Status | Meaning | Client Action |
|---|---|---|
| 204 No Content | Success, nothing to return | Nothing specific; client may stay on same view. |
| 205 Reset Content | Success, clear the view | Reset the form/UI to its initial state. |
When Not to Use 205
- If you need to return data – use 200 OK with a body.
- If you don't want to clear the view – use 204 No Content instead.
- If the request failed – use 400 or 500 series.
Frequently Asked Questions
Is 205 Reset Content supported by all browsers?
Yes, all modern browsers (Chrome, Firefox, Safari, Edge) support 205 and will reset form fields and the view as expected. However, older browsers may treat it as 204 and not clear anything.
Can I use 205 with AJAX/fetch requests?
Yes, but the browser's automatic view reset only happens for full‑page navigations (e.g., form submissions). For AJAX, you need to manually reset the UI in your JavaScript code after receiving the 205.
Should I use 205 or 303 (See Other) after a POST?
It depends. 303 See Other redirects the client to a different URL (e.g., a thank‑you page) and prevents resubmission on refresh. 205 Reset Content keeps the client on the same page but clears the form. Choose 303 if you want to navigate away, 205 if you want to stay on the same page.