102
Informational
102 Processing
Server has received the request and is still processing it — no response is ready yet.
Description
The 102 Processing status code is an interim response used to inform the client that the server has accepted the complete request, but has not yet completed it. This prevents the client from timing out while waiting for a long-running request. Defined in WebDAV (RFC 2518), it is rarely used in standard HTTP.
Common Causes
- Long-running WebDAV operations
- Server-side batch processing that takes more than a few seconds
- Misconfigured middleware emitting spurious 102 responses
How to Fix
- Implement progress endpoints or webhooks instead of relying on 102
- Use async job patterns: respond 202 immediately, poll for status
- If you see unexpected 102s, check proxy/middleware configuration
Check your website's HTTP status code
Check now →