Add support for SSL_CERT_FILE, REQUESTS_CA_BUNDLE, and CURL_CA_BUNDLE
See original GitHub issuePart of #33 these three environment variables all have the same behavior, to specify where a CA bundle is if none are specified by default and trust_env
is True.
We should check the three environment variables in the order above, as SSL_CERT_FILE is a PEP and a standard whereas the other are products of other projects.
If multiple are set and that file doesn’t exist we should skip it and try the next environment variable.
We’ll also have to document these environment variables within docs/environment.md
.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
One data point: to get async/await support, we switched from requests to httpx for a production service at work today, and we had to change this environment variable. It would be nice if requests supported
SSL_CERT_FILE
andSSL_CERT_DIR
but it doesn’t: https://github.com/psf/requests/pull/2903#issuecomment-206520463.Yeah, I think our starting point should be the PEP - https://www.python.org/dev/peps/pep-0476/#trust-database - Ie. let’s support
SSL_CERT_FILE
andSSL_CERT_DIR
.We could always walk back from that point to add support requests and curl style env vars in addition, but I don’t think it’s obvious if we want to do that or not.