Headers only rules 🆕

A Headers only rule rewrites HTTP headers and does nothing else. It never touches the response body, the status code or the timing. If a request matches, its headers are edited and the request carries on exactly as it would have.

Why it is a separate rule type

Mock and Modify rules can already set headers, so a rule type dedicated to them only earns its place because it works differently. It is applied by the browser itself instead of by tweak inside the page, and that buys three things:

1. It reaches every request, not just the ones your JavaScript makes with fetch or XMLHttpRequest. Page navigations, <script>, <img>, stylesheets, fonts and beacons are all in scope.
2. It can set headers the page is forbidden from setting. Referer, Origin, User-Agent and the other forbidden header names are a fetch/XHR restriction. The browser is not the page, so the restriction does not apply here. Try to set one on a Mock or Modify rule and tweak will tell you as much, and point you back at this rule type.
3. It can stay on when tweak is stopped, see scope below.

What you give up is everything that needs the page: no response payload, no hooks, no logpoints or breakpoints, no delay, no status code, and no count of intercepted requests. The rule row hides those fields rather than showing them disabled.

The two tables

A headers only rule has exactly two tabs, one per direction:

• Response headers: applied to what comes back, before the page sees it.
• Request headers: applied to what goes out, before it leaves the browser.

Both use the same table as Mock and Modify rules, plus one extra column.

The Operation column

Each row picks what to do with the header:

Operation	What it does
Set	Replaces the header value, or adds the header when it is missing.
Append	Adds a value next to the existing one instead of replacing it.
Remove	Strips the header out entirely.

Appending to request headers is limited

Browsers only accept Append on a fixed list of request headers. Pick it on any other request header and the Key cell turns red with an explanation. The row is kept, but it will be applied as Set. Response headers have no such restriction: appending a second Set-Cookie is one of the main reasons to use this rule type.

The request headers that do support Append are Accept, Accept-Encoding, Accept-Language, Access-Control-Request-Headers, Cache-Control, Connection, Content-Language, Cookie, Forwarded, If-Match, If-None-Match, Keep-Alive, Range, TE, Trailer, Transfer-Encoding, Upgrade, User-Agent, Via, Want-Digest and X-Forwarded-For. The extension does not spell them out, so this page is the full list.

tip

While a row is set to Append, the Key autocomplete narrows to that list, so you cannot accidentally type a header the browser will refuse.

Scope: where the rule applies

Headers only rules replace the Status code and Delay fields with a Scope dropdown.

Scope	Behaviour
Active tab	The default. Applied only while tweak is running, and only on the tab it is running on, like any other rule.
Global	Applied on every tab, whether or not tweak is running, and it survives a browser restart.

Global is the advanced option. It is useful when you want an override to simply be on (a proxy header on every tab, all day), but it is also the harder mistake to undo, because stopping tweak does not turn it off.

caution

While at least one enabled Global rule exists, the run/stop button is locked in the running state. tweak cannot honestly claim to be paused while the browser is still applying your overrides on every tab. To stop them, disable the rule with its own switch.

Matching

The url expression and the regular expression toggle work the same way as on any other rule, with one difference worth knowing: the browser's matcher is RE2, which does not support backreferences or lookahead. If you write an expression the browser cannot compile, the rule row tells you instead of silently doing nothing.

The HTTP method dropdown accepts * to match any method, which is what a new headers only rule starts with.

What the free plan gets

Here's a quick overview on free vs. paid capabilities.

Capability	Free	Paid
Response headers, Set	✅	✅
Response headers, Append / Remove	❌	✅
Request headers (any operation)	❌	✅
Both scopes	✅	✅

Defaults

Switching a rule to Headers only seeds it so that it already does something: the url expression becomes .* with the regex toggle on, the method becomes *, the scope is Active tab, and one X-Powered-By: tweak row is added to the response headers table. An empty url expression would install no rule at all, so a freshly switched rule would otherwise look enabled while doing nothing.

Any field you have already edited is left alone.

---

Was this page helpful?

Need something else? Request a feature

  Thanks for your feedback!