InformAction Forums

Sorry if this question has already been asked, I have used noscript for a very, very long time so I've had this problem for years. I'm sure others have run into this.

But how do we handle random subdomains like xxxx.cloudfront.net for example? I can allow the main domain, but every visit I have to temporarily allow these random subdomains.

A feature I've had on my wishlist for a long time is some sort of main domain context aware whitelisting where if I'm on imdb.com then *.cloudfront.net is allowed, but nowhere else.

In my experience those aren't random.

When you figure out which specific cloudfront.net domains imdb needs, you can set them CUSTOM with contextual permission for imdb (click the "ANY SITE" drop-down in the NoScript popup). Then when reviewing NoScript Options > Per-site Permissions, knowing why you have these cloudfront.net domains listed only requires looking at what contextual permissions are set.

Setting contextual permission for all cloudfront.net domains is possible too, but you would need to do it manually along the lines of viewtopic.php?p=106460#p106460
Do note that each subdomain of cloudfront.net can be owned by a different site, so it is not unlike allowing *.com

I hope you're right, I honestly haven't noticed if they've changed for sure on sites I often use like imdb.com, only assumed.

But the biggest issue is actually on most of aws consoles, where they load a whole list of random cloudfront subdomains sometimes.