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
Thank you for kindly creating, publishing and maintaining ureq, we've found it very useful as a non-async http client.
In ureq 2.9.7, we had the following code for a tool that needed to support requests to generally trusted servers (via the OS's cert store) and also to support the option of custom certificates provided by the user. Via native-tls.
With ureq v3, it would seem that we can either use RootCerts::PlatformVerifier or RootCerts::Specific. For our use case, do you recommend using something like rustls_native_certs::load_native_certs to load the certificates, add any custom ones and then use RootCerts::Specific?
It seems reasonable as I type it out, but I wanted to check if that seems like the best route?
The text was updated successfully, but these errors were encountered:
Thank you for kindly creating, publishing and maintaining ureq, we've found it very useful as a non-async http client.
In ureq 2.9.7, we had the following code for a tool that needed to support requests to generally trusted servers (via the OS's cert store) and also to support the option of custom certificates provided by the user. Via native-tls.
With ureq v3, it would seem that we can either use
RootCerts::PlatformVerifier
orRootCerts::Specific
. For our use case, do you recommend using something likerustls_native_certs::load_native_certs
to load the certificates, add any custom ones and then useRootCerts::Specific
?It seems reasonable as I type it out, but I wanted to check if that seems like the best route?
The text was updated successfully, but these errors were encountered: