InformAction Forums

Hi, i used the search and read the faq, but i did not find an answer to this ...

I'm using NS with Firefox and i would like to disable every scripts on every host / ip.
But ...
I would like to keep the meta refresh within html head working.
In my understanding meta refresh is a pure HTML function.
Why does NS block it ?

To temporarily allow this one site is not an option, because all sites came from the same host (some kind of proxy / tunnel) but may contain unproved content.

Thanks for your help.

make sure there are no websites in your whitelist and try
noscript options -> advanced -> untrusted -> un-check "forbid meta redirections..."
?

Poorly nothing ...

Are you sure this is NoScript blocking meta refreshes?
verify that about:config -> accessibility.blockautorefresh is set to false

Yeah, i'm sure.

accessibility.blockautorefresh is set to false

And this behavior changes if i set NS to "Allow all scripts generally" (i'm using German Version, don't know the function is named in english).

AtomicOne wrote:And this behavior changes if i set NS to "Allow all scripts generally" (i'm using German Version, don't know the function is named in english).

That does not necessarily mean NoScript is blocking the meta refreshes.

As a test, can you completely disable NoScript ("Yes, remove ALL protections"), restart browser, then go
about:config -> set javascript.enabled to false
Are the meta refreshes blocked then?
If _not_, try creating a new profile with only NoScript latest development build installed, *leaving all default settings as-is*. If the meta refreshes are blocked in this new profile, you might have found a NoScript bug; if they are allowed, you'll probably need to do Standard Diagnostic on your normal profile.

Please let us know how it goes, thanks.

barbaz wrote:As a test, can you completely disable NoScript ("Yes, remove ALL protections"), restart browser, then go
about:config -> set javascript.enabled to false
Are the meta refreshes blocked then?

No, with this configuration refreshes are working.

barbaz wrote:If _not_, try creating a new profile with only NoScript latest development build installed, *leaving all default settings as-is*. If the meta refreshes are blocked in this new profile, you might have found a NoScript bug; if they are allowed, you'll probably need to do Standard Diagnostic on your normal profile.

Please let us know how it goes, thanks.

Ok, i've done that.
Now refreshes are working for active tabs, but not for background tabs.

AtomicOne wrote:refreshes are working for active tabs, but not for background tabs.

http://htipe.wordpress.com/2010/06/24/n ... sh-option/


Unfortunately I don't know what else to say about your regular profile, sorry.

barbaz wrote:

AtomicOne wrote:refreshes are working for active tabs, but not for background tabs.

http://htipe.wordpress.com/2010/06/24/n ... sh-option/


Unfortunately I don't know what else to say about your regular profile, sorry.

HEY ... That solved my problem.

Many thanks.

But i still don't understand why NoScript blocks this.
This is not a "Script" functionality. It's pure HTML.
Anyhow ...

AtomicOne wrote: But i still don't understand why NoScript blocks this.
This is not a "Script" functionality. It's pure HTML.

To prevent tabnabbing attacks, where an ordinary page changes (in the background) into what looks like a login page, and unsuspecting users assume that something timed out and try to log back in.

Just to note, those blocks are noted in Error Console: