http_parser: fix error return in Finish()
#24738
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nodejs-github-bot
added
c++
|
cc @nodejs/http |
|
Update: No changes to llhttp needed, as it turned out today. |
`http_parser_execute(..., nullptr, 0)` returns either `0` or `1`. The expectation is that no error must be returned if it is `0`, and if it is `1` - a `Error` object must be returned back to user. The introduction of `llhttp` and the refactor that happened during it accidentally removed the error-returning code. This commit reverts it back to its original state. Fix: nodejs#24585
indutny
force-pushed
the
fix/http-finish
branch
from
db61379
to
95bd7b2
Compare
4 tasks
This was referenced Dec 1, 2018
lpinca
approved these changes
Dec 2, 2018
jasnell
approved these changes
Dec 2, 2018
|
Landed in 84aba432bf, thank you! |
indutny
added a commit
that referenced
this pull request
Dec 2, 2018
`http_parser_execute(..., nullptr, 0)` returns either `0` or `1`. The expectation is that no error must be returned if it is `0`, and if it is `1` - a `Error` object must be returned back to user. The introduction of `llhttp` and the refactor that happened during it accidentally removed the error-returning code. This commit reverts it back to its original state. Fix: #24585 PR-URL: #24738 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
BridgeAR
pushed a commit
that referenced
this pull request
Dec 5, 2018
`http_parser_execute(..., nullptr, 0)` returns either `0` or `1`. The expectation is that no error must be returned if it is `0`, and if it is `1` - a `Error` object must be returned back to user. The introduction of `llhttp` and the refactor that happened during it accidentally removed the error-returning code. This commit reverts it back to its original state. Fix: #24585 PR-URL: #24738 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
This was referenced Dec 7, 2018
refack
pushed a commit
to refack/node
that referenced
this pull request
Jan 14, 2019
`http_parser_execute(..., nullptr, 0)` returns either `0` or `1`. The expectation is that no error must be returned if it is `0`, and if it is `1` - a `Error` object must be returned back to user. The introduction of `llhttp` and the refactor that happened during it accidentally removed the error-returning code. This commit reverts it back to its original state. Fix: nodejs#24585 PR-URL: nodejs#24738 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
mscdex
added a commit
to mscdex/io.js
that referenced
this pull request
Feb 1, 2019
This was referenced Feb 1, 2019
BethGriggs
pushed a commit
that referenced
this pull request
Feb 5, 2019
Refs: #24738 Fixes: #25858 PR-URL: #25863 Reviewed-By: Fedor Indutny <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
rvagg
pushed a commit
that referenced
this pull request
Feb 28, 2019
Refs: #24738 Fixes: #25858 PR-URL: #25863 Reviewed-By: Fedor Indutny <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
mscdex
added a commit
to mscdex/io.js
that referenced
this pull request
Feb 28, 2019
mscdex
added a commit
to mscdex/io.js
that referenced
this pull request
Mar 9, 2019
BethGriggs
pushed a commit
that referenced
this pull request
Mar 11, 2019
Refs: #24738 Fixes: #25858 PR-URL: #25939 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Beth Griggs <[email protected]>
BethGriggs
pushed a commit
that referenced
this pull request
Mar 20, 2019
`http_parser_execute(..., nullptr, 0)` returns either `0` or `1`. The expectation is that no error must be returned if it is `0`, and if it is `1` - a `Error` object must be returned back to user. The introduction of `llhttp` and the refactor that happened during it accidentally removed the error-returning code. This commit reverts it back to its original state. Backport-PR-URL: #25938 Fix: #24585 PR-URL: #24738 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
http_parser_execute(..., nullptr, 0)returns either0or1. Theexpectation is that no error must be returned if it is
0, and ifit is
1- aErrorobject must be returned back to user.The introduction of
llhttpand the refactor that happened during itaccidentally removed the error-returning code. This commit reverts it
back to its original state.
Fix: #24585
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes