-
Notifications
You must be signed in to change notification settings - Fork 30k
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
HTTP Parser issues with newline \n
#34576
Labels
http
Issues or PRs related to the http subsystem.
Comments
ronag
changed the title
HTTP Parser Issues with newline
HTTP Parser issues with newline Jul 31, 2020
\n
\n
I think |
ronag
added a commit
to nxtedition/node
that referenced
this issue
Jul 31, 2020
headers timeout should not occur *after* headers have been received. Fixes: nodejs#34576
4 tasks
codebytere
pushed a commit
that referenced
this issue
Aug 5, 2020
headers timeout should not occur *after* headers have been received. Fixes: #34576 PR-URL: #34578 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Fedor Indutny <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Pranshu Srivastava <[email protected]>
This was referenced May 27, 2022
This was referenced Sep 29, 2022
This was referenced Oct 5, 2022
This was referenced Oct 8, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following issue was found while working against a CouchDB changes stream which uses a newline
\n
as a form of a heartbeat on a long polling connection.OS: MacOS, Node 14.6
Will invoke
kOnTimeout
afterkOnHeadersComplete
. Also will stop invokingkOnExecute
but will keep invokingkOnBody
.Refs: nodejs/undici#268
Refs: nodejs/undici#269
The text was updated successfully, but these errors were encountered: