HTTP 423 Locked Error - Meaning & Fix
The HTTP 423 Locked error indicates that the resource you are trying to access is currently locked. This lock prevents the resource from being modified or accessed. The response typically includes details in WebDAV's XML format.
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
Common fixes
Verify the status of the resource and ensure it is not locked by another process or user.
Check the server's configuration settings to ensure that access permissions and resource locks are correctly set.
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.
# Response example HTTP/1.1 423 Locked Content-Type: application/xml Content-Encoding: compress423Locked
Forget HTTP errors with Scraper API
Web scraper API
Public data delivery from a majority of websites
From
49