You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From docs for socket.setKeepAlive([enable][, initialDelay]):
Set initialDelay (in milliseconds) to set the delay between
the last data packet received and the first keepalive probe.
So really keepAliveMsecs doesn't mean how often keep alive probe will be sent, it means delay between the last data received and the first keep alive probe.
The text was updated successfully, but these errors were encountered:
mscdex
added
http
Issues or PRs related to the http subsystem.
doc
Issues and PRs related to the documentations.
labels
Jun 18, 2016
This is correct, in that the HTTP client documentation is not correct, as the time is only the initial delay of the keep alive probe, not the interval between the probes. nodejs/node-v0.x-archive#4109 has a good discussion about this, though all Node.js documentation (and even the libuv documentation) are very terse on this subject and not very clear :)
Documentation for
keepAliveMsecs
says:But internally http.Agent just uses
keepAliveMsecs
insocket.setKeepAlive(true, self.keepAliveMsecs);
(https://github.com/nodejs/node/blob/master/lib/_http_agent.js#L73)From docs for
socket.setKeepAlive([enable][, initialDelay])
:So really
keepAliveMsecs
doesn't mean how often keep alive probe will be sent, it means delay between the last data received and the first keep alive probe.The text was updated successfully, but these errors were encountered: