Open
Conversation
This was referenced Feb 10, 2026
|
I've been working on this exact issue (hacky approach in #33) and was looking for a better approach. I see you have |
Author
|
Added! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The reqwest dependency uses
rustls-tlswhich bundles Mozilla's root CAs viawebpki-roots. This means the HTTP client ignores system certificate stores and environment variables likeSSL_CERT_FILE, blocking me from connecting to endpoints using internal/private CAs (e.g. statsig-forward-proxy with platform-issued TLS certificates).Switching to
rustls-tls-native-rootsmakes reqwest userustls-native-certsto load certificates from the system store at runtime, which respectsSSL_CERT_FILEandSSL_CERT_DIR.