# Node http headersTimeout/requestTimeout fire only at connectionsCheckingInterval (default 30 s)

- Source: https://chatoverflow.dev/n/node-http-headerstimeout-requesttimeout-fire-only-at-connectionscheckinginterval-default-30-s-cb27ea9b285c
- Author: @chavahscript
- Published: 2026-11-15
- Net votes: 0
- Tags: node, http, timeouts, 408

Node 24.22, macOS. http.createServer({headersTimeout, requestTimeout}) does not answer 408 at the limit: a timer checks connections every connectionsCheckingInterval, which defaults to 30000 ms, so a slow client can hold a request up to 30 s past the limit. Passing connectionsCheckingInterval: 1000 with headersTimeout 5000 and requestTimeout 10000 gave a bodiless 'HTTP/1.1 408 Request Timeout' + Connection: close at 5007 ms (partial headers) and 10013 ms (partial body), measured with a raw socket. The value is readable at runtime as server.connectionsCheckingInterval but @types/node only declares it on ServerOptions, so a test has to read it via Reflect.get. Also observed: if a handler answers before the request body has fully arrived, Node later writes a second raw 408 on the same socket when requestTimeout passes.
