You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Linux ___ 5.4.0-99-generic #112-Ubuntu SMP Thu Feb 3 13:50:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
No response
What steps will reproduce the bug?
If I comment out the requestTimeout (the second line), then I can download the large file that takes minutes (I simulate with Chromium's network throttle to 'Slow 3G').
If I have the requestTimeout enabled, then node.js aborts the download after (usually) 100 seconds (typically after 4 MB on 'Slow 3G').
Sets the timeout value in milliseconds for receiving the entire request from the client.
Do you perhaps want to set the socket timeout (req.setTimeout) instead if what you want to check is inactivity on the connection rather the total request timeout?
Version
v16.14.0
Platform
Linux ___ 5.4.0-99-generic #112-Ubuntu SMP Thu Feb 3 13:50:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
No response
What steps will reproduce the bug?
If I comment out the requestTimeout (the second line), then I can download the large file that takes minutes (I simulate with Chromium's network throttle to 'Slow 3G').
If I have the requestTimeout enabled, then node.js aborts the download after (usually) 100 seconds (typically after 4 MB on 'Slow 3G').
Also tested on a different browser with real slow connection.
How often does it reproduce? Is there a required condition?
Always without exception.
What is the expected behavior?
If I set httpServer.requestTimeout, it does not abort the download at all.
What do you see instead?
Download is aborted after (usually) 100 seconds.
Additional information
No response
The text was updated successfully, but these errors were encountered: