3 ms·
> https://addons.mozilla.org/en-US/firefox/addon/requestpolicy/ https://addons.mozilla.org/en-US/firefox/addon/requestpolicy... I like and use RequestPolicy on
by anglebracket 13y ago
> https://addons.mozilla.org/en-US/firefox/addon/requestpolicy/ https://addons.mozilla.org/en-US/firefox/addon/requestpolicy...
I like and use RequestPolicy on a daily baiss, but unfortunately the version on AMO hasn't been updated for some time now. There are a number of long-standing issues (like clicking links in the view source view,) including one that allows bypassing the whitelist entirely [0].
>this one has better granularity (you can specify the type of content [...]
Mmm, RequestPolicy's meant to allow or deny cross-domain communications full stop. It doesn't care too much about what happens once it's allowed.
The granularity offered in HTTP switchboard is better suited to dealing with cross-domain "annoyances" than RequestPolicy.
>[...]for each (sub)domain).
Not quite the same, but RequestPolicy allows you to use the effective TLD, full domain, or scheme + full domain + port for your rules (it's under preferences.) By default it uses the effective TLD.
[0] http://blog.saynotolinux.com/2013/11/bypassing-requestpolicys-whitelist.html http://blog.saynotolinux.com/2013/11/bypassing-requestpolicy...
- pygy_ 13y ago> Not quite the same, but RequestPolicy allows you to use the effective TLD, full domain, or scheme + full domain + port for your rules (it's under preferences.) By default it uses the effective TLD. The trouble is that the setting is global. If you chose "full domain", the UI doesn't allow you to whilelist a TLD anymore, which is annoying for some CDNs (some sites change the subdomain of their CDN for each page load).
- anglebracket 13y agoYeah, that's a design issue in RequestPolicy that I'd like to see fixed. I never use the full domain option because it's such a pain to use on sites with many subdomains.