-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TLS Hostname Verification supports only one server #44
Comments
Yeah it's a bit weird, I'm not at all sure why this line in TCPMemcachedNodeImpl.java : |
For AWS elasticache, the DNS hostname for all the nodes in a memcached cluster has similar domain name / suffix. i.e. |
@QuChen88 that makes sense (as to the design choice) it just doesn't generalise outside of the AWS elasticache case, which is unfortunate (but understandable given the client) |
I can connect to more than one server using MemcachedClient. But there is ability to specify only one host name for ConnectionFactoryBuilder#setHostnameForTlsVerification
ConnectionFactoryBuilder#hostnameForTlsVerification seems redundant. Why doesn't TCPMemcachedNodeImpl use NodeEndPoint or SocketAddress and get the hostname it is communicating with?
The text was updated successfully, but these errors were encountered: