Skip to content
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

Closed
addaleax opened this issue Jul 16, 2018 · 2 comments
Closed

http2: need a way to deal with aborted connections #21836

addaleax opened this issue Jul 16, 2018 · 2 comments
Assignees
Labels
http2 Issues or PRs related to the http2 subsystem.

Comments

@addaleax
Copy link
Member

  • Platform: various
  • Subsystem: http2

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:

// TODO(addaleax): This is a *hack*. HTTP/2 needs to have a proper way of
// dealing with this kind of issue.
process.once('uncaughtException', (err) => {
if (err.code === 'ECONNRESET') return;
throw err;
});

/cc @nodejs/http2 @apapirovski

@addaleax addaleax added the http2 Issues or PRs related to the http2 subsystem. label Jul 16, 2018
@mcollina
Copy link
Member

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?

@addaleax
Copy link
Member Author

I think it should be emitted by the server’s stream. Isn’t it?

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.

@addaleax addaleax self-assigned this Jul 17, 2018
addaleax added a commit to addaleax/node that referenced this issue Jul 17, 2018
addaleax added a commit to addaleax/node that referenced this issue Jul 17, 2018
addaleax added a commit that referenced this issue Jul 23, 2018
Refs: #21836
Refs: #21561

PR-URL: #21861
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Minwoo Jung <[email protected]>
targos pushed a commit that referenced this issue Jul 24, 2018
Refs: #21836
Refs: #21561

PR-URL: #21861
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Minwoo Jung <[email protected]>
targos pushed a commit that referenced this issue Jul 24, 2018
Fixes: #21836

PR-URL: #21861
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Minwoo Jung <[email protected]>
kjin pushed a commit to kjin/node that referenced this issue Aug 23, 2018
Fixes: nodejs#21836

PR-URL: nodejs#21861
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Minwoo Jung <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
http2 Issues or PRs related to the http2 subsystem.
Projects
None yet
Development

No branches or pull requests

2 participants