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

feature request: content_security_policy_report_only in manifest.json #197

Open
Jack-Works opened this issue Apr 13, 2022 · 5 comments
Open
Labels
topic: csp Related to content security policy enforcement

Comments

@Jack-Works
Copy link

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy-Report-Only

@Jack-Works
Copy link
Author

image

Without this feature, I cannot specify a Report Only CSP because it does not accept CSP Report Only via a meta tag.

@Jack-Works
Copy link
Author

@carlosjeurissen
Copy link
Contributor

This depends on the not yet further explored discussion about CSP reporting initiated by #97 during #166. Seems it could be a good opportunity to talk about this.

@Jack-Works
Copy link
Author

I hope we can add it consistently as the status quo API asap. There is no way to opt-in the CSP in our extension in a gradually way 😂

@Rob--W Rob--W added the topic: csp Related to content security policy enforcement label Apr 27, 2022
@carlosjeurissen
Copy link
Contributor

As for syntax, I'm proposing to use an object structure like:

"content_security_policy_report_only": {
  "extension_pages": "...",
  "sandbox": "..."
}

This aligns it with the content_security_policy syntax proposed by Google and Mozilla. Which makes sure it is flexible and familiar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: csp Related to content security policy enforcement
Projects
None yet
Development

No branches or pull requests

4 participants