search

Carcraftz / TLS-Fingerprint-API

Privacy protection for the 21st century. Modern websites like Facebook can track details about your HTTP client even if you prevent sending a User Agent! This repo proxies your requests using a fork of go’s networking library (fhttp) and my fork of cclient (TLS fingerprint mimicry library) to prevent detection at the TLS stack level.
237 stars 59 forks source link

200 empty response #14

Open bjermeland opened 2 years ago

bjermeland commented 2 years ago

Worked great so far to avoid fingerprints, but getting detected by Bet365 now (most likely CF blocking it).

Reproduce:

  1. Go to random event at Bet365
  2. Find a request containing 'web?' in networks tab, copy as curl
  3. Paste it into your API

It returns 200 OK, with empty response body. Without your API, I'm getting 403 Forbidden by CF.

Carcraftz commented 2 years ago

I don't think 200 empty response is a fingerprinting block.

Visiting the URL directly in chrome results in the same thing. I think you might need to set a referrer header.

bjermeland commented 2 years ago

Getting same issue when copy-pasting exactly same request into your API with all headers, so they must be detecting it somehow. 100% not IP related. Do you have any ideas how they can be detecting it still?

Colombo97 commented 2 years ago

Its happening with me too. Same thing, same url, same copypaste

Colombo97 commented 2 years ago

@bjermeland Did you solve it?