HTTP 423 Locked — What It Means & How to Fix It
About HTTP 423 Locked
The HTTP 423 Locked status code indicates the resource being accessed is locked and cannot be modified. 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: This status code is defined in the WebDAV specification.. The resource is currently locked by another user or process.. The client must wait for the lock to be released or request an unlock.. Lock information may be included in the response.. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.
The most common reasons this occurs include: Another user has a WebDAV lock on the file or resource.. A document is checked out by another user in a version control system.. An administrative lock prevents modifications to the resource.. 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 be released by the other user or process.. Request an unlock if you have the necessary permissions.. Check who holds the lock and coordinate with them.. If the lock is stale, an administrator may need to forcefully remove it.. 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.
Quick Answer
What does HTTP 423 Locked mean?
It means the resource is currently locked and cannot be modified. Another user or process has a lock on it.
Overview
The HTTP 423 Locked status code indicates the resource being accessed is locked and cannot be modified.
Key Details
- This status code is defined in the WebDAV specification.
- The resource is currently locked by another user or process.
- The client must wait for the lock to be released or request an unlock.
- Lock information may be included in the response.
Common Causes
- Another user has a WebDAV lock on the file or resource.
- A document is checked out by another user in a version control system.
- An administrative lock prevents modifications to the resource.
Steps
- 1Wait for the lock to be released by the other user or process.
- 2Request an unlock if you have the necessary permissions.
- 3Check who holds the lock and coordinate with them.
- 4If the lock is stale, an administrator may need to forcefully remove it.