Skip to content

Web APIs must set a non-HTML content-type on all responses, including 300s, 400s and 500s #23

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
Open
julienw opened this issue Nov 18, 2019 · 0 comments
Open

Web APIs must set a non-HTML content-type on all responses, including 300s, 400s and 500s #23

julienw opened this issue Nov 18, 2019 · 0 comments
Labels
security

Comments

@julienw
Copy link
Contributor

julienw commented Nov 18, 2019

This recommendation comes from #18.

We should enforce this at the root level: if the result is a HTML-like content-type, we should force it to something else. This should be possible with a simple middleware.
Maybe that exists in a ready-to-use package already.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
security
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@julienw