node-http-proxy-ttfb-timeout

Node.js HTTP proxy requests hang on keep-alive connections because standard timeouts often fail to trigger on reused sockets, requiring a reliable Time-To-First-Byte (TTFB) timeout mechanism to detect upstream service unresponsiveness.

To implement a TTFB timeout for a Node.js reverse proxy, apply a timeout mechanism that safely monitors both new and reused HTTP/S connections, ensuring timely failure detection when upstream services become temporarily unavailable.

Node.js http.request does not natively guarantee reliable timeouts on reused keep-alive sockets due to race conditions, making a dedicated TTFB timeout implementation necessary for robust failure detection.

The best way to fix hanging requests in a Node.js reverse proxy is to implement a robust Time-To-First-Byte (TTFB) timeout that handles keep-alive connection race conditions across http.request and https.request.

You need a TTFB timeout for HTTP proxying when your upstream service might become temporarily unstable, causing subsequent requests on persistent keep-alive connections to fail to complete indefinitely.

Yes, you can use the same robust TTFB timeout mechanism for both http.request and https.request to ensure consistent timeout handling and timely failure detection across your Node.js reverse proxy implementation.