DockerHttpClient (both zero-dep and apache) always use default hostname verifier

[idontusenumbers]

Situation:

There is currently no way to use the docker-java library to connect to docker over TCP/HTTPS without using the default hostname verifier.

ApacheDockerHttpClient.Builder.build() eventually calls new SSLConnectionSocketFactory() leading to a default HttpsSupport.getDefaultHostnameVerifier() which requires Subject Alternative Names match the host/IP being used to connect.

Although possibly what many or most people want, this precludes certain use cases.

Target: ApacheDockerHttpClient construction is flexible enough to support a custom hostname verifier.

Proposal:

Add additional builder methods to ApacheDockerHttpClient.Builder to accept a custom hostname verifier.

[idontusenumbers]

After looking at the code, stuffing a hostname verifier into the SSLConfig seems like a better path forward.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[idontusenumbers]

PR is still pending