HTTP 422 Unprocessable Content vs 425 Too Early
Both HTTP 422 (Unprocessable Content) and 425 (Too Early) belong to the 4xx Client Error category. 422 indicates that the server understands the content type and syntax, but was unable to process the contained instructions. Common in API validation errors. Meanwhile, 425 means that the server is unwilling to risk processing a request that might be replayed. Used with TLS 1.3 early data (0-RTT).
Description
The server understands the content type and syntax, but was unable to process the contained instructions. Common in API validation errors.
When You See It
When form validation fails — correct syntax but invalid data (e.g., email format wrong, date in the past).
How to Fix
Check the response body for specific validation errors and correct the input data.
Description
The server is unwilling to risk processing a request that might be replayed. Used with TLS 1.3 early data (0-RTT).
When You See It
When a server rejects a request sent as TLS 1.3 early data due to replay risk.
How to Fix
Retry the request after the TLS handshake completes.
Key Differences
HTTP 422: The server understands the content type and syntax, but was unable to process the contained instructions. Common in API validation errors.
HTTP 425: The server is unwilling to risk processing a request that might be replayed. Used with TLS 1.3 early data (0-RTT).
You encounter 422 when when form validation fails — correct syntax but invalid data (e.g., email format wrong, date in the past).
You encounter 425 when when a server rejects a request sent as TLS 1.3 early data due to replay risk.
When to Use Which
For 422 (Unprocessable Content): Check the response body for specific validation errors and correct the input data. For 425 (Too Early): Retry the request after the TLS handshake completes.