Method not allowed

Status #

405

Meaning #

The API responds with ‘Method not allowed’ if you’ve executed a request method against a route that isn’t designed to perform respective requirement the request method intends.

The HyperText Transfer Protocol (HTTP) 405 Method Not Allowed response status code indicates that a client requested a read or write activity against a server’s route, which endpoint isn’t configured to process/perform respective kind of activity.

On the one hand the 405 error is an error which solely can be the cause of a server-side problem. On the other hand, from the technical view the error belongs to a client-side issue, because at the moment when the request is fired by the client he is responsible to choose an allowed method and it isn’t the fault of the server how the configuration/endpoint’s provisioned functionality is at hand. This is the reason why this type of error is categorized within the scope of client-side (4xx) responses.

Request #

PATCH https://api.gridscale.io/hybrid-core/v2/hybrid-cores

Response #

Header:

HTTP/1.1 405 Method Not Allowed
Content-Type: application/json; charset=utf-8
...

Body:

{
  "errors": [
    {
      "type": "https://my.gridscale.io/docs/apis/problems/hybrid-core/v2/method-not-allowed",
      "title": "Method not allowed",
      "status": 405,
      "detail": "PATCH on /hybrid-core/v2/hybrid-cores isn't allowed.",
      "DocURL": "https://my.gridscale.io/docs/apis/hybrid-core/v2/introduction",
    }
  ]
}