- Регистрация
- 22.01.2019
- Сообщения
- 1 214
- Благодарностей
- 3 364
- Баллы
- 113
reCAPTCHA v2 restored for Google Search and other services
A modified version of reCAPTCHA v2, which contains an additional parameter data-s, has recently appeared at google.com/sorry/index. This parameter is unique and generated upon every new page visit or refresh. To resolve a captcha in Google, one has to transmit this parameter over the rucaptcha’s API (data-s) or anticaptcha’s API (recaptchaDataSValue).
Please note that this parameter needs to be parsed before JavaScript scripts are initialized. Otherwise, the acquired token (response) will be invalid.
Please note that this parameter needs to be parsed before JavaScript scripts are initialized. Otherwise, the acquired token (response) will be invalid.
Improved reCAPTCHA v2 token acceptability 2
We have updated the reCAPTCHA v2 solving algorithm which helped increase the success rate with the Chrome method. Also, we can boast significant improvements in the no-browser solving method HttpRequest, but it will need good resident proxies.
If you used profiles when solving captchas, you need to delete them and start googling over again.
Enhanced performance
Interface response was improved, and now the program consumes less memory at high loads.
API for obtaining solving statistics
Now you can get some JSON-format stats that will reflect how your program works. The report will feature all the figures from the main tab Workflow.
Look at this CURL example to see what a request looks like:
What’s New in 2.10.16.2
Added:
+ Data-s parameter is now supported in rucaptcha’s API and antigate’s API for solving captchas in Google Search and other services. Data-s parameter is used for rucaptcha, recaptchaDataSValue for anticaptcha.
+ CapMonster now consumes less memory at peak loads.
+ Improved interface response at high loads.
+ Improved reCAPTCHA v2 token acceptability. If you used profiles, remove them and start promoting them over again.
+ Receive app performance stats in JSON format over API. The stats report features values of all the labels from the app’s main form. Example: curl "http://127.0.0.3:80/getRecognitionStatistics" --data "key=sampleKey".
+ Added a hint for the Proxy Protocol in Sitekey Addon (it had been unclear what “automatic” stood for).
Fixed:
• Use of profiles and http captcha solving method would lead to reduced performance and clogging of log files.
• Memory leak, that occurred when during recaptcha recognition at peak loads, was found and fixed.
• Fixed a bug where some recaptchas wouldn’t be recognized if sent one after one.
• Fixed a bug when the full list clear function wouldn’t clear the list of actually used proxies when uploading proxies from the list.
• Proxy upload from a link wouldn’t work for some websites if an https link was used.
• Proxy upload from a file or link would ignore proxies where a host was indicated in place of an IP address.
• Utility processes would initialize on a secondary way rather than absolute. That would led to faulty operation thereof, if CapMonster was initialized by a script with now working directory specified.
We have updated the reCAPTCHA v2 solving algorithm which helped increase the success rate with the Chrome method. Also, we can boast significant improvements in the no-browser solving method HttpRequest, but it will need good resident proxies.
If you used profiles when solving captchas, you need to delete them and start googling over again.
Enhanced performance
Interface response was improved, and now the program consumes less memory at high loads.
API for obtaining solving statistics
Now you can get some JSON-format stats that will reflect how your program works. The report will feature all the figures from the main tab Workflow.
Look at this CURL example to see what a request looks like:
POST request:
http://127.0.0.3:80/getRecognitionStatistics?key=sampleKey
Response:
{
"RecognitionsCount": 0, // Processed captchas
"HandledSitekeyCount": 0, // Tasks handled
"SuccessSitekeyCount": 0, // Success tasks SitekeyAddon
"BannedIpSitekeyCount": 0, // Banned IP
"BadIpSitekeyCount": 0, // Bad IP (Timeout)
"AutoRecognitionsCount": 0, // Solved captchas
"AverageRecognitionTime": 0, // Average recognition time
"AverageRecognitionTimeSitekey": 0, // Average recognition time SitekeyAddon
"ThreadsCount": 0, // Slots in process
"EnoughSystemResources": true, // Whether system resources are sufficient
"InsufficientThreadsLocalCount": -1, // Insufficient threads in local modules
"InsufficientThreadsRemoteCount": -1, // Insufficient threads in remote modules
"TasksInQueue": 0, // Tasks in queue
"TotalMoneySaved": 0, // Amount of money saved
"TotalMoneySavedSitekey": 0, // Amount of money saved by SitekeyAddon
"TasksInProcess": "0" // Tasks in process SitekeyAddon
}What’s New in 2.10.16.2
Added:
+ Data-s parameter is now supported in rucaptcha’s API and antigate’s API for solving captchas in Google Search and other services. Data-s parameter is used for rucaptcha, recaptchaDataSValue for anticaptcha.
+ CapMonster now consumes less memory at peak loads.
+ Improved interface response at high loads.
+ Improved reCAPTCHA v2 token acceptability. If you used profiles, remove them and start promoting them over again.
+ Receive app performance stats in JSON format over API. The stats report features values of all the labels from the app’s main form. Example: curl "http://127.0.0.3:80/getRecognitionStatistics" --data "key=sampleKey".
+ Added a hint for the Proxy Protocol in Sitekey Addon (it had been unclear what “automatic” stood for).
Fixed:
• Use of profiles and http captcha solving method would lead to reduced performance and clogging of log files.
• Memory leak, that occurred when during recaptcha recognition at peak loads, was found and fixed.
• Fixed a bug where some recaptchas wouldn’t be recognized if sent one after one.
• Fixed a bug when the full list clear function wouldn’t clear the list of actually used proxies when uploading proxies from the list.
• Proxy upload from a link wouldn’t work for some websites if an https link was used.
• Proxy upload from a file or link would ignore proxies where a host was indicated in place of an IP address.
• Utility processes would initialize on a secondary way rather than absolute. That would led to faulty operation thereof, if CapMonster was initialized by a script with now working directory specified.