diff options
| author | mm-matthias <43849132+mm-matthias@users.noreply.github.com> | 2024-06-16 20:27:44 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-06-16 20:27:44 (GMT) |
| commit | 4f59f8638267aa64ad2daa0111d8b7fdc2499834 (patch) | |
| tree | 7e252e5714a8c4a5da4213e801ee985fe7142eeb /Python | |
| parent | 92cebaa4911786683e87841bf7788351e7595ac2 (diff) | |
| download | cpython-4f59f8638267aa64ad2daa0111d8b7fdc2499834.zip cpython-4f59f8638267aa64ad2daa0111d8b7fdc2499834.tar.gz cpython-4f59f8638267aa64ad2daa0111d8b7fdc2499834.tar.bz2 | |
gh-118596: Add thread-safety clarifications to the SSLContext documentation (#118597)
Add thread-safety clarifications to the SSLContext documentation. Per the issue:
This issue has also come up [here](https://github.com/psf/requests/pull/6667) where the matter was clarified by @tiran in [this comment](https://github.com/psf/requests/pull/6667):
> `SSLContext` is designed to be shared and used for multiple connections. It is thread safe as long as you don't reconfigure it once it is used by a connection. Adding new certs to the internal trust store is fine, but changing ciphers, verification settings, or mTLS certs can lead to surprising behavior. The problem is unrelated to threads and can even occur in a single-threaded program.
Diffstat (limited to 'Python')
0 files changed, 0 insertions, 0 deletions