http socket might get reset instead of normal close while handling timeout

• Version: v10.15.1
• Platform: Linux 0fe3a1d57e94 4.9.125-linuxkit #1 SMP Fri Sep 7 08:20:28 UTC 2018 x86_64 GNU/Linux
• Subsystem: http,net

We were experiencing unexpected dropped connections between AWS ALB and nodejs application resulting in 502 errors from load balancer.

Managed to replicate a condition when nodejs abnormally closes socket with RST packet instead of normal FIN packets.

Here's exact conditions:

server.timeout = 10 * 1000;
server.keepAliveTimeout = 0;

We kept doing requests to the same connection every 10 seconds to trigger the condition.

Note that data was received and acknowledged, but instead of handling data or closing socket in a normal way nodejs reset the tcp connection.