| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
As long as data of the in-flight response is not yet written to the socket, we can reply an error response without corrupting the client.
|
Review requested:
|
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM once CI failures are fixed
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM!
Sorry, something went wrong.
remove obsolete comment
fix comment Co-authored-by: Luigi Pinca <luigipinca@gmail.com>
There was a problem hiding this comment.
lgtm
Sorry, something went wrong.
Sorry, something went wrong.
|
Shall we proceed to get this PR landed? |
Sorry, something went wrong.
As long as data of the in-flight response is not yet written to the socket, we can reply an error response without corrupting the client. PR-URL: #44818 Reviewed-By: Paolo Insogna <paolo@cowtech.it> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Ricky Zhou <0x19951125@gmail.com>
| Back | FazBrowse Home | New Git URL |
Fix #37685, which is introduced in e8d7fed. It is too conservate (from the perspective from avoiding corrupting the client) to reply an error message.
Cases where we should reply an error message are covered in those 4 tests this PR modified, while the case where the socket should be immediately destroyed is covered in test/parallel/test-http-header-badrequest.js.