InformAction Forums

Hi.

This started after updating to Firefox 28 last nite. Every google result that I go into shows a 302 moved page and the yellow redirect bar for allow, deny, and more. If I hit either the allow, or the 302 moved link it brings me to the correct site.

In order to bypass this problem, I have to temp allow google.com which I've never needed to do.

I have nothing else allowed and cookies are not on. I have adblockplus, noscript, wot, and requestpolicy. I do have google.com in https cookies only, but again my cookies are not on.

I don't believe I have a redirect virus at all.

Just thought I'd post this here in case is related to something with google and noscript?

Thanks!

If you disable all extensions except for NoScript, does the problem persist?

Thank you!

It worked properly after disabling the addons. When I added them back in it was requestpolicy causing the problem.

Request policy hasn't been working properly for a few months, so I guess with another Firefox update there are even more problems with it. I saw a comment on it somewhere where one wrote that RP isn't working with x version of firefox. That was a few months ago. I've had problems too, so, I know what the person means.

I need to keep RequestPolicy on, so I guess I'll be having this google problem occur.

Thank you so much therube!

Seems it works sometimes or not. Today it also doesn't for me. See more:
http://forums.informaction.com/viewtopi ... 592#p68592

If you disable RequestPolicy, you just don't see any longer, that you are redirected by google, what NoScript tries to avoid usualy.

If you install the latest development build from http://noscript.net/getit#devel , you should no longer be redirected. And you could enable RequestPolicy again.

Seems this is back again. I get redirects on google searches, which are blocked by RequestPolicy (continued).

Not seeing that here with google forbidden and NoScript 2.6.9.22rc1... have you got any custom user scripts for google or have you modified about:config > noscript.surrogate.glinks.* preferences?

With version 2.6.9.22 it works as expected, so it's a regression, which came with 2.6.9.23rc1

OK looks like the glinks surrogate is just plain gone from 2.6.9.23rc1. Wonder what else changed...

Weirdly though, according to the diff - and digging in the source - it's still there... and I don't see anything obvious that would cause it to disappear...

Ah, found it.
Giorgio, you're missing a semi-colon after the 2mdn surrogate replacement and it's killing a bunch of default prefs...

Fixed in 2.6.9.23rc2, thanks Giorgio