CapMonster 2.10.16.2 (11.06.2020)

New:
[+] 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.