| Previous | Next |
| HTTP_STATUS_PAGE_EXPIRED | HTTP_STATUS_ENHENCE_CALM |
HTTP_STATUS_METHOD_FAILURE
Older Spring Framework APIs exposed 420 as METHOD_FAILURE. It is a framework-specific historical value, so its actual meaning depends on the application that returned it rather than on HTTP itself.
Inspect the server framework version, controller or filter that created the response, and its response body. Clients should not assign a universal retry or authentication meaning to code 420.
Spring Framework 3.2 HttpStatus documentation
Operational meaning of HTTP 420 for HTTP_STATUS_METHOD_FAILURE
HTTP 420 (HTTP_STATUS_METHOD_FAILURE) is a client-error response. AllStat records its meaning as “420 Method Failure”. For HTTP_STATUS_METHOD_FAILURE, interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling for HTTP_STATUS_METHOD_FAILURE
- Treat HTTP_STATUS_METHOD_FAILURE as a condition visible at the request boundary; inspect authentication, syntax, preconditions, routing, and resource state before retrying.
- For HTTP_STATUS_METHOD_FAILURE, preserve the response body and challenge or retry-related headers because they often carry the actionable reason.
- For HTTP_STATUS_METHOD_FAILURE, automatic retry is safe only when the method and status contract allow it and the request has been corrected.
For HTTP_STATUS_METHOD_FAILURE, for telemetry, record HTTP 420, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.