Currently specifying a bad content-type results in a server error. We could do two things to improve the dev experience:
- Return a
406 Not Acceptable instead of a server error.
- Include the error and irritating content-type in the response.
The same is probably true for content-language and content-encoding.
Currently specifying a bad
content-typeresults in a server error. We could do two things to improve the dev experience:406 Not Acceptableinstead of a server error.The same is probably true for
content-languageandcontent-encoding.