What is HTTP 423 Locked Error?
The HTTP 423 Locked error is an HTTP status code that indicates a resource is currently locked and cannot be accessed.
The 423 Locked status code is specific to some WebDAV servers and is not typically encountered by web browsers accessing regular web pages.
The response should contain data in WebDAV’s XML format.
Root Causes of HTTP Error 423
Here are the following root causes of the HTTP 423 error:
- User Authentication Issues:
The error often relates to user authentication problems.
- Request Header Fields:
Incorrectly configured request header fields can trigger this error.
- Lock Token:
If a lock token was submitted but not accepted, it can lead to a 423 error.
How to Fix the HTTP 423 Locked Error?
By rectifying this error you have to determine the source.
First, identify whether the issue lies on the client side or the server side.
Client Side:
- Ensure proper user authentication and correct request headers.
- Check if any lock tokens were submitted but not accepted.
Server Side:
- Administer an administrative unlock if the resource is not meant to be locked.
- Please wait for the resource to become available or request its release from the entity holding the lock.
- Look for any misconfigurations on the server side.
Other Solutions:
Refresh the page:
Try reloading the page by pressing F5 or clicking the refresh button.
Clear your browser cache and cookies, and retry the request:
Sometimes, clearing your browser’s cache and cookies can solve the problem. This is because it forces your browser to fetch the latest version of the web page.
When you clear them, you get new info from the website’s server.
If you use Google Chrome, here’s how to clear its cache and cookies:
- Click the three dots in the top-right corner of your window. You can also use the keyboard shortcut (Ctrl + H).
- Go to History History.
- Click on Clear Browsing Data.
- A new window will appear. Choose the Time range, if you wish to erase all data, select All Time.
- Select what you’d like to clear- this could be browsing history, cookies, and other site data, or cached images and files.
- Then, hit the Clear Data button.
Conclusion
The HTTP 423 Locked status code, which is specific to the WebDAV protocol, signals that a resource is currently locked and cannot be accessed.
By implementing the solutions provided above, you can confidently address and resolve this issue.
I hope this article helps you rectify this error.
For further learning, you can also check the following HTTP status code:
- 416 Requested Range Not Satisfiable
- 417 expectation failed
- 418 I’m a Teapot: What is the HTTP Status Code 418?
- 421 Misdirected Request
- HTTP Status Code 422 Error
Frequently Asked Questions
What does an HTTP error status code mean?
HTTP status codes communicate request outcomes. 4xx codes mean the client did something wrong (404 not found, 403 forbidden, 429 too many requests). 5xx codes mean the server did something wrong (500 internal error, 502 bad gateway, 503 unavailable, 504 timeout). The exact code tells you where to look for the fix.
How do I fix HTTP 500 Internal Server Error?
500 means the server crashed processing your request. Three places to look: (1) Server logs (Apache error log, nginx error log, your Flask/Django console). (2) Database connection or query errors. (3) Unhandled exceptions in your application code. If you see 500 in production, check application logs first; the actual error message is usually clear.
How do I fix HTTP 502 Bad Gateway?
502 means the proxy (nginx/Apache) couldn’t reach your application server (gunicorn/uvicorn/PHP-FPM). Check: (1) Is your app server running? systemctl status gunicorn. (2) Is it listening on the port nginx expects? netstat -plnt. (3) Are there OOM crashes killing the worker? dmesg | grep -i oom. Restart the app service first as the quick fix.
What is the difference between HTTP 401 and 403?
401 Unauthorized: you’re not logged in (or your auth token is missing/expired). The fix: authenticate first. 403 Forbidden: you’re logged in but don’t have permission for this resource. The fix: check user roles/permissions. Two different fix paths despite similar-sounding names.
Where can I find more HTTP error fixes?
Browse the HTTP Errors reference hub for 35+ specific status code explanations and fixes. For backend troubleshooting see the Python Tutorial or PHP Tutorial hubs.
Caren Bautista
Technical Writer at PIES IT Solution
Responsible for crafting clear, well-structured, and beginner-friendly content across the platform. Handles the writing, proofreading, and editorial review of tutorials, guides, and documentation to ensure every article is accurate, readable, and easy to follow.
Expertise: Technical Writing · Content Creation · Documentation · Editorial Writing · JavaScript · TypeScript · Python · Python Errors · HTTP Errors · MS Excel · View all posts by Caren Bautista →