Proxies masu shaidar shiga a Node.js: Axios, native fetch da Got
Daga Tawagar Injiniyoyi ta ProxyV4 · Updated:
Hanya mafi inganci don amfani da proxy na Node.js tare da Axios ita ce tura HttpsProxyAgent a matsayin httpsAgent, tare da proxy: false. Tsarin Axios na kansa na proxy: { host, port } baya buɗe ramin HTTP CONNECT, don haka yana yankewa a kan adiresoshin https://; a maimakon haka, native fetch() yana buƙatar ProxyAgent na undici. Wannan shafi yana nuna kowane client tare da adireshin ProxyV4 http://user:pass@ip:port da yadda ake tabbatar da IP na fita.
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
Zaɓi lambar snippet don client ɗin HTTP ɗinka
Dukkan clients guda uku suna ɗaukar adireshin URL na proxy iri ɗaya. Ƙirƙira shi daga layin ip:port:user:pass da ke cikin odarka; tsarin yana kasancewa http:// saboda client ɗin yana magana da proxy ta hanyar HTTP sannan yana tura TLS ta cikinsa.
| Client | Girkawa | Haɗa 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' }) } }) |
Dalilin da ya sa `proxy: false` ke da muhimmanci a Axios
Axios yana duba sauye-sauyen muhalli na HTTP_PROXY da HTTPS_PROXY da kansa. Idan an saita ɗaya daga cikinsu a kan na'urar (wanda aka saba gani a CI runners da containers) kuma ka sake tura agent, saitunan biyu za su yi karo da juna. proxy: false yana gaya wa Axios ya yi watsi da muhallin da kuma dabarun proxy na ciki, domin agent ɗin ya zama shi kaɗai ne ke yanke shawarar inda buƙatar za ta nufa.
Sake amfani da agents a buƙatu da yawa
- Ƙirƙiri agent guda ɗaya ga kowane IP na proxy a wajen zagayen buƙatarka; agent ɗin yana riƙe da soket ɗin keep-alive, kuma ƙirƙirar sabon agent a kowace kira yana zubar da su
- Idan kana da proxies da yawa, ajiye
Mapdaga IP zuwa agent sannan ka zaɓa daga ciki, maimakon gina agents a lokacin aiki - Sanya
timeouta kowace kira (misalitimeout: 10000a Axios) don kada shafin da ya tsaya ya riƙe worker har abada - Kana buƙatar jerin proxy a matsayin bayanai? Na'urar canza fasalin proxy tana mayar da layukan
ip:port:user:passzuwa jeri na JSON da zaka iyarequirekoimport
Abin da ingantaccen IP mai karko ke bayarwa ga aikin Node.js
Keɓaɓɓen IPv4 na ProxyV4 na abokin ciniki ɗaya ne a duk tsawon lokacin haya kuma yana riƙe adireshi iri ɗaya lokacin da ka sabunta, don haka API da aka ba izini, zaman shiga ko adadin ƙa'idar buƙata da ke da alaƙa da wannan IP yana ci gaba da aiki tsakanin sauye-sauyen turawa. Ba a auna bandwidth, wanda ke sa ma'aikatan da ke aiki na dogon lokaci su kasance abin dogaro. Don dabarun binciken shafuka da tafiyar da aiki, duba hanyar amfani ta web scraping.
Mataki bayan mataki
- 1
Girka client da agent
Gudanar da
npm install axios https-proxy-agenta cikin aikin (konpm install undiciidan kana amfani da nativefetch). - 2
Gina agent sau ɗaya
Ƙirƙiri
const agent = new HttpsProxyAgent('http://user:pass@ip:port');tare da lambobin daga odarka ta ProxyV4. - 3
Aika buƙata ta cikinsa
Kira
const res = await axios.get('https://proxyv4.com/api/my-ip', { httpsAgent: agent, proxy: false, timeout: 10000 });. - 4
Kwatanta IP ɗin
console.log(res.data)ya kamata ya nuna IP na proxy ɗin. Idan ya nuna adireshin uwar garkenka na ainihi, ba a yi amfani da agent ɗin ba.
Tambayoyi da aka fi yi
Me ya sa proxy: { host, port, auth } a Axios ke faduwa a shafukan HTTPS?
Wannan zaɓin yana aika buƙatar HTTP ta yau da kullun zuwa proxy maimakon fara neman ramin HTTP CONNECT, don haka ba a taɓa kafa TLS zuwa inda aka nufa yadda ya kamata ba. Yi amfani da httpsAgent: new HttpsProxyAgent('http://user:pass@ip:port') sannan ka saita proxy: false.
Yaya zan ƙara proxy zuwa native fetch() a Node 18, 20 ko 22?
fetch na Node yana aiki ne a kan undici, don haka shigo da ProxyAgent daga undici kuma ka tura { dispatcher: new ProxyAgent('http://user:pass@ip:port') } a matsayin wani ɓangare na zaɓuɓɓukan fetch().
Kalmar sirrina tana ɗauke da @ ko :. Shin URL ɗin zai lalace?
Zai iya lalacewa, saboda waɗannan haruffa suna da ma'ana a cikin URL. Yi lambar percent-encode ga kalmar sirri tare da encodeURIComponent(password) kafin ka gina http://user:pass@ip:port.
Buƙatar ta dawo da 407. Menene matsalar?
Proxy ɗin ya ba da amsa amma ya ƙi shigar. Sake duba sunan mai amfani da kalmar sirri daga odarka; shafin magance matsalar 407 yana lissafa abubuwan da aka saba samu.
Tushe
Static IPv4 don ma'aikatan Node.js ɗinka
Keɓaɓɓen IPv4 a ƙasashe 7 tare da static ISP a US da Vietnam, ba a auna shi ba, abokin ciniki ɗaya ga kowane IP. Sayi ɗaya ko da yawa.
Duba farashin US na yanzu