406 Not Acceptable
This is an educational reference page about HTTP 406 Not Acceptable. The page itself is served as 200 OK so it can be indexed as HTTP documentation.
The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request. See Content negotiation.
Specification
Registered in the IANA HTTP Status Code Registry as Not Acceptable. Defined in RFC 9110, Section 15.5.7.
Header and content rules
What RFC 9110 says about a 406 response, quoted from the RFC. The 4xx class rules also apply.
- SHOULD (server; content): Send content listing the available representations and their resource identifiers. Table row
The server SHOULD generate content containing a list of available representation characteristics and corresponding resource identifiers from which the user or user agent can choose the one most appropriate. RFC 9110 §15.5.7
The same rule is in the response obligations table and its JSON.