-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
[Security] Fix XSS Vulnerability where content-type header wasn't explicitly set #21704
[Security] Fix XSS Vulnerability where content-type header wasn't explicitly set #21704
Conversation
📣 Hi @sarahalsmiller! a backport is missing for this PR [21704] for versions [1.15,1.17,1.18,1.19] please perform the backport manually and add the following snippet to your backport PR description:
|
…licitly set (#21704) * explicitly add content-type anywhere possible and add middleware to set and warn * added tests, fixed typo * clean up unused constants * changelog * fix call order in middleware
📣 Hi @sarahalsmiller! a backport is missing for this PR [21704] for versions [1.15,1.17,1.18,1.19] please perform the backport manually and add the following snippet to your backport PR description:
|
📣 Hi @sarahalsmiller! a backport is missing for this PR [21704] for versions [1.15,1.17,1.18] please perform the backport manually and add the following snippet to your backport PR description:
|
2 similar comments
📣 Hi @sarahalsmiller! a backport is missing for this PR [21704] for versions [1.15,1.17,1.18] please perform the backport manually and add the following snippet to your backport PR description:
|
📣 Hi @sarahalsmiller! a backport is missing for this PR [21704] for versions [1.15,1.17,1.18] please perform the backport manually and add the following snippet to your backport PR description:
|
Description
Added middleware to ensure that content-type header is always set to mitigate XSS vulnerability.
Testing & Reproduction steps
Links
PR Checklist