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.

Sign up for GitHub

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

Jump to bottom

Safari http2 fingerprints are not correct #215

Open

perklet opened this issue Dec 27, 2023 · 0 comments

perklet commented Dec 27, 2023 •

edited

Loading

It seems that the Safari targets are using the same SETTINGS frame and WINDOW_UPDATE as Chrome targets. i.e.

"akamai_text": "1:65536;3:1000;4:6291456;6:262144|15663105|0|m,s,p,a"

However, it should be:

"akamai_text": "4:4194304;3:100|10485760|0|m,s,p,a"

Not only some settings are skipped, but the order of them is also reversed. WINDOW_UPDATE is also different from Chrome.

I have fixed this in my fork, but I doubt that it's still able to be merged due to significant changes being made.

Edit: typo.

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment