On 10/11/2025 4:32 AM, Ryan Schmitt wrote:
I ran our internal integration test suite against the current core+client
commits. I didn't find much, just two notes:

1. The async client has started decompressing responses. I had to add a
call to `.disableContentCompression()`. This API is new in 5.6. This may be
an issue for libraries that use the async client, since it makes it harder
to "straddle" multiple versions of the client and obtain consistent
behavior from all of them.

This is a new feature in a feature release. Feature releases can have behavioral differences with earlier versions. There is going to be a note in the release notes regarding this change.

2. Our tests for insecure mode SSL (self-signed certs, obsolete TLS
versions, etc) started failing. I had to fix this by adding a
`HostnameVerificationPolicy.CLIENT` argument to the
`DefaultClientTlsStrategy` constructor call, in addition to the custom
`HostnameVerifier` I am already supplying. I think this must have been
caused by a constructor delegation change in `DefaultClientTlsStrategy`,
where the default policy was changed from `CLIENT` to `null` (which later
gets turned into `BOTH`).


Please raise a JIRA if you think there is a defect.

Oleg

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to