CORS Unblock
No more CORS error by appending 'Access-Control-Allow-Origin: *' header to local and remote web requests when enabled
Disable Content-Security-Policy for web application testing. When the icon is coloured, CSP headers are disabled.
Review user movement across collected snapshots.
View collected rating snapshots from the latest 7-day window to assess rating stability.
Compare 1-day, 7-day, and 30-day net growth and growth rate.
Review publication date, version, supported languages, and crawl timestamps.
Review the store description, core capabilities, and common use cases.
Use at your own risk. Disables the current page's Content Security Policy. Useful when testing what resources a new third-party tag includes onto the page.
Inspect the latest comments and rating distribution.
Store average score: 3.5. The bars below are calculated from synced review text only, so they may be empty for extensions that have public ratings but no synced comments yet.
Review related products from the Chrome Web Store detail page.
No more CORS error by appending 'Access-Control-Allow-Origin: *' header to local and remote web requests when enabled
Drops X-Frame-Options and Content-Security-Policy HTTP response headers, allowing all pages to be iframed.
Enable cross origin requests blocked by CORS or CSP. Disable CORS and CSP in selected hostnames, preserve security of other websites
Automatically generate content security policy headers online for any website.
A browser extension to disable http header Content-Security-Policy and html meta Content-Security-Policy
A extension that set csp value empty
There is a small issue - the CSP setting does not remain set. I need to toggle it again and reload the page if I want to see it working. It used to remember its state before.
works like a charm!
Works good
Works perfectly. Thank you very much!
Don't work
It has no effect on the CSP headers when enabled and active for given tab.
Doesn't work, or no longer works.
I observed the following bug: If a website sends a Content-Security-Policy for one request, and then stops sending it for follow-up requests, Chromium still acts as if the old Content-Security-Policy is in effect. This happens if the extension is merely loaded in the browser (not activated by its button). Made me tear my hair out for a bit :)
Doesn't work with latest Chrome
Sadly did not work with latest google chrome, on 302 redirects where csp has been set to ultra hard bad mode.