Closed r00t-Taurus closed 3 months ago
AFAIK, TLS fingerprints on iOS should be more uniformed, since there is not other browser engine on iOS except for webkit(Safari). Akamai also considers the http2 fingerprints along with the TLS ones.
You can change the fingerprints for each request with options like CURLOPT_CIPHER_SUITES
and those mentioned on yifeikong/curl-impersonate.
curl-cffi==0.6.0b9
If I understand correctly, then all the options in the impersonate parameter should be legal for the site? But I came across a site with strange behavior
If you execute this code, it returns
403
and says that the ip is blocked, it really can be ip blocking, so you can try to install a proxy But if you changechrome99_android
to any safari, for examplesafari17_0
, then everything starts working (sometimes you need to make a request a couple of times for the site to start skipping it), why is that? after all, it would be more logical to usechrome99_android
, since the headers indicate"User-Agent": "Kleinanzeigen/15.18.0 (Android 7.1.2; google G011A)",
But this is not the whole strangeness.If you run this you will get
403
I tried all the parameters available inimpersonate
, but they all give403
, but if you remove theimpersonate
parameter, then everything starts to work, why is that? after all, these are legitimate tls fingerprints, can't it block real devices? As far as I know, the site uses akamai. Is it possible to issue a different ja3 every time?