Ryan Tomlinson

As far as I can tell, it has something to do with trying to obtain the trust before it's set. It's similar to this old stack overflow post: https://stackoverflow.com/questions/38761837/ios-ssl-connection-in-swift#answer-39422996:~:text=%2F%2F%20If%20you%20try%20and%20obtain,that%20the%20oject%20is%20always%20nil! I...

I fixed this with something similar to @chinabrant, however I don't use self-signed certs. I use cert-pinning in client app. ```swift if isTLS { inStream.setProperty(StreamSocketSecurityLevel.negotiatedSSL, forKey: Stream.PropertyKey.socketSecurityLevelKey)   outStream.setProperty(StreamSocketSecurityLevel.negotiatedSSL, forKey: Stream.PropertyKey.socketSecurityLevelKey)  ...

@snjeza Thanks for the suggestion, unfortunately this did not work for me though.   Did these and still seeing the same errors

Unfortunately that's not working for me

I raised a PR to bump the library to use httpclient5, since we use SendGrid in our project that we're upgrading to httpclient5.

I used the official Apache guide for the migration: https://hc.apache.org/httpcomponents-client-5.3.x/migration-guide/migration-to-classic.html, as well as other resources like some of the namespace mappings from here: https://docs.openrewrite.org/recipes/apache/httpclient5/upgradeapachehttpclient_5_classmapping.

My suggestion for this PR would be to release it under a new major version, such that it is clear that it is a breaking change for consumers. Then we...

Thank you for working on this patch @jbrinegar! This will help eliminate a big blocker for us in trying to upgrade our stack to JDK 23.