Nika i-RSelenium browser i-proxy yayo lapho kuvulwa iseshini

Sebenzisa i-extraCapabilities emzileni we-browser, futhi wehlukanise ukwenqatshwa kwe-session protocol ne-browser engakwazi ukufinyelela i-proxy.

Nikeza i-proxy njenge-ikhono leseshini ye-browser ngaphambi kwe-driver$open(), ekusetshenzisweni kwe-RSelenium okwamukelwa yi-WebDriver server i-session protocol:

browser_proxy <- list(
  proxyType = 'manual',
  httpProxy = 'proxy.example:8080',
  sslProxy = 'proxy.example:8080'
)

driver <- RSelenium::remoteDriver(
  remoteServerAddr = 'webdriver.example',
  port = 4444L,
  browserName = 'chrome',
  extraCapabilities = list(proxy = browser_proxy)
)
driver$open()

remoteServerAddr ikhomba insizakalo ye-WebDriver. Ikhono lichaza lapho i-browser iya khona ngokulandelayo. Isilungiselelo se-proxy se-HTTP ku-R sisodwa asilungiseleli lowo mzila we-browser.

Sebenzisa host:port ku-httpProxy naku-sslProxy. Eyesibili ikhetha izindawo ze-HTTPS; akusho ukuthi kukhona isilaleli se-proxy esivikelwe nge-TLS. Umuntu ofaka isicelo se-HTTP esidlangalaleni ovela kuhlu lwama-proxy e-HTTP unikeza i-host ne-port yalezi zinkambu, inqobo nje uma i-host ye-browser ingafinyelela kuyo.

Yikuphi ukwehluleka okwenzeka kuqala?

Uma ukuvulwa kweseshini kunqatshwa, hlola ukuhambisana kwe-protocol ngaphambi kokushintsha i-proxy endpoint. Umthombo we-remoteDriver we-RSelenium uthumela ama-desiredCapabilities amadala; noma iyiphi i-WebDriver server yamanje ingase yenqabe leyo fomethi ngaphambi kokuba kube khona i-browser yokuhlola umzila.

Uma iseshini ivuleka kodwa ukuzulazula kwehluleka, hlola ukufinyeleleka kusuka ku-host yangempela ye-browser. Ku-container noma i-Grid node, localhost isho leyo node, hhayi isiteshi sokusebenza se-R.

Izihloko ezihlobene