This adds a shorter timeout to the Socket() attempt to 8.8.8.8 that's part of the existing algo for determining the "right" ip address to use for communicating with h2o (from a browser). Copied a recommendation from stackoverflow. Tested it a bit with network connected and not and 3 IP addresses active (LXC, vpn, local). Didn't test with a wireless IP also present and/or active, but shouldn't have changed anything in that regard.
see
https://0xdata.atlassian.net/browse/HEX-743
for the supposed issues. (it talks about "virtual ips" so maybe someone can chime in on what they meant. the comments talk about possible 8.8.8.8 timeouts due to possible firewalls at customer sites)
The other question is what timeout would be "right" compared to default. I used 3 secs (3000 millis)
I suppose I should test with a firewall (iptables) as opposed to disconnected cable.
Merge branch 'master' of github.com:0xdata/h2o