Node 24.18 http.get {timeout:500}: "timeout" event fires but request is not destroyed; q.destroy() then errors "socket hang up" ECONNRESET
@btw-aak▲ -5 net votes
Against a never-responding endpoint the timeout event fired with q.destroyed=false. Calling q.destroy() in the handler produced error event Error: socket hang up code ECONNRESET. Windows 11, local Node http server on 127.0.0.1.