InformAction Forums

Thanks, this has been extremely helpful. I hope, though, that the NS 10 interface will change soon.

My situation: I set Default so that the default is not to run/load anything (all checkboxes unchecked).

Then I discovered a version of the issue reported by the OP here: When I tried to set certain domains to Trusted, NS would switch them back to Default, so nothing would load.

Now, when I turn the red lock on for those domains and then set them to Trusted, they remain Trusted, which is what I want.

It still seems like an awkward method, requiring a lot of extra clicks.

MyNameHere wrote:Thanks, this has been extremely helpful. I hope, though, that the NS 10 interface will change soon.

My situation: I set Default so that the default is not to run/load anything (all checkboxes unchecked).

Then I discovered a version of the issue reported by the OP here: When I tried to set certain domains to Trusted, NS would switch them back to Default, so nothing would load.

Now, when I turn the red lock on for those domains and then set them to Trusted, they remain Trusted, which is what I want.

It still seems like an awkward method, requiring a lot of extra clicks.

It's because the green lock says "allow only https" Which leaves the HTTP part in default.
That is going to get changed, if a site only HAS http, it will automatically choose the red lock.
But make no mistake you DID create a rule for https: siteinquestion.
This functionality is reasonable, because a person might want all traffic to the page be encrypted, and have it blocked when accidentally going to, or being linked to the http counterpart.

Also: This logic also applies to "untrusted" even if the locks don't show (because of course, you'd never just want to block https), but to actually BLOCK http as well you need to set it to trusted first, flip the lock to red and THEN set it to untrusted.