Ukuthumela i-FCM nge-proxy akuhambisi uxhumano lwefoni
Hlukanisa indlela ye-Admin API ye-Firebase kusuka kuxhumano lwenethiwekhi lwe-FCM oluhlala njalo lwedivayisi ye-Android eyamukelayo.
I-backend ingathumela ngempumelelo isicelo se-Firebase Cloud Messaging nge-proxy yebhizinisi kuyilapho idivayisi ye-Android ingasitholi isaziso. Isicelo se-Admin API se-backend kanye noxhumano lwe-FCM lwedivayisi kuyimizila ehlukene.
Imihlahlandlela yenethiwekhi ye-Firebase ithi iphrothokholi yedivayisi ye-FCM ayikwazi ukudluliswa nge-proxy yenethiwekhi. Ukulungisa i-HTTP client kumthumeli akugquli lowo xhumano lwedivayisi oluhlala njalo lube isicelo se-proxy ye-HTTP.
Kumadivayisi e-Android, amachweba e-TCP okuya kuyo abhalwe phansi yi-5228, 5229, 5230 kanye no-443. I-FCM ivamise ukusebenzisa u-5228, namanye amachweba ayatholakala. Sebenzisa inqubomgomo efanele kunethiwekhi lapho amadivayisi amukelayo axhumana khona.
Sebenzisa imihlahlandlela yegama lomsingathi eshicilelwe yi-Firebase lapho i-firewall ibekela umkhawulo izindawo; ayikhuthazi izinhlu ze-IP ezivunyelwe ezingaguquki ngoba amakheli angashintsha. Amadivayisi adinga futhi i-DNS esebenzayo kanye nomzila ozinzile woxhumano lwawo lwesikhathi eside.
Uma umthumeli ehluleka ngesikhathi sokuthola ithokheni noma isicelo se-Admin API, hlola lokho kudluliswa kwe-HTTP ohlangothini lweseva. Ngamajoyina e-HTTP e-Firebase Admin Java, lungisa ngokuhlanganyela ukudluliswa kwe-API nokudluliswa kobufakazi. Uma ukuthumela kuphumelela kodwa ukulethwa kwehluleka, gcina lowo mphumela futhi uphenye umzila wedivayisi esikhundleni sokushintsha kaninginingi ubufakazi be-proxy be-backend.