Gio.TlsConnection.prototype.set_require_close_notify

function set_require_close_notify(require_close_notify: Boolean): void {
    // Gjs wrapper for g_tls_connection_set_require_close_notify()
}
  

Sets whether or not conn expects a proper TLS close notification before the connection is closed. If this is true (the default), then conn will expect to receive a TLS close notification from its peer before the connection is closed, and will return a Gio.TlsError.eof error if the connection is closed without proper notification (since this may indicate a network error, or man-in-the-middle attack).

In some protocols, the application will know whether or not the connection was closed cleanly based on application-level data (because the application-level data includes a length field, or is somehow self-delimiting); in this case, the close notify is redundant and sometimes omitted. (TLS 1.1 explicitly allows this; in TLS 1.0 it is technically an error, but often done anyway.) You can use Gio.TlsConnection.prototype.set_require_close_notify to tell conn to allow an "unannounced" connection close, in which case the close will show up as a 0-length read, as in a non-TLS Gio.SocketConnection, and it is up to the application to check that the data has been fully received.

Note that this only affects the behavior when the peer closes the connection; when the application calls Gio.IOStream.prototype.close itself on conn, this will send a close notification regardless of the setting of this property. If you explicitly want to do an unclean close, you can close conn's Gio.TlsConnection.base_io_stream rather than closing conn itself.

Since 2.28