mirror of
https://github.com/lwthiker/curl-impersonate.git
synced 2025-08-04 19:02:28 +00:00
9d05a81030
Add support for impersonating Chrome 110. Chrome 110 comes with TLS extension permutation enabled by default. We mimic this behavior in libcurl with the new CURLOPT_SSL_PERMUTE_EXTENSIONS option, which enables the corresponding flag in BoringSSL. --------- Co-authored-by: Johann Saunier <saunier.johann@gmail.com>
The tests verify that curl-impersonate has the same network signature as that of the supported browsers. They do not test curl's functionality itself.
Running the tests
The tests assume that you've built both curl-impersonate-chrome and curl-impersonate-ff docker images before (see Building from source).
To run the tests, build with:
docker build -t curl-impersonate-tests tests/
then run with:
docker run --rm curl-impersonate-tests
This simply runs pytest in the container. You can pass additional flags to pytest such as --log-cli-level DEBUG.
How the tests work
For each supported browser, the following tests are performed:
- A packet capture is started while
curl-impersonateis run with the relevant wrapper script. The Client Hello message is extracted from the capture and compared against the known signature of the browser. curl-impersonateis run, connecting to a localnghttpdserver (a simple HTTP/2 server). The HTTP/2 pseudo-headers and headers are extracted from the output log ofnghttpdand compared to the known headers of the browser.
What's missing
The following tests are still missing:
- Test that
curl-impersonatesends the same HTTP/2 SETTINGS as the browser.