Thursday 8 June 2017

Bypass Google captcha for server requests

I am creating an application, which needs to make a Google search and retrieve the link of the first result. Unfortunately, after making multiple requests, I am asked to enter a captcha code to verify that I am not a robot. Is there a way to bypass this check from Node or should I just wait until making new searches?

react-redux-template@1.0.0 backend /media/rnaidenov/OS/Users/Rado/Documents/Education/FestWithMe cd backend && nodemon app.js

[nodemon] 1.11.0 [nodemon] to restart at any time, enter rs [nodemon] watching: . [nodemon] starting node app.js Db.prototype.authenticate method will no longer be available in the next major release 3.x as MongoDB 3.6 will only allow auth against users in the admin db and will no longer allow multiple credentials on a socket. Please authenticate using MongoClient.connect with auth credentials. [Error: Error on response (503):null : https://www.google.com/search?hl=en&q=Field%20Day%20ra&start=0&sa=N&num=5&ie=UTF-8&oe=UTF-8&gws_rd=ssl

To continue, please type the characters below:



.jsonly{display: none}


About this page

Our systems have detected unusual traffic from your computer network. This page checks to see if it's really you sending the requests, and not a robot. Why did this happen?

This page appears when Google automatically detects requests coming from your computer network which appear to be in violation of the Terms of Service. The block will expire shortly after those requests stop. In the meantime, solving the above CAPTCHA will let you continue to use our services.

This traffic may have been sent by malicious software, a browser plug-in, or a script that sends automated requests. If you share your network > connection, ask your administrator for help — a different computer using the same IP address may be responsible. Learn more

Sometimes you may be asked to solve the CAPTCHA if you are using advanced terms that robots are known to use, or sending requests very quickly.


via Radoslav Naidenov

No comments:

Post a Comment