http2: sessionError vs aborted

[ronag]

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?

[gireeshpunathil]

@nodejs/http2

[antsmartian]

Friendly ping : @nodejs/http2

[apapirovski]

Likely means these clients don’t gracefully terminate their sessions. Unfortunately lack if conformance with the spec is rather common.

[ronag]

Is there are reason why we can't/shouldn't normalize that into 'aborted'? Would potentially make using http2 in NodeJS easier?

[mcollina]

I'm +1 in using 'aborted', especially in the compat mode.

[ronag]

@rexagod maybe something you'd like to pick up?