Ama-proxy aqinisekisiwe ku-Node.js: Axios, native fetch ne-Got
Ibhalwe yiThimba Lonjiniyela lakwa-ProxyV4 · Updated:
Indlela ethembekile yokusebenzisa i-proxy ye-Node.js nge-Axios yi-HttpsProxyAgent edluliswa njenge-httpsAgent, ikhona ne-proxy: false. Izilungiselelo ze-Axios ngokwayo ze-proxy: { host, port } azivuli umhubhe we-HTTP CONNECT, ngakho-ke ziyehluleka kuma-URL e-https://; i-fetch() yoqobo idinga i-ProxyAgent ye-undici kunalokho. Leli khasi libonisa iklayenti ngalinye eline-URL ye-ProxyV4 ye-http://user:pass@ip:port nokuthi ungaqinisekisa kanjani i-IP yokuphuma.
new HttpsProxyAgent('http://user:pass@ip:port')- 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$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
Khetha isiqeshana seklayenti lakho le-HTTP
Owakho womathathu amaklayenti asebenzisa i-URL ye-proxy efanayo. Yakhe kusuka kulayini we-ip:port:user:pass ku-oda lakho; uhlelo luhlala luyi-http:// ngoba iklayenti likhuluma i-HTTP ne-proxy bese lidlulisa i-TLS ngomhubhe kuyo.
| Iklayenti | Faka | Ukuxhuma i-proxy |
|---|---|---|
| Axios | npm i https-proxy-agent | axios.get(url, { httpsAgent: new HttpsProxyAgent('http://user:pass@ip:port'), proxy: false }) |
Native fetch (Node 18+) | npm i undici | fetch(url, { dispatcher: new ProxyAgent('http://user:pass@ip:port') }) |
| Got | npm i hpagent | got(url, { agent: { https: new HttpsProxyAgent({ proxy: 'http://user:pass@ip:port' }) } }) |
Kungani i-`proxy: false` ibalulekile ku-Axios
I-Axios ihlola okuguquguqukayo kwemvelo kwe-HTTP_PROXY ne-HTTPS_PROXY ngokwayo. Uma eyodwa yazo isethiwe emshinini (kujwayelekile kubagijimi be-CI nasezitsheni ze-container) futhi udlulisa ne-ejenti, lezi zilungiselelo ezimbili zizoshayisana. I-proxy: false itshela i-Axios ukuthi inganaki imvelo kanye ne-logic yayo ye-proxy eyakhelwe ngaphakathi, ukuze i-ejenti kube yiyona yodwa enqumayo lapho isicelo siya khona.
Ukusebenzisa kabusha ama-ejenti ezicelweni eziningi
- Dala i-ejenti eyodwa nge-IP ngayinye ye-proxy ngaphandle kweluphu yakho yesicelo; i-ejenti igcina amasokhethi e-keep-alive, kanti i-ejenti entsha kucingo ngalunye iyawalahla
- Ngama-proxy amaningi, gcina i-
Mapkusuka ku-IP kuya ku-ejenti bese ukhetha kuyo, kunokwakha ama-ejenti ngesikhathi esisodwa - Nikeza ucingo ngalunye i-
timeout(ngokwesibonelotimeout: 10000ku-Axios) ukuze okuhlosiwe okukodwa okumile kungabambeli isisebenzi unomphela - Udinga uhlu lwe-proxy njengedatha? Isiguquli sefomethi ye-proxy proxy format converter siguqula imigqa ye-
ip:port:user:passibe yi-array ye-JSON ongayisebenzisa nge-requirenoma i-import
Lokho i-IP ezinzile eyinikeza umsebenzi we-Node.js
I-IPv4 yangasese ye-ProxyV4 ingeyekhasimende elilodwa kuso sonke isikhathi sokuqashwa futhi igcina ikheli elifanayo uma uvuselela, ngakho-ke i-API egunyaziwe, iseshini engenisiwe noma ibhajethi ye-rate-limit eboshwe kuleyo IP kuhlala kusebenza phakathi kokuthunyelwa. I-bandwidth ayikalwa, okugcina izisebenzi ezisebenza isikhathi eside zibikezeleka. Ukuze uthole amaphethini okukhasa kanye nejubane, bheka isibonelo sokusetshenziswa se-web scraping use case.
Isinyathelo ngesinyathelo
- 1
Faka iklayenti kanye ne-ejenti
Gijima
npm install axios https-proxy-agentkuphrojekthi (nomanpm install undiciuma usebenzisa i-fetchyoqobo). - 2
Yakha i-ejenti kanye
Dala
const agent = new HttpsProxyAgent('http://user:pass@ip:port');ngamanani avela ku-oda lakho le-ProxyV4. - 3
Thumela isicelo ngayo
Biza
const res = await axios.get('https://proxyv4.com/api/my-ip', { httpsAgent: agent, proxy: false, timeout: 10000 });. - 4
Qhathanisa i-IP
console.log(res.data)kufanele iphrinte i-IP ye-proxy. Uma iphrinta ikheli leseva yakho, i-ejenti ayisebenzanga.
Imibuzo evame ukubuzwa
Kungani i-Axios proxy: { host, port, auth } yehluleka kumasayithi e-HTTPS?
Leyo nketho ithumela isicelo se-HTTP esijwayelekile ku-proxy esikhundleni sokucela kuqala umhubhe we-HTTP CONNECT, ngakho-ke i-TLS eya kulokho okuhlosiwe ayilungi kahle. Sebenzisa httpsAgent: new HttpsProxyAgent('http://user:pass@ip:port') bese usetha proxy: false.
Ngiyifaka kanjani i-proxy ku-fetch() yoqobo ku-Node 18, 20 noma 22?
I-fetch ye-Node isebenza ku-undici, ngakho khipha i-ProxyAgent kusuka ku-undici bese udlulisa { dispatcher: new ProxyAgent('http://user:pass@ip:port') } njengengxenye yezinketho ze-fetch().
Iphasiwedi yami iqukethe @ noma :. Ingabe i-URL izophuka?
Ingaphuka, ngoba lezo zinhlamvu zinencazelo ngaphakathi kwe-URL. Faka i-percent-encode kuphasiwedi nge-encodeURIComponent(password) ngaphambi kokwakha i-http://user:pass@ip:port.
Isicelo sibuyisa 407. Yini engalungile?
I-proxy iphendulile kodwa yenqaba ukungena ngemvume. Phinda uhlole igama lomsebenzisi nephasiwedi kusuka ku-oda lakho; ikhasi lokuxilonga le-407 troubleshooting page libala izimbangela ezijwayelekile.
Imithombo
I-IPv4 emile yezisebenzi zakho ze-Node.js
I-IPv4 yangasese emazweni angu-7 kanye ne-ISP emile e-US nase-Vietnam, engalinganiselwe, ikhasimende elilodwa nge-IP ngayinye. Thenga eyodwa noma eziningi.
Hlola izintengo ezibukhoma zase-US