423 Locked
A WebDAV code: the resource is locked, and the request can't change it until the lock is released.
- Class
- 4xx Client error. The request is the problem: a wrong address, missing credentials, data the server can't accept.
- Defined in
- RFC 4918 (WebDAV)
What causes it
WebDAV lets a client lock a file while it is being edited, so that two people don't overwrite each other's work. A write to a locked file by anyone but the holder of the lock gets a 423. Programs that open documents straight from a WebDAV share work this way.
What to do about it
Wait until the other person closes the file, or ask them to. If you hold the lock yourself, send its token along in the If header. A lock left behind by a program that crashed runs out by itself after its timeout.
Not to be confused with
| 409 Conflict | A conflict with the state of the resource that is not a lock. |
|---|---|
| 403 Forbidden | Refused for lack of permission. |
All codes are on the list of HTTP status codes, which can be searched by number and by word.
Other 4xx codes
- 400 Bad Request
- 401 Unauthorized
- 402 Payment Required
- 403 Forbidden
- 404 Not Found
- 405 Method Not Allowed
- 406 Not Acceptable
- 407 Proxy Authentication Required
- 408 Request Timeout
- 409 Conflict
- 410 Gone
- 411 Length Required
- 412 Precondition Failed
- 413 Content Too Large
- 414 URI Too Long
- 415 Unsupported Media Type
- 416 Range Not Satisfiable
- 417 Expectation Failed
- 418 I'm a teapot
- 421 Misdirected Request
- 422 Unprocessable Content
- 424 Failed Dependency
- 425 Too Early
- 426 Upgrade Required
- 428 Precondition Required
- 429 Too Many Requests
- 431 Request Header Fields Too Large
- 451 Unavailable For Legal Reasons