| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Hey thank you for your contribution, would you mind adding a test for this? |
Sorry, something went wrong.
|
Good point, I forgot. Will add it now! |
Sorry, something went wrong.
|
For some reason "now" became "3 days". :) |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
I'm not 100% sure about this, but I think this needs to be opened against v12.x-staging rather than v12.x. (Someone else, please confirm!) @nodejs/releasers |
Sorry, something went wrong.
That's correct |
Sorry, something went wrong.
Sorry, something went wrong.
|
/cc @nodejs/http |
Sorry, something went wrong.
|
@targos should this still be included in the next v12 release? @nodejs/http @nodejs/http2 @nodejs/streams PTAL |
Sorry, something went wrong.
Sorry, something went wrong.
|
I hope it would be included. |
Sorry, something went wrong.
PR-URL: #33307 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
PR-URL: #33307 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
| Back | FazBrowse Home | New Git URL |
Setting headersTimeout to 0 does not disable the checks as expected but rather makes any request fail immediately.
This PR fixes the problem. This should also be backported to 10.x.
Node 13 and 14/master are fine since headersTimeout live now in HTTPParser which correctly checks for the value being greater than 0.
Checklist