Thanks for looking into the issue.
> If someone knows how to fix this properly, please just send them a patch.
Probably not me, but I just opened a ticket: https://trac.ffmpeg.org/ticket/5973.
Closed by accident... But I doubt we can do much about your PAC problem, since we need to be JavaScript-capable to be able to support PAC, which apparently won't happen.
Feel free to ask questions though, I'd be happy to provide pointers if I can.
As expected, Lantern configures the system proxy with a PAC file. Sorry, googler doesn't support that (neither does curl/wget/etc.). You might be able to find out which proxy nodes Lantern is connecting to (with tcpdump or Wireshark for instance) and manually set the proxy with our `--proxy` option.
That doesn't help, you can't even finish the request with curl.
I don't know how Lantern works and can't seem to find an explanation (other than "better than a VPN" which is apparently marketing bullshit). My guess is it's a per-process proxy that covers your browsers but doesn't work with arbitrary processes like curl or googler's python.
The problem is we only allow a one-time redirection, whereas you're being redirected multiple times. We've never seen this before. We could account for that, but I'd like to see the output of
```sh
$ curl -IL 'https://www.google.com/search?ie=UTF-8&num=10&oe=UTF-8&q=hello&start=0'
```
first.