HTTP 102 Processing
HTTP 102 Processing is a WebDAV interim response that tells the client the server has received the request and is still processing it. It prevents the client from timing out during long-running WebDAV operations that may take minutes to complete. 102 is defined in RFC 2518 (WebDAV) and is rarely used outside of WebDAV-specific implementations.
Quick reference
| Code | 102 |
|---|---|
| Name | Processing |
| Category | 1xx Informational |
| Specification | RFC 2518 §10.1 |
| IANA status | Assigned |
| Cacheable | No — interim response |
| Client action | Continue waiting. The server is processing the request and will send a final response when complete. |
| In-depth guide | HTTP 102 full guide → |
What HTTP 102 means
RFC 2518 defines 102 Processing as 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 and assuming the request was lost. The server sends 102 to say "I'm still working on this" and eventually sends a final response (200, 207, etc.) when processing completes.
102 is specifically designed for WebDAV operations that can take a long time — bulk COPY or MOVE operations on large directory trees, for example. A COPY of thousands of files may take many minutes. Without periodic 102 responses, the HTTP client would time out and cancel the request, even though the server is still processing correctly.
102 is a 1xx informational response — it is interim, not final. Clients must keep the connection open and continue waiting for the final response after receiving a 102.
WebDAV context
WebDAV (Web Distributed Authoring and Versioning) adds file management capabilities to HTTP. Methods like COPY, MOVE, MKCOL, PROPFIND, and LOCK can operate on entire directory trees with potentially hundreds or thousands of resources. When a single WebDAV request processes a large collection, it may run for minutes. 102 provides the mechanism for the server to keep the client informed that processing is ongoing.
RFC 2518 was superseded by RFC 4918, which retains the 102 Processing definition. Note that RFC 8297 introduced 103 Early Hints for a different use case (preloading linked resources) — the two codes are unrelated despite their proximity.
FAQ
What does HTTP 102 Processing mean?
HTTP 102 is an interim WebDAV response meaning the server received the request and is still processing it. The final response will arrive when processing completes. The client should keep waiting.
When does HTTP 102 occur?
Only in WebDAV environments during long-running operations like COPY or MOVE of large collections. In non-WebDAV HTTP applications, 102 is almost never encountered.
How is 102 different from 202?
102 is an interim 1xx response — the connection stays open and the final response arrives on the same connection. 202 Accepted is a final 2xx response meaning the request was accepted for async processing; the client must poll a separate endpoint for the result.
Is 102 used outside of WebDAV?
Rarely. It was defined for WebDAV and has not been widely adopted for other use cases. For general async operation patterns, 202 Accepted with a status endpoint is the standard approach.
Related resources
On this site: HTTP 102 Processing — full guide · HTTP 100 Continue · HTTP 103 Early Hints · HTTP 202 Accepted
Standards: RFC 2518 §10.1 · IANA HTTP Status Code Registry · MDN Web Docs: 102