Block META redirect within NOSCRIPT element at Google search

[Mc]

Oh, I didn't see al_9x posted about the blank page above. So let's wait. It's Sunday

[Decklan]

I'm trying NoScript 2.1.9rc2 at default settings and I'm still getting a blocked redirect but try change "noscript.forbidMetaRefresh" to false and see what happens while browsing. Surprising.

Sorry do not read what I wrote in this post. I'll sleep a little to avoid stupidity.

No worries.
The sleep suggestion was for Giorgio. I thought he might be an hour ahead of you, but it looks like you're in the same time zone.
So I guess it was for both of you. The issue will still be there tomorrow.

Thanks Tom T. you are right it was later and it was time to sleep for me too. Sunday another day. I'll explain my stupidity "noscript.forbidMetaRefresh" option concerns with the gui option "Forbid META redirections inside <NOSCRIPT> elements" the value true/false enable/disable it. Suddenly I was browsing almost normally, only catch little message of NoScript link (or redirection) before load well the destination web, but it was because I disabled Forbid META redirections inside <NOSCRIPT> elements when I set "noscript.forbidMetaRefresh" to false. Then I thought "go to sleep".

Thanks to all.

[Decklan]

By the way Firefox has its own light Meta Redirect blocker (Tools - Options - Advanced - General - Accessibility - ‘Warn me when web sites try to redirect or reload the page’). Will it have the same behavior? if so Firefox developers should have the same problem. Firefox 8 release in few days.

[Uncle Squid]

Using NoScript 2.1.9rc2, the default noscript.forbidMetaRefresh.exceptions did not work for me.

I had to change it from this:

Code: Select all

^https?://www\.google\.(?:[a-z]{2,3}|[a-z]{2}\.[a-z]{2,3})/search\?q=

to this:

Code: Select all

^https?://www\.google\.(?:[a-z]{2,3}|[a-z]{2}\.[a-z]{2,3})/(search\?.*q=|url\?url=)

[Mc]

Code: Select all

^https?://www\.google\.(?:[a-z]{2,3}|[a-z]{2}\.[a-z]{2,3})/(search\?.*q=|url\?url=)

doesn't work here either.

[al_9x]

Code: Select all

^https?://www\.google\.(?:[a-z]{2,3}|[a-z]{2}\.[a-z]{2,3})/(?:search|url)\?

This should match search and redirect pages.

[Giorgio Maone]

Code: Select all

^https?://www\.google\.(?:[a-z]{2,3}|[a-z]2\.[a-z]{2,3})/(?:search)|(?:url)\?

This should match search and redirect pages.

Image results are affected as well, and I suspect other stuff is too.
I'm gonna change the preference to just

Code: Select all

^https?://(?:www|encrypted)\.google\.(?:[a-z]{2,3}|[a-z]2\.[a-z]{2,3})/ t.co

in next build (including Twitter's URL shortener).

[al_9x]

Image results are affected as well, and I suspect other stuff is too.

Images and pretty much all searches now go through /search. Perhaps those who don't have google whitelisted can report if they encounter useful redirect blocking on google. If not, exempting all of google is ok, otherwise search|url should suffice.

[Tom T.]

it looks like when google wants to redirect, the page is there and functional, but hidden by a style in <noscript>, and it can be unhidden. Not sure if this is preferable to letting it refresh, but it's an option.

sources="!www.google.com/search?"
replacement="if (getComputedStyle(document.body).display === 'none') document.body.style.display = 'inherit';"

Thanks, but the ideal would be if Giorgio is able to make this unnecessary by tweaking the rc build again. Awaiting that.

In the meantime, the useragent switch is a cool work-around, and I still prefer the script-free, cookie-free, non-refresh alternative. IMHO. YMMV.

[Giorgio Maone]

Please check latest development build 2.1.9rc3.

@al_9x:
I'm talking about links to result details/pages, like
http://www.google.it/imgres?imgurl=http ... CFsQ9QEwBg

[Tom T.]

Please check latest development build 2.1.9rc3.

Yes, on Fx 3.6.23, NS 2.1.9rc3, Google script and cookies blocked, search results do appear, and the links work fine.

*But* ... there is still notification of NS blocking a META refresh at the top. Since everything works now, this can be ignored, but is it possible to make it go away? -- just for the annoyance? If it's too much trouble, no worries.

Edit:

By the way Firefox has its own light Meta Redirect blocker (Tools - Options - Advanced - General - Accessibility - ‘Warn me when web sites try to redirect or reload the page’)

I activated that, out of curiosity. (Always have relied on NS's.) When I submitted a post, it blocked the automatic return to my posted message, and I needed either to click "allow" or to click "return to your message". I like NS's wiser selectivity better, and de-activated the Firefox one. (Fx 3.6.23)

[Tom T.]

Yes, on Fx 3.6.23, NS 2.1.9rc3, Google script and cookies blocked, search results do appear, and the links work fine.

*But* ... there is still notification of NS blocking a META refresh at the top. Since everything works now, this can be ignored, but is it possible to make it go away? -- just for the annoyance? If it's too much trouble, no worries.

This doesn't happen on Fx 7.01.
In both cases, all google script and cookies are blocked.
RP allows requests from google to gstatic.

Edit: In F3, it doesn't matter whether RP allows requests. The symptom occurs with google > gstatic both allowed and denied.

META refresh in F3, but not in F7?

[Mc]

Perfect
All searches work, keyword searches don't need an added &gbv=1 and I don't see notifications in SeaMonkey 2.4 (=Fx7) and SeaMonkey 2.5 beta (=Fx8).
Thank you, Giorgio

[Decklan]

Yes, on Fx 3.6.23, NS 2.1.9rc3, Google script and cookies blocked, search results do appear, and the links work fine.

*But* ... there is still notification of NS blocking a META refresh at the top. Since everything works now, this can be ignored, but is it possible to make it go away? -- just for the annoyance? If it's too much trouble, no worries.

This doesn't happen on Fx 7.01.
In both cases, all google script and cookies are blocked.
RP allows requests from google to gstatic.

Edit: In F3, it doesn't matter whether RP allows requests. The symptom occurs with google > gstatic both allowed and denied.

META refresh in F3, but not in F7?

Testing NoScript 2.1.9rc4. Strange happen to me in Firefox 7.01 with my present Firefox profile and with a clean install. At google homepage when I type (for example) "noscript" to search this work fine and show well results page, but when I click on some of the results (for example "noscript.net/") there is still notification of NS blocking a META refresh at the top left corner until destination link is loaded. NoScript whitelist is clean only appear grayed ones. Google script and cookies are blocked too. As said this can be ignored, if can't make it go away no worries, I can live with it perfectly, is a minor problem compared to what had until now.

Thank you all and thank you, Giorgio.

[Giorgio Maone]

Testing NoScript 2.1.9rc4.

Did you reset the noscript.forbidMetaRefresh.exception about:config preference to its (now changed) default value?