Skip to the content

405 Method Not Allowed

The address exists but doesn't accept this method, such as a POST to a page that can only be read. The Allow header lists what works.

Class
4xx Client error. The request is the problem: a wrong address, missing credentials, data the server can't accept.
Defined in
RFC 9110

What it looks like

HTTP/1.1 405 Method Not Allowed
Allow: GET, HEAD

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

What causes it

When the server knows the method but doesn't support it for this resource: a DELETE on a collection that is read-only, a POST to a static file, a GET to an address that only takes POST. The response has to include an Allow header with the methods that are accepted.

What to do about it

Compare the method you sent with the Allow header and with the documentation of the API.

Two common causes lie outside your own code. One is a redirect on the way that turned your POST into a GET, visible as a 301 or 302 just before the 405. The other is a form that posts to a static page or to the wrong address.

Not to be confused with

501 Not ImplementedThe server doesn't know the method at all, for any address.
404 Not FoundThe address itself doesn't exist.
403 ForbiddenThe method is fine, but you are not allowed.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12