Node.js HTTP/2 nge-HTTP CONNECT nge-createConnection

I-HTTP/1.1 proxy ingathwala ama-HTTP/2 frames endawo ngaphakathi kwe-CONNECT. I-proxy akudingeki ukuthi isebenzise lawo mafreyimu angaphakathi, kodwa iklayenti kufanele lenze ukudluliswa kwe-protocol ngokulandelana.

Ngemva kokuqinisekisa impendulo ephelele ye-CONNECT nokugcina tunnelSocket, engeza i-TLS yendawo bese unikeza i-stream esunguliwe ku-HTTP/2:

import tls from 'node:tls';
import http2 from 'node:http2';

const secureSocket = tls.connect({
  socket: tunnelSocket,
  servername: 'api.example',
  ALPNProtocols: ['h2'],
});
secureSocket.once('error', failRoute);
secureSocket.once('secureConnect', () => {
  if (secureSocket.alpnProtocol !== 'h2') {
    secureSocket.destroy();
    failRoute(new Error('Destination did not negotiate h2'));
    return;
  }
  const session = http2.connect('https://api.example', {
    createConnection: () => secureSocket,
  });
  session.on('error', failRoute);
  useSession(session);
});

createConnection ibuyisela i-TLS stream osele ihanjiswa yi-proxy esikhundleni sokuvula enye i-socket eqondile. I-servername yendawo inikeza i-SNI nobunikazi besitifiketi, ngokuqinisekisa kuvuliwe. Ukuhlola kwe-ALPN kwenqaba indawo engaxoxanga nge-h2.

I-failRoute kufanele ihlanze umzila; i-useSession inegunya lezicelo nokuvalwa kwesesheni. Sebenzisa izikhathi zokuxhumana nokusebenza ezizungeze le ngxenye.

Isixhumi sangaphandle sisengumnikazi wokuqondisa i-CONNECT host:port, ukuqinisekisa ku-proxy, ukuphatha ukwenqaba kanye namabhayithi agcinwe ngemuva kwezihloko. Qeda lokho ngaphambi kokunikeza i-socket ku-TLS; isandulela se-HTTP/2 esithunyelwa ngqo kumlaleli we-proxy HTTP/1.1 siqala kusendlalelo esingalungile.