Bari node-fetch ya zaɓi wakilin proxy bayan juyar da hanya

Yi amfani da aikin wakili don maƙasudin HTTP da HTTPS domin juyar da hanya ta iya zaɓar wakilin proxy da ya dace.

URL ta farko na iya zama HTTPS yayin da URL da aka juya hanya ta zama HTTP. Zaɓi wakilin bisa ga maƙasudin kowace buƙata, maimakon ɗaure wakili ɗaya da URL ta farko.

Don fakitin node-fetch da aka shigo da shi a cikin manhajar ESM, ba da aiki:

import fetch from 'node-fetch';
import { HttpProxyAgent } from 'http-proxy-agent';
import { HttpsProxyAgent } from 'https-proxy-agent';

const proxyUrl = 'http://proxy.example:8080';
const httpAgent = new HttpProxyAgent(proxyUrl);
const httpsAgent = new HttpsProxyAgent(proxyUrl);

const response = await fetch('https://api.example/', {
  agent: url => url.protocol === 'http:' ? httpAgent : httpsAgent,
});

Maye gurbin URL na API da ƙarshen wurin proxy. Don API na jama'a da aka yarda da shi ta hanyar mai shiga tsakani na jama'a, jerin proxy na HTTP yana ba da 'yan takara don proxyUrl. Wakilan biyu na iya amfani da mai sauraron proxy na HTTP ɗaya; sunayensu suna nufin buƙatar zuwa ga maƙasudin.

URL da aka ba mai zaɓiWakilin da aka zaɓa
https://…httpsAgent
http://…httpAgent

Saboda haka aikin yana ci gaba da zaɓar wakilin da ya dace idan juyar da hanya ta canza ka'idar maƙasudin. proxyUrl yana ci gaba da bayyana mai shiga tsakani, ba tare da la'akari da wannan shawarar ba.

Ƙirƙiri wakilan sau ɗaya don aikin kuma sake amfani da su. Sarrafa matsayin da aka mayar da kuma karanta jikin amsa a cikin lambar da ke kira. Wannan mu'amalar wakili ta node-fetch ce; fetch da ke cikin Node yana amfani da wata mu'amalar jigilar daban.

Labarai masu alaƙa