Skip to content
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.

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

awc: Add rustls 0.23 #3362

Closed
wants to merge 14 commits into from
Closed

Conversation

asonix
Copy link
Contributor

@asonix asonix commented May 12, 2024

PR Type

Feature

PR Checklist

  • Tests for the changes have been added / updated.
  • Documentation comments have been added / updated.
  • A changelog entry has been made for the appropriate packages.
  • Format code with the latest stable rustfmt.
  • (Team) Label with affected crates and semver status.

Overview

Followup to #3361

  • Add rustls 0.23 in awc via three features, rustls-0_23 for custom-configuration only, and the webpki-roots and native-roots features like in rustls 0.22
  • Fix root store lookup when rustls-0_22-native-roots is enabled
  • Add documentation to ClientBuilder::new, and Connector::new
  • Add rustls-0.23 to actix-test

asonix added 12 commits May 3, 2024 14:03
When the feature for rustls 0.22 is enabled, and rustls 0.23 is also
present in a project, there suddently exist multiple paths for errors
when building middleware chains due to the use of two consecutive `?`
operators without specifying the intermediate error type.

This commit addresses the issue by removing the first `?`, so that the
first error type will always be known, and the second `?` always has a
well defined implementation.
This also fixes certificate lookup when native-roots is enabled for rustls 0.22.
@asonix asonix mentioned this pull request May 12, 2024
5 tasks
@asonix
Copy link
Contributor Author

asonix commented May 12, 2024

This one was a bit tricky since awc with webpki or native roots now implicitly relies on the rustls default provider, and creating the ClientConfig will panic if there is no global default and the number of crypto backends enabled is not exactly 1

I did what I could with documentation & another base rustls 0.23 feature to try to mitigate this issue

@robjtede robjtede closed this May 18, 2024
@robjtede
Copy link
Member

seems everything was included in #3363

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants