search

RequestPolicy / requestpolicy

RequestPolicy is a Firefox extension that gives you control over cross-site requests. --- Be sure to look at the dev-1.0 branch as that's where all of the interesting work is happening. See also: https://www.requestpolicy.com/1.0.html
https://www.requestpolicy.com/
107 stars 17 forks source link

Multiple wildcards in a rule in 1.0 #337

Open alexlehm opened 12 years ago

alexlehm commented 12 years ago

I am using one site that apparently does version changes via the dns name of the appspot.com subdomain, e.g. on one day the main domain game.appspot.com points to 1-0b-dot-game.appspot.com, the next day it points to 1-0c-dot-game.appspot.com.

For this to be handled automatically the hostname wildcard requires to be *-dot-game.appspot.com or *-*-game.appspot.com, but this currently doesn't match.

alexlehm commented 11 years ago

getting back to my issue, I noticed two more sites that could benefit from this:

instagram apparently uses urls of the form destilleryimagesN.s3.amamzonaws.com (or maybe that is being used by an additional service that processes instagram images), when this is used on an additional site, you have to add about 12 rules to make a site work. This would be easier if you just could put a rule with destilleryimages*.s3.amamzonaws.com into the allowed list.

another site (8tracks.com) seems to change their cloudfront.com key every day, so it would be useful to allow .cloudfront.com but that is not possible since cloudfront.com is considered a three level url to identify the site. This would be easier if the wildcard expression could be written directly as .cloudfront.com to allow all url keys (this has a minor chance of allowing some kind of tracker url that may use cloudfront.com as well, but that is difficult to work around since the cloudfront keys are all random apparently)