Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handling of unaccepted/wrong content-type #37

Open
FiV0 opened this issue Dec 16, 2021 · 1 comment
Open

Handling of unaccepted/wrong content-type #37

FiV0 opened this issue Dec 16, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@FiV0
Copy link
Contributor

FiV0 commented Dec 16, 2021

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.
@malcolmsparks
Copy link
Contributor

100% agree

@armincerf armincerf added the enhancement New feature or request label Jan 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@malcolmsparks @armincerf @FiV0