HTTP 102 Processing vs 428 Precondition Required
HTTP 102 (Processing) is a 1xx Informational response, while 428 (Precondition Required) 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, 428 means that the server requires the request to be conditional (e.g., include If-Match header) to prevent lost updates.
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 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
102 is a 1xx Informational response, while 428 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 428: The server requires the request to be conditional (e.g., include If-Match header) to prevent lost updates.
You encounter 102 when during long-running WebDAV operations.
You encounter 428 when when an API requires optimistic concurrency control via ETags.
When to Use Which
For 102 (Processing): Wait for the final response. This is an interim status to prevent timeouts. For 428 (Precondition Required): Fetch the resource first to get its ETag, then include If-Match in your update request.