See https://github.com/dropwizard/dropwizard/issues/1663 and corresponding pull request https://github.com/dropwizard/dropwizard/pull/1664.
Cheers, Tim On Monday, August 1, 2016 at 6:20:05 PM UTC-6, Tim Bartley wrote: > > Tried modifying dropwizard-client JerseyClientConfiguration and > HttpClientConfiguration to follow the same patter of setting DnsResolver's > which compiled but my HostnameVerifier was not called. Need to look further > as to why .... > > Cheers, > > Tim > > On Monday, August 1, 2016 at 11:25:19 AM UTC-6, Tim Bartley wrote: >> >> >> 11:19 AM (4 minutes ago) >> Hi, >> >> It seems like the ability to create an HTTP client with a custom >> HostnameVerifier using DropWizard's JerseyClientBuilder() has been lost in >> 1.0.0 (maybe earlier). >> >> I know there's lot's of TLS configuration now available but I still need >> to perform custom hostname verification. It's not immediately clear there's >> a work around for this. Any reason not to provide the old >> "using(HostnameVerifier hnv)" method on the JerseyClientBuilder again? >> >> Cheers, >> >> Tim >> > -- You received this message because you are subscribed to the Google Groups "dropwizard-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
