Rust headless_chrome: deji aqoonsiga proxy HTTP ka hor socodka
Dooro proxy HTTP marka browser-ka la bilaabo oo daa Fetch xaqiijinta tab-ka headless_chrome ka hor socodka.
Gudaha crate Rust headless_chrome, dejinta bilaabista browser-ka waxay doorataa dhexdhexaadiye HTTP. Maareeyaha Fetch ee tab-ka waxa uu bixiyaa akoonka marka Chromium uu codsado:
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()?;Shaqada ku wareegsan waxay gudbisaa khaladaadka, proxy_user iyo proxy_password-na waa qiyam String oo ka yimid habaynta akoonka ee jira ee codsiga. Deji xaqiijinta ka hor inta socodku uusan kicin karin caqabadda.
Doodda labaad ee enable_fetch waxay daaysaa dhacdooyinka xaqiijinta. Chromium ma tixgeliso macluumaadka isticmaalaha ee ku dhex jira --proxy-server sida is-weydaarsiga aqoonsigan.
Hay browser-ka iyo tab-ka nool inta shaqadu socoto. Haddii sidoo kale la rakibay dhexgalka Fetch gaar ah, qeex cidda sii wadda codsiyada la joojiyay iyo cidda ka jawaabta caqabadaha; codsi la joojiyay oo aan la xallin ayaa joojin kara socodka.
Dejintan fudud ee xaqiijinta tab-ka waxay u qadanaysaa caqabadda proxy ee loogu talagalay. Socodka shaqada ee leh xaqiijin origin aan xiriir lahayn wuxuu u baahan yahay qexasho cad oo caqabadda ah halkii akoonka dhexdhexaadiyaha loo isticmaali lahaa server kasta. Xaddidaadda Chromium ee SOCKS5 ee magaca isticmaalaha iyo furaha sirta ah sidoo kale way ka duwan tahay waddadan xaqiijinta HTTP.