You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On client connections, the optional parameter server_hostname specifies the hostname of the service which we are connecting to. This allows a single server to host multiple SSL-based services with distinct certificates, quite similarly to HTTP virtual hosts. Specifying server_hostname will raise a ValueError if server_side is true.
Then redis-py documents examples on how to pass an SSLContext with the ssl_ocsp_context=ctx argument, so it seems feasible to achieve.
Does it sound good? May in the future a ssl_server_name argument be added to redis.Redis()to simplify the usage?
I should provide feedback of my experiment on this soon.
Thanks for reading!
The text was updated successfully, but these errors were encountered:
Hi,
I'm trying to proxy with Traefik multiple Redis instances, that run in different Docker Swarm stacks.
Traefik provide HostSNI rule to route a TCP connection to the corresponding Docker container.
So my goal would be to establish with
redis-py
a Redis connection with SSL providing theServer Name Identification
.This seems to be possible with ssl.SSLContext.wrap_socket:
Then
redis-py
documents examples on how to pass anSSLContext
with thessl_ocsp_context=ctx
argument, so it seems feasible to achieve.Does it sound good? May in the future a
ssl_server_name
argument be added toredis.Redis()
to simplify the usage?I should provide feedback of my experiment on this soon.
Thanks for reading!
The text was updated successfully, but these errors were encountered: