Need help whitelisting reCAPTCHA iframes/frames

Ask for help about NoScript, no registration needed to post
random3344

Need help whitelisting reCAPTCHA iframes/frames

Post by random3344 »

So basically what I'm trying to achieve is to globally whitelist recaptcha iframes/frames, so far I've found FRAME@https:\/\/(www\.)?google\.com to be working (I deliberately don't want to allow non-https content) but using this rule allows all frames from google.com. I tried FRAME@https:\/\/(www\.)?google\.com\/recaptcha/.* and some variations of this but it doesn't seem to be working. Is there any way to whitelist only recaptcha without whitelisting the whole google.com domain?
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:39.0) Gecko/20100101 Firefox/39.0
random3344

Re: Need help whitelisting reCAPTCHA iframes/frames

Post by random3344 »

Forgot to say that I'm editing this about:config entry: noscript.allowedMimeRegExp
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:39.0) Gecko/20100101 Firefox/39.0
barbaz
Senior Member
Posts: 11143
Joined: Sat Aug 03, 2013 5:45 pm

Re: Need help whitelisting reCAPTCHA iframes/frames

Post by barbaz »

You can't do it that way: viewtopic.php?f=7&t=17879
You need to use ABE to accomplish that
*Always* check the changelogs BEFORE updating that important software!
-
random3344

Re: Need help whitelisting reCAPTCHA iframes/frames

Post by random3344 »

And apparently using FRAME@https://google\.com actually works more like (.*)google\.com(.*), since it allows non-https and all subdomains too apparently. Why call this "regexp" when the only thing you can actually do is whitelist based on domain and port, everything else seems to be ignored.. Involving ABE rules into this is too much hassle for me so I will just have to stick to whitelisting google.com, including all subdomains, ignoring protocol. Thx for your time anyway.
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:39.0) Gecko/20100101 Firefox/39.0
random3344

Re: Need help whitelisting reCAPTCHA iframes/frames

Post by random3344 »

Correction: FRAME@https?://google\.com doesn't allow subdomains. My bad, the way this "regex" works is quite confusing and apparently not documented anywhere. Definently doesn't work like standard regex though.
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:39.0) Gecko/20100101 Firefox/39.0
Post Reply