Sa Pub/Sub Java gRPC tashar don HTTP CONNECT

Yi amfani da tashar abokin ciniki da aka ƙirƙira sa'ad da haɗin Pub/Sub Java gRPC ke buƙatar HTTP CONNECT proxy. Saitin URLConnection na yau da kullum ba ya kafa wannan tsarin tashar.

Ga abokin ciniki na 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 da TopicAdminSettings azuzuwan Pub/Sub v1 ne; HttpConnectProxiedSocketAddress ya fito daga io.grpc kuma InetSocketAddress daga java.net. Misalin yana ɗauka cewa ana amfani da manufar adireshin intanet na yau da kullum da wannan tashar ke amfani da ita.

Mai ganowa yana mayar da adireshin haɗin proxy tare da ainihin manufa. Mai gina gRPC yana buƙatar a warware adireshin proxy. Bar ƙarshen sabis ɗin a matsayin Pub/Sub: maye gurbinsa da sunan uwar garken proxy zai rasa manufar sabis da kuma TLS da ake nufi.

Cire kiran sunan mai amfani/ kalmar sirri don proxy mara tabbaci; ana iya samun 'yan takarar HTTP na jama'a a cikin jerin proxy na HTTP. Waɗannan kira sune hanyar shaidar HTTP CONNECT, ba SOCKS ko aiwatar da NTLM na gama gari ba.

Idan gazawar ta faru kafin aikin gRPC yayin da shaidar da aka ƙirƙira da kanta ta sami token, duba hanyar HTTP ta wannan shaidar. Tana waje da tashar da aka nuna a nan.