HTTP 423 Locked — WebDAV Resource Lock Conflict

Fix HTTP 423 Locked error in WebDAV when a resource is locked by another user or process, preventing modifications until the lock is released. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.

Here are the key things to understand: HTTP 423 Locked is a WebDAV extension status code indicating the resource is currently locked. Locks prevent concurrent modifications to the same resource by multiple users. WebDAV supports both shared locks (multiple readers) and exclusive locks (single writer). Locks have a timeout value after which they automatically expire. The Lock-Token header identifies the specific lock that must be provided to modify the resource. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.

The most common reasons this occurs include: Another user has an exclusive write lock on the resource. A previous editing session did not properly release the lock before closing. Server-side process holding a lock during batch operations. Stale lock from a crashed client that did not send UNLOCK before disconnecting. Identifying the root cause is the first step toward finding the right solution.

To resolve this, follow these recommended steps: Wait for the lock to expire — check the Timeout header in the 423 response for the remaining duration. Contact the user who holds the lock and ask them to save and close the file. Use a WebDAV client to send an UNLOCK request if you have the lock token. Ask the server administrator to forcibly remove stale locks. For developers: implement lock refresh and proper UNLOCK on client close/crash. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.

This article is part of our HTTP Status Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.