Message.connectRequestCertificate

gulong connectRequestCertificate(T)(T callback,  Flag!"After" after =  No.After) if (isCallable!T
    &&  is(ReturnType!T ==  bool)
   && (Parameters!T.length <  1 || (ParameterStorageClassTuple!T[0]  ==  ParameterStorageClass.none &&  is(Parameters!T[0] :  gio.tls_client_connection.TlsClientConnection)))
   && (Parameters!T.length <  2 || (ParameterStorageClassTuple!T[1]  ==  ParameterStorageClass.none &&  is(Parameters!T[1] :  soup.message.Message)))
   &&  Parameters!T.length <  3)

Connect to RequestCertificate signal.

Emitted during the msg's connection TLS handshake when tls_connection requests a certificate from the client.

You can set the client certificate by calling [soup.message.Message.setTlsClientCertificate] and returning true. It's possible to handle the request asynchornously by returning true and call [soup.message.Message.setTlsClientCertificate] later once the certificate is available. Note that this signal is not emitted if propertySession:tls-interaction was set, or if [soup.message.Message.setTlsClientCertificate] was called before the connection TLS handshake started.

Parameters

`callback`	signal callback delegate or function to connect `bool callback(gio.tls_client_connection.TlsClientConnection tlsConnection, soup.message.Message message)` `tlsConnection` the #GTlsClientConnection (optional) `message` the instance the signal is connected to (optional) `Returns` true to handle the request, or false to make the connection fail with [gio.types.TlsError.CertificateRequired].
`after`	Yes.After to execute callback after default handler, No.After to execute before (default)

Returns

Signal ID