Page 1 of 1
cloudfront.net
Posted: Tue Oct 04, 2016 5:30 pm
by ahardy42
Hi,
already got my main problem solved but while I'm here, I thought I'd ask something that's been bothering me with whitelisting.
cloudfront.net keeps occurring all over the net. What is cloudfront.net anyway?
A while back I first noticed cloudfront.net because I realised its javascript was crashing Firefox. Since then I've always banned it but have to do so everywhere it crops up because of its subdomains.
I figure there's no way of blacklisting the whole domain, but I thought I'd ask in case there is some NoScript-fu that I don't know about.
Thanks
Re: cloudfront.net
Posted: Tue Oct 04, 2016 5:41 pm
by barbaz
Cloudfront is an Amazon-owned CDN company. It's discussed in this sticky:
viewtopic.php?f=7&t=268
I'd recommend that you just leave it in default "not allowed" state, and only script-allow specific subdomains you need. I know from experience what it's like to completely block Cloudfront by default.

Re: cloudfront.net
Posted: Tue Oct 04, 2016 11:04 pm
by Thrawn
barbaz wrote:I know from experience what it's like to completely block Cloudfront by default.

Rather like blocking
*.com, I'd imagine.
Re: cloudfront.net
Posted: Tue Oct 04, 2016 11:22 pm
by barbaz
Yeah, in terms of usability, it's like letting *.com only load stuff only from *.com
If you're interested in a more detailed discussions -
viewtopic.php?f=7&t=18206
viewtopic.php?f=7&t=20339
If you're a power user, see also
viewtopic.php?f=7&t=20430&p=73814#p73814 (I now use
µMatrix for that job.)
Re: cloudfront.net
Posted: Wed Oct 05, 2016 9:03 am
by ahardy42
OK, it's good to know what cloudfront.net actually is - and that some sites actually need it to function.
My aims with NoScript (and tell me if I'm wasting my time doing it) beyond the security aspect are (1) to increase browser speed by ignoring cruft and (2) to prevent distracting adverts being loaded by script.
That's why I wanted to totally ignore cloudfront.net, and thanks for the instructions, but I think I'll follow your best practices and allow or forbid cloudfront.net subdomains on a case-by-case basis.
The slight problem about leaving *.cloudfront.net subdomains at default forbidden is that the NoScript toolbar icon and status bar will both show that something is default forbidden. I guess that's good because it'll remind me that something's blocked, so any quirky website behaviour might stem from that and prompt me to allow the cloudfront subdomain.
Thanks
Re: cloudfront.net
Posted: Wed Oct 05, 2016 3:51 pm
by barbaz
You're welcome
ahardy42 wrote:My aims with NoScript (and tell me if I'm wasting my time doing it) beyond the security aspect are (1) to increase browser speed by ignoring cruft and (2) to prevent distracting adverts being loaded by script.
Not a waste of time if you understand the limitations.
1) Definitely NoScript will speed up your browser in that way. It does for me.
2) NoScript is not an ad blocker. This side-effect only works if the ads scripts are on a totally different domain than any needed scripts.
Re: cloudfront.net
Posted: Wed Oct 05, 2016 4:15 pm
by ahardy42
barbaz wrote:
2) NoScript is not an ad blocker. This side-effect only works if the ads scripts are on a totally different domain than any needed scripts.
Yes exactly. I have come across several sites that use Javascript from other domains to load up ads, which they manage to do despite the presense of AdBlocker Plus. Presumably a deliberate move. Sorry but I can't remember which sites they were.
I just remember being surprised at the appearance of ads after allowing some sites on a new site I was visiting.
Re: cloudfront.net
Posted: Wed Oct 05, 2016 4:22 pm
by barbaz
Are those ads still unblocked if you switch ABP for
uBlock Origin?