Reset Content

Server perspective

Use 205 when the request succeeded and the user agent should reset the document view that submitted it.

When to use

• •Return 205 for data-entry workflows where the next sensible step is a clean input state
• •Use it sparingly when the reset behavior is part of the product contract
• •Form submissions that should clear the form after success
• •Data entry interfaces that need to be reset
• •Survey or questionnaire submissions
• •Content creation forms that should be cleared after submission
• •Bulk data input scenarios where users repeat the same action

How to respond

• •Do not include a response body
• •Make sure the client experience is designed to handle the reset intentionally

Headers to consider

• •No status-specific header is required for the reset signal.

Response body

• •Do not include a response body in a 205 response

Server-side pitfalls

• •Do not depend on generic browsers magically clearing complex application UI for you
• •Use 204 instead when success is enough and reset behavior is not part of the contract
• •When you don't want the client to reset anything (use 204 No Content)
• •When returning data that should be displayed (use 200 OK)
• •For API endpoints that don't involve forms (use 204 No Content)
• •When the form should retain its values after submission

Examples