Cannot connect to localhost without global connectivity

[breyed]

On Windows, if there are no network cards installed or they are all disabled (e.g. Windows 8 airplane mode), attempts to resolve localhost fail. The problem is that WebSocket++ uses the default value for the basic_resolver_query constructor's resolve_flags parameter is address_configured, which is AI_ADDRCONFIG on Windows. However, as implemented AI_ADDRCONFIG is actually detrimental, particularly for resolution of loopback and link-local addresses. See the Boost ticket 8503 for details.

[breyed]

I included the fix for this issue in pull request 243. In retrospect, I think I should have made a separate branch and pull request for the change (I'm new to git and pull requests).

[zaphoyd]

I need to do a bit more research about the tradeoffs of not being able to resolve localhost queries vs triggering dns/connection timeouts on machines with single stack IPv4 or IPv6 connectivity connecting to dual stack hosts. In the mean time, connecting to 127.0.0.1 or [::1] rather than "localhost" should allow you connect to servers running on the loopback in airplane mode.