You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To get a rustls `ClientConfig` configured to use the platform verifier use:
92
92
93
93
```rust
94
-
letconfig=rustls_platform_verifier::tls_config();
94
+
userustls::ClientConfig;
95
+
userustls_platform_verifier::ConfigVerifierExt;
96
+
letconfig=ClientConfig::with_platform_verifier();
95
97
```
96
98
97
99
This crate will use the [rustls process-default crypto provider](https://docs.rs/rustls/latest/rustls/crypto/struct.CryptoProvider.html#using-the-per-process-default-cryptoprovider). To construct a `ClientConfig` with a different `CryptoProvider`, use:
/// **Important:** You must ensure that your `reqwest` version is using the same Rustls
50
52
/// version as this crate or it will panic when downcasting the `&dyn Any` verifier.
51
53
///
52
-
/// If you require more control over the rustls `ClientConfig`, you can
53
-
/// instantiate a [Verifier] with [Verifier::default] and then use it
54
-
/// with [`DangerousClientConfigBuilder::with_custom_certificate_verifier`][rustls::client::danger::DangerousClientConfigBuilder::with_custom_certificate_verifier].
54
+
/// If you require more control over the rustls [`ClientConfig`], you can import the
55
+
/// [`BuilderVerifierExt`] trait and call `.with_platform_verifier()` on the [`ConfigBuilder`].
55
56
///
56
57
/// Refer to the crate level documentation to see what platforms
57
58
/// are currently supported.
59
+
#[deprecated(since = "0.4.0", note = "use the `ConfigVerifierExt` instead")]
0 commit comments