alejandrin.Ritchie answered on March 23rd 20 at 18:46
There is quite a complex interaction of several protocols.
HTTP request if the server is actually dead, then TCP will try to reach him several times. If the answer is not, the browser will give the appropriate error.
That is, the browser do not make.
Jazlyn.Klein49 answered on March 23rd 20 at 18:48
As far as I know, HTTP does not reglamentary, so it remains to usmotrenie client.
WebKit's probably waiting for up to timeout, and then terminates the connection.
NodeJS - can be different customers of the library and behave in different ways, too, but with a high probability of default are doing the same