From 483363b03d206416d28c36785eea2562142b36a3 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Thu, 14 Aug 2003 20:09:31 +0000
Subject: [PATCH] Fix longstanding thinko in SSL protocol documentation: the
 server's initial response is 'S', not 'Y', when it is willing to do SSL.

---
 doc/src/sgml/protocol.sgml | 6 +++---
 1 file 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