CORS Switch — Allow CORS per site

Fix CORS errors while you develop: allow CORS only for the sites you pick, with cookies supported and automatic shut-off.

Getting "blocked by CORS policy" while you develop? CORS Switch lets your app call any API by adding the right Access-Control-Allow-Origin headers — only for the sites you choose, and only for as long as you need. HOW IT WORKS 1. Open your app (for example http://localhost:3000). 2. Click the CORS Switch icon and turn it on for this site. 3. Reload — your fetch and XHR requests to other domains now pass the CORS check. WHY DEVELOPERS USE IT • Per-site, not global — CORS is allowed only for requests made by the sites you enable. Every other website keeps normal browser security. • Credentials that work — CORS Switch echoes your exact origin and sets Access-Control-Allow-Credentials, so requests with cookies or an Authorization header work. Most "Allow CORS" extensions send "*", which browsers reject for credentialed requests. • Preflight headers — PUT, PATCH, DELETE and common headers like Authorization and Content-Type are allowed. • Auto shut-off — each site switches off automatically after 1 hour, so you never browse the web with CORS disabled by accident. • Always visible — the toolbar icon shows ON when CORS is allowed for the current tab. • Private by design — built on Chrome's declarativeNetRequest API. No account, no analytics, no data collection. Your requests never leave your browser. CORS SWITCH PRO (coming soon) Unlimited sites, custom shut-off timers, extra allowed headers and settings import/export. See https://cors.zelenye.com GOOD TO KNOW • Use CORS Switch for development and testing, not for everyday browsing. • If a server answers the OPTIONS preflight with an error status (404/405), the browser still blocks the request — an extension cannot change status codes. Questions or bugs: support@zelenye.com