U habee kanaalka gRPC ee Pub/Sub Java ee HTTP CONNECT

Isticmaal bixiyaha kanaalka ee macmiilka la soo saaray marka xiriirka Pub/Sub Java gRPC uu u baahan yahay proxy HTTP CONNECT. Dejinta caadiga ah ee URLConnection ma dhisi qaabkan kanaalka.

Macmiilka topic-admin:

var channelProvider = TopicAdminSettings
    .defaultGrpcTransportProviderBuilder()
    .setChannelConfigurator(channel -> channel.proxyDetector(target ->
        HttpConnectProxiedSocketAddress.newBuilder()
            .setProxyAddress(new InetSocketAddress("proxy.example", 8080))
            .setTargetAddress((InetSocketAddress) target)
            .setUsername(proxyUser)
            .setPassword(proxyPassword)
            .build()))
    .build();

var settings = TopicAdminSettings.newBuilder()
    .setTransportChannelProvider(channelProvider)
    .build();
try (TopicAdminClient client = TopicAdminClient.create(settings)) {
    // Perform the application's intended topic-admin operation here.
}

TopicAdminClient iyo TopicAdminSettings waa fasallada Pub/Sub v1; HttpConnectProxiedSocketAddress wuxuu ka yimaadaa io.grpc iyo InetSocketAddress java.net. Tusaalahu waxay u malaynaysaa bartilmaameedka ciwaanka internetka ee caadiga ah ee kanaalkani isticmaalo.

Qalabka ogaanshaha wuxuu soo celiyaa ciwaanka xiriirka proxy oo ay la socoto bartilmaameedka asalka ah. Dhismaha gRPC wuxuu u baahan yahay in ciwaanka proxy la xalliyo. U dhaaf barta ugu dambeysa ee adeegga Pub/Sub: ku beddelashada magaca martigeliyaha proxy waxay lumin lahayd bartilmaameedka adeegga iyo aqoonsiga TLS ee loogu talagalay.

Ka saar wicitaannada magaca isticmaalaha/furaha sirta ah ee proxy aan la xaqiijin; musharraxiinta HTTP ee dadweynaha waxaa laga heli karaa liiska proxy HTTP. Wicitaannadaas waa is-dhexgalka aqoonsiga HTTP CONNECT, ma aha SOCKS ama hirgelinta NTLM guud.

Haddii guuldarradu dhacdo ka hor hawlgalka gRPC inta aqoonsi si madaxbannaan loo abuuray uu helayo token, baadh wadada HTTP ee aqoonsigaas. Waxay ka baxsan tahay bixiyaha kanaalka ee halkan lagu muujiyay.