The Akamai fingerprint of cycletls doesnt match the fingerprint of the browser im attempting to imitate.
tls.peet.ws calls akamai_fingerprint and akamai_fingerpring_hash are both different from the actual browser
I am aware of two bugs, one is that we are sending SETTINGS_MAX_FRAME_SIZE on chrome when we should not be and the second one is incorrect pseudo header order for firefox. I'll have fixes in the next release
Description
The Akamai fingerprint of cycletls doesnt match the fingerprint of the browser im attempting to imitate. tls.peet.ws calls akamai_fingerprint and akamai_fingerpring_hash are both different from the actual browser
I use the latest version.
Reproduction code:
Results returned by cycletls:
Results returned by actual chrome:
Issue Type
Bug
Operating System
Windows 10
Node Version
Other
Golang Version
Go 16.x
Relevant Log Output
No response