102 Processing
A WebDAV interim response telling the client the server has accepted the request and is still working on it.
What it means
HTTP 102 Processing was defined for WebDAV to keep a connection alive during a request that takes a long time to complete. The server sends it to say the request was received and is being worked on, so the client should not assume the connection died and time out. It is not a final response, and the spec that defined it has since been deprecated.
When it happens
It shows up with WebDAV operations that touch many resources at once, such as a large COPY or MOVE across a collection, where the server needs time before it can return a real answer. Ordinary websites never send it.
How to fix it
- Nothing to fix — 102 is an interim signal, not an error.
- If a WebDAV client times out anyway, raise its read timeout so it waits for the final response.
- Because the status is deprecated, prefer not to rely on it in new code.
SEO impact
None. It is a WebDAV-only interim response that search engines never encounter on indexable pages.
Find out which of your URLs return 102
Paste a list of URLs and Sitewell checks the status code of every one at once — free and without signup.
Related codes
An interim response telling the client the initial part of a request was received and it should continue sending the body.
101 Switching ProtocolsThe server agrees to switch the connection to a different protocol, such as upgrading from HTTP to WebSocket.
103 Early HintsAn interim response that lets the browser start fetching critical assets before the final page arrives.
Related guides
A plain-English primer on HTTP status codes for SEOs: what the 2xx, 3xx, 4xx, and 5xx families mean, which ones affect rankings, and the codes worth knowing.
How to find and fix broken linksA practical walkthrough for finding broken links on your site, working out why each one breaks, and fixing them so visitors and crawlers stop hitting dead ends.