I-Selenium WebDriver nama-proxy adinga ukungena: okusebenzayo
Ibhalwe yiThimba Lonjiniyela lakwa-ProxyV4 · Updated:
Ukuqinisekiswa kwe-proxy ku-Selenium kudinga elinye icebo, ngoba ifulegi le-ChromeDriver le---proxy-server=http://ip:port alikwazi ukuphatha i-username nephasiwedi; i-Chrome iyayilahla i-user:pass ebhaliwe bese ibonisa ibhokisi lokungena i-WebDriver engakwazi ukuligcwalisa. Izixazululo ezimbili ezithembekile yi-selenium-wire, ephatha ukungena kwe-ProxyV4 ku-Python, kanye nesandiso esincane se-Chrome esiphendula i-onAuthRequired kunoma yiluphi ulimi lwe-Selenium.
http://user:pass@ip:port (selenium-wire / Chrome proxy extension)- 1 IP$1.85
- 3+ IPs$1.70
- 10+ IPs$1.60
- 25+ IPs$1.50
- 50+ IPs$1.40
- 100+ IPs$1.30
- 200+ IPs$1.20
- 500+ IPs$1.10
- 1 IP$2.25
- 3+ IPs$2.10
- 10+ IPs$2.00
- 25+ IPs$1.90
- 50+ IPs$1.80
- 100+ IPs$1.70
- 200+ IPs$1.60
- 500+ IPs$1.50
Ukuqhathaniswa kwezinketho
| Indlela | Uyilungiselela kanjani | Ilungele ini |
|---|---|---|
selenium-wire (Python) | seleniumwire_options={'proxy': {'http': 'http://user:pass@ip:port', 'https': 'http://user:pass@ip:port'}} | Indlela eshesha kakhulu ku-Python; i-proxy ingashintshwa isiphequluli sisavuliwe |
| Isandiso sokungena | Isandiso esiyi-zip lapho iskripthi sangemuva siphendula chrome.webRequest.onAuthRequired | I-Java, C#, Python kanye ne-undetected-chromedriver ngokufanayo |
| Dlulela ku-Playwright | browser.newContext({ proxy: { server, username, password } }) | Amaphrojekthi amasha; ukungena kwe-proxy kwakhelwe ngaphakathi, asikho isandiso |
Kwenzekani nge---proxy-server evamile
I-Chrome ithatha ikheli le-proxy emgqeni womyalo kodwa iyaziba iziqinisekiso zokungena ezibhalwe kuyo. Lapho i-proxy iphendula nge-407, i-Chrome ivula ibhokisi lokungena langaphakathi. Lelo bhokisi lingaphandle kwe-DOM yekhasi, ngakho-ke i-find_element ayikwazi ukulibona bese iskripthi silinda kuze kuphele isikhathi. Ngakho-ke, yonke indlela esebenzayo ihlinzeka iziqinisekiso zokungena kwenye indawo hhayi efulegini.
Qaphela ukuthi i-selenium-wire ayisathuthukiswa ngenkuthalo. Isasebenza ezinhlelweni eziningi, kodwa kumaphrojekthi azohlala isikhathi eside indlela yesandiso noma i-Playwright iyisinqumo esiphephile.
Ukugcina ukusebenza kwe-Selenium ene-proxy kusebenza ngempumelelo
- Setha
options.page_load_strategy = 'eager'ukuze iskripthi siqhubeke uma i-DOM isilungile kunokuba silinde izikripthi ezihamba kancane zezinkampani zangaphandle - Kwizikhathi ezingenakhanda ku-Chrome 109 noma entsha sebenzisa
--headless=new; izandiso, kuhlanganise nesandiso sokungena, zisebenza njengakwifestile evamile - Cisha ukulayishwa kwezithombe kuzintandokazi ze-Chrome uma udinga umbhalo kuphela njengamanani noma izihloko
- Faka
driver.quit()kubhulokhi le-try / finallyukuze ukuphahlazeka kungashiyi izinqubo ze-Chrome ngemuva
Ngaphambi kokuba wandise
Iseshini ngayinye ye-WebDriver iyisiphequluli esiphelele, ngakho nika iseshini ngayinye i-IP yayo uma isayithi ihlanganisa ama-akhawunti ngekheli. I-IPv4 yangasese ye-ProxyV4 iqashiswa ikhasimende elilodwa futhi igcina ikheli layo uma uvuselela, okugcina ama-akhawunti okuhlola asebenza isikhathi eside ku-IP efanayo. Hlola ama-proxy amasha nge-proxy checker kuqala ukuze ulayini omubi ungaveli njenge-Selenium timeout edidayo.
Uma ukusebenza kusavula amakhasi kusuka ku-IP yeseva uqobo noma kuma ngephutha le-tunnel, isigaba se-Selenium kokuthi proxy not working sibala izimbangela ezivamile ngokulandelana.
Isinyathelo ngesinyathelo
- 1
Faka i-selenium-wire
Endaweni yakho ebonakalayo, sebenzisa
pip install selenium-wire. - 2
Chaza i-proxy
Yakha
sw_options = {'proxy': {'http': 'http://user:pass@ip:port', 'https': 'http://user:pass@ip:port'}}kusuka ku-oda lakho le-ProxyV4. - 3
Qala i-Chrome ngalezo zinketho
Dala i-driver nge-
driver = webdriver.Chrome(seleniumwire_options=sw_options), ungenisawebdriverkusuka ku-seleniumwire. - 4
Hlola i-IP yokuphuma
Biza
driver.get('https://proxyv4.com/api/my-ip')bese uqinisekisa ukuthi ikhasi libonisa ikheli le-proxy.
Imibuzo evame ukubuzwa
Kungani i---proxy-server=http://user:pass@ip:port izitshwa ku-ChromeOptions?
I-Chrome isusa iziqinisekiso zokungena enanini le---proxy-server ngamabomu. Zihlinzeke nge-selenium-wire, isandiso se-onAuthRequired, noma shintshela ku-Playwright, eyamukela i-username nephasiwedi ngokuqondile.
Ingabe i-selenium-wire ingayishintsha i-proxy ngaphandle kokuqalisa kabusha isiphequluli?
Yebo. Nika i-dict entsha, driver.proxy = {'http': 'http://...', 'https': 'http://...'}, bese izicelo ezilandelayo zisebenzisa i-proxy entsha eya phezulu.
Ingabe isandiso sokungena siyasebenza ku-Chrome engenakhanda?
Yebo, nge---headless=new. Imodi endala ye---headless yayingalayishi izandiso ngendlela efanayo.
I-Selenium iphelelwa yisikhathi ekhasini ngalinye nge-proxy. Yini elandelayo?
Layisha i-endpoint ye-IP nge-cURL usebenzisa iziqinisekiso zokungena ezifanayo. Uma i-cURL ihluleka nayo, ulayini noma imbobo yiyona eyinkinga; umhlahlandlela we-proxy timeout guide ubala okufanele ukuhlole.
Imithombo
Ama-IP azinzile ezikhathi ze-Selenium
I-IPv4 yangasese emazweni ayi-7 kanye ne-ISP emile e-US nase-Vietnam, enomsebenzisi nephasiwedi, engenamkhawulo kanye nekhasimende elilodwa nge-IP ngayinye.
Bheka amanani abukhoma ase-US