Ku duub SOCKS socket TLS Node.js

SocksClient.createConnection waxay soo celisaa stream ku xiran destination-ka la codsaday. HTTPS, stream-kaas wali wuxuu u baahan yahay TLS handshake ka hor inta uusan qaadin codsiga HTTP.

import { SocksClient } from 'socks';
import tls from 'node:tls';

const targetHost = 'service.example';
const info = await SocksClient.createConnection({
  proxy: { host: 'proxy.example', port: 1080, type: 5 },
  command: 'connect',
  destination: { host: targetHost, port: 443 },
  timeout: 10000,
});
const secure = tls.connect({
  socket: info.socket,
  servername: targetHost,
});
secure.on('error', onTransportError);
secure.on('data', onResponseBytes);
secure.once('secureConnect', () => {
  secure.write(
    `GET /data HTTP/1.1\r\nHost: ${targetHost}\r\nConnection: close\r\n\r\n`
  );
});

Liiska proxy SOCKS5 waxay bixisaa musharaxiin host-ka iyo port-ka proxy. onTransportError iyo onResponseBytes waxay ka tirsan yihiin app-ka jira; tan labaad waa in ay falanqayso stream-ka jawaabta HTTP. Qaybaha xogta TLS ma aha fariimaha HTTP oo si madax-bannaan u buuxa.

servername waa magaca DNS ee destination-ka. tls.connect heerka hoose ee Node ma shido SNI si caadi ah, magaca host-ka proxy-na ma aha aqoonsiga shahaadada websaytka.

Ka fogow dami xaqiijinta shahaadada. Bixinta socket-ka xiran waxay ka fogaataa furitaanka xiriir toos ah oo gaar ah websaytka iyadoo ilaalinaysa aqoonsiga TLS.

Waqtiga SOCKS wuxuu xaddidaa gorgortankaas. Isweydaarsiga TLS iyo app-ka dambe wali wuxuu u baahan yahay waqtiga, joojinta iyo siyaasadda nadiifinta ee ujeeddada wacaha.