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.

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

Should respect content-type or 406 the ones not supported. #438

Open
xadhoom opened this issue Jul 22, 2022 · 0 comments
Open

Should respect content-type or 406 the ones not supported. #438

xadhoom opened this issue Jul 22, 2022 · 0 comments

Comments

@xadhoom
Copy link

xadhoom commented Jul 22, 2022

Right now the saas always return the content-type as application/json, even when the client does not support it.

If application/json is the only content-type supported, the service should answer 406 Not Acceptable when application/json is not in the Accept headers, OR provide a valid representation of the resources according to the Accept headers.

Which basically means it should return an html or text page if the client accepts only text/html or text/plain. Obviously all the others content types should be refused with a 406.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant