Skip to content

Store Browser / HTTP client fingerprint in Session #3628

@barjin

Description

@barjin

The Session class should carry all the data necessary to make repeatable requests to a server. Together with the proxy URL and the cookie jar, we should store the browser / HTTP client fingerprint (i.e., user-agent, TLS settings, etc.), to make the repeated requests as similar as possible.

The actual format of the fingerprint is TBD.

Metadata

Metadata

Assignees

No one assigned

    Labels

    t-toolingIssues with this label are in the ownership of the tooling team.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions