205 Reset Content
Tells the user agent to reset the document view which caused the request to be sent.
Usually happens because:
- ☑ Form submission endpoints clearing input
- ☑ Admin panels resetting configuration form
🔍 Quick Checklist:
Meaning
The HTTP 205 Reset Content status code indicates that the server has fulfilled the request and desires that the user agent reset the 'document view' which caused the request to be sent, such as clearing a form.
Root Causes
- Form submission endpoints clearing input boxes for new data entry.
- Admin panels resetting configuration form inputs after saving variables.
| Cause | Frequency |
|---|---|
| Form submission endpoints clearing input | ⭐⭐⭐⭐⭐ |
| Admin panels resetting configuration form | ⭐⭐⭐⭐ |
Common Mistakes
- Returning HTTP 205 but leaving form contents active due to missing client-side state actions.
- Returning body payloads on 205, violating specifications.
How to Fix
Framework-Specific Examples
Returning 205 Reset Content in Express controllers.
app.post('/survey', (req, res) => {
res.status(205).end();
});Server Configuration Examples
Nginx setting proxy header rules to prevent payload inclusions on 205.
# Nginx auto filters headers for 205Prevention
- Use modern fetch frameworks to monitor status and clear client forms dynamically.
- Verify response headers do not indicate content length > 0.
Frequently Asked Questions (FAQ)
Q: How does 205 Reset Content differ from 204 No Content?
While both return no response body, a 205 response explicitly commands the client browser to reset the UI state (like clearing all text fields in a form), whereas 204 leaves the UI exactly as is.
Q: Is 205 Reset Content cached?
No. The 205 Reset Content status code is never cached, as it always indicates a state-changing server transaction.
Q: Do modern browsers clear HTML forms automatically on 205?
Historically yes, browsers cleared forms. In modern SPA environments, you must monitor fetch response statuses and trigger form.reset() explicitly.
Q: Can 205 contain an XML body?
No. According to the HTTP specification, a 205 response must not contain any message body payload whatsoever.