From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Barry Lind <blind(at)xythos(dot)com> |
Cc: | Rich Cullingford <rculling(at)sysd(dot)com>, pgsql-jdbc(at)postgresql(dot)org, Brian Lindauer <lindauer(at)sysd(dot)com> |
Subject: | Re: SSL support in PG 7.4 |
Date: | 2003-08-07 13:19:42 |
Message-ID: | 14667.1060262382@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Barry Lind <blind(at)xythos(dot)com> writes:
> In general that may be true. And I didn't into this very much at the
> time I did my initial v3 protocol work. But in glancing at the code
> just now, it needs to at least correctly handle a v3 style error
> response from an ssl handshake request, no?
Actually not. Any modern postmaster will give you either 'Y' or 'N'
back for an SSL request, whether it's compiled with SSL support or not.
An 'E' response is only possible from postmasters that predate the
introduction of SSL support ... and so it'll be V2 format for sure.
(I'm not sure that you really care what follows 'E' in this case,
anyway. You can just drop the connection and try again without SSL.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Fernando Nasser | 2003-08-07 14:09:41 | Re: pgsql - query |
Previous Message | anaheim | 2003-08-07 11:11:49 | PooledConnectionImpl creates Connections with autoCommit set to false |