HTTP 100 Continue vs 423 Locked
HTTP 100 (Continue) is a 1xx Informational response, while 423 (Locked) is a 4xx Client Error response. 100 indicates that the server has received the request headers and the client should proceed to send the request body. This lets the client know it can continue with the request or abort if the headers were rejected. In contrast, 423 means that the resource is locked and cannot be modified (WebDAV).
Description
The server has received the request headers and the client should proceed to send the request body. This lets the client know it can continue with the request or abort if the headers were rejected.
When You See It
When a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.
How to Fix
This is an interim response — no fix needed. The client should continue sending the request body.
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
100 is a 1xx Informational response, while 423 is a 4xx Client Error response.
HTTP 100: The server has received the request headers and the client should proceed to send the request body. This lets the client know it can continue with the request or abort if the headers were rejected.
HTTP 423: The resource is locked and cannot be modified (WebDAV).
You encounter 100 when when a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.
You encounter 423 when when trying to edit a file that another user has locked in WebDAV.
When to Use Which
For 100 (Continue): This is an interim response — no fix needed. The client should continue sending the request body. For 423 (Locked): Wait for the lock to be released, or request the lock owner to unlock it.