Admin method not allowed

Identifiers

Field	Value
Type URI	https://echo.labstack.com/pro/problems/admin-method-not-allowed
Code	admin_method_not_allowed
HTTP status	405

HTTP status	English title
405	Method Not Allowed

When it occurs

The console does not serve this HTTP method here. It serves GET and HEAD, and POST only when actions or POST reads are enabled. The console also uses this code when Config.Middleware returns HTTP 405.

Client handling

Use a method that the Allow header lists.

Example response

If your application installs a custom handler, the body may differ.

HTTP/1.1 405 Method Not Allowed
Content-Type: application/problem+json
Cache-Control: no-store

{
  "code": "admin_method_not_allowed",
  "detail": "",
  "status": 405,
  "title": "Method Not Allowed",
  "type": "https://echo.labstack.com/pro/problems/admin-method-not-allowed"
}

Server correction

Check the client’s method and the endpoint’s Allow header. Ordinary views use GET. Declared POST lookups, action preview and commit use POST.

Response fields

Admin console

• code (string, always): The stable code above.
• detail (string, always): The console always sends detail. It is often empty and never contains the underlying error.
• status (integer, always): The HTTP status of the response.
• title (string, always): The HTTP status text, such as Conflict, unless the panel supplies its own title.
• type (string, always): The exact type URI above.

Headers:

• Cache-Control (always): no-store. The console sends it on every problem response, along with its usual security headers.
• Allow (conditional): Methods the console serves: GET, HEAD, plus POST when enabled. Sent when the console’s own method check refused the request.

Notes:

• Fields are written in alphabetical order.
• The console rewrites every 404 response to admin_not_found with an empty detail.

Related behavior

See the admin console for access checks, action IDs and audit failures.