Hlela ishaneli ye-gRPC ye-Pub/Sub Java ye-HTTP CONNECT

Sebenzisa umhlinzeki weshaneli weklayenti elikhiqiziwe lapho ukuxhumana kwe-Pub/Sub Java gRPC kudinga i-proxy ye-HTTP CONNECT. Isilungiselelo esivamile se-URLConnection asisakhi lokhu kulungiselelwa kweshaneli.

Kuklayenti le-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 ne-TopicAdminSettings yizigaba ze-Pub/Sub v1; i-HttpConnectProxiedSocketAddress ivela ku-io.grpc kanti i-InetSocketAddress ivela ku-java.net. Isibonelo sithatha umgomo ojwayelekile wekheli le-inthanethi elisetshenziswa yile shaneli.

Isitholi sibuyisela ikheli lokuxhumana le-proxy kanye nomgomo wangempela. Umakhi we-gRPC udinga ukuthi ikheli le-proxy lixazululwe. Shiya indawo yokugcina yesevisi iyi-Pub/Sub: ukuyishintsha ngegama lomsingathi we-proxy kuzolahlekelwa umgomo wesevisi kanye nobuwena be-TLS obuhlosiwe.

Susa izingcingo zegama lomsebenzisi/iphasiwedi ze-proxy engaqinisekisiwe; abazakheli be-HTTP bomphakathi batholakala ohleni lwama-proxy e-HTTP. Lezo zingcingo ziyisixhumi sezicelo ze-HTTP CONNECT, hhayi i-SOCKS noma ukuqaliswa kwe-NTLM okuvamile.

Uma ukwehluleka kwenzeka ngaphambi komsebenzi we-gRPC ngenkathi ubufakazi obudalwe ngokuzimela buthola ithokheni, hlola indlela ye-HTTP yalobo bufakazi. Ingaphandle komhlinzeki weshaneli oboniswe lapha.