HTTP 205 — Reset Content
HTTP 205 tells the browser to clear the form or document view that produced the request. The classic case is a form POST that succeeded and should now reset so the user can enter fresh input.
When 205 shows up
- Form submission endpoints asking the browser to blank the form afterwards.
- Multi-entry workflows where each submission starts a clean slate.
Mocking a 205 response
A response with this status can be faked end to end with a local mock rule — no backend changes needed. The configuration below mirrors the rule fields the ApiSimul editor uses (method, path, status, delay in milliseconds, response body):
{
"method": "GET",
"path": "/forms/feedback",
"status": 205,
"delay": 220,
"enabled": true,
"body": null
}Dynamic placeholders such as {{random.name}}, {{string.uuid}} or {{number.int 1 100}} can appear inside the body to vary each response, which keeps client-side list rendering and retry logic honest during development.
Frequently asked questions
What does HTTP 205 mean?
The request succeeded and the sender should reset the view that initiated it. Like 204 it carries no body, but it additionally instructs the client to reset its state.
How can I test a 205 response without a real backend?
Define a mock rule with the method and path your client requests and set the status to 205. The example configuration above returns this response after the listed delay, so the client exercises its 205 handling exactly as it would against a live server.
Related status codes
Need the response in your own project? Spin up rules for any status with the ApiSimul mock server, or browse every status code page.