You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "rdhabalia (via GitHub)" <gi...@apache.org> on 2023/09/18 20:20:57 UTC
[GitHub] [pulsar] rdhabalia commented on pull request #8957: [PIP-60] Add TLS SNI support for cpp and python clients
rdhabalia commented on PR #8957:
URL: https://github.com/apache/pulsar/pull/8957#issuecomment-1724311016
I am confused here. How does this change support SNI routing in client side.
To support SNI proxy routing, client needs two URL: sni-proxy-url + actual broker service URL as we have added in Java client library: https://github.com/apache/pulsar/pull/6566
```
ClientBuilder clientBuilder = PulsarClient.builder()
.serviceUrl(brokerServiceUrl)
.proxyServiceUrl(proxyUrl, ProxyProtocol.SNI);
```
I am really confused what exactly we are trying to do here and how is it related to SNI proxy?
I also checked CPP + SNI doc PR which is also kind of misleading the usage: https://github.com/apache/pulsar/pull/9937/files
can someone please help me to understand how does it actually perform SNI routing?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org