-
Notifications
You must be signed in to change notification settings - Fork 687
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
Add rule(s) to check the usage of the Content-Security-Policy
HTTP header
#25
Comments
Content-Security-Policy
HTTP header Content-Security-Policy
HTTP header
I don't think the owner is updating that site for CSP spec changes :( The following resources are pretty sweet and indicates we could do with a new hint for when CSP is missing According to "Adopting a strict policy": https://csp.withgoogle.com/docs/strict-csp.html "setting While the csp-evaluator (repo: https://github.com/google/csp-evaluator) reports: Meanwhile I have updated |
Thanks, great reply. From the webappsec issue, I think this is great advice:
What I'd suggest to you guys is to not raise the error for the case of small CSP headers that are disabling JS. Continue to raise the error for non-HTML CSP headers that are too long or impotent (implies poor server configuration as per your original intent here). Originally posted by @chrisgraham in #3403 (comment) |
Please review so as to allow CSP, etc., on SVG, as it can contain style, script, foreignObject. |
X-WebKit-CSP
,X-Content-Security-Policy
).TODO
: Look into what other checks we can add for that this (e.g.: validate the content of the header,upgrade-insecure-requests
)See also:
The text was updated successfully, but these errors were encountered: