-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
http2: need a way to deal with aborted connections #21836
Comments
I think it should be emitted by the server’s stream. Isn’t it? Can you attach a full stacktrace? Is this causing problems on Windows? |
Yes. But how would one know that? It’s not like this is documented or necessarily logical, because network connections match HTTP/2 sessions, not HTTP/2 streams. I’ll be opening a PR with a test update + docs shortly. |
Fixes: nodejs#21836 PR-URL: nodejs#21861 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Minwoo Jung <minwoo@nodesource.com>
The test issues in #21561 highlighted that we have an issue in HTTP/2 with dealing with aborted connections. At this point, it’s not obvious how to do so in a cross-platform manner without triggering uncaught exceptions.
This part of the test should not be necessary:
node/test/parallel/test-http2-respond-with-file-connection-abort.js
Lines 32 to 37 in d94950e
/cc @nodejs/http2 @apapirovski
The text was updated successfully, but these errors were encountered: