| Previous | Next |
| HTTP_STATUS_BAD_METHOD | HTTP_STATUS_PROXY_AUTH_REQ |
HTTP_STATUS_NONE_ACCEPTABLE
The server has no representation it is willing to send that satisfies headers such as Accept, Accept-Language, or Accept-Encoding. Many servers choose a default representation instead, so 406 is relatively uncommon.
Log the complete negotiation headers and compare them with the formats the endpoint actually produces. Avoid sending overly restrictive media-type or language requirements.
Operational meaning of HTTP 406 for HTTP_STATUS_NONE_ACCEPTABLE
HTTP 406 (this result) is a client-error response. AllStat records its meaning as “406 Not Acceptable”. 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
- Treat this result as a condition visible at the request boundary; inspect authentication, syntax, preconditions, routing, and resource state before retrying.
- preserve the response body and challenge or retry-related headers because they often carry the actionable reason.
- automatic retry is safe only when the method and status contract allow it and the request has been corrected.
For telemetry, record HTTP 406, 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.