Add, replace, or strip HTTP request and response headers. No content scripts. No page access. No ads.
Users
6
−2 in 30 days
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
0 in 30 days
Store rank
#238K
#199K among extensions
Version
0.1.0
updated 6 Aug 2026
Users
monthly, 2 months
Latest, 16 Oct 2026:6 usersMove the mouse over the chart for any month
Ratings count
monthly, 2 months
Latest, 16 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About Interpose — Modify HTTP Headers
Interpose edits the HTTP headers your browser sends and receives.
Set an Authorization token, spoof a User-Agent, strip a Referer, add a debug
flag, force a CORS header on a response, or point a URL somewhere else. One
click to switch it all off.
WHAT IT DOES
• Request headers — set, append to, or remove
• Response headers — the same three operations
• Redirects — match a URL pattern, send it elsewhere
• Profiles — separate setups for local, staging, production; switch in a click
• Scope — apply everywhere, or only to URLs matching a pattern
• Exclusions — domains it will never touch, whatever else is configured
• Dynamic values — {{uuid}}, {{timestamp}}, {{isotime}}, {{random}}, {{randint}}
• Import / export — plain JSON, no account needed
• Master switch — off means no rules are registered at all
WHAT IT DOESN'T DO
No content scripts. Interpose never runs code inside your pages — it cannot
read what you type, see what you browse, or inject anything into a site. The
permission that would allow that is not in its manifest, so this is a
structural guarantee rather than a promise.
No network calls. Nothing you configure leaves your machine. There is no
account, no sign-in, no sync server, no analytics, and no telemetry.
No ads. Not now, not in a later update.
Permissions requested, in full:
• declarativeNetRequest — the only API Chrome offers for changing headers
• storage — saves your rules on your own machine
• host access — Chrome requires it before any header rule can apply
Header changes happen through Chrome's declarativeNetRequest API, at the
network layer, without the extension ever seeing your page.
MOVING FROM ANOTHER HEADER EDITOR
Interpose reads ModHeader's exported profiles directly. Open the menu, choose
Import, pick your export file — your headers, response headers and URL
replacements come across with their enabled states intact.
HONEST LIMITATIONS
Two things Chrome does not allow any extension to do, so you know before you
install rather than after:
• accept-encoding cannot be changed. Chrome rewrites it after extensions run,
because it has to control which compression formats it can decode.
• append works only on a fixed list of request headers that Chrome permits
(accept, accept-language, cache-control, cookie, user-agent, and a handful
of others). Use set for anything else.
Dynamic values like {{uuid}} resolve when rules are compiled, not per request —
Chrome's rules hold fixed values once registered. Press the ↻ button to roll
new ones.
OPEN SOURCE
The whole extension is under 1,000 lines with no dependencies and no build
step. The file that decides what happens to your traffic is about 200 lines,
and the "src" link in the extension footer opens it straight from your own
installed copy. You can check that every claim on this page is true without
taking anyone's word for it.
Source: https://github.com/nicholaswekesa75-arch/Interpose
MIT licensed.
Growth
Window
Users
Change
Ratings
Rating
7 days
−1
−14.3%
0
0.00
30 days
−2
−25.0%
0
0.00
Chrome Web Store search rankings
Where Interpose — Modify HTTP Headers appears when people search the store, with the 30 day change