HTTP 205 Reset Content vs 428 Precondition Required
HTTP 205 (Reset Content) is a 2xx Success response, while 428 (Precondition Required) is a 4xx Client Error response. 205 indicates that the server fulfilled the request and the client should reset the document view (e.g., clear a form). In contrast, 428 means that the server requires the request to be conditional (e.g., include If-Match header) to prevent lost updates.
Description
The server fulfilled the request and the client should reset the document view (e.g., clear a form).
When You See It
After form submissions where the server wants the client to reset the form for new input.
How to Fix
The client should clear the form or reset the view. Rarely used in practice.
Description
The server requires the request to be conditional (e.g., include If-Match header) to prevent lost updates.
When You See It
When an API requires optimistic concurrency control via ETags.
How to Fix
Fetch the resource first to get its ETag, then include If-Match in your update request.
Key Differences
205 is a 2xx Success response, while 428 is a 4xx Client Error response.
HTTP 205: The server fulfilled the request and the client should reset the document view (e.g., clear a form).
HTTP 428: The server requires the request to be conditional (e.g., include If-Match header) to prevent lost updates.
You encounter 205 when after form submissions where the server wants the client to reset the form for new input.
You encounter 428 when when an API requires optimistic concurrency control via ETags.
When to Use Which
For 205 (Reset Content): The client should clear the form or reset the view. Rarely used in practice. For 428 (Precondition Required): Fetch the resource first to get its ETag, then include If-Match in your update request.