undici: Headers Timeout Error

Bug Description

On our error reporting system, we see Headers Timeout Errors.

HeadersTimeoutError: Headers Timeout Error
    at Timeout.onParserTimeout [as _onTimeout] ([NODE_MODULES]/undici/lib/client.js:1005:28)
    at listOnTimeout (node:internal/timers:561:11)
    at processTimers (node:internal/timers:502:7)

That’s part of the onHeadersComplete method. That method is being called from wasm_on_headers_complete.

I am not sure why these are happening. I don’t know enough to provide more information.

Reproducible By

I don’t know how to reproduce this. Happens in the background because it’s wrapped in a setTimeout

Expected Behavior

Logs & Screenshots

Environment

Node 16.14.0-alpine

Additional context

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 18 (3 by maintainers)

Most upvoted comments

Am I the only programmer left in the world? How come there is still no answer all over the internet about how to increase the Headers timeout natively in node.js?

Am I dreaming? It is Node.js 19 already, and I’m still bounded by uneditable 30s timeout??? And no general cry? Did everyone abandon Node.js development without telling me?

+18

thematan on Apr 9, 2023

It’s a bug in node’s native fetch. Node-fetch works fine

On Sun, Apr 9, 2023, 7:55 AM Matan Cohen @.***> wrote:

Am I the only programmer left in the world? How come there is still no answer all over the internet about how to increase the Headers timeout natively in node.js?

Am I dreaming? It is Node.js 19 already, and I’m still bounded by uneditable 30s timeout??? And no general cry? Did everyone abandon Node.js development without telling me?

— Reply to this email directly, view it on GitHub https://github.com/nodejs/undici/issues/1272#issuecomment-1501147658, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIQ4BJKXRIIJZIU6K2CIBTXALEVVANCNFSM5QNACCTA . You are receiving this because you commented.Message ID: @.***>

+13

ehartford on Apr 9, 2023

Does anyone know why this issue is closed?

albertodiazdorado on Mar 13, 2024

@thematan

Am I the only programmer left in the world? How come there is still no answer all over the internet about how to increase the Headers timeout natively in node.js?

Am I dreaming? It is Node.js 19 already, and I’m still bounded by uneditable 30s timeout??? And no general cry? Did everyone abandon Node.js development without telling me?

I feel your pain. I just updated to node 20 and have longer timeouts by default (unfortunate that I’m replying months later)

gtarsia on Jul 20, 2023

Oh no. Thanks but I mean I have a problem with deploying contracts using @openzeppelin/hardhat-upgrades. And I guess it uses node’s native fetch in its sub modules. So I thought you had the same problem with contract deployment and wanted to ask about patch on @openzeppelin/hardhat-upgrades modules. @ehartford

hawkofsky on Jun 15, 2023

Interesting. If I get more info, I will add it here. I will close for now

umarov on Mar 10, 2022