--- title: "205 Reset Content — what it means and how to fix it" description: "The request succeeded and the client should clear the form that sent it. What causes an HTTP 205, what to try as a visitor, and what to check if it is your own site." url: https://atoneplace.net/error/205/ site: "At One Place" --- # HTTP 205 — Reset Content **HTTP 205: Reset Content** The request succeeded and the client should clear the form that sent it. ## What 205 actually means Like 204, but with an extra instruction: reset the document view — in practice, empty the form fields so the user can enter another entry. It was designed for data-entry screens where someone submits record after record. Modern applications handle this in JavaScript instead, so 205 is almost never seen. ## Common causes - A data-entry form submission designed for repeated entries - A legacy application following the original form-submission model ## If you're just trying to view the page 1. Nothing — your submission was accepted and the form has been cleared for the next one 2. If the form did not clear, your browser simply ignored the instruction; the data was still saved ## If it's your site 1. Very few clients actually implement the reset behaviour; do not rely on it 2. Use 204 plus explicit client-side handling if you need the form cleared 3. Like 204, a 205 must not carry a body ## Reference - **Status code:** 205 - **Reason phrase:** Reset Content - **Category:** 2xx — Success - **Defined in:** RFC 9110 §15.3.6 ## Common questions ### What does HTTP 205 mean? The request succeeded and the client should clear the form that sent it. Like 204, but with an extra instruction: reset the document view — in practice, empty the form fields so the user can enter another entry. It was designed for data-entry screens where someone submits record after record. ### How do I fix a 205 error? Nothing — your submission was accepted and the form has been cleared for the next one ### Is 205 a client error or a server error? 205 is in the 2xx range, which means success. It is not an error at all. ## Related pages - [200 OK](https://atoneplace.net/error/200/) - [204 No Content](https://atoneplace.net/error/204/) - [201 Created](https://atoneplace.net/error/201/) - [206 Partial Content](https://atoneplace.net/error/206/) - [202 Accepted](https://atoneplace.net/error/202/) - [207 Multi-Status](https://atoneplace.net/error/207/) - [203 Non-Authoritative Information](https://atoneplace.net/error/203/) - [208 Already Reported](https://atoneplace.net/error/208/) - [226 IM Used](https://atoneplace.net/error/226/) ## Sources - Hypertext Transfer Protocol (HTTP) Status Code Registry — IANA (https://www.iana.org/assignments/http-status-codes/) - RFC 9110: HTTP Semantics — IETF (https://www.rfc-editor.org/rfc/rfc9110.html)