|
1 | | -<!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.40 2003/08/13 18:56:21 tgl Exp $ --> |
| 1 | +<!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.41 2003/08/14 20:09:31 tgl Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="protocol"> |
4 | 4 | <title>Frontend/Backend Protocol</title> |
|
1151 | 1151 | <para> |
1152 | 1152 | To initiate an SSL-encrypted connection, the frontend initially sends |
1153 | 1153 | an SSLRequest message rather than a StartupMessage. The server then |
1154 | | - responds with a single byte containing <literal>Y</> or <literal>N</>, |
| 1154 | + responds with a single byte containing <literal>S</> or <literal>N</>, |
1155 | 1155 | indicating that it is willing or unwilling to perform SSL, respectively. |
1156 | 1156 | The frontend may close the connection at this point if it is dissatisfied |
1157 | | - with the response. To continue after <literal>Y</>, perform an SSL |
| 1157 | + with the response. To continue after <literal>S</>, perform an SSL |
1158 | 1158 | startup handshake (not described here, part of the SSL specification) |
1159 | 1159 | with the server. If this is successful, continue with |
1160 | 1160 | sending the usual StartupMessage. In this case the StartupMessage and |
|