Open yuhhere opened 1 year ago
I don't really know in detail how HTTP3 works, but just wondering if it's harder to impersonate browsers on this protocol version, or conversely easier?
From the README: https://github.com/lwthiker/curl-impersonate/blob/main/README.md :
The resulting curl looks, from a network perspective, identical to a real browser.
From https://curl.se/docs/http3.html https://github.com/curl/curl/blob/master/docs/HTTP3.md ::
HTTP/3 and QUIC support in curl is considered EXPERIMENTAL until further notice. It needs to be enabled at build-time.
It's probably trivial to passively fingerprint curl HTTP/3 as compared with e.g. Chrome and Firefox's HTTP/3 QUIC UDP packets?
With curl 8.5.0, HTTP3 is no longer experimental, for the ngtcp2 builds.
https://curl.se/changes.html#8_5_0 https://github.com/curl/curl/pull/12235
Is it possible to use HTTP 3 with this version of curl? I know you're able to extend the default curl to add http 3 support but I'm not sure how one would make those changes to this library.