Hi
TLSClientParameters have boolean properties indicating how a host name
should be verified, which is usually enough, but JAX-RS 2.0 Client API
requires a support for concrete HostnameVerifier implementations, so at
the moment I'm simply extending TLSClientParameters to support a typed
property - if it is set then it will be preferred, if not - the default
verifier selection will be used.
I think we can also support setting the verifier as a message contextual
property - this will avoid updating TLSClientParameters, but I reckon
the former option might be better, we can also then allow setting custom
verifiers from Spring/Blueprint as the next step,
Comments welcome, I'll proceed with the former option if no one objects
Cheers, Sergey