| Previous | Next |
| HTTP_STATUS_UNPROCESSABLE_ENTITY | HTTP_STATUS_FAILED_DEPENDENCY |
HTTP_STATUS_LOCKED
The resource might be locked directly or through an ancestor collection. The response body can identify lock information and the affected resource in a WebDAV multistatus format.
Check the lock token, lock owner, depth, timeout, and whether the client is operating on a member of a locked collection. Do not remove a lock without confirming that another client is not editing the resource.
The response can result from a missing lock token, a lock held by another principal, or a request that would modify a locked descendant. Inspect the WebDAV lock discovery information and the If header used by the client. Acquiring or refreshing the correct lock is preferable to repeatedly sending the same write.
Looking for a different code? Search another status or error code.