102 HTTP Origin: Network OSI layer 7 · Application Last updated 18 Nov 2026

HTTP 102 Processing

An interim WebDAV response saying the server accepted a long-running request and is still working on it.

Exact message you may see HTTP 102 ProcessingHTTP/1.1 102 Processingstatus 102 processing WebDAV102 Processing response
Seen on: HTTP WebDAV

Meaning

102 tells the client not to time out while a slow WebDAV operation (COPY, MOVE, PROPFIND on a big tree) runs. It is deprecated and rarely sent now; if you see it stuck, the server never sent the final response, so check the backend operation, timeouts and proxies that drop interim responses.

Common causes

  • Long WebDAV operation on a large collection
  • Backend never finishes or hangs
  • Proxy/CDN swallowing interim 1xx responses
  • Client not handling 1xx
  • Server timeout shorter than the operation

⚡ Quick fix

  1. Check the server log for the slow operation
  2. Raise proxy/server timeouts for WebDAV paths
  3. Make the client ignore 1xx and wait for the final status

Detailed fix by platform

cURL

  1. curl -v -X PROPFIND -H "Depth: infinity" https://dav.example.com/files/

How to diagnose

  1. Final status — Received?
  2. Operation — Still running?
  3. Proxy — Passing 1xx?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

#fragment — The #fragment part of the URL never reaches the server (hash/anchor ignored in logs and redirects) (HTTP)#fragment+ vs %20 — Query string space encoded as + vs %20 (wrong values, 404 or signature mismatch) (HTTP)+ vs %20100 — HTTP 100 Continue (HTTP)100103 — HTTP 103 Early Hints (HTTP)103200 — API returns 200 OK with an error in the body (errors hidden from clients and monitors) (HTTP)200201 — HTTP 201 Created (HTTP)201202 — HTTP 202 Accepted (HTTP)202203 — HTTP 203 Non-Authoritative Information (HTTP)203102

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.