Norton meta redirect not getting blocked?

[Grumpy Old Lady]

Something weird going on and I don't have a lot of time this evening to do a proper screenshot post, so will just link to the page with a quick description and see if anyone else can reproduce.

In a clean profile, all NS defaults, go to
http://safeweb.norton.com/dirtysites
It goes to a noscript redirect message style page - - reports to me that it needs JS, but when I toggle norton.com, the same page - a noscript redirect message comes up.

In my own custom profile the redirect was blocked, as expected. I tried it a few times, and at one call the NS blue "redirect has been blocked" message flashed up briefly and then was overlaid by the NS notification bar, which had been migrated to the top of the page for just this time. A really big display change, very noticeable. But there were no NS messages in the console.
However, after I'd disabled NS to test toggling JS, then enabled it again, the redirects weren't being blocked - - I now have the noscript redirect page served with both norton.com toggled allow or forbid.
Something's getting in before NS?
I have a very variable amount of latency on this connection.
Sorry I have to rush out now. I shall check in tomorrow if possible.

[therube]

Are you sure you are (re)loading the /dirtysites/ web page & not the /noscript/ page?

Code: Select all

<noscript>
	<meta http-equiv="REFRESH" content="0;URL=/noscript/">
</noscript>

Once you have gone /noscript/ you never go back . So you have to reopen http://safeweb.norton.com/dirtysites.

All looks to be working as expected here.

Blocked, goes to /noscript/.
Allowed loads normally.
Blocked & with Forbid META redirections enabled also loads normally.

(Now I have run across some really screwy sites that still do not work correctly even after being Allowed. Doing things like storing the /noscript/ error in a cookie.)

[Grumpy Old Lady]

Quoth therube

Once you have gone /noscript/ you never go back ;-)

Ah,I don't get around much, do I. ... if I had a brain I'd be dangerous :-)
The poor visitor using the default NS was somewhat disbelieving about my "just toggle NS if a page doesn't work" ha ha.