HTTP 205 Reset Content
Updated Free mock REST & WebSocket APIs
HTTP 205 Reset Content — The request succeeded and the client should reset the document view (e.g. clear a form).
- Class
- 2xx Success
- Defined in
- RFC 9110 §15.3.6
- Official
- Yes (IANA registry)
- Cacheable by default
- No (unless Cache-Control/Expires say so)
Try it: get a real 205 response
Our test endpoint answers every request with 205 Reset Content.
curl -i https://mockfox.dev/api/status/205Use it in tests, health-check monitors or to see how your client handles a 205. Add ?delay=2000 to slow it down.
What does HTTP 205 mean?
Intended for data-entry interfaces: after a successful submission the user agent should clear the form so another entry can be typed. Like 204 it must not include a body. Browsers don't actually implement the reset behaviour, so you'll rarely see it outside APIs.
Handling 205
- Visitors: Nothing to fix — this is a success status.
- Developers: Make sure clients handle this status as success (
response.okis true for 200–299) and know whether to expect a body.
Example 205 response
HTTP/1.1 205 Reset Content Date: Sun, 18 Oct 2026 10:00:00 GMT
2xx Success: The request was received, understood and accepted. See the full list of HTTP status codes.
Related status codes
- 204 No ContentThe request succeeded and there is intentionally no response body.
- 200 OKThe request succeeded and the response contains the result.
Related tools
Frequently asked questions
What does HTTP 205 Reset Content mean?
The request succeeded and the client should reset the document view (e.g. clear a form).
Is 205 an error?
No. 205 is a success status.
Where is 205 defined?
In RFC 9110 §15.3.6. It's listed in the IANA HTTP Status Code Registry.
How can I test how my app handles a 205?
Call https://mockfox.dev/api/status/205 — it responds with 205 to any method, with CORS enabled. Add ?delay=2000 to simulate a slow response.