Layin buƙatar da ke tafiyar da HTTP na Node ta hanyar wakili

A cikin buƙatar HTTP ta yau da kullum ta hanyar wakilin gaba, Node yana haɗawa da wakilin kuma yana aika URL ɗin manufa a cikin layin buƙata. Ƙimomi uku suna bayyana wannan buƙata ɗaya:

Wannan misalin Node 22 yana bayyana rabuwa a fili:

const http = require('node:http');
const destination = new URL('http://example.com/news?q=proxy');

const request = http.get({
  hostname: 'proxy.example',
  port: 8080,
  path: destination.href,
  headers: { Host: destination.host },
  signal: AbortSignal.timeout(15000),
}, (response) => {
  console.log(response.statusCode);
  response.on('error', console.error);
  response.resume();
});
request.on('error', console.error);

Ƙarshen wuri ne na ajiya; zaɓi ɗan takara daga jerin wakilan HTTP don gwajin HTTP na jama'a kuma duba amsarsa. Misalin yana kwashe amsar bayan buga matsayinta; aikace-aikace na iya cinye jikin maimakon haka. Tambayar ta kasance ɓangare na maƙasudin buƙata.

Me ya sa cikakken URL ya kamata ya kasance a can

Sabar tushen yawanci tana karɓar maƙasudi kamar /news?q=proxy. Wakilin gaba kuma yana buƙatar manufar, don haka HTTP/1.1 ya bayyana maƙasudin a cikakkiyar siffa:

GET http://example.com/news?q=proxy HTTP/1.1
Host: example.com

A ƙarƙashin dokokin HTTP/1.1, wakilin da ya karɓi cikakkiyar siffa yana amfani da ikon URI yayin turawa kuma yana maye gurbin filin Host da aka karɓa mara daidaituwa. Aika kan Host mai daidaituwa na manufa har yanzu yana sa buƙatar da za ta fita ta kasance babu shakka. Sunan masaukin haɗin Node shi ne mai shiga tsakani, don haka saita kan da gangan maimakon dogaro da adireshin haɗin.

Idan ana buƙatar tabbatarwa, takardun shaidar wakilin nasa ne na tsallakensa. Zaɓin buƙata auth na Node yana ƙirƙirar kan Authorization don albarkatun; ba zaɓi ba ne na shiga wakili gaba ɗaya. Yi amfani da tsarin da wakilin ke buƙata da abokin ciniki na wakili da ya dace idan musayar ta fi rikitarwa.

HTTPS yana ƙara rami

Wannan misalin ya shafi turawa HTTP kawai. Haɗin HTTPS ta hanyar wakilin HTTP na yau da kullum yana fara neman CONNECT example.com:443, sannan ya fara TLS zuwa manufar cikin ramin da aka karɓa. Canza URL ɗin misali zuwa HTTPS baya ƙara waɗannan matakan.

Don HTTPS ko aiki gauraye, yi amfani da wakili ko mai aikawa da aka kula da shi tare da tallafin rami da ake buƙata. Don sifofin Node masu jituwa, zaɓi ɗaya shine fetch na Undici tare da ProxyAgent. Riƙe wannan ƙaramin misali na abokin ciniki na asali don lokuta inda musayar HTTP ta yau da kullum ita ce abin da kuke buƙatar sarrafawa ko fahimta.