aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2003-08-14 20:09:31 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2003-08-14 20:09:31 +0000
commit483363b03d206416d28c36785eea2562142b36a3 (patch)
tree07df4d6bb9ab52566cdf93e51af7c708a9af0de0
parent4529d2cf274fe48735c67a833dab600c42c842c6 (diff)
downloadpostgresql-483363b03d206416d28c36785eea2562142b36a3.tar.gz
postgresql-483363b03d206416d28c36785eea2562142b36a3.zip
Fix longstanding thinko in SSL protocol documentation: the server's
initial response is 'S', not 'Y', when it is willing to do SSL.
-rw-r--r--doc/src/sgml/protocol.sgml6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml
index c4605a13efc..1de14ddeb61 100644
--- a/doc/src/sgml/protocol.sgml
+++ b/doc/src/sgml/protocol.sgml
@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.40 2003/08/13 18:56:21 tgl Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.41 2003/08/14 20:09:31 tgl Exp $ -->
<chapter id="protocol">
<title>Frontend/Backend Protocol</title>
@@ -1151,10 +1151,10 @@
<para>
To initiate an SSL-encrypted connection, the frontend initially sends
an SSLRequest message rather than a StartupMessage. The server then
- responds with a single byte containing <literal>Y</> or <literal>N</>,
+ responds with a single byte containing <literal>S</> or <literal>N</>,
indicating that it is willing or unwilling to perform SSL, respectively.
The frontend may close the connection at this point if it is dissatisfied
- with the response. To continue after <literal>Y</>, perform an SSL
+ with the response. To continue after <literal>S</>, perform an SSL
startup handshake (not described here, part of the SSL specification)
with the server. If this is successful, continue with
sending the usual StartupMessage. In this case the StartupMessage and