Thanks for your answer, let's try to find where is the error.
Tom T. wrote:
Unable to reproduce on Win XP, Fx 12.0, NS 2.4.1rc3, even after multiple page reloads resulting from allowing the disqus script and its related items in Blocked Objects menu -- and that's with the additional ABE NAT-pinning rule discussed here.
Notice that I don't even get to that point, I only see an empty page with the ABE warning on the top.
Tom T. wrote:
Have you added any ABE rules beyond the default SYSTEM rule?
No, I've never touched the ABE rules.
Tom T. wrote:
I've tried with a freshly created FF profile and it is still happening.
Try a freshly-created profile with a fresh install of NS, and *no* other add-ons, to eliminate the possibility that the problematic system has an extension conflict.
This is exactly what I've done, I created a new profile and installed NoScript 2.4.1 from mozilla addons.
Tom T. wrote:If you have access to other systems, or if anyone else can reproduce on, say, Mac, etc., please advise.
I've been able to reproduce it on two other systems:
- CentOS, FF 12.0 downloaded from the official website
- Red Hat EL, using FF 10.0 distributed with the system
Once again I tested with new profiles where I've only installed NoScript 2.4.1.
It also happens when I search for that URL in google and I follow the link but in this case the warning instead of chrome://... shows what looks like the referrer URL.
Thanks for your answer, let's try to find where is the error.
[quote="Tom T."]
Unable to reproduce on Win XP, Fx 12.0, NS 2.4.1rc3, even after multiple page reloads resulting from allowing the disqus script and its related items in Blocked Objects menu -- and that's with the additional ABE NAT-pinning rule discussed here.
[/quote]
Notice that I don't even get to that point, I only see an empty page with the ABE warning on the top.
[quote="Tom T."]
Have you added any ABE rules beyond the default SYSTEM rule?
[/quote]
No, I've never touched the ABE rules.
[quote="Tom T."]
[quote] I've tried with a freshly created FF profile and it is still happening.[/quote]
Try a freshly-created profile with a fresh install of NS, and *no* other add-ons, to eliminate the possibility that the problematic system has an extension conflict.
[/quote]
This is exactly what I've done, I created a new profile and installed NoScript 2.4.1 from mozilla addons.
[quote="Tom T."]If you have access to other systems, or if anyone else can reproduce on, say, Mac, etc., please advise.[/quote]
I've been able to reproduce it on two other systems:
- CentOS, FF 12.0 downloaded from the official website
- Red Hat EL, using FF 10.0 distributed with the system
Once again I tested with new profiles where I've only installed NoScript 2.4.1.
It also happens when I search for that URL in google and I follow the link but in this case the warning instead of chrome://... shows what looks like the referrer URL.