Why does my response rule not appear in DevTools Network?
The Network panel may show the server’s original wire response. HeaderForge modifies eligible response headers while Chrome processes the response for the application. Test the application behavior or inspect a JavaScript-readable header in page code.
Why is my request Append rule inactive?
Chrome supports request Append only for a fixed set of lowercase standard header names. Use Set for custom request headers.
What is the difference between Set and Append?
Set replaces the current value. Append adds another value where the header format supports multiple values. Set is the normal choice for custom headers and single-value headers.
What does Remove do?
Remove deletes the named header from a matching request or response. No value is needed.
Can HeaderForge disable CORS or CSP?
No. HeaderForge can request eligible response-header changes, but browser security enforcement is not reliably bypassed by changing headers. Use a development server, proxy, or explicit test configuration instead.
Why did my rule not apply?
Check that the rule and global switch are enabled, the header name is valid, and the URL filter matches the request URL. Also account for caches, service workers, redirects, browser restrictions, and other extensions.
Are my rules private?
Rules are stored locally in chrome.storage.local. Export is the only feature that copies them outside the extension, and it copies them to your clipboard.
Which browsers are supported?
HeaderForge targets current Chromium browsers that support Manifest V3 and the required Declarative Net Request APIs, including Chrome, Edge, Brave, Arc, and Opera.
Need an answer that is not listed here? Contact HeaderForge support.