On Thursday, September 17, 2020 at 7:54:23 AM UTC+8 gneuner2 wrote:
>
> That's true - Windows tries IPv6 first
Windows does not try IPv6 first.
Client applications that call `getaddrinfo` with `AF_UNSPEC` , ask for both
IPv4 and IPv6 addresses when resolving names. When that happens, the
On 9/16/2020 5:59 PM, Alex Harsanyi wrote:
On Windows at least, "localhost" resolves to two IP addresses (in this
order): "::1" (IPv6) and "127.0.0.1". The Racket `tcp-connect`
function will try the fist one first, and since you probably don't
bind your web server to the IPv6 address, the
On Windows at least, "localhost" resolves to two IP addresses (in this
order): "::1" (IPv6) and "127.0.0.1". The Racket `tcp-connect` function
will try the fist one first, and since you probably don't bind your web
server to the IPv6 address, the connection times out, than `tcp-connect`
tries
On Wed, 16 Sep 2020 08:14:11 -0700, Stephen Foster
wrote:
>Turns out it's largely a "my system thing": requests to "localhost" are
>slow, but 127.0.0.1 are fast. On Chrome and curl, both were fast, which is
>why I assumed the slowdown was in some Racket package. It's more likely a
>DNS issue.
Thanks everyone. We resolved the issue over on the http-easy package:
https://github.com/Bogdanp/racket-http-easy/issues/6
I'll summarize for the curious:
Turns out it's largely a "my system thing": requests to "localhost" are
slow, but 127.0.0.1 are fast. On Chrome and curl, both were fast,
5 matches
Mail list logo
