Page 2 of 5
Re: Block META redirect within NOSCRIPT element at Google se
Posted: Sat Nov 05, 2011 9:54 pm
by me
I see your new results.
I too have tested with FFv2.00.20 and 3.6.23, both in individual sub directories,
not sharing anything except main system libraries.
FFv3.6.23 is running NoScript v2.1.8.
FFv2.0.20 is running NoScript v1.9.9.33, since v2.1.8 does not go back that far.
When I use these versions Google searches of any kind work, even directly at google.com.
I am also running Request Policy with FFv3.6.23, currently v5.22, which I should upgrade now that I noticed it.
I try to keep all of my browser settings very restrictive, allowing as little as possible,
and simply using temporary permissions if needed.
I have not ever needed to allow Google or Gstatic to simply get a list of search terms displayed using Request Policy.
They are needed to view Google Maps though.
Still when I use a newer FF version, Google currently gets stopped by NoScript for a META REDIRECT violation.
FireFox v5 or newer:
Simply go to google.com and type in a search term and press enter.
It is at this point that NoScript will stop the resulting output with the blocked META redirect warning.
Requiring one to click it to see the results of your search.
Thanks Again.
Re: Block META redirect within NOSCRIPT element at Google se
Posted: Sat Nov 05, 2011 10:25 pm
by Giorgio Maone
Please check
latest development build 2.1.9rc1, thanks.
Re: Block META redirect within NOSCRIPT element at Google se
Posted: Sat Nov 05, 2011 11:23 pm
by Mc
I'm still getting a blocked redirect (or blank page, with much source content) with the keyword bookmark example
http://www.google.com/search?q=%s searching for any word, but if I just load the bookmark, google comes up.
Re: Block META redirect within NOSCRIPT element at Google se
Posted: Sat Nov 05, 2011 11:34 pm
by Tom T.
I too get a META redirect, with scripting and cookies disallowed. 2.1.9rc2
Allowing
https://encrypted.google.com is still necessary.
Re: Block META redirect within NOSCRIPT element at Google se
Posted: Sat Nov 05, 2011 11:49 pm
by Giorgio Maone
@Mc: are you forcing HTTPS on google.com?
@Tom T.: does changing the
noscript.forbidMetaRefresh.exception about:config preference to
Code: Select all
^https?://(?:www|encrypted)\.google\.(?:[a-z]{2,3}|[a-z]2\.[a-z]{2,3})/search\?q=
help?
Re: Block META redirect within NOSCRIPT element at Google se
Posted: Sat Nov 05, 2011 11:56 pm
by Tom T.
investigating.....
Re: Block META redirect within NOSCRIPT element at Google se
Posted: Sun Nov 06, 2011 12:04 am
by Tom T.
No, I still get a META redirect, and the page won't load until I TA
https://encrypted.google.com
Re: Block META redirect within NOSCRIPT element at Google se
Posted: Sun Nov 06, 2011 12:06 am
by Mc
Giorgio Maone wrote:@Mc: are you forcing HTTPS on google.com?
No, that's set to Never.
On blank pages I get many CSS Warnings, btw, mostly Error in parsing value... Declaration dropped.
Re: Block META redirect within NOSCRIPT element at Google se
Posted: Sun Nov 06, 2011 12:13 am
by Tom T.
On Fx 3.6.23, I get *no* messages in Error Console while the redirection is being blocked by NS.
Edit: On Fx 7.01 Portable, I get no messages in either Error Console or Web Developer console while the redirect is being blocked.
Re: Block META redirect within NOSCRIPT element at Google se
Posted: Sun Nov 06, 2011 12:21 am
by Decklan
Tom T. wrote:On Fx 3.6.23, I get *no* messages in Error Console while the redirection is being blocked by NS.
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.
Greetings to all
Re: Block META redirect within NOSCRIPT element at Google se
Posted: Sun Nov 06, 2011 12:33 am
by Tom T.
@ Giorgio: I need to log off for a while. If there is a new dev build or other fix to try, I'll check back in an hour or two.
And get some sleep!

Re: Block META redirect within NOSCRIPT element at Google se
Posted: Sun Nov 06, 2011 1:22 am
by Decklan
Decklan wrote:Tom T. wrote:On Fx 3.6.23, I get *no* messages in Error Console while the redirection is being blocked by NS.
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.
Re: Block META redirect within NOSCRIPT element at Google se
Posted: Sun Nov 06, 2011 2:42 am
by Tom T.
Decklan wrote:Decklan wrote:
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.

Re: Block META redirect within NOSCRIPT element at Google se
Posted: Sun Nov 06, 2011 8:04 am
by al_9x
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';"
Re: Block META redirect within NOSCRIPT element at Google se
Posted: Sun Nov 06, 2011 8:23 am
by Mc
Tom T. wrote:Decklan wrote:Decklan wrote:
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.

And for me

I tried the setting of Decklan yesterday too and got the blank page with my keyword search (
http://www.google.com/search?q=%s) as well. So it's not stupid to do so

Today I tried opening the bookmark directly with that unchecked (set to false) and... I got a blank page.