Feature Request
Is your feature request related to a problem? Please describe
Some SSL-aware proxies relies on the SNI to route connections[1]. Also, libpq sends SNI by default[2]. I think it's better for r2dbc-postgresql to provide an option to support SNI as well.
[1] https://www.postgresql.org/message-id/7289d5eb-62a5-a732-c3b9-438cee2cb709@enterprisedb.com
[2] https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNECT-SSLSNI
Describe the solution you'd like
IMO, there should be an option to control the behavior, for example a global / per connection, and turn it on by default to be aligned with libpq, and then the lib sets SNI accordingly in the createSslProvider.
Describe alternatives you've considered
None
Teachability, Documentation, Adoption, Migration Strategy
Feature Request
Is your feature request related to a problem? Please describe
Some SSL-aware proxies relies on the SNI to route connections[1]. Also,
libpqsends SNI by default[2]. I think it's better for r2dbc-postgresql to provide an option to support SNI as well.[1] https://www.postgresql.org/message-id/7289d5eb-62a5-a732-c3b9-438cee2cb709@enterprisedb.com
[2] https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNECT-SSLSNI
Describe the solution you'd like
IMO, there should be an option to control the behavior, for example a global / per connection, and turn it on by default to be aligned with
libpq, and then the lib sets SNI accordingly in thecreateSslProvider.Describe alternatives you've considered
None
Teachability, Documentation, Adoption, Migration Strategy