Ukubaluleka kokuqala kwe-proxy ne-bypass variable ku-gRPC C-Core
Landela ukubaluleka kokuqala kwe-proxy ne-bypass kwe-gRPC Core ngaphandle kokucabanga ukuthi olunye ukuqaliswa kwe-gRPC lusebenzisa i-mapper efanayo.
Ukushintsha http_proxy kungase kungenzi lutho uma isethingi ye-gRPC enokubaluleka okuphezulu isivele ikhona. Qala ngokuhlonza ukuqaliswa: ukuziphatha okulandelayo kungokwe-mapper ye-HTTP proxy ezenzakalelayo ye-gRPC C-Core kanye nalokho okuncike kuyo.
I-mapper ihlola i-channel proxy argument, bese i-grpc_proxy, bese i-https_proxy, bese i-http_proxy, futhi ima enanini lokuqala elilungisiwe.
Ukutholwa kwe-bypass kunokulandelana kwako: i-no_grpc_proxy ibaluleke ngaphezu kwe-no_proxy. Inani elidala lapho lingase lichaze ukuthi kungani umgomo othile ugwema i-proxy elungiswe ngenye indlela.
Le mapper isebenzisa i-HTTP CONNECT. I-proxy URI yayo ebhaliwe ilindele i-HTTP scheme; isevisi ye-gRPC evikelwe nge-TLS ayidingi ngokwayo i-proxy endpoint evikelwe nge-TLS. Hlola ukuqinisekiswa okusekelwayo ngokwehlukana esikhundleni sokucabanga ukuthi noma iyiphi i-browser login scheme iyatholakala. Ngomgomo womphakathi we-gRPC lapho abalamuli bomphakathi bevunyelwe, uhlu lwama-proxy e-HTTP lunikeza abazongenela i-endpoint ye-HTTP proxy URI ekhethiwe; qinisekisa ukufinyelela kumgomo wangempela we-CONNECT kanye nechweba.
Ukuqaliswa kwe-gRPC nge-Java, Go, JavaScript noma olunye ulimi kungase kube nekhodi yokuthutha nokulungiselela okuhlukile. Ungasebenzisi uhlu lwezinto eziguquguqukayo ze-C-Core njengomthetho jikelele kukho konke okubizwa nge-gRPC.
Nge-channel ehlulekile, gcina i-proxy ekhethiwe, isinqumo se-bypass, umgomo kanye nesigaba sephutha. I-HTTP API efinyeleleka ngelinye iklayenti ayifakazisi ukuthi le mapper isebenzise izilungiselelo ezifanayo noma ukuthi i-proxy ivumela indawo ye-CONNECT edingekayo.