http2: throw better error when accessing unbound socket proxy

[jasnell]

Fixes the bug in the sense that a better error message is provided. Generally speaking, once the connection has been closed, users should not continue to the use the socket proxy object. So, throw whenever they try to.

Fixes: #22268

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• commit message follows commit guidelines

[nodejs-github-bot]

@jasnell build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/651/pipeline

[szmarczak]

There's another ways to expose the original socket:

session.socket.ref()session.socket.unref()session.socket.setEncoding()session.socket.setKeepAlive()session.socket.setNoDelay()

Should these be fixed?

[BridgeAR]

I am not sure if this is the ideal solution but the code looks good to me.

[BridgeAR]

What is expected to happen sync?

[jasnell]

What do you mean?

[jasnell]

Should these be fixed?

Yeah, I'll take another look.

[jasnell]

Added additional tests for the ref(), unref(), setEncoding(), setKeepAlive(), and setNoDelay() functions.

[jasnell]

CI: https://ci.nodejs.org/job/node-test-pull-request/16733/

[Trott]

Resume Build: https://ci.nodejs.org/job/node-test-pull-request/16749/

[Trott]

Theoretically semver-major (I think?) if it doesn't end up in the same release as the "HTTP/2 is stable!" thing, so let's get this thing landed.

I personally don't know that I would have chosen an HTTP2 error for this (and others) instead of one of the existing SOCKET errors, but maybe more specific is good and I make bad decisions. 🙃

[Trott]

@nodejs/http2

[mcollina]

LGTM

[jasnell]

Landed in dd03706

[szmarczak]

@jasnell I think you missed something :P

You can't do session.socket.destroy() because it'll throw ERR_HTTP2_NO_SOCKET_MANIPULATION, but you can do session.socket.ref().destroy(). As I said, these functions expose the original socket:

session.socket.ref()session.socket.unref()session.socket.setEncoding()session.socket.setKeepAlive()session.socket.setNoDelay()

So ProxySocket should look like:

get(session,prop){switch(prop){case'setTimeout': returnsession.setTimeout.bind(session);case'destroy': case'emit': case'end': case'pause': case'read': case'resume': case'write': case'setEncoding': case'setKeepAlive': case'setNoDelay': thrownewERR_HTTP2_NO_SOCKET_MANIPULATION();case'ref': case'unref': returnsocket[prop].bind(session.socket);default: constsocket=session[kSocket];if(socket===undefined)thrownewERR_HTTP2_SOCKET_UNBOUND();constvalue=socket[prop];returntypeofvalue==='function' ? value.bind(socket) : value;}} ... set(session,prop,value){switch(prop){case'setTimeout': session.setTimeout=value;returntrue;case'destroy': case'emit': case'end': case'pause': case'read': case'resume': case'write': case'setEncoding': case'setKeepAlive': case'setNoDelay': case'ref': case'unref': thrownewERR_HTTP2_NO_SOCKET_MANIPULATION();default: constsocket=session[kSocket];if(socket===undefined)thrownewERR_HTTP2_SOCKET_UNBOUND();socket[prop]=value;returntrue;}

[mcollina]

@szmarczak good spot! would you like to open a PR to fix that?

[szmarczak]

Yeah, sure.

[szmarczak]

@mcollina Here it is: #22650