3 ms·
I've always thought of developing a Hacker's browser. One where there are no restrictions of what it can do. For example, you can't write a chrome extension to
by msie 3y ago
I've always thought of developing a Hacker's browser. One where there are no restrictions of what it can do. For example, you can't write a chrome extension to spoof the Referrer header on requests. The Chrome browser is more locked down than you think.
- hattmall 3y agoVB webbrowser control. I'm pretty sure you could do anything imaginable.
- modeless 3y agoDoesn't this one do that? https://chrome.google.com/webstore/detail/referer-control/hnkcfpcejkafcihlgbojoidoihckciin https://chrome.google.com/webstore/detail/referer-control/hn...
- msie 3y agoHmm, if you look at the reviews, it doesn't seem to work for everybody. Also seems to make a "referrer" header instead of "Referrer".
- extheat 3y agoWhat other restrictions are you referring to? This SO post seems to cover how to change headers (including Referrer) in Chrome API: https://stackoverflow.com/q/30999159/11173996 https://stackoverflow.com/q/30999159/11173996 There is also Chromium which you can build and patch if you really need low level changes to the browser not achievable from JS, but nothing immediately comes to mind to necessitate that.
- msie 3y agoIt doesn't look easy to change and even then, there is some doubt whether it works with newer Chrome versions. Anyways, the Chrome developers are purposely making hard if not impossible to change the Referrer and other headers. Part of the blame is to comply with standards but there should be some flag to turn off that behaviour.