HTTP 423 Locked vs 429 Too Many Requests
Both HTTP 423 (Locked) and 429 (Too Many Requests) belong to the 4xx Client Error category. 423 indicates that the resource is locked and cannot be modified (WebDAV). Meanwhile, 429 means that the user has sent too many requests in a given time (rate limiting). The response should include a Retry-After header.
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.
Description
The user has sent too many requests in a given time (rate limiting). The response should include a Retry-After header.
When You See It
When hitting API rate limits or making too many requests too quickly.
How to Fix
Check the Retry-After header. Implement exponential backoff. Consider caching responses.
Key Differences
HTTP 423: The resource is locked and cannot be modified (WebDAV).
HTTP 429: The user has sent too many requests in a given time (rate limiting). The response should include a Retry-After header.
You encounter 423 when when trying to edit a file that another user has locked in WebDAV.
You encounter 429 when when hitting API rate limits or making too many requests too quickly.
When to Use Which
For 423 (Locked): Wait for the lock to be released, or request the lock owner to unlock it. For 429 (Too Many Requests): Check the Retry-After header. Implement exponential backoff. Consider caching responses.