| Previous | Next |
| HTTP_STATUS_URI_TOO_LONG | HTTP_STATUS_RANGE_NOT_SATISFIABLE |
HTTP_STATUS_UNSUPPORTED_MEDIA
The conflict can be in Content-Type, Content-Encoding, or the bytes themselves. It is distinct from 406, which concerns the formats the client is willing to receive.
Compare the declared media type and charset with the endpoint contract. Send the exact expected serialization and avoid setting JSON or form headers for a different body format.
Compare the request Content-Type, any content encoding, and the endpoint's documented input formats. A JSON endpoint can reject XML, an unsupported charset, or a representation encoded in an unaccepted way. Changing the Accept header alone does not fix the format of the request body being submitted.
Looking for a different code? Search another status or error code.