Firebase Admin Node httpAgent: ukumboza kwe-proxy ngokwesevisi
Khomba ukuthi yimiphi imisebenzi ye-Firebase Admin Node esebenzisa i-HTTP agent elungisiwe ngaphambi kokuthatha ukuthi yonke i-SDK traffic isebenzisa i-proxy efanayo.
Ucingo lokuqinisekisa lusebenza nge-proxy, kodwa ukuxhumana kwedathabheyisi kuyahluleka. Kuhlelo lokusebenza lwe-Firebase, lokho kungaba umehluko wezokuthutha hhayi i-proxy ephazamisekayo.
Inketho yohlelo lokusebenza httpAgent ku-Admin Node SDK isebenza kumasevisi enza izingcingo ze-REST, kuhlanganise i-Auth ne-Messaging. Ububanzi bayo obhalisiwe abubandakanyi i-Realtime Database ne-Firestore. Izinto zokuqinisekisa nazo zinelungiselelo lazo le-agent ngokusebenzisa izindlela zefekthri yokuqinisekisa ezifanele.
| Umsebenzi ohlulekayo | Ilungiselelo okufanele lihlolwe |
|---|---|
| Ucingo lwesevisi ye-Admin REST | I-HTTP agent yohlelo lokusebenza |
| Ukuthola ithokheni yokuqinisekisa | Ilungiselelo le-HTTP lento yokuqinisekisa |
| Ukuxhumana kwedathabheyisi | Ukusekelwa kwezokuthutha kwekhlayenti ledathabheyisi ngokwalo |
Yingakho ukwengeza i-agent ekuqaleni kungenakho ukuqinisekisa ukuthi konke ukuxhumana okulandelayo kuzothatha indlela efanayo. Rekhoda isevisi nendawo okuya kuyo ehlulekayo ngaphambi kokushintsha ilungiselelo eselivele lisebenza kwesinye isevisi.
Izingxoxo zakudala zihlanganisa ithuluzi lomugqa womyalo we-Firebase nama-SDK ohlelo lokusebenza. Ukulungiswa kwe-CLI ukuze kufundwe http_proxy akubonisi ukuthi ikhlayenti ledathabheyisi ngaphakathi kwenqubo yakho ye-Node isebenzisa inketho efanayo.
Sebenzisa isixhumi esibonakalayo selungiselelo esisekelwayo sokuthutha okudingayo ngempela. Ukufaka isichibi kuncike kwe-WebSocket engaphakathi kungabonakala sengathi sithinta ukuxhumana okukodwa kuyilapho enye indlela ishoda ingashintshiwe, futhi kwenza ukubuyekezwa kokuncika kwesikhathi esizayo kube nzima ukuqondwa.