HTTP 400 Bad Request vs 506 Variant Also Negotiates
HTTP 400 (Bad Request) is a 4xx Client Error response, while 506 (Variant Also Negotiates) is a 5xx Server Error response. 400 indicates that the server cannot process the request due to malformed syntax, invalid request message framing, or deceptive request routing. In contrast, 506 means that the server has an internal configuration error: the chosen variant resource is configured to engage in content negotiation itself.
Description
The server cannot process the request due to malformed syntax, invalid request message framing, or deceptive request routing.
When You See It
When sending malformed JSON, missing required fields, or invalid query parameters.
How to Fix
Check the request body format, validate all required fields, and ensure proper encoding.
Description
The server has an internal configuration error: the chosen variant resource is configured to engage in content negotiation itself.
When You See It
Rare. Indicates a misconfigured server-side content negotiation loop.
How to Fix
Fix the server's content negotiation configuration.
Key Differences
400 is a 4xx Client Error response, while 506 is a 5xx Server Error response.
HTTP 400: The server cannot process the request due to malformed syntax, invalid request message framing, or deceptive request routing.
HTTP 506: The server has an internal configuration error: the chosen variant resource is configured to engage in content negotiation itself.
You encounter 400 when when sending malformed JSON, missing required fields, or invalid query parameters.
You encounter 506 when rare. Indicates a misconfigured server-side content negotiation loop.
When to Use Which
For 400 (Bad Request): Check the request body format, validate all required fields, and ensure proper encoding. For 506 (Variant Also Negotiates): Fix the server's content negotiation configuration.