423 Locked
The resource that is being accessed is locked.
❌ 423 Locked Quick Fix⏱️ Est. Fix Time: 3 minutes
Usually happens because:
- ☑ Accessing files locked by concurrent
🔍 Quick Checklist:
Meaning
The HTTP 423 Locked WebDAV status code indicates that the resource that is being accessed is locked. WebDAV clients must unlock the resource first before performing write operations.
Root Causes
- Accessing files locked by concurrent edit operations inside WebDAV folders.
| Cause | Frequency |
|---|---|
| Accessing files locked by concurrent | ⭐⭐⭐⭐⭐ |
Common Mistakes
- Failing to submit correct lock-token headers when trying to overwrite a locked file.
How to Fix
1Obtain lock tokens or check folder lock locks before editing.
2Issue UNLOCK commands to release resources.
Framework-Specific Examples
Express router returning WebDAV status 423.
Express Example
app.put('/dav/file', (req, res) => {
res.status(423).send('Resource Locked');
});Server Configuration Examples
Configuring Nginx WebDAV lock support.
Nginx Config
dav_methods PUT DELETE MKCOL COPY MOVE;
# WebDAV lock directivesPrevention
- Check file lock state using PROPFIND methods before starting heavy edits.
Frequently Asked Questions (FAQ)
Q: What protocol introduced the 423 status code?
It was introduced by WebDAV (Web Distributed Authoring and Versioning) extensions in RFC 4918.
Q: How do WebDAV clients unlock resources?
The client must issue an HTTP UNLOCK request pointing to the target URL, carrying the corresponding Lock-Token header.
Q: Is 423 cacheable?
No. The 423 Locked status code is never cached.
Q: Can I use 423 in database APIs?
Yes. If an account is locked due to security blocks or consecutive password failures, 423 is a highly semantic status code to return.