So if HttpClient's verifier is enabled by default, it won't allow
connections to the fallbacks because it will reject the cert.

On Sunday, December 1, 2013, oxtoacart wrote:

> In src/main/java/org/lantern/util/HttpClientFactory.java:
>
> >          log.debug("Configuring defaults...");
> > -        // We wrap our own socket factory in HttpClient's socket factory here
>
> Ah, I hadn't noticed that. I'm pretty sure that the default HttpClient
> already does hostname verification, so as long as we're connecting to an
> https endpoint at the far end, its cert should get validated. From what I
> can tell, the reason that the reason we provided our own
> LanternHostNameVerifier() was in order to trust the fallback server's cert,
> whose hostname and ips don't match how we're actually connecting to it.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/getlantern/lantern/pull/1159/files#r8014024>
> .
>