-
Notifications
You must be signed in to change notification settings - Fork 435
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
[CSP] Modify existing content security policy not work #1845
Comments
now i use https://chrome.google.com/webstore/detail/disable-content-security/ieelmcmcagommplceebfedjlakkhpden |
If it worked earlier you can switch "Modify existing content security policy (CSP) headers" from "Auto" to "Yes". This will restore the old behavior. However, Tampermonkey can't support CSP relaxing in Chrome when manifest v3 becomes mandatory and also won't support CSP relaxing in Firefox in the near future. |
Then is never worked with a strict page CSP. You have to set the option to "Remove" (which is working fine here) or better use a bundler like webpack to include all sources in one script, or use |
(Please fill out the issue template with your details)
Expected Behavior
Modify existing content security policy (CSP) headers: Remove entirely (possibly unsecure)
Actual Behavior
not work, cannot remove csp headers
still show "Refused to load the script 'https://esm.sh/octokit' because it violates the following Content Security Policy directive"
Seems to have a version before is valid. I remember when I first wrote this script (a month ago) it worked.
Specifications
Script
(Please give an example of the script if applicable.)
The text was updated successfully, but these errors were encountered: