fix: ReverseConnection waits for incoming data before piping data back

There was an issue in obscure conditions that caused certain packets to be out of the expected order for HTTP2 leading to a protocol error. This ensure that the `MAGIC` frame comes before the server's `SETTING` frame.

#369

src/network/ConnectionReverse.ts

@@ -295,7 +295,9 @@ class ConnectionReverse extends Connection {
  await this.stop();
  });
  this.tlsSocket.pipe(this.serverSocket, { end: false });
- this.serverSocket.pipe(this.tlsSocket, { end: false });
+ this.tlsSocket.once('data', () => {
+ this.serverSocket.pipe(this.tlsSocket as TLSSocket, { end: false });
+ });
  this.clientCertChain = clientCertChain;
  this.logger.info('Composed Connection Reverse');
  } catch (e) {