WhereGoes

102 Processing

1xx informational

WebDAV interim response telling the client the server accepted the full request but has not finished processing it yet, so waiting is expected.

Common causes

  • A long COPY, MOVE, or PROPFIND runs over a large collection.
  • A batch job is still executing while the client waits.
  • The proxy idle timeout is shorter than the backend operation duration.

How to fix it

  • Split huge WebDAV operations into smaller batches that finish quickly.
  • Raise the proxy read timeout above the expected operation duration.
  • Move long work behind a 202 with a polling URL so the connection is not held open.

What it means for redirects and SEO

Interim, so search crawlers wait rather than recording it, and a long 102 can stall the fetch. Link checkers may time out if the WebDAV operation never completes. Ordinary page crawling almost never sees it.

Related codes