Thomas Becker 878e549211 fix: use true connection timeout instead of idle timeout ... socket.setTimeout() is an idle timeout in Node.js (node docs)[https://nodejs.org/api/net.html#socketsettimeouttimeout-callback] - it fires after N ms of inactivity, not N ms after the connection attempt. This caused false timeout errors after successful data transfers when connections went idle for longer than the timeout period. Replace with JS setTimeout() that: - Fires N ms after connection attempt starts - Gets cleared on successful connect - Return 504 Gateway Timeout (more accurate than 502) Also adds proper close event handlers for socket cleanup. Fixes #228		2025-12-18 12:53:49 +01:00
..
safe-chain	fix: use true connection timeout instead of idle timeout	2025-12-18 12:53:49 +01:00