- Software and systems
- HTTP service
506
HTTP 506 Variant Also Negotiates: meaning and next diagnostic branch
Risk level
Medium
Proceed carefully and stop if the check is unclear.
Urgency
Medium
Quick answer
HTTP 506 Variant Also Negotiates means: Transparent content negotiation has a circular configuration in which a selected variant also negotiates. It identifies a protocol result, not the failed component. Preserve one request/response pair and discriminate one route versus the whole service, deployment/configuration version, server logs and whether Retry-After or capability documentation exists.
Safety first
Stop and check this first
- Do not expose stack traces, repeatedly restart production or buy capacity without saturation evidence.
Safe checks you can perform
- Freeze one complete failing exchange
- Change one variable and repeat once
- Stop before retries hide the first failure
Leave these tasks to a qualified professional
- Do not attempt this professional task: Trace-led handoff for HTTP 506
What a technician must be able to justify
A technician is coming
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Trace-led handoff for HTTP 506
What they doCorrelate request ID with exception, deployment diff, saturation, health checks and feature negotiation; prove code, configuration or capacity ownership before remediation.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Checks and evidence, step by step
Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
- 1
Freeze one complete failing exchange
No special tools
Procedure
Record HTTP 506, timestamp, method, scheme/host/path without secrets, response headers and body, request ID, client, deployment version and every proxy/CDN/gateway hop. Redact credentials and personal data.
Do not expose stack traces, repeatedly restart production or buy capacity without saturation evidence.
Evidence: IANA HTTP Status Code Registry · RFC 2295 - Transparent Content Negotiation
- 2
Change one variable and repeat once
No special tools
Procedure
Compare one known-good route and the failing route at the same deployment. Check health and Retry-After once; roll back only under the service’s approved deployment procedure.
Do not expose stack traces, repeatedly restart production or buy capacity without saturation evidence.
Evidence: IANA HTTP Status Code Registry · RFC 2295 - Transparent Content Negotiation
- 3
Stop before retries hide the first failure
No special tools
Procedure
One route isolates application/configuration; every route isolates shared runtime or capacity. 501 is missing capability, while 503 is temporary availability; buying capacity is justified only by measured saturation.
Do not expose stack traces, repeatedly restart production or buy capacity without saturation evidence.
Evidence: IANA HTTP Status Code Registry · RFC 2295 - Transparent Content Negotiation
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and systems
- Brand
- HTTP
- Product type
- HTTP service
Known code variants
- 506 Anche la variante negozia
- 506 La variante négocie aussi
- 506 La variante también negocia
- 506 Variant Also Negotiates
- 506 Variante verhandelt ebenfalls
- HTTP 506
- HTTP status 506
What it means
Registered meaning: Transparent content negotiation has a circular configuration in which a selected variant also negotiates. The next decision boundary is one route versus the whole service, deployment/configuration version, server logs and whether Retry-After or capability documentation exists. Before changing infrastructure or buying support, require: Correlate request ID with exception, deployment diff, saturation, health checks and feature negotiation; prove code, configuration or capacity ownership before remediation.
Warnings and stop conditions
- Mediumsource verified
Do not expose stack traces, repeatedly restart production or buy capacity without saturation evidence.
Evidence: IANA HTTP Status Code Registry · RFC 2295 - Transparent Content Negotiation
Symptoms and causes
Probable causes · in order
- What the registered HTTP status establishesConfirmed
IANA registers 506 as Variant Also Negotiates. The controlling specification establishes: Transparent content negotiation has a circular configuration in which a selected variant also negotiates.
Evidence: IANA HTTP Status Code Registry · RFC 2295 - Transparent Content Negotiation
- The evidence that changes the next branchPossible
Capture one route versus the whole service, deployment/configuration version, server logs and whether Retry-After or capability documentation exists. One route isolates application/configuration; every route isolates shared runtime or capacity. 501 is missing capability, while 503 is temporary availability; buying capacity is justified only by measured saturation.
Evidence: IANA HTTP Status Code Registry · RFC 2295 - Transparent Content Negotiation
Virtual technician
Does 506 still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
IANA HTTP Status Code Registry
Internet Assigned Numbers Authority · 2025 · standard
- 2
RFC 2295 - Transparent Content Negotiation
IETF / RFC Editor · 1998 · standard
Was this entry useful?