Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

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

Copy link
Copy link
Open
@idontusenumbers

Description

@idontusenumbers
Issue body actions

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.