Skip to content

Allow consumers to select the rustls crypto provider #220

Description

@mlieberman85

Every rustls feature in the workspace routes to reqwest/rustls, which hardcodes aws-lc-rs. There is no exposed path to reqwest's rustls-no-provider, so a consumer cannot choose ring. Projects that want to avoid C dependencies, or that have already standardized on ring, will run into issues.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions