At One Place

HTTP 102 — Processing

HTTP 102
Processing
A WebDAV server is still working on a long request and is telling the client not to time out.

What 102 actually means

This is a keep-alive signal from WebDAV. Some WebDAV operations — copying a large collection, for example — take long enough that a client would give up before the real response arrived, so the server sends an interim 102 to say it is still working. It was defined in RFC 2518 and deliberately left out of the later WebDAV revision, RFC 4918, so it is registered but effectively deprecated.

Common causes

  • A WebDAV server is midway through a long-running COPY, MOVE or PROPFIND
  • A legacy WebDAV implementation still following RFC 2518

If you're just trying to view the page

  1. Nothing — the operation is still running and a real response should follow
  2. If it never completes, the WebDAV server or the network between you and it is the problem, not this code

If it's your site

  1. Prefer async job semantics (202 plus a status URL) over 102 for anything new
  2. Some HTTP clients and proxies mishandle unexpected 1xx responses; verify yours does not hang

Reference

Status code
102
Reason phrase
Processing
Category
1xx — Informational
Defined in
RFC 2518 §10.1

Common questions

What does HTTP 102 mean?
A WebDAV server is still working on a long request and is telling the client not to time out. This is a keep-alive signal from WebDAV. Some WebDAV operations — copying a large collection, for example — take long enough that a client would give up before the real response arrived, so the server sends an interim 102 to say it is still working.
How do I fix a 102 error?
Nothing — the operation is still running and a real response should follow
Is 102 a client error or a server error?
102 is in the 1xx range, which means informational. It is not an error at all.

Related pages

Sources

  1. Hypertext Transfer Protocol (HTTP) Status Code Registry — IANA
  2. RFC 9110: HTTP Semantics — IETF

How these figures are compiled and checked