i doubt if utls's fingerprint has been detected
in some site, when is use utls to imitate browsers like chrome and firefox,but it will has the err: ReadVersion: expected 'H', got '\x00' at position 0 when receive response but when i use golang's tls it will not has the error,so i doubt if utls's fingerprint has been detected and be blocked!
I wonder if utls fingerprint masking has been unmasked
On some sites, when I use uTLS to imitate browsers like Chrome and Firefox, I get the following error:
ReadVersion: expected 'H', got '\x00' at position 0 when receiving a response.
However, when I use Go's native TLS, I do not encounter this error. So, I wonder if uTLS's fingerprint has been detected and blocked.
discussion
Can you tell us which site or at least which cdn is catching it?
Do the fingerprints match when you go to tls.browserleaks.com ?
Which urls exactly? Because that Looks like more a potential bug in implementation than a detection