3 ms·
Set a UA and any headers and/or cookies with regular cURL compiled with HTTP/3. This can be done with wrapper scripts very easily. 99.999% of problems solved wi
by anon6362 2y ago
Set a UA and any headers and/or cookies with regular cURL compiled with HTTP/3. This can be done with wrapper scripts very easily. 99.999% of problems solved with no special magic buried in an unclean fork.
- andrewmcwatters 2y agoThat’s not the point of this fork. And “unclean fork” is such an unnecessary and unprofessional comment. There’s an entire industry of stealth browser technologies out there that this falls under.
- psanford 2y agoThat doesn't solve the problem of TLS handshake fingerprinting, which is the whole point of this project.
- mmh0000 2y agoYou should really read the "Why" section of the README before jumping to conclusions: ``` some web services use the TLS and HTTP handshakes to fingerprint which client is accessing them, and then present different content for different clients. These methods are known as TLS fingerprinting and HTTP/2 fingerprinting respectively. Their widespread use has led to the web becoming less open, less private and much more restrictive towards specific web clients With the modified curl in this repository, the TLS and HTTP handshakes look exactly like those of a real browser. ``` For example, this will get you past Cloudflare's bot detection.
- 01HNNWZ0MV43FF 2y agoThe README indicates that this fork is compiled with nss (from Firefox) and BoringSSL (from Chromium) to resist fingerprinting based on the TLS lib. CLI flags won't do that.