method_not_allowed

HTTP 405   title: Method not allowed

What it means

The path names a verb that exists, called with the other method: a GET at an action’s path, or a POST at a query’s. Distinct from verb_not_found precisely because the verb is there.

What it carries

• Allow — names the method the verb accepts.
• hint — names the call to make.

What to do next

Re-issue with the method in Allow. Queries are GET <endpoint>/<query-name> with arguments in the query string; actions are POST <endpoint>/<action-name> with a JSON body. The catalog at GET <endpoint>/schema says which each verb is.

An operator is not required to answer this code. A verb dialed with the method its kind does not take may simply be the bare 404 its web framework gives any unrouted path — which is what the reference implementation does. Read the kind off schema and dial the method it requires; do not infer from a 404 that the verb is absent.

On the wire

{
  "type":   "https://kiosk.tech/problems/method_not_allowed",
  "title":  "Method not allowed",
  "status": 405,
  "detail": "… what went wrong on THIS request …",
  "code":   "method_not_allowed"
}

This page documents the RFC 9457 type URI https://kiosk.tech/problems/method_not_allowed. The URI is an identifier, not a locator a client should fetch: branch on the document’s code member. The normative definition lives in the error vocabulary of the Kiosk specification (§9 of the formal spec).