Re: ssl preread for postgres connection

2023-05-14 Thread J Carter
On Sun, 14 May 2023 19:09:30 +0100 J Carter wrote: > Hello, > > > On Sun, 14 May 2023 17:33:10 +0300 > > Maxim Dounin wrote: > > > Hello! > > > > On Sun, May 14, 2023 at 09:55:54AM +0400, Roman Arutyunyan wrote: > > > > > Hi Eduard, > > > > > > On Sat, May 13, 2023 at 10:43:59PM -0600,

Re: ssl preread for postgres connection

2023-05-14 Thread J Carter
Hello, > On Sun, 14 May 2023 17:33:10 +0300 > Maxim Dounin wrote: > Hello! > > On Sun, May 14, 2023 at 09:55:54AM +0400, Roman Arutyunyan wrote: > > > Hi Eduard, > > > > On Sat, May 13, 2023 at 10:43:59PM -0600, Eduard Vercaemer wrote: > > > for some context, I recently I tried configuring

Re: ssl preread for postgres connection

2023-05-14 Thread Maxim Dounin
Hello! On Sun, May 14, 2023 at 09:55:54AM +0400, Roman Arutyunyan wrote: > Hi Eduard, > > On Sat, May 13, 2023 at 10:43:59PM -0600, Eduard Vercaemer wrote: > > for some context, I recently I tried configuring nginx as a tcp proxy that > > routes > > connections based on sni to multiple upstream

Re: ssl preread for postgres connection

2023-05-13 Thread Roman Arutyunyan
Hi Eduard, On Sat, May 13, 2023 at 10:43:59PM -0600, Eduard Vercaemer wrote: > for some context, I recently I tried configuring nginx as a tcp proxy that > routes > connections based on sni to multiple upstream services > > the server only exposes one tcp port, and receives all connections

ssl preread for postgres connection

2023-05-13 Thread Eduard Vercaemer
for some context, I recently I tried configuring nginx as a tcp proxy that routes connections based on sni to multiple upstream services the server only exposes one tcp port, and receives all connections there, for example a connection to redis.example.com:1234 would be proxy_pass'ed to some port