Si browser-ka RSelenium proxy-giisa u helo marka la furayo session-ka
Isticmaal extraCapabilities ee marinka browser-ka, kana sooc diidmada borotokoolka session-ka iyo browser aan gaadhi karin proxy-ga.
U dhiib proxy-ga sida awoodda session-ka browser-ka ka hor driver$open(), deployment RSelenium oo server-ka WebDriver uu aqbalaayo borotokoolka session-ka:
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 waxay tilmaamaysaa adeegga WebDriver. Awooddu waxay qeexdaa halka browser-ku u socdo xiga. Dejinta proxy HTTP ee R oo kaliya ma habayso marinka browser-kaas.
Isticmaal host:port gudaha httpProxy iyo sslProxy. Midda dambe waxay doorataa meelaha HTTPS; macneheedu maaha dhageyste proxy oo TLS ilaaliso. Musharax HTTP dadweyne oo ka socda liiska proxy HTTP wuxuu bixiyaa host iyo port goobahan, haddii host-ka browser-ku gaari karo.
Ciladdee ayaa marka hore dhacday?
Haddii furitaanka session-ka la diido, hubi iswaafajinta borotokoolka ka hor inta aanad beddelin barta dambeeya proxy-ga. Isha remoteDriver ee RSelenium waxay diraa desiredCapabilities duug ah; server kasta oo WebDriver hadda jira wuu diidi karaa qaabkaas ka hor inta aan browser u jirin si loo tijaabiyo marinka.
Haddii session-ku furmo laakiin socodku guuldareysto, hubi gaaritaanka host-ka dhabta ah ee browser-ka. Container ama node Grid, localhost waxay ka dhigan tahay node-kaas, ma aha xarunta shaqada R.