{"json_modified": "2016-08-31T04:14:01.044390", "uuid": "da1ac378-2cf0-4f93-b42e-c49d4b22d0c9", "title": "406 Not Acceptable", "url": "/en-US/docs/Web/HTTP/Status/406", "tags": ["Reference", "HTTP", "Status code"], "translations": [], "modified": "2016-08-31T04:14:01", "label": "406 Not Acceptable", "localization_tags": [], "locale": "en-US", "id": 192933, "last_edit": "2016-08-31T04:13:57", "summary": "The HTTP <code><strong>406</strong></code><strong><code> Not Acceptable</code></strong> client error response code indicates that a response matching the list of acceptable values defined in <a href=\"/en-US/docs/Web/HTTP/Headers/Accept-Charset\" title=\"The Accept-Charset request HTTP header advertises which character set the client is able to understand. Using content negotiation, the server then selects one of the proposals, uses it and informs the client of its choice within the Content-Type response header. Browsers usually don't set this header as the default value for each content type is usually correct and transmitting it would allow easier fingerprinting.\"><code>Accept-Charset</code></a> and <a href=\"/en-US/docs/Web/HTTP/Headers/Accept-Language\" title=\"The Accept-Language request HTTP header advertises which languages the client is able to understand, and which locale variant is preferred. Using content negotiation, the server then selects one of the proposals, uses it and informs the client of its choice with the Content-Language response header. Browsers set adequate values for this header according their user interface language and even if a user can change it, this happens rarely (and is frown upon as it leads to fingerprinting).\"><code>Accept-Language</code></a> cannot be served.", "sections": [{"id": "Quick_Links", "title": null}, {"id": "Status", "title": "Status"}, {"id": "Specifications", "title": "Specifications"}, {"id": "Browser_compatibility", "title": "Browser compatibility"}, {"id": "See_also", "title": "See also"}], "slug": "Web/HTTP/Status/406", "review_tags": []}