102 Processing

WebDAV interim response telling the client the server is still working on a long request.

102 at a glance

Code: 102
Name: Processing
Class: 1xx Informational
Status: IANA-registered standard code
Defined in: RFC 2518, Section 10.1
Cacheable by default: No. Interim (1xx) responses are never stored by caches.

What 102 means

102 Processing was defined by WebDAV (RFC 2518) so a server handling a slow request, such as a recursive COPY or DELETE on a large collection, could keep the client from timing out. RFC 4918, which replaced RFC 2518, dropped it, but the code remains registered. Few servers send it and many clients ignore it.

What typically causes a 102

Some WebDAV servers during long COPY, MOVE or DELETE operations on big directory trees.
A handful of APIs that use it as a keep-alive for slow jobs.

Fix it on the server

For long-running work, prefer 202 Accepted with a status URL; intermediaries handle that far better than 102.

Fix it as a client or visitor

Treat it like any 1xx: keep waiting for the final response. If your HTTP library errors on it, upgrade the library.

Example response

HTTP/1.1 102 Processing

HTTP/1.1 207 Multi-Status
Content-Type: application/xml; charset=utf-8