HeaderWright — Modify HTTP Headers

Set and remove HTTP request and response headers by profile; append on request only. No webRequest — it cannot read your traffic.

Set and remove HTTP request and response headers, organized into profiles you switch on and off. Append works on request headers. No webRequest permission — nothing in the extension can read your traffic, and you can verify that by reading the manifest. What it does: - Header profiles — set or remove request and response headers, or append to request headers, grouped and named so you can keep separate setups for separate jobs - What you see is what Chrome has registered — each profile card lists the rule Chrome currently holds, one line per header (side, operation, full name, value), read back from the browser rather than from what was saved. HeaderWright does not inspect traffic, so whether a rule changes a particular request is a separate question from whether Chrome has registered it. - Per-domain scoping — each profile applies only to the domains you list (subdomains included) - Master on/off toggle, with a badge that reports the result of the last registration: ON or OFF when it succeeded, and a warning when it failed or left some profiles unregistered - Import and export profiles as plain JSON — deterministic and byte-stable, so you can keep a setup in git Permissions, up front: - Built entirely on Manifest V3's declarativeNetRequest API. No webRequest, so there is no code path that can observe your requests. - No access to any site at install. When you add a profile for a domain, the browser asks for permission on that domain and its subdomains only — and you can revoke it per domain at any time. - No account, no sync, no backend, no telemetry. Profiles live in local extension storage. Source: github.com/antrixy/headerwright Response headers support set and remove; append is request-only for now. Requires Chrome 116 or later.