HTTP 102 Processing vs 202 Accepted
HTTP 102 (Processing) is a 1xx Informational response, while 202 (Accepted) is a 2xx Success 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, 202 means that the request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon.
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 request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon.
When You See It
For async operations like batch jobs, email sending, or background tasks that take time to complete.
How to Fix
Poll the provided status URL or wait for a callback/webhook.
Key Differences
102 is a 1xx Informational response, while 202 is a 2xx Success 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 202: The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon.
You encounter 102 when during long-running WebDAV operations.
You encounter 202 when for async operations like batch jobs, email sending, or background tasks that take time to complete.
When to Use Which
For 102 (Processing): Wait for the final response. This is an interim status to prevent timeouts. For 202 (Accepted): Poll the provided status URL or wait for a callback/webhook.