More
More
205 Reset Content
The request succeeded and the client should reset the form or view that sent it.
- Code
205- Reason phrase
- Reset Content
- Class
- 2xx Success
- Defined in
- RFC 9110 section 15.3.6
- Cacheable by default
- No
What it means
Success: the request was received, understood and accepted.
Common causes. Rarely used; meant for data entry forms.
What to do. Clear the form.
How clients and crawlers treat it
Caching. Not cacheable by default (RFC 9110 section 15.1 does not list it). A cache stores it only when the response says so with Cache-Control or Expires.
Example response
HTTP/1.1 205 Reset Content Content-Type: text/plain; charset=utf-8 Reset Content
How to send 205
nginx
location /example {
return 205 'Reset Content';
}
PHP
http_response_code(205); echo 'Reset Content'; exit;
Node.js
res.writeHead(205, { 'Content-Type': 'text/plain' });
res.end('Reset Content');
Python (Flask)
# in a view function return 'Reset Content', 205
Change the paths to suit. In nginx, add_header needs always to apply to error responses.
Related codes
- 204No ContentThe request succeeded and there is deliberately no body.
- 206Partial ContentThe server is sending only the part of the file the client asked for in its Range header.
- 203Non-Authoritative InformationThe request succeeded, but a proxy changed the response from what the origin server sent.
- 207Multi-StatusA WebDAV response that carries several separate status codes in its XML body.
All status codes · All 2xx codes
Names and numbers from the IANA HTTP Status Code Registry. Google Search behaviour as documented by Google Search Central.