0

I use http-proxy-middleware to access various web-sites, including those having TLS fingerprint checks. My problem is that the proxy's TLS fingerprint is not corresponding to the User-Agent header I'm passing, that's why my visits are sometimes being rejected by antibot protection. Is there a way to make http-proxy-middleware reveal only specific things I want during TLS handshake?

If there are no workarounds for http-proxy-middleware, could you please recommend a proxy tool for NodeJS that could be configured in such a way?

Improve this question
2
  • 2
    the proxy's TLS fingerprint is not corresponding to the User-Agent header I'm passing ... can you explain what 'TLS fingerprint' means to you and how the User-Agent header is involved in it? Commented Jun 2, 2024 at 21:41
  • @PresidentJamesK.Polk - Let me explain my logic. Each client has its own TLS features that can be used to make a fingerprint. For example, Chrome installed in my PC has TLS 1.1 and 1.0 enabled by default, while they are disabled in my Firefox (I'm using browserleaks.com/tls for reference). http-proxy-middleware client has its own characteristics. So basically you can compare User Agents (with some other data) and their known default SSL/TLS capabilites set by the vendor to tell whether they match a general pattern (used widely) or not. Commented Jun 3, 2024 at 7:54
Related questions
616
performing HTTP requests with cURL (using PROXY)
1155
How is an HTTP POST request made in node.js?
545
How do I pull from a Git repository through an HTTP proxy?
Load 6 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.