Frequently asked questions

Is Wireflip a VPN or network proxy?

No. It is a request interception tool inside Chrome and Firefox. It does not route other applications, change your public IP, or provide geographic proxying.

Why did CORS Unlocker become Wireflip?

CORS repair is now one part of a broader request-lab workflow: observe traffic, change headers, redirect or block requests, return local mocks, and simulate slow or failing APIs. The new name avoids describing the product as only a CORS switch.

Will my v1 settings survive the update?

Yes. The first v2 startup performs a one-time migration, keeps a local recovery snapshot, and validates the new state. After that, v2 is the only source of truth.

Why does Chrome show a debugging banner?

Advanced mode uses Chrome’s debugger API and the DevTools Protocol to pause requests before browser CORS enforcement. Chrome always discloses this attachment. Rules mode does not use CDP and does not show the banner.

When does Advanced mode detach?

When you switch it off, close the tab, another debugger takes over, or navigate the top-level tab to a different origin.

Does Wireflip upload my traffic?

No. Rules stay in extension storage and request logs are kept in the extension service worker’s memory. The product has no traffic-upload or analytics endpoint.

Can it execute JavaScript rules?

Not arbitrary JavaScript. Wireflip accepts validated JSON action scripts. This keeps behavior inspectable and avoids MV3 remote-code and eval problems.

What can a website do through the npm SDK?

It can detect the installed extension, read status for its own origin, ask the user to enable CORS, disable its own CORS rule, open the workspace, or create a disabled rule draft. It cannot silently enable arbitrary interception, attach Advanced mode, or affect another origin.

Which npm package should I install?

After the new SDK is published, install wireflip and import { intercept } from it. It is not yet available on npm; existing users should keep cors-unlocker@0.1.0 for now. The old hostname and SDK bridge are retained, and migration is optional. See the migration guide for release status and upgrade steps.

Is Firefox supported?

Yes. Firefox uses blocking WebRequest rather than Chrome CDP. CORS, headers, redirects, blocking, delay, failure simulation, traffic inspection, the SDK, and response-body replacement are supported. Firefox preserves the server’s original HTTP status when replacing a response body, so its static mock behavior is not identical to Chrome.