CORS Unblock

4.1

121 Ratings
100.0K
Installs
Aug 21, 2023
Updated
Download

#Cross-Origin #Security #Web Security

What is CORS Unblock

CORS Unblock is a plugin that addresses CORS errors by manipulating 'Access-Control-Allow-Origin' and other related headers for both local and remote web requests

It also provides additional features such as removing CSP-related headers, overwriting server status codes, and modifying headers for cross-origin frame embedding

The plugin is essential for developers working on web applications that require cross-origin resource sharing

Similar Web Traffic For https://webextension.org/listing/access-control.html

9.2M
Last Month's Visits
23.0M
Last 3 Month's Visits
--
Last 6 Month's Visits

Total Visitors

Visits Over Time

9.2M

Top Countries

Top 5 Countries

Traffic Sources

Marketing Mix

100%

4.1

121 Ratings
See all reviews

T. A.T. A.

This does not work for local html & local file. Sample html is below: --- <html> <body> <script type="text/javascript" src="https://mozilla.github.io/pdf.js/build/pdf.js"></script> <script type="text/javascript" src="https://mozilla.github.io/pdf.js/build/pdf.worker.js"></script> <script type="text/javascript"> var url = "file:///Users/amagaiwork/Desktop/sample.pdf"; var pages = [], heights = [], width = 0, height = 0, currentPage = 1; var scale = 1.5; function draw() { var ca... Show more

StephenStephen

Works very well and very well thought, by default it's disabled for security reasons but it can be enabled on a site-by-site basis by just clicking the icon, perfect for local javascript development! Also worth mentioning the plugin is opensource and also available on Firefox and Microsoft Edge in addition to Google Chrome. Kudos to the developers for such an easy and well working plugin!

alexeyalexey

Not in this case "The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute" in this case (and, in fact it will work better everywhere), header should be origin of request.