Rust headless_chrome: saita bayanan HTTP proxy kafin kewayawa

A cikin Rust crate headless_chrome, saitin buɗe burauza yana zaɓar mai shiga tsakani na HTTP. Mai kula da Fetch na shafin yana bayar da asusun lokacin da Chromium ya nemi shi:

let proxy = "http://proxy.example:8080";
let options = headless_chrome::LaunchOptions::default_builder()
    .proxy_server(Some(proxy))
    .build()?;
let browser = headless_chrome::Browser::new(options)?;
let tab = browser.new_tab()?;

tab.enable_fetch(None, Some(true))?;
tab.authenticate(Some(proxy_user), Some(proxy_password))?;
tab.navigate_to("https://www.example.org/")?;
tab.wait_until_navigated()?;

Aikin da ke kewaye yana isar da kurakurai, kuma proxy_user da proxy_password String ne daga tsarin asusun da aikace-aikacen ke da shi. Saita tabbacin kafin kewayawa ta iya haifar da ƙalubalen.

Hujja ta biyu ta enable_fetch tana kunna abubuwan tabbaci. Chromium ba ya ɗaukar bayanan mai amfani da ke cikin --proxy-server a matsayin wannan musayar bayanan shiga.

Ka riƙe burauza da shafin a raye don aikin. Idan an kuma shigar da tsangwamar Fetch ta musamman, bayyana wanda zai ci gaba da buƙatun da aka dakatar da wanda zai amsa ƙalubale; barin buƙatar da aka dakatar ba a warware ba na iya tsayar da kewayawa.

Wannan sauƙin tabbacin shafin yana ɗaukan ƙalubalen proxy da aka nufa. Tsarin aiki da tabbacin origin mara alaƙa yana buƙatar bayyana iyakar ƙalubalen a fili maimakon sake amfani da asusun mai shiga tsakani ga kowane uwar garke. Har ila yau iyakar Chromium a SOCKS5 kan sunan mai amfani da kalmar sirri ta bambanta da wannan hanyar tabbacina ta HTTP.