InformAction Forums

Can I block meta refresh element with NoScript?

NoScript blocks some meta refresh elements (those inside <noscript> elements) because they're often used to redirect users with JavaScript disabled on a silly pages just saying they must enable it.
If you want to block any meta refresh element, just open Tools|Options|Advanced|General and tick the "Warn me whenever a web site tries to redirect me" checkbox.
Otherwise, if you want to block them on per-site basis, you can use the Refresh Blocker extension.

Thanks!

Giorgio Maone wrote:NoScript blocks some meta refresh elements (those inside <noscript> elements) because they're often used to redirect users with JavaScript disabled on a silly pages just saying they must enable it.
If you want to block any meta refresh element, just open Tools|Options|Advanced|General and tick the "Warn me whenever a web site tries to redirect me" checkbox.
Otherwise, if you want to block them on per-site basis, you can use the Refresh Blocker extension.

I try to block meta refresh in SM 2.0b2, which has no such setting. RefreshBlocker doesn't work, even in blacklist mode. NoRedirect works blocking redirects, but I can't block meta refresh, don't know what I do wrong or if it just doesn't work in SM.
Would ABE do it?

Mc wrote:Would ABE do it?

Nope, unless you know the destination in advance.

Giorgio Maone wrote:

Mc wrote:Would ABE do it?

Nope, unless you know the destination in advance.

It's just a site refresh, no redirection.

Mc wrote:It's just a site refresh, no redirection.

No, then.

Yes RefreshBlocker looks to be incompatible with SeaMonkey 2. (It says so once you install it, & then it looks to be ineffectual when you add a site to block.)

Further the Preference item accessibility.blockautorefresh (which does exist & work in FF3) does not exist or work in SeaMonkey 2 .


Sample META Refresh webpage (click the like this example link).
PS: To get refreshblocker to block that page, I placed ^.*fluffbucket in the blacklist (using FF).

therube wrote:Yes RefreshBlocker looks to be incompatible with SeaMonkey 2. (It says so once you install it, & then it looks to be ineffectual when you add a site to block.)

Further the Preference item accessibility.blockautorefresh (which does exist & work in FF3) does not exist or work in SeaMonkey 2 .


Sample META Refresh webpage (click the like this example link).
PS: To get refreshblocker to block that page, I placed ^.*fluffbucket in the blacklist (using FF).

In Fx I use just the setting which toggles accessibility.blockautorefresh to cover unknown refreshing sites. For SM exists an unconfirmed bug about that setting https://bugzilla.mozilla.org/show_bug.cgi?id=465303

The Web Developer extension does work in SeaMonkey 2 & does have an options to Disable Meta Redirects (among many other things).

therube wrote:The Web Developer extension does work in SeaMonkey 2 & does have an options to Disable Meta Redirects (among many other things).

Thanks therube that works, a little bit weird though so I needed some time testing. Seems it always allows one refresh.
AMO doesn't list that extension for SeaMonkey, BTW

Mc wrote: I try to block meta refresh in SM 2.0b2, which has no such setting. RefreshBlocker doesn't work, even in blacklist mode.

Version 0.5.1 from the developer's site http://www.vakuumverpackt.de/refreshblocker/ works in SeaMonkey (after the known modifications).

Giorgio Maone wrote:

Mc wrote:Would ABE do it?

Nope, unless you know the destination in advance.

Regarding this RFE, the only redirect that promped the RFE at this time always has destination http://www.yahoo.com.

I'd still like the feature in general, but what would the ABE rule be to prevent being redirected from mail.yahoo.com to http://www.yahoo.com upon logout of mail -- without interfering with login and navigation within mail, of course? Thanks.