Fix longstanding thinko in SSL protocol documentation: the server's

initial response is 'S', not 'Y', when it is willing to do SSL.

diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml
index ee16d60426265355496ddd9fafd70014934412f7..d5a283bc4b8e7b7977e31f0f3da86a6f146a2368 100644 (file)
--- a/doc/src/sgml/protocol.sgml
+++ b/doc/src/sgml/protocol.sgml
@@ -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