Explain X-XSS-Protection:0 recommendation #769
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was surprised to see the recommendation to not set or disable the X-XSS-Protection header. Then I remembered reading some articles about enabling it could have the opposite effect, i.e. more XSS.
This PR adds a link to the XSS prevention cheat sheet which does a good job of explain why it should be turned off. Could be handy for those who are not yet "in the know" of these reasons.
Please make sure that for your contribution: