HTTP 405 Method Not Allowed: Meaning and Fix

405 Method Not Allowed

Meaning	This URL does not allow that HTTP method.
When	A client sends GET to a POST-only route, or the reverse.
Causes	A wrong method or a route that only accepts some verbs.
Fix	Use the method in the Allow header.
Retry	Do not retry with the same method.
Alert?	Usually no. It is a client bug unless a deploy suddenly rejects a method you use.

Runs in your browser. Nothing you enter is stored.

Most 405s are not an incident

It is a client bug unless a deploy suddenly rejects a method you use.

curl -sS -X POST https://api.trigv.com/v1/events \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $TRIGV_API_KEY" \
  -d '{"channel":"ops","title":"HTTP 405","level":"warning"}'

Get an API key All status codes

How to use it

Read what 405 means before changing a retry loop.
Check the common causes against the response body and the server log.
Follow the retry note. Retrying a 400 with the same body will fail again.
Alert only in the cases the verdict describes.

About this tool

HTTP 405 Method Not Allowed means This URL does not allow that HTTP method. Servers send it when A client sends GET to a POST-only route, or the reverse.

Common causes: A wrong method or a route that only accepts some verbs. The practical fix is: Use the method in the Allow header.

Retry: Do not retry with the same method.

Alert on it? Usually no. It is a client bug unless a deploy suddenly rejects a method you use.

Trigv is a push for the moment a status starts mattering, not a log of every response. If the code is one you should hear about, the snippet posts a single event with level error or warning. The status page itself does not call your API.

Questions

What is HTTP 405?

This URL does not allow that HTTP method.

Should the client retry?

Do not retry with the same method.

Should I alert on it?

Usually no. It is a client bug unless a deploy suddenly rejects a method you use.

How is this different from reading the spec?

The page adds a plain retry note and an alert verdict for people running the service, not only for people parsing the response.

400 Bad Request The server could not understand the request. 401 Unauthorized The request is missing valid authentication. 403 Forbidden The server understood the request and refuses it. Cron Job Alert Script Wrap a command so a failed, slow, or finished cron job sends a Trigv alert.

HTTP 405 Method Not Allowed