Fifiko na proxy da masu canza bypass a gRPC C-Core
Bi fifikon proxy da bypass na gRPC Core ba tare da ɗauka cewa wata aiwatar da gRPC tana amfani da mapper ɗaya ba.
Canza http_proxy na iya yin komai a banza idan an riga an sami saitin gRPC mai fifiko mafi girma. Fara da gano aiwatarwar: halin da ke gaba na mapper ɗin HTTP proxy na asali na gRPC C-Core ne da waɗanda suka dogara da shi.
Mapper ɗin yana duba hujjar proxy ta tashar, sannan grpc_proxy, sannan https_proxy, sannan http_proxy, kuma yana tsayawa a ƙimar farko da aka saita.
Gano bypass yana da nasa tsari: no_grpc_proxy yana da fifiko bisa no_proxy. Tsohuwar ƙima a wurin na iya bayanin dalilin da wata manufa ta guje wa proxy da aka saita a wata hanya.
Wannan mapper ɗin yana amfani da HTTP CONNECT. URI ɗin proxy da aka rubuta a takarda yana tsammanin tsarin HTTP; sabis ɗin gRPC da TLS ke karewa ba ya buƙatar da kansa ƙarshen proxy da TLS ke karewa. Duba ingantaccen tabbaci daban maimakon ɗauka cewa kowane tsarin shiga na burauza yana samuwa. Don manufar gRPC ta jama'a inda aka yarda da masu shiga tsakani na jama'a, jerin proxy na HTTP yana bayar da 'yan takarar ƙarshe don URI ɗin proxy na HTTP da aka zaɓa; tabbatar da isa ga ainihin manufar CONNECT da tashar jiragen ruwa.
Aiwatar da gRPC a Java, Go, JavaScript ko wata harshe na iya samun lambar jigilar kaya da tsari daban. Kada ka yi amfani da jerin masu canza C-Core a matsayin ƙa'ida ta duniya ga duk abin da ake kira gRPC.
Don tashar da ta kasa, riƙe zaɓaɓɓen proxy, shawarar bypass, manufa da matakin kuskure. HTTP API da ake iya samu ta wani abokin ciniki ba ya tabbatar da cewa wannan mapper ɗin ya yi amfani da saituna ɗaya ko kuma proxy ɗin yana yarda da wurin CONNECT da ake buƙata.