Headers not set on some requests

[ghost]

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.

[DingoEatingFuzz]

I took a few minutes to do some preliminary investigating and I believe the issue is with this line: https://github.com/DingoEatingFuzz/chrome-headers-middleman/blob/master/background.js#L8

Chrome (and probably Firefox) provides the type of web request, and right now headers middleman only intercepts main_frame ones.

I'm sure I had a reason for this, but it's lost to the sands of time at this point.

I recommend forking, experimenting, and reporting your findings. Did it work as expected? Were there unintended consequences?

If it worked well, we can merge it in. If there were side effects, we can consider options. For instance, having a set of web request types applicable per rule or ruleset.