Feature Request: allow *.domain.tld inside one url

Bug reports and enhancement requests
Post Reply
SpoonOfDoom
Posts: 3
Joined: Wed Nov 29, 2017 8:27 am

Feature Request: allow *.domain.tld inside one url

Post by SpoonOfDoom »

I have a feature request: I'd like to be able to allow all subdomains of a certain domain if they're loaded by a certain site. To make clear what I mean, my use case is the following:

I use the AWS web console quite a bit. That site loads some of its scripts from cloudfront, which apparently uses a procedurally generated url, e.g. d1idiovbex4hy4.cloudfront.net.
My problem is, every few days/weeks these cloudfront urls seem to be regenerated, and the page content stays blank. I need to allow these new urls by hand, and my whitelist slowly fills up with random cloudfront urls. But I don't want to just generally allow everything from cloudfront, because that might also be used by less trustworthy sites.
What I'd like to be able to do is: allow *.cloudfront.net if I'm on console.aws.amazon.com, but not automatically on other domains.
I'm not sure how the old NoScript versions handled this, but I'm pretty sure I didn't need to deal with this back then, once I had allowed everything for console.aws.amazon.com.
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Tomatix
Senior Member
Posts: 60
Joined: Tue Dec 05, 2017 3:05 pm

Re: Feature Request: allow *.domain.tld inside one url

Post by Tomatix »

I think your suggestion belongs here: https://forums.informaction.com/viewtop ... =7&t=24023
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
barbaz
Senior Member
Posts: 11066
Joined: Sat Aug 03, 2013 5:45 pm

Re: Feature Request: allow *.domain.tld inside one url

Post by barbaz »

SpoonOfDoom wrote:What I'd like to be able to do is: allow *.cloudfront.net if I'm on console.aws.amazon.com, but not automatically on other domains.
So you are asking two things -

1) Bring back ability to allow entire TLDs (see the thread Tomatix linked)

2) Per-site permissions (already planned)
SpoonOfDoom wrote:I'm not sure how the old NoScript versions handled this, but I'm pretty sure I didn't need to deal with this back then, once I had allowed everything for console.aws.amazon.com.
Old NoScript versions were able to allow *.cloudfront.net, and per-site permissions were possible using ABE.
*Always* check the changelogs BEFORE updating that important software!
-
Post Reply