Page 1 of 1

[RESOLVED] Google Problem

Posted: Mon Nov 28, 2011 8:12 pm
by SetQ
I have Firefox 8.01 with :

Avast Web Rep 6.0.1289
CheckPlaces 2.6.1
Microsoft .Net Framework Assistant 0.0.0
NoScript 2.2.1
Scrapbook 1.4.8
SiteDelta 0.12.1
XMarks 4.0.2
FlashBlock 1.5.15.1 (Disabled)

And when in google main page i try search, it does not search anything
The URI for the text "Test Adsl" is:
http://www.google.es/#sclient=psy-ab&hl ... 52&bih=719

But that's all. There's no results in the page, only the Google icon, the input box and the magnifing glass icon.

The Google menu with "Web, Images, Videos, Maps, News, Gmail, More" operates and works. Only text search box don't works.

If i search in the firefox navigation bar, then the search works.

Sorry for my english, and Thank's. I would like a solution, thank you.

Re: Google Problem

Posted: Mon Nov 28, 2011 8:25 pm
by Giorgio Maone
Is "google.es" allowed?

Re: Google Problem

Posted: Mon Nov 28, 2011 8:28 pm
by therube
Believe it has something to do with the ampersand (#) & NoScript?

Your link returns nothing for me either.

If I do the search directly, I get this: http://www.google.com/search?q=Test+Adsl&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:unofficial&client=seamonkey-a

Note the &q= rather then the #.

Re: Google Problem

Posted: Mon Nov 28, 2011 8:28 pm
by therube
OK, with google.es Allowed, it works, but why should that matter?

Re: Google Problem

Posted: Mon Nov 28, 2011 8:29 pm
by therube
Believe it has something to do with the ampersand (#) & NoScript?
Believe it has something to do with the ampersand (#) & NoScript & the site in question not being Allowed?

And if everything from the # is being truncated, then why is it not logged in Error Console?

Re: Google Problem

Posted: Mon Nov 28, 2011 8:56 pm
by Giorgio Maone
therube wrote:OK, with google.es Allowed, it works, but why should that matter?
the hash (#...) part of the URL is never sent on the server side.
Therefore, if you use that as your search URL, it means that all the search is done via AJAX and you need JavaScript to be allowed.
If you don't allow JavaScript, Google correctly fallbacks to normal query strings (?...), which send parameters on the server side for processing.

Re: Google Problem

Posted: Tue Nov 29, 2011 2:59 am
by Tom T.
I don't understand why there's a hash at all.
And when in google main page i try search, it does not search anything
Entering

Code: Select all

www.google.es
in the Address Bar brings up a perfectly functional Google page (in Spanish). No scripting or cookies allowed.

I type "cuba" in the Search bar, and the resulting URL is

Code: Select all

http://www.google.es/search?sclient=psy-ab&hl=es&site=&source=hp&q=cuba&btnG=Buscar
Which produces the annoying META block, and
Por favor, haz clic aquí si no has sido redireccionado en unos segundos.
which is exactly what English Google does, an issue which still hasn't been fixed, after Google apparently fixed it once, then broke it again. (IIRC, NS META exception was removed after Google fixed it the first time. Should it be replaced? -- not that I use Google anyway.)

Clicking on aqui provides the correct results page, with links that work.
Giorgio Maone wrote:the hash (#...) part of the URL is never sent on the server side.
Therefore, if you use that as your search URL, it means that all the search is done via AJAX and you need JavaScript to be allowed.
I'm sure there's a bit of a language barrier, but why would OP enter that full URL to do his test search?

I could be mistaken, but I took it to mean that that was the URL that was displayed *after* s/he entered the search term and hit Enter or whatever.

Sorry if I've misunderstood anything. And it would still be nice if the METAs would go away -- is the exception the only answer, or do you have any pull at Google, Giorgio?

Re: Google Problem

Posted: Wed Nov 30, 2011 1:52 am
by therube
Not that I'm really understanding, but based on what Giorgio said, I guess that particular link (from wherever it came from, perhaps some server logs, or similar can be found in forum posts) is not (specifically) made to be client facing. A user normally would not be seeing the #... type link. The ?... type link is what is expected & works regardless. It is with the #... where there could be issues (when JavaScript is disabled, be it by NoScript or otherwise).

Re: Google Problem

Posted: Wed Nov 30, 2011 4:58 pm
by SetQ
Thanks for mentioning the # "hash" and the problem belongs to Google. It really gave me a clue to my problem. It was simply that it should disable the feature of "Google Instant", now the search function properly again!.

Thank you all!.

Re: [RESOLVED] Google Problem

Posted: Wed Nov 30, 2011 10:16 pm
by Tom T.
¡De nada! :)