102 Processing
A WebDAV interim response meaning the request was received and is still being worked on, sent to stop the client timing out.
At a glance
- Status code
- 102 Processing
- Class
- 1xx, informational, an interim response before the real one
- Defined in
- RFC 2518, removed in RFC 4918
- Cacheable by default
- no
- Response body
- No body. Interim only.
In detail
102 was defined for WebDAV methods that can legitimately take minutes, such as a deep COPY or MOVE across a large collection. The server emits it periodically so the client knows the connection is alive.
It was removed from the revised WebDAV specification and is effectively obsolete. Modern long-running operations return 202 Accepted with a status URL instead, which survives a dropped connection.
Prefer 202 Accepted plus a polling endpoint for anything slow. A held-open connection loses all its state when a proxy times out, and most proxies time out well before a deep COPY finishes.
Examples
HTTP/1.1 102 Processing
HTTP/1.1 207 Multi-Status
Content-Type: application/xmlThings that catch people out
- Many HTTP clients and intermediaries do not forward unknown 1xx codes, so a 102 that never reaches the client is normal rather than broken.
- Sending 102 does not extend a proxy read timeout that counts bytes of the final response.
Try it: HTTP Request Builder
Build a request with any method, headers and body, send it, and read the status line the server returns.
HTTP Request Builder
LOCAL · Browser-OnlyBuild and test HTTP requests with custom headers and body
Authentication
Headers
Generate Code
curl -X GET 'https://api.example.com/endpoint' \
-H 'Content-Type: application/json'Showing a sample URL. Enter your endpoint above to update the snippet.
Related HTTP status codes
All http status codes →202 Accepted
The request was accepted for processing but is not finished, and may still fail. Nothing has necessarily happened yet.
207 Multi-Status
A WebDAV response carrying several independent status codes at once, one for each resource the request touched.
100 Continue
The server has read the request headers, is willing to accept the body, and the client should now send it.
103 Early Hints
An interim response that sends Link headers early so the browser can start preloading assets while the server is still building the real response.
200 OK
The request succeeded. What the body contains depends on the method: a GET returns the resource, a POST returns the result of the action.
201 Created
The request succeeded and created one or more new resources. The Location header carries the URL of the primary one.
Tools for this
- HTTP Request Builder Free online HTTP request builder - build and test HTTP requests with custom headers and body
- HTTP Headers Checker Free online HTTP headers checker - view HTTP response headers for any URL