Whitelisting HTTP sites if JS is allowed for HTTPS only?

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

Whitelisting HTTP sites if JS is allowed for HTTPS only?

Post by Guest »

I have NS configured to temporarily allow JavaScript for the current top-level site, and would like to restrict active content to HTTPS connections. However, I need access to some HTTP sites with JavaScript that wouldn't work in this configuration. Is there a way - perhaps by setting an about:config variable - to allow active content for all HTTPS sites *and* HTTP sites whitelisted as http://host.dom.ain entries?
Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20100101 Firefox/17.0
barbaz
Senior Member
Posts: 11068
Joined: Sat Aug 03, 2013 5:45 pm

Re: Whitelisting HTTP sites if JS is allowed for HTTPS only?

Post by barbaz »

Don't temp-allow JS for the current top-level site;
add "https:" to your whitelist (without the quotes, is also case-sensitive)
then go to NoScript Options -> Appearance, uncheck Base 2nd-level domains and Full domains if you want, but make sure to check Full addresses
now you should just be able to use the NS menu to do what you want.
*Always* check the changelogs BEFORE updating that important software!
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 SeaMonkey/2.21
Guest

Re: Whitelisting HTTP sites if JS is allowed for HTTPS only?

Post by Guest »

This is exactly what I want to avoid: cluttering the whitelist with lots of https:// entries - because I've noticed that I'm browsing more HTTPS than HTTP sites.
Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20100101 Firefox/17.0
barbaz
Senior Member
Posts: 11068
Joined: Sat Aug 03, 2013 5:45 pm

Re: Whitelisting HTTP sites if JS is allowed for HTTPS only?

Post by barbaz »

Guest wrote:This is exactly what I want to avoid: cluttering the whitelist with lots of https:// entries
???
With those settings you would only have the one entry "https:" taking the place of all that for you - one entry isn't exactly clutter IMO. You need to type that in NoScript Options -> Whitelist manually; NoScript won't offer you that option in the menus or the GUI at all.
*Always* check the changelogs BEFORE updating that important software!
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 SeaMonkey/2.21
Guest

Re: Whitelisting HTTP sites if JS is allowed for HTTPS only?

Post by Guest »

Sorry for misunderstanding you - I didn't read your reply carefully and thought I'd have to add one https://host.dom.ain entry for each HTTPS site. Whitelisting "https:" (without quotes) does the trick, thanks a lot!
Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20100101 Firefox/17.0
User avatar
Thrawn
Master Bug Buster
Posts: 3106
Joined: Mon Jan 16, 2012 3:46 am
Location: Australia
Contact:

Re: Whitelisting HTTP sites if JS is allowed for HTTPS only?

Post by Thrawn »

And be careful doing this, because although it's not quite as bad as allowing scripts globally, it is close.
======
Thrawn
------------
Religion is not the opium of the masses. Daily life is the opium of the masses.

True religion, which dares to acknowledge death and challenge the way we live, is an attempt to wake up.
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
Post Reply