HTTP 102 Processing
Updated Free mock REST & WebSocket APIs
HTTP 102 Processing — An interim WebDAV response saying the server is still working on a long request.
- Class
- 1xx Informational
- Defined in
- RFC 2518 (WebDAV)
- Official
- Registered, but deprecated/reserved
What does HTTP 102 mean?
Defined by the original WebDAV spec to stop clients timing out during slow operations such as a recursive COPY. It was dropped from RFC 4918 and is rarely sent today; most servers simply take longer or use 202 Accepted with a status URL.
Handling 102
- Visitors: You'll never see this in a browser — it's an interim response handled automatically before the final status.
- Developers: Your HTTP client handles 1xx responses internally; fetch() never exposes them. Inspect them with
curl -vor a packet capture.
Example 102 response
HTTP/1.1 102 Processing
1xx Informational: Interim responses: the request was received and processing continues. See the full list of HTTP status codes.
Related status codes
- 202 AcceptedThe request was accepted for processing, but the processing hasn't finished.
- 207 Multi-StatusA WebDAV response whose XML body holds a separate status for each of several resources.
- 504 Gateway TimeoutA gateway or proxy didn't get a response from the upstream server in time.
Related tools
Frequently asked questions
What does HTTP 102 Processing mean?
An interim WebDAV response saying the server is still working on a long request.
Is 102 an error?
No. 102 is an informational interim response; a final status follows.
Where is 102 defined?
In RFC 2518 (WebDAV). It's listed in the IANA HTTP Status Code Registry, but marked deprecated or reserved.