HTTP 400 Bad Request vs 423 Locked
Both HTTP 400 (Bad Request) and 423 (Locked) belong to the 4xx Client Error category. 400 indicates that the server cannot process the request due to malformed syntax, invalid request message framing, or deceptive request routing. Meanwhile, 423 means that the resource is locked and cannot be modified (WebDAV).
Description
The server cannot process the request due to malformed syntax, invalid request message framing, or deceptive request routing.
When You See It
When sending malformed JSON, missing required fields, or invalid query parameters.
How to Fix
Check the request body format, validate all required fields, and ensure proper encoding.
Description
The resource is locked and cannot be modified (WebDAV).
When You See It
When trying to edit a file that another user has locked in WebDAV.
How to Fix
Wait for the lock to be released, or request the lock owner to unlock it.
Key Differences
HTTP 400: The server cannot process the request due to malformed syntax, invalid request message framing, or deceptive request routing.
HTTP 423: The resource is locked and cannot be modified (WebDAV).
You encounter 400 when when sending malformed JSON, missing required fields, or invalid query parameters.
You encounter 423 when when trying to edit a file that another user has locked in WebDAV.
When to Use Which
For 400 (Bad Request): Check the request body format, validate all required fields, and ensure proper encoding. For 423 (Locked): Wait for the lock to be released, or request the lock owner to unlock it.