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
Currently, we configure TLS globally per HTTPClient. Usually, that's fine but there are use cases where we need different TLS settings per server etc.
As @Lukasa point out, this unfortunately has consequences for the connection pool: Currently we key the pool with (protocol, host, port) which would then no longer work and we'd have to change the key to (protocol, host, port, TLS config) which doesn't sound too bad of a change and enables quite a few new use cases.
The text was updated successfully, but these errors were encountered:
Currently, we configure TLS globally per
HTTPClient
. Usually, that's fine but there are use cases where we need different TLS settings per server etc.As @Lukasa point out, this unfortunately has consequences for the connection pool: Currently we key the pool with
(protocol, host, port)
which would then no longer work and we'd have to change the key to(protocol, host, port, TLS config)
which doesn't sound too bad of a change and enables quite a few new use cases.The text was updated successfully, but these errors were encountered: