HTTP/1xx (Informational)
102 Processing
WebDAV interim response indicating the server has accepted the full request but has not yet completed it.
❓ Why does this happen?
Long-running WebDAV operations (COPY, MOVE on large collections) keep the client from timing out.
✅ How to fix it
No action required. If clients time out, increase client read timeouts or move work to an async job queue.
Return or handle 102 in your stack
// Route Handlers cannot return 1xx responses: the Response constructor
// only accepts status codes 200-599. 102 Processing is emitted by the server/CDN layer.Live 102 mock endpoint
102 is an interim 1xx response. Browsers and the Fetch API never expose 1xx codes as a final response, so it cannot be mocked directly. Try /api/mock/200 instead.
Frequently Asked Questions
What does HTTP Status 102 mean?
Why am I getting a 102 status code?
How do I fix a 102 Processing error?
Other 1xx status codes
Browse the full HTTP status codes directory or troubleshoot terminal errors in the Error Fix Encyclopedia.