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.

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

[enhancement] How can we fix Content Security Policy, Subresource Integrity and X-Content-Type-Options.. #21

Open
mobilelifeful opened this issue Aug 27, 2023 · 1 comment

Comments

@mobilelifeful
Copy link

https://observatory.mozilla.org/analyze/hellotham.github.io

Thank you.

@ChristineTham
Copy link
Collaborator

Hello

Unfortunately, the implementation of X-Frame-Options header and Content Security Policy’s frame-ancestors is deployment dependent and must be implemented in the web server, not as meta tags in the code.

In any case, content security policy is not a set and forget setting, so it's best that this is something you review and declare yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants