Friday, January 18, 2008

Google Search Engine to protect automated request - but why me?

Today i was searching on "mysql data generator" tools using Google search. Suddenly after 1st or 2nd search result page i took more then 20min to click on 3rd page request by clicking the NEXT button in Google Search result page. And here i faced this screen for the 1st time - a page of 403 Forbidden message of Google - We're Sorry! . Even after entering the 1st CAPTCHA value it asked 2nd time to enter the CAPTCHA.

Did you faced this ever doing any Google search before? I need to reproduce this step manually. Not sure why my usual Google search appeared to be like an Automated Request as like as a Computer Virus or a Spyware Application or whatever it claimed? :) Really interesting!

And is it really the way Google gonna verify each and every search click using a CAPTCHA? :) I really love to search anything comes into my mind to search in Google rather using Live Search, Yahoo search or any other search engine. But is Google out of their Search Engine bandwidth? :)

May be i am missing any other important point here. Want to know - Why this verification is really important to Google? :) And what really made Google to identify me in this way? :)


Tahmid Munaz said...

Google Online Security Blog :)

The Reason behind - We're Sorry!

Enjoy! :)

Tahmid Munaz said...

Corrected Link :)

Omi Azad said...

Well, from my experience and some other bloggers reference, what I understand that when you are using Google and your connection changes, Google thinks you are not a human.

For example you are on a local internet connection and using Google, you just take your computer into your car and connect to the Internet with any wireless service. Now Google will ask you to type the code on the image, to make sure you are not a robot. Robots doesn't change IP. :)

Tahmid Munaz said...

Thanks for dropping by Mr. Omi Azad.

Actually it occurred suddenly one day in my regular surfing schedule. I was not even in any different network or not even in any wireless connection. It was just the typical network where i used to work in my daily life.

Till now i faced this issue 2 times in two different places and the reason behind this could be my continuous "PING -t" from my windows command line to check whether my line is dropping or not? :p

This could be the only reason for my network :P

Creative Commons License
This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 License.