Repository navigation
http2: sessionError vs aborted #28267
Description
A little confusion regarding the 'sessionError' on http2 servers.
I'm getting a lot of sessionErrors with ECONNRESET. This feels more like clients killing their connections, i.e. aborted rather than an server/session error?
I believe currently we are handling most cases where a incoming connection is unexpectedly closed we emit aborted events rather than error?
Or is there something else that could cause such an error?
Is this a potential bug?
Activity
gireeshpunathil commentedon Oct 29, 2019
@nodejs/http2
antsmartian commentedon Jan 8, 2020
Friendly ping : @nodejs/http2
apapirovski commentedon Jan 8, 2020
Likely means these clients don’t gracefully terminate their sessions. Unfortunately lack if conformance with the spec is rather common.
ronag commentedon Jan 8, 2020
Is there are reason why we can't/shouldn't normalize that into
'aborted'? Would potentially make using http2 in NodeJS easier?mcollina commentedon Jan 9, 2020
I'm +1 in using
'aborted', especially in the compat mode.ronag commentedon Apr 19, 2020
@rexagod maybe something you'd like to pick up?
github-actions commentedon Jun 27, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
github-actions commentedon Jul 28, 2026
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.