423 Locked
A WebDAV response saying the file or resource is locked, so the server will not change it until the lock is released.
What 423 Locked means
WebDAV clients can LOCK a resource while editing it. Other requests that try to change it get 423 until the owner unlocks it or the lock times out.
Common causes
- Another user or app has the file open for editing.
- A stale lock left behind after a client crashed.
How to fix 423 Locked
- Wait for the other user to finish, or close the file in the app that holds it.
- If you own the lock, send its token in the If header.
- Ask the server admin to remove a stale lock, or wait for it to expire.
Headers that go with it
Lock-TokenIf
Example response
HTTP/1.1 423 Locked
Content-Type: text/plain; charset=utf-8
423 LockedHow to check for a 423 response
cURL
# Print only the status code
curl -s -o /dev/null -w "%{http_code}\n" https://example.com/JavaScript (Node.js)
const res = await fetch("https://example.com/");
if (res.status === 423) {
console.log(res.status, res.statusText);
}Python
import requests
res = requests.get("https://example.com/")
if res.status_code == 423:
print(res.status_code, res.reason)Go
res, err := http.Get("https://example.com/")
if err != nil {
log.Fatal(err)
}
defer res.Body.Close()
if res.StatusCode == 423 {
fmt.Println(res.Status)
}Specification
423 Locked is defined in RFC 4918, section 11.3.
Related status codes
- 424
A WebDAV response saying the request failed because another action it depended on failed first.
- 409
The request conflicts with the current state of the resource, such as saving a version that someone else already changed.
- 207
A WebDAV response that carries a separate status code for each of several resources, wrapped in an XML body.