Buɗaɗɗiyar burauza ta Puppeteer ɗaya na iya riƙe mahallin wakili daban-daban

Yi amfani da BrowserContextOptions.proxyServer a cikin Puppeteer25.16.0 sa'ad da ƙungiyoyin shafuka ke buƙatar hanyoyin wakili daban-daban a cikin burauza ta Chromium ɗaya.

Puppeteer 25.16.0 yana ba da zaɓi proxyServer lokacin ƙirƙirar mahallin burauza. Ga burauzar Chromium data kasance, shafuka a cikin sabon mahalli na iya amfani da matsakanci da aka zaɓa, ciki har da ɗan takarar HTTP na jama'a daga jerin wakilan HTTP:

const context = await browser.createBrowserContext({
  proxyServer: 'http://proxy.example:8080',
});
try {
  const page = await context.newPage();
  await page.goto('https://www.example.com/');
} finally {
  await context.close();
}

Ƙirƙiri wani mahalli da wani proxyServer don hanya ta biyu. Shafuka biyu da aka ƙirƙira a cikin mahalli ɗaya suna raba manufar wakili ta wannan mahallin; buɗe sabon shafi shi kaɗai ba ya zaɓar sabuwar ƙarshen hanya.

Zaɓin shine proxyServer. Tsofaffin misalan createIncognitoBrowserContext na wata ƙarni na API ne da ya gabata.

BrowserContextOptions kuma yana karɓar proxyBypassList. Riƙe keɓancewar kai tsaye a cikin manufar wannan mahallin maimakon ɗauka sun fito daga wani mahalli.

Ga wakilin HTTP da aka tallafa mai sunan mai amfani da kalmar sirri, Page.authenticate yana bayar da shaidar shiga kafin kewayawa. Adireshin wakili yana zaɓar matsakanci, kuma kiran tabbatarwa yana bayar da asusun.

Wannan hanyar sadarwar burauza ce. Fakitin da ke tsare buƙatar shafi kuma ya cika ta da amsar abokin ciniki na Node HTTP yana ƙirƙirar wata hanyar jigilar daban, da nata ɗabi'ar kuki, kan kai da TLS.

Mai kira har yanzu yana da alhakin rayuwar burauzar da aka raba. Rufe mahalli ɗaya yana rufe shafukansa masu alaƙa ba tare da kawo ƙarshen sauran mahallin ba.

Labarai masu alaƙa