WhereGoes

423 Locked

4xx client error

WebDAV response indicating that the resource is locked by another client, often via a LOCK token, and cannot be modified until it is released.

Common causes

  • Another client holds an exclusive write lock.
  • A lock was orphaned by a crashed client.
  • The request omitted the required lock token.

How to fix it

  • Send the lock token in the If header of the write request.
  • Expire stale locks with a timeout on the LOCK call.
  • Expose lock owners so editors can request a release.

What it means for redirects and SEO

Locked content returns a hard error, so crawlers skip it. Long-held WebDAV locks are the usual cause. Release locks promptly or expose a read-only route.

Related codes