Skip to content

Safari http2 fingerprints are not correct #215

@perkfly

Description

@perkfly

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions