I am having an issue with a local portal which must have stepped up their game, because curl-impersonate no longer works like it used to.
I tried everything, changing the IPs, testing Firefox & Chrome impersonation using different browser versions, trying previous releases — no matter what, I am being detected and asked to enable JS. Meanwhile, the same URL opens just fine across different browsers — which I am doing anonymously, with no cookies involved. Even tried with two of my dev systems.
It does work every now and then, still, I can't put my finger on what exactly changes, must be something on their end. Either way, it used to work reliably, now it almost doesn't at all. I run out of ideas, there's clearly something that makes curl-impersonate not so stealthy anymore. I suspect that curl-impersonate fingerprint is specific enough, and together with the requests being fired at a a fairly regular interval, they decide it was a robot, after all.
Sample run:
docker run --rm lwthiker/curl-impersonate:0.6-ff curl_ff102 "https://allegro.pl/strefaokazji"
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0<html><head><title>allegro.pl</title><style>#cmsg{animation: A 1.5s;}@keyframes A{0%{opacity:0;}99%{opacity:0;}100%{opacity:1;}}</style></head><body style="margin:0"><p id="cmsg">Please enable JS and disable any ad blocker</p><script data-cfasync="false">var dd={'rt':'i','cid':'xxxxxxxxxxxxxxxx ==','hsh':'xxxxxxxxxxxxxxxx','b':1352779,'s':29560,'host':'geo.captcha-delivery.com'}</script><script data-cfasync="false" src="https://interstitial.captcha-delivery.com/i.js"></script></body></html>
100 523 100 523 0 0 1229 0 --:--:-- --:--:-- --:--:-- 1242
I am having an issue with a local portal which must have stepped up their game, because curl-impersonate no longer works like it used to.
I tried everything, changing the IPs, testing Firefox & Chrome impersonation using different browser versions, trying previous releases — no matter what, I am being detected and asked to enable JS. Meanwhile, the same URL opens just fine across different browsers — which I am doing anonymously, with no cookies involved. Even tried with two of my dev systems.
It does work every now and then, still, I can't put my finger on what exactly changes, must be something on their end. Either way, it used to work reliably, now it almost doesn't at all. I run out of ideas, there's clearly something that makes curl-impersonate not so stealthy anymore. I suspect that curl-impersonate fingerprint is specific enough, and together with the requests being fired at a a fairly regular interval, they decide it was a robot, after all.
Sample run: