2015-11-06 21:39:33 +01:00
|
|
|
---
|
|
|
|
|
set: 4
|
|
|
|
|
code: 406
|
|
|
|
|
title: Not Acceptable
|
2015-11-07 05:34:40 +01:00
|
|
|
references:
|
|
|
|
|
"Rails HTTP Status Symbol": ":not_acceptable"
|
2015-11-06 21:39:33 +01:00
|
|
|
---
|
|
|
|
|
|
2015-11-07 05:34:40 +01:00
|
|
|
The 406 (Not Acceptable) status code indicates that the target resource does not
|
|
|
|
|
have a current representation that would be acceptable to the user agent,
|
|
|
|
|
according to the proactive negotiation header fields received in the request
|
|
|
|
|
([RFC7231 Section 5.3][2]), and the server is unwilling to supply a default
|
|
|
|
|
representation.
|
|
|
|
|
|
|
|
|
|
The server SHOULD generate a payload containing a list of available
|
|
|
|
|
representation characteristics and corresponding resource identifiers from which
|
|
|
|
|
the user or user agent can choose the one most appropriate. A user agent MAY
|
|
|
|
|
automatically select the most appropriate choice from that list. However, this
|
|
|
|
|
specification does not define any standard for such automatic selection, as
|
|
|
|
|
described in [RFC7231 Section 6.4.1][3].
|
|
|
|
|
|
|
|
|
|
Source: [RFC7231 Section 6.5.6][1]
|
|
|
|
|
|
|
|
|
|
[1]: <http://tools.ietf.org/html/rfc7231#section-6.5.6>
|
|
|
|
|
[2]: <http://tools.ietf.org/html/rfc7231#section-5.3>
|
|
|
|
|
[3]: <http://tools.ietf.org/html/rfc7231#section-6.4.1>
|
