HTTP 405 Method Not Allowed

Client error code, RFC 9110, section 15.5.6

What it means

The address exists, but not for this method. For example a form sent POST to something that only accepts GET.

A real response

This is the request and the answer our test server gave when we asked it to return 405.

GET /c/405 HTTP/1.1
Host: example.com

HTTP/1.1 405 Method Not Allowed
Date: Sat, 14 Nov 2026 10:00:00 GMT
Content-Type: text/html; charset=utf-8
Allow: GET, HEAD
Content-Length: 11

<p>demo</p>

If you run the site

A 405 response must send an Allow header that lists the supported methods. Check that the form or API call uses the method the route is written for, and that the server configuration (or a CDN or proxy rule) does not block POST, PUT or DELETE.

If you are a visitor

Usually a problem in the site or app, not in your device. Reload and try again, or tell the site.

A common mistake

Not sending the Allow header, so the client does not learn what is allowed.

Registered in the IANA HTTP Status Code Registry as Method Not Allowed, defined in RFC 9110, section 15.5.6.

This is an independent guide. It is not connected with the IETF, IANA, any browser maker or any company named here. Meanings were checked against the RFC texts on 14 November 2026. Responses shown were recorded on 14 November 2026 from a small test server on the author's own computer.