Repository navigation
http: RangeError #59772
Copy link
Copy link
Closed
Labels
httpIssues and PRs related to the http subsystem.Issues and PRs related to the http subsystem.http2Issues and PRs related to the http2 subsystem.Issues and PRs related to the http2 subsystem.
Description
Activity
- addedhttpIssues and PRs related to the http subsystem.Issues and PRs related to the http subsystem.
on Sep 5, 2025 I think this might be related to http2 to http1 fallback. @nodejs/http2 Not sure I quite follow the logic yet...
Found what causes this:
import http2 from 'node:http2' import https from 'node:https' import { readFileSync } from 'node:fs' const server = http2.createSecureServer({ key: readFileSync('../proxy/cert/server.key'), cert: readFileSync('../proxy/cert/server.crt'), allowHTTP1: true, }) .on('request', (req, res) => { console.log(req.httpVersion, server.keepAliveTimeout, server.keepAliveTimeoutBuffer) // 1.1 undefined undefined }) .listen(9999) server.keepAliveTimeout = 1e3 https.get('https://localhost:9999', { rejectUnauthorized: false }, (res) => { res.end() })
- addedhttp2Issues and PRs related to the http2 subsystem.Issues and PRs related to the http2 subsystem.
on Sep 6, 2025 @ronag
I recently opened PR #59243 (http: add server.keepAliveTimeoutBuffer option),
which touches a similar area of the HTTP keep-alive handling.I thought this issue might be related to
keepAliveTimeout/
keepAliveTimeoutBufferbeing leftundefinedwhen falling back from HTTP/2 to HTTP/1.I now see that follow-up PRs (#59773, #59784) are already in progress to fix this.
Sorry for the noise..Closing as this issue was fixed in #59784
Metadata
Metadata
Assignees
Labels
httpIssues and PRs related to the http subsystem.Issues and PRs related to the http subsystem.http2Issues and PRs related to the http2 subsystem.Issues and PRs related to the http2 subsystem.
Node.js v24.6.0
This should not be possible... looks like a node core bug to me