New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
request.setTimeout stopped working properly #186
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've been using version 1.13.0 until the recent security issue. After upgrading to 1.14.7, I've noticed some of my code that relies on follow-redirects fails. Specifically, scenarios where a timeout occurs during stream. Currently tested on node 14.17.0
How to reproduce:
create a server.js file. Note the artificial stream, that fakes a timeout between the packets:
Create a client.js file:
When follow-redirects is used, the callback of setTimeout doen't fire. The request just ends, and the file is downloaded partially, without any error.
However, when the native http.request function is used, the timeout event fires as expected.
This wasn't the situation in version 1.13.0. I don't know in which version it broke though.
Can you look into it?
The text was updated successfully, but these errors were encountered: