| 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.
Operational meaning of HTTP 423 for HTTP_STATUS_LOCKED
HTTP 423 (HTTP_STATUS_LOCKED) is a client-error response. AllStat records its meaning as “423 Locked”. For HTTP_STATUS_LOCKED, interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling for HTTP_STATUS_LOCKED
- Treat HTTP_STATUS_LOCKED as a condition visible at the request boundary; inspect authentication, syntax, preconditions, routing, and resource state before retrying.
- For HTTP_STATUS_LOCKED, preserve the response body and challenge or retry-related headers because they often carry the actionable reason.
- For HTTP_STATUS_LOCKED, automatic retry is safe only when the method and status contract allow it and the request has been corrected.
For telemetry, record HTTP 423, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.