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

Re-evaluate need of x-xss-protection for security extractor. #87

Open
MRuecklCC opened this issue May 18, 2022 · 0 comments
Open

Re-evaluate need of x-xss-protection for security extractor. #87

MRuecklCC opened this issue May 18, 2022 · 0 comments
Labels
feature Anything related to the behavior of the feature extractors

Comments

@MRuecklCC
Copy link
Contributor

Currently the x-xss-protection header is checked in the security extractor. However, Mozilla recommends to set this only if legacy browser support is required: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection

Maybe it makes sense to it from the required header?

Relevant files:

  • docs/acceptance.md#(Sicherheit alias Security)
  • src/features/security.py
@MRuecklCC MRuecklCC added the feature Anything related to the behavior of the feature extractors label Sep 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature Anything related to the behavior of the feature extractors
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MRuecklCC