HTTP 102 Processing
An interim WebDAV response saying the server accepted a long-running request and is still working on it.
HTTP 102 ProcessingHTTP/1.1 102 Processingstatus 102 processing WebDAV102 Processing response 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
- Check the server log for the slow operation
- Raise proxy/server timeouts for WebDAV paths
- Make the client ignore 1xx and wait for the final status
Detailed fix by platform
cURL
curl -v -X PROPFIND -H "Depth: infinity" https://dav.example.com/files/
How to diagnose
- Final status — Received?
- Operation — Still running?
- 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:
Similar errors
Most viewed in HTTP
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 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.
Report a correction or suggest an improvement
Last updated 18 Nov 2026