Fixed error handling in geo ip lookup closes #2011

Mind taking a look at this @aranhoide?
I think the best solution is to just move the geo IP lookup to the Go side.
That just takes a little fiddling with the startup sequence.

On Tuesday, November 25, 2014, aranhoide <notifications@github.com> wrote:

> In src/main/java/org/lantern/S3Config.java:
>
> > @@ -42,16 +39,7 @@
> >      }
> >
> >      public static final FlashlightMasquerade MASQUERADE =
> > -            new FlashlightMasquerade(DEFAULT_HOSTS_TO_CERTS, new MasqueradeListener() {
> > -
> > -                @Override
> > -                public void onTestedAndVerifiedHost(String host) {
> > -                    synchronized (TESTED_AND_VERIFIED_HOSTS) {
> > -                        LOG.info("Adding tested and verified host: {}", host);
> > -                        TESTED_AND_VERIFIED_HOSTS.add(host);
> > -                    }
> > -                }
> > -            });
> > +            new FlashlightMasquerade(DEFAULT_HOSTS_TO_CERTS);
>
> So the Java side is using domain fronting directly, and IIUC we're
> managing the set of masquerades that the Lantern side uses separately from
> the ones in the Go side? If we wanted to get rid of the duplicate
> management of masquerades, an option would be to just start a "get mode"
> flashlight provisionally, and shut it down later if we find we don't need
> it.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/getlantern/lantern/pull/2013/files#r20919273>.
>


-- 
--
President
Brave New Software Project, Inc.
https://www.getlantern.org
pgp A998 2B6E EF1C 373E 723F A813 045D A255 901A FD89