fix: add rustls-platform-verifier flag for importing ConfigBuilderExt#276
Conversation
djc
left a comment
There was a problem hiding this comment.
This was just an oversight, thanks!
Those are just oversights, too -- happy if you want to send another PR for adding it in |
|
Hi, thank you for the approval!
Yes, I will make a PR to add
Yes please! In my opinion, a dedicated feature name is nicer to enable Thanks! |
|
Good catch, thank you |
Hello! Thank you so much for actively developing!
I found a (maybe) potential bug when I import
hyper-rustlswithrustls-platform-verifierfeature. Ifhyper-rustlswithrustls-platform-verifier(+aws-lc-rsorring) anddefault-features = false, we cannot build the following codewith error message: "no method named
with_platform_verifierfound for structConfigBuilderin the current scope".The reason why this build failure occurs is that in
src/connector/builder.rs,ConfigBuilderExtis imported only when either one ofrustls-native-certsorwebpki-rootsis enabled. Thus, I fixed the code a bit (just added feature flag).Of course I know that feature
rustls-platform-verifieris not public on README.md and thatnative-tokio, i.e.,rustls-native-certs, seems to be prioritized over the feature. But I am very happy if this would be considered! Thank you.Jun