turns out #Windows is slow to fail connect attempts to non-listening ports entirely on purpose because it waits and resends the SYN several times, contrary to how other TCP stacks behave.
⇧
turns out #Windows is slow to fail connect attempts to non-listening ports entirely on purpose because it waits and resends the SYN several times, contrary to how other TCP stacks behave.
daniel:// stenberg://
in reply to daniel:// stenberg:// • • •with this knowledge we are pondering what we can to do make things less annoying for #curl on Windows.
What now takes a few milliseconds on my Linux machine, takes several seconds on Windows. Not ideal.
Derick Rethans
in reply to daniel:// stenberg:// • • •Derick Rethans
in reply to daniel:// stenberg:// • • •Christian
in reply to daniel:// stenberg:// • • •simendsjo
in reply to daniel:// stenberg:// • • •kurtseifried (he/him)
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to kurtseifried (he/him) • • •LisPi
in reply to daniel:// stenberg:// • • •They provide no user-level or application-level override options?
That's kind of gross and annoying.
daniel:// stenberg://
in reply to LisPi • • •daniel:// stenberg://
Unknown parent • • •daniel:// stenberg://
Unknown parent • • •Alba 🌸
Unknown parent • • •Pedro Pérez
in reply to daniel:// stenberg:// • • •@shaknais
I think @mildsunrise means you want the SYN to be retried if you just reached timeout without response (as both Linux and Windows do), but in this case the problem is Windows retries even when getting a RST, which is indeed a bit... unexpected.
daniel:// stenberg://
Unknown parent • • •Alba 🌸
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
Unknown parent • • •Alba 🌸
in reply to Alba 🌸 • • •Dianne S
in reply to daniel:// stenberg:// • • •I want to be inside the head of whoever decided a SYN should be retried even after a RST is received.
"Oh well... maybe something *will* start listening on that port in the near future, so let's retry..."
SMH.
mi
in reply to Dianne S • • •daniel:// stenberg://
in reply to mi • • •Dianne S
in reply to daniel:// stenberg:// • • •$ curl localhost:6789
curl: (7) Failed to connect to localhost port 6789 after 0 ms: Couldn't connect to server
(Linux, though.)
Eugen Neuber
in reply to daniel:// stenberg:// • • •Brett Edmond Carlock
in reply to daniel:// stenberg:// • • •@dalias
What would a justification for this behavior be? I'm going to assume someone had a good reason to change from convention...
#Windows