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

What we will see on the server side? #44

Open
NoamRotter opened this issue Feb 15, 2024 · 4 comments
Open

What we will see on the server side? #44

NoamRotter opened this issue Feb 15, 2024 · 4 comments

Comments

@NoamRotter
Copy link

Hi,
For the traffic that will go through the proxy servers,
Do we expect to see any other changes/additions in the HTTP request/response headers?
Or, all the headers will stay intact but only the IP will be of the proxy?

Thanks.

@DavidSchinazi
Copy link
Collaborator

That's right, the IP will change but we do not expect any changes to HTTP headers.

@emergencynap
Copy link

Will the TLS fingerprint change? Reason I ask is because many bot prevention sites use JA3 fingerprinting based on TLS to detect if a user is a bot and present a captcha.

@DavidSchinazi
Copy link
Collaborator

TLS is still performed end-to-end between Chrome and the website, and IP Protection won't impact TLS. In particular, IP Protection won't change the TLS client hello, and therefore not the JA3 fingerprint either.

@NoamRotter
Copy link
Author

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants