Skip to content

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

Description

@addaleax
  • 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

Activity

  1. added
    http2Issues and PRs related to the http2 subsystem.
    on Jul 16, 2018
  2. mcollina commented on Jul 17, 2018

    @mcollina
    SponsorMember

    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?

  3. addaleax commented on Jul 17, 2018

    @addaleax
    MemberAuthor

    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.

  4. self-assigned this
    on Jul 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

http2Issues and PRs related to the http2 subsystem.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions