HTTP 423 Locked Error - Meaning & Fix

Main causes

A resource on the server is locked due to an active editing session by another user.
The resource is part of a batch operation that has not yet completed, causing it to be temporarily locked.
Incorrect or outdated client-side caching that fails to recognize the resource has been unlocked.
Administrative locks placed on certain resources to prevent changes during critical operations or maintenance.

# Request example 
curl -X POST https://sandbox.oxylabs.io/ -H 'Accept: application/xml;q=0.9' -H 'Accept-Encoding: compress' -H 'User-Agent: Chrome/91.0.4472.124'

Try Scraper API with 5K results

How to fix the error?

Verify the status of the resource and ensure it is not locked by another process or user.
Contact the administrator to unlock the resource if you do not have the necessary permissions.
Review and resolve any conflicts or dependencies that might be causing the resource to be locked.
Check the server's configuration settings to ensure that access permissions and resource locks are correctly set.

# Response example 
HTTP/1.1 423 Locked
Content-Type: application/xml
Content-Encoding: compress


423
Locked

Leave the HTTP errors behind with our API

Web Scraper API

Self-Service

Public data delivery from a majority of websites

From

Try free for 1 week

Common scraping HTTP error codes

401 Unauthorized	403 Forbidden	404 Not found	405 Method not allowed	406 Not acceptable
407 Proxy authentication required	408 Request timeout	409 Conflict	410 Gone	411 Length required
412 Precondition failed	413 Payload too large	414 Uri too long	415 Unsupported media type	416 Range not satisfiable
417 Expectation failed	421 Misdirected request	422 Unprocessable entity	423 Locked	424 Failed dependency
426 Upgrade required	428 Precondition required	429 Too many requests	431 Request header fields too large	444 Connection: close
451 Unavailable for legal reasons	499 Client closed request	501 Not implemented	503 Service unavailable	505 Http version not supported
506 Variant also negotiates	507 Insufficient storage	508 Loop detected	510 Not extended	511 Network authentication required