Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unique TLS signatures or JA3 fingerprints with each request #169

Closed
codeman5000 opened this issue Dec 6, 2023 · 4 comments
Closed

Unique TLS signatures or JA3 fingerprints with each request #169

codeman5000 opened this issue Dec 6, 2023 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@codeman5000
Copy link

codeman5000 commented Dec 6, 2023

Hello,
i'm not really sure but i like to know if with each request it is possible to create a unique TLS signatures or JA3 fingerprints with the same impersonated browser.
i have this idea that bots after some time block requests if they detect the same fingerprints.
randomizing the available impersonations is not enough, when doing a lot of requests per minute on some sites.

Is it possible to use an impersonation of a browser, lets say Chrome 107 but have a unique fingerprint with each request made with this impersonate version

thx in advance.

@codeman5000 codeman5000 added the enhancement New feature or request label Dec 6, 2023
@perklet
Copy link
Collaborator

perklet commented Dec 7, 2023

You can create unique fingerprints for each request, but they won't be the same as what browsers use. As far as I know, randomized fingerprints won't work, since the number of known browsers is very limited. If you were a website owner, an allowlist mode makes more sense.

@codeman5000
Copy link
Author

Hello thx for your answer.
It is clear to me i cannot modify the browser fingerprint.
is there any way in the request I can randomise so the fingerprint of the request with all its data is unique?
i noticed a site where i get a lot of blocks.
if I do a normal request some bots read extra stuff and implement it into the unique fingerprint, like fonts installed on your host, browser size, ...

kind regards
w

@perklet
Copy link
Collaborator

perklet commented Dec 7, 2023

curl_cffi only help you with TLS fingerprints. For other fingerprints generated in the browser via JavaScript, I think you need to use other projects. One of such techniques is called anti-detect browsers.

@perklet
Copy link
Collaborator

perklet commented Jan 9, 2024

Tracked in #194, closing this one.

@perklet perklet closed this as not planned Won't fix, can't repro, duplicate, stale Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants