Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This simple http server responds differently in Node v14 vs v15.
Response in Node v14
Response in Node v15
I haven't done a thorough research with node and http specs as to why this behaviour is different but as I understand, the
102
response doesn't return a body. But if you try to send it, Node 14 smartly ignores it and does not send aContent-Length
header. However Node 15 sends this header, which is whyhttp-parser-js
waits for the body and never fireskOnMessageComplete
.