InformAction Forums

Hi,

trying to call up localhoste.631 (CUPS) - that works.
Navigating to printers: http://localhost:631/printers/ - blank page.
adding localhost as trusted site and reload - setting jumps back to 'Default'
Solution - disable NoScript
Bug or feature?
TIA!

DocB wrote:Hi,

trying to call up localhoste.631 (CUPS) - that works.
Navigating to printers: http://localhost:631/printers/ - blank page.
adding localhost as trusted site and reload - setting jumps back to 'Default'
Solution - disable NoScript
Bug or feature?
TIA!

1. Should be moved to support forum [@mods]
2. Which version of noscript?
3. did you correctly choose the red lock, or maybe assume that putting it to green was"locking" the rule?

Sadly I don't have any service running to test it with, but creating a red(lock) http://localhost rule worked, it did stick, and even was nice enough to convert it to a red "...127.0.0.1" rule automatically.

edit: noscript 10.1.3 (shouldn't ask when I don't write it myself )

I'm using verson 10.1.2rc1

There is no lock shown - just when I set it to 'Trusted' it switches back after reload.
In Noscript-settings, entry for localhost is green, but obviously ignored

DocB wrote:I'm using verson 10.1.2rc1

There is the start of your problem.

Upgrade to 10.1.3 (or 10.1.3c3 if you seriously mind the resize bug)
And then recheck your permissions for the scopes (default trusted untrusted), and also confirm that in the debug output at the bottom of the options page.

There is no lock shown - just when I set it to 'Trusted' it switches back after reload.
In Noscript-settings, entry for localhost is green, but obviously ignored

The entry itself shouldn't be green. If the lock is green the rule should be black (but it means you made a rule for HTTPS://*127.0.0.1 which is not what you wanted)
If you want to make a rule that pertains to http, you need to set the lock to red which will then in turn make the entry text be red, too.

10.1.3 also brings back the specific difference between making a domain wide rule [...page] or a URL specific one [http(s)://sub.page.dom]
the redlock on the [...page] rules means both https and http, the urls specific ones pertain to either/or specifically

download link for versions:
https://addons.mozilla.org/en-US/firefo ... /versions/

DocB wrote:Bug or feature?

Neither. You have a support question.

I tested with CUPS on Ubuntu. Both NoScript 10.1.2rc1 and 10.1.3 behave as expected for me. But the behavior of NoScript 10.1.3 is more intuitive, so +1 to upgrading. atm you'll need to upgrade manually, as the dev channel is currently lagging behind a few versions.

Moving to NoScript Support as suggested by Pansa.

Hi,
after upgrade to 10.1.5.1 this issue is fixed, thanks.

Still 2 major topics left:
- black screen when switching tabs
- empty popup with some xss warning, when accessing third party site for login (see: bugzilla.opensuse.org -> login)

Are there separate bugs open for these?

DocB wrote:Are there separate bugs open for these?

Feel free to use the forum search, this is what it's there for.

DocB wrote:- black screen when switching tabs

Search turned up https://forums.informaction.com/viewtop ... =7&t=24027