René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"net: setKeepAlive options ignored before connect","articleBody":"\u003c!--\r\nThank you for reporting a possible bug in Node.js.\r\n\r\nPlease fill in as much of the template below as you can.\r\n\r\nVersion: output of `node -v`\r\nPlatform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)\r\nSubsystem: if known, please specify the affected core module name\r\n\r\nIf possible, please provide code that demonstrates the problem, keeping it as\r\nsimple and free of external dependencies as you can.\r\n--\u003e\r\n\r\n* **Version**: v13.7.0\r\n* **Platform**: linux 5.5.2\r\n* **Subsystem**: net\r\n\r\n\u003c!-- Please provide more details below this comment. --\u003e\r\n\r\nIf `setKeepAlive()` is called on a tcp socket before the `connect` event, then the `initialDelay` parameter is ignored.\r\nThis bug was alread reported [here](https://github.com/nodejs/node-v0.x-archive/issues/8572) for version 0.12, but it still seems to be there in 13.7.\r\n\r\nIf, for instance, I call `setKeepAlive(true, 10000)` before the `connect` event, the default initialDelay of 7200s is used.\r\n`netstat -ntp --timers` gives:\r\n```\r\ntcp        0      0 10.10.15.220:56866      10.10.15.148:6666       ESTABLISHED 132820/node          keepalive (7132.09/0/0)\r\n```\r\n","author":{"url":"https://github.com/lgpasquale","@type":"Person","name":"lgpasquale"},"datePublished":"2020-02-06T15:05:24.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/31663/node/issues/31663"}