For now, it's possible to customize a TLS connection by specifying SSLContext. While it is already very useful, it is incomplete without the ability to specify HostnameVerifier. (Basically, I want to be able to connect to a TLS endpoint with a certificate that doesn't have to have a matching Common Name or Alternative Names.)

I propose adding the method hostnameVerifier() to ArangoDB.Builder, which would propagate a HostnameVerifier to com.arangodb.internal.http.HttpConnection, which in turn would pass it to the created SSLConnectionSocketFactory instance.

It should be quite easy to implement, I'll try to submit a PR when I have some time.