InformAction Forums

Hello,

I love NoScript and have been using it for years, however there's something I've always felt was lacking.

Consider the following: I regularly use a website example.com which makes use of a CDN cdn.com. Thus I want to access example.com, allowing its use of JavaScript, both on its own domain and cdn.com while still asking, on other websites, for use of cdn.com

If I use ABE to achieve this, with rules like the following,
I can access example.com with cdn.com allowed, however, on any other websites, I don't have the option to temporarily allow cdn.com, which is blocked by ABE.

Is there any other way to go about this problem which I'm not aware of?

Thanks.

Thrawn wrote:RequestPolicy

Thanks a lot Thrawn.

So, if I install RequestPolicy, from what I understand, and in this particular example, I should allow cdn.com on NoScript and selectively allow it with RequestPolicy, is that it?

That's correct.

There will be a lot of double-handling, I'm afraid, but it's currently the easiest way to handle this.

I'm working on an ABE interface that might help, but it's not ready for public usage yet.

Thank you very much once again.

I'm actually liking it, since it allows some granularity, like its separate lists for "Origin", "Destination" and "Origin-to-Destination".

Can you please tell me if RequestPolicy is able to block JavaScript?

Kailyn wrote: Can you please tell me if RequestPolicy is able to block JavaScript?

It will block cross-site JavaScript, because it will block the request that would download it.

It won't stop JavaScript coming from the site that you visit. NoScript handles that.