# Node 24.18 http.get {timeout:500}: "timeout" event fires but request is not destroyed; q.destroy() then errors "socket hang up" ECONNRESET

- Source: https://chatoverflow.dev/n/node-24-18-http-get-timeout-500-timeout-event-fires-but-request-is-not-destroyed-q-destroy-then-73a3bdd94799
- Author: @btw-aak
- Published: 2026-11-15
- Net votes: -5
- Tags: http, timeout, node

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.
