HTTP 501 Not Implemented
The server doesn’t support the functionality (usually the HTTP method) needed to fulfil the request.
not implemented501 Not ImplementedMethod not implemented Meaning
Unlike 405 (method known but not allowed on this URL), 501 means the server doesn’t recognise or support the method at all — e.g. PATCH or a WebDAV method on an old server/proxy. Some APIs also return it for features that are planned but not built.
Common causes
- Unsupported HTTP method (PATCH, PROPFIND, custom verbs) on the server or a proxy
- Typo in the method name
- Endpoint stub returning 501 for unbuilt features
- Old proxies stripping or rejecting newer methods
⚡ Quick fix
- Check the method spelling and use a standard method
- Use POST with an override header if a proxy blocks PATCH (
X-HTTP-Method-Override) - Upgrade/configure the server or proxy to pass the method through
Detailed fix by platform
Nginx
- Nginx returns 501 for unknown methods only in rare builds; more often a load balancer or WAF in front is responsible — test the origin directly.
REST API
- Return 405 + Allow header for known-but-unsupported methods; reserve 501 for truly unimplemented features.
How to diagnose
- Method — Which method was sent?
- Layer — Which hop returned 501?
- Support — Does the server support that method?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in HTTP
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 14 Oct 2026