You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe adding parameter for delay/latency in session.get could improve the bypass (with a jitter/random) ?
Something like : curl -L -X POST "http://localhost:8191/v1" -H "Content-Type: application/json" --data-raw "{\"cmd\": \"request.get\",\"delay\": 5000,\"maxTimeout\": 60000,\"url\":\"foo.bar\",\"session\": 974}"
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
regarding the issue #951 I've remarked that for some websites (ygg in my case) Cloudflare seems easily to find that the interaction by FlareSolverr is not human and FS failed to bypass the protection. But I success in 95% of time to pass it manually in the Chromedriver window (exemple : https://github-production-user-asset-6210df.s3.amazonaws.com/28442699/281680024-d1dee066-6a03-4ff2-8437-308a6145e2e9.mp4)
Maybe adding parameter for delay/latency in session.get could improve the bypass (with a jitter/random) ?
Something like :
curl -L -X POST "http://localhost:8191/v1" -H "Content-Type: application/json" --data-raw "{\"cmd\": \"request.get\",\"delay\": 5000,\"maxTimeout\": 60000,\"url\":\"foo.bar\",\"session\": 974}"
Beta Was this translation helpful? Give feedback.
All reactions