Horudhaca proxy iyo doorsoomeyaasha dhaqaaqa ee gRPC C-Core
Raac horudhaca proxy iyo dhaqaaqa gRPC Core adigoon ka malaynayn in fulinta kale ee gRPC isticmaasho isla mapper.
Beddelka http_proxy waxba ma qaban karo haddii dejinta gRPC oo mudnaan sare leh horey u jirto. Ku bilow aqoonsiga fulinta: dhaqanka soo socda waxaa iska leh mapper-ka HTTP proxy ee caadiga ah ee gRPC C-Core iyo kuwa ku tiirsan.
Mapper-ku wuxuu eegaa doodda proxy ee kanaalka, ka dib grpc_proxy, ka dib https_proxy, ka dib http_proxy, wuuna istaagaa qiimaha ugu horreeya ee la habeeyay.
Ogaanshaha dhaqaaqa wuxuu leeyahay noloshiisa: no_grpc_proxy wuxuu ka sarreeyaa no_proxy. Qiime duug ah oo halkaas yaalla wuxuu sharxi karaa sababta bartilmaameed uga fogaado proxy si kale loo habeeyay.
Mapper-kani wuxuu isticmaalaa HTTP CONNECT. URI proxy-ga la diiwaangeliyay wuxuu filayaa nidaam HTTP; adeegga gRPC ee TLS ilaalinaysa iskiis uma baahna barta dhamaadka proxy ee TLS ilaalinaysa. Si gooni ah u hubi xaqiijinta la taageeray halkii aad ka malayn lahayd in nidaam kasta oo gelitaan browser uu diyaar yahay. Bartilmaameedka gRPC ee dadweynaha ah halkaas oo dhexdhexaadiyeyaasha dadweynaha la ogol yahay, liiska proxy-yada HTTP wuxuu bixiyaa musharaxiin barta dhamaadka ee URI proxy HTTP la doortay; xaqiiji gelitaanka bartilmaameedka iyo dekedda CONNECT ee dhabta ah.
Fulinta gRPC ee Java, Go, JavaScript ama luqad kale waxay yeelan kartaa koodh gaadiid iyo habayn kale. Ha u adeegsan liiska doorsoomeyaasha C-Core sidii sharci guud wax kasta oo la yiraahdo gRPC.
Kanaalka guuldareystay, hayso proxy-ga la doortay, go'aanka dhaqaaqa, bartilmaameedka iyo marxaladda khaladka. HTTP API laga gaari karo macmiil kale ma caddeeyo in mapper-kani isticmaalay isla dejinta ama in proxy-gu ogolaado meesha CONNECT ee loo baahan yahay.