Malte Granderath
Malte Granderath
This seems to be due to two concrete issues: - We are not configuring the `SSLConnectionSocketFactory` correctly whenever we create a `PoolingHttpClientConnectionManager` and that defaults to creating the default socket...
@Jackie-Jiang I am not fully sure that the upgrade will actually solve for this problem. I looked through the source of the http client and it seems like it would...
@Jackie-Jiang made the adjustment. Version 5 should fix the issue where the connection factory is not being picked up from the `PoolingHttpClientConnectionManager` so this has become a simpler change.
@Jackie-Jiang could I get some more 👀 on this?
@Jackie-Jiang sorry for the bump but would really like this to get in. We've been running this internally for quite a while now