dingoeatingfuzz / chrome-headers-middleman Goto Github PK

In addition to a relaxed whitelist pattern, more specific blacklist patterns would be convenient. For instance, blacklisting an auth end point removes a lot of confusion.

Many of the other header-modifying addons have the super useful feature of being able to toggle with a click.

Note: I'm not sure if this is the right place to report this issue, as I haven't tested the Chrome version, but @WyohKnott disabled issues in his fork for the Firefox port and the AMO page links here for support.

It seems that headers are only set on document requests, and not other types of requests such as script. For example, I set X-Forwarded-For to 3.157.156.231 on nick.com and mtvnservices.com, but the page doesn't load correctly, possibly due to missing headers on the other requests.

Sometimes it's desired to temporarily pause a rule. Right now the only way to do this is removing the header completely. This often works, but it's obviously not the right thing to do.