HTTP 102 Processing vs 425 Too Early
HTTP 102 (Processing) is a 1xx Informational response, while 425 (Too Early) is a 4xx Client Error response. 102 indicates that the server has received and is processing the request, but no response is available yet. Prevents the client from timing out. In contrast, 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 has received and is processing the request, but no response is available yet. Prevents the client from timing out.
When You See It
During long-running WebDAV operations.
How to Fix
Wait for the final response. This is an interim status to prevent timeouts.
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
102 is a 1xx Informational response, while 425 is a 4xx Client Error response.
HTTP 102: The server has received and is processing the request, but no response is available yet. Prevents the client from timing out.
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 102 when during long-running WebDAV operations.
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 102 (Processing): Wait for the final response. This is an interim status to prevent timeouts. For 425 (Too Early): Retry the request after the TLS handshake completes.