fantapsody opened a new issue, #16416: URL: https://github.com/apache/pulsar/issues/16416
**Describe the bug** The async-http-client used in pulsar-admin doesn't set SNI properly when `tlsEnableHostnameVerification` is `false`, see https://github.com/AsyncHttpClient/async-http-client/blob/master/client/src/main/java/org/asynchttpclient/netty/ssl/DefaultSslEngineFactory.java#L65. This will fail https requests that rely on SNI routing, like a pulsar cluster deployed behind an istio gateway. The behavior was introduced in the PR https://github.com/apache/pulsar/pull/15824 since the async-http-client doesn't split the flag for SNI header and hostname verification. @michaeljmarshall **To Reproduce** Set `tlsEnableHostnameVerification` to `false` in the `client.conf`, and use pulsar-admin to operate a pulsar cluster behind the istio gateway. **Expected behavior** The pulsar-admin should set the SNI header properly. **Screenshots** N/A **Desktop (please complete the following information):** - OS: MAC OS X **Additional context** -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
