| Previous | Next |
| HTTP_STATUS_VERSION_NOT_SUPPORTED | HTTP_STATUS_INSUFFICIENT_STORAGE |
HTTP_STATUS_VARIANT_ALSO_NEGOTIATES
It indicates that the selected variant is itself configured to negotiate, creating a circular reference. This is a server configuration problem rather than a request formatting problem.
Review variant maps, negotiation metadata, and rewrite rules. Remove the recursion so that a selected variant resolves to a concrete representation.
Operational meaning of HTTP 506 for HTTP_STATUS_VARIANT_ALSO_NEGOTIATES
HTTP 506 (HTTP_STATUS_VARIANT_ALSO_NEGOTIATES) is a server-error response. AllStat records its meaning as “506 Variant Also Negotiates”. For HTTP_STATUS_VARIANT_ALSO_NEGOTIATES, 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_VARIANT_ALSO_NEGOTIATES
- Correlate HTTP_STATUS_VARIANT_ALSO_NEGOTIATES with origin, gateway, load-balancer, and dependency logs to locate which hop generated it.
- For HTTP_STATUS_VARIANT_ALSO_NEGOTIATES, record request and trace identifiers, upstream timing, retry count, and the health of the selected backend.
- For HTTP_STATUS_VARIANT_ALSO_NEGOTIATES, use bounded retries with backoff only for idempotent work and only when the service policy permits them.
For telemetry, record HTTP 506, 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.