What 501 means
The server doesn’t support the functionality needed to fulfil the request. Typically it doesn’t recognise the request method at all. It’s cacheable by default.
When servers send it
For unknown or unsupported methods, and sometimes in APIs for features that are planned but not built.
Common causes
- An unusual method such as
PROPFINDor a made-up one sent to an ordinary server. - An API endpoint stubbed out as “not yet implemented”.
How to fix it as a developer
- If the URL exists but just doesn’t allow this method, 405 Method Not Allowed is more accurate.
- Check for typos in the method name in your client.
How to fix it as a visitor
- There’s nothing you can do. The feature isn’t available on this server.
Related codes
- 405 Method Not Allowed: This URL exists but doesn’t accept that method (for example POST). The Allow header lists the ones it does.
- 500 Internal Server Error: Something went wrong on the server, and it has no more specific code to describe it.
- 505 HTTP Version Not Supported: The server won’t use the HTTP version in the request.
Where it’s defined
501 Not Implemented is defined in RFC 9110, section 15.6.2. It’s a 5xx code, the server error class: the server, or something behind it, failed to deal with a valid request.
Other 5xx codes
500 Internal Server Error · 502 Bad Gateway · 503 Service Unavailable · 504 Gateway Timeout · 505 HTTP Version Not Supported · 511 Network Authentication Required · 520 Web Server Returned an Unknown Error · 521 Web Server Is Down · 522 Connection Timed Out · 523 Origin Is Unreachable · 524 A Timeout Occurred · 525 SSL Handshake Failed · 526 Invalid SSL Certificate
Or search them all in the HTTP status code list.