Please note, this is a STATIC archive of website developer.mozilla.org from 03 Nov 2016, cach3.com does not collect or store any user information, there is no "phishing" involved.

Revision 1111727 of 406 Not Acceptable

  • Revision slug: Web/HTTP/Status/406
  • Revision title: 406 Not Acceptable
  • Revision id: 1111727
  • Created:
  • Creator: fscholz
  • Is current revision? Yes
  • Comment fix github url

Revision Content

{{HTTPSidebar}}

The HTTP 406 Not Acceptable client error response code indicates that a response matching the list of acceptable values defined in {{HTTPHeader("Accept-Charset")}} and {{HTTPHeader("Accept-Language")}} cannot be served.

In reality, this error is very rarely used: instead of responding using this error code that will be cryptic for the end user (and difficult to fix), servers ignore the relevant header and serve an actual page to the user. It is assumed that even if the user won't be completely happy, it will prefer this to an error code.

If a server returns such an error status, the body of the message should contain the list of the available representations of the resources, allowing to manually choose among them.

Status

406 Not Acceptable

Specifications

Specification Title
{{RFC("7231", "406 Not Acceptable" , "6.5.6")}} Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content

Browser compatibility

{{Compat}}

See also

Revision Source

<div>{{HTTPSidebar}}</div>

<p>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 {{HTTPHeader("Accept-Charset")}} and {{HTTPHeader("Accept-Language")}} cannot be served.</p>

<p>In reality, this error is very rarely used: instead of responding using this error code that will be cryptic for the end user (and difficult to fix), servers ignore the relevant header and serve an actual page to the user. It is assumed that even if the user won't be completely happy, it will prefer this to an error code.</p>

<p>If a server returns such an error status, the body of the message should contain the list of the available representations of the resources, allowing to manually choose among them.</p>

<h2 id="Status">Status</h2>

<pre class="syntaxbox">
406 Not Acceptable</pre>

<h2 id="Specifications">Specifications</h2>

<table class="standard-table">
 <tbody>
  <tr>
   <th scope="col">Specification</th>
   <th scope="col">Title</th>
  </tr>
  <tr>
   <td>{{RFC("7231", "406 Not Acceptable" , "6.5.6")}}</td>
   <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
  </tr>
 </tbody>
</table>

<h2 id="Browser_compatibility">Browser compatibility</h2>

<p class="hidden">The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out <a href="https://github.com/mdn/browser-compat-data">https://github.com/mdn/browser-compat-data</a> and send us a pull request.</p>

<p>{{Compat}}</p>

<h2 id="See_also">See also</h2>

<ul>
 <li>{{HTTPHeader("Accept-Language")}}</li>
 <li>{{HTTPHeader("Accept-Charset")}}</li>
 <li>HTTP <a href="/en-US/docs/Web/HTTP/Content_negotiation">content negotiation</a></li>
</ul>
Revert to this revision