Hoogle Search
Within LTS Haskell 24.52 (ghc-9.10.3)
Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.
-
gi-gio GI.Gio.Objects.TlsConnection Construct a GValueConstruct with valid value for the “require-close-notify” property. This is rarely needed directly, but it is used by new.
getTlsConnectionRequireCloseNotify :: (MonadIO m, IsTlsConnection o) => o -> m Boolgi-gio GI.Gio.Objects.TlsConnection Get the value of the “require-close-notify” property. When overloading is enabled, this is equivalent to
get tlsConnection #requireCloseNotify
setTlsConnectionRequireCloseNotify :: (MonadIO m, IsTlsConnection o) => o -> Bool -> m ()gi-gio GI.Gio.Objects.TlsConnection Set the value of the “require-close-notify” property. When overloading is enabled, this is equivalent to
set tlsConnection [ #requireCloseNotify := value ]
tlsConnectionGetRequireCloseNotify :: (HasCallStack, MonadIO m, IsTlsConnection a) => a -> m Boolgi-gio GI.Gio.Objects.TlsConnection Tests whether or not conn expects a proper TLS close notification when the connection is closed. See tlsConnectionSetRequireCloseNotify for details. Since: 2.28
-
gi-gio GI.Gio.Objects.TlsConnection 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 TlsErrorEof 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 tlsConnectionSetRequireCloseNotify 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 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 iOStreamClose 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 TlsConnection:baseIoStream rather than closing conn itself, but note that this may only be done when no other operations are pending on conn or the base I/O stream. Since: 2.28
-
gi-gio GI.Gio.Objects.TlsInteraction Invoke the interaction to ask the user to choose a certificate to use with the connection. It invokes this interaction in the main loop, specifically the MainContext returned by mainContextGetThreadDefault when the interaction is created. This is called by called by TlsConnection when the peer requests a certificate during the handshake. Derived subclasses usually implement a certificate selector, although they may also choose to provide a certificate from elsewhere. Alternatively the user may abort this certificate request, which may or may not abort the TLS connection. The implementation can either be a synchronous (eg: modal dialog) or an asynchronous one (eg: modeless dialog). This function will take care of calling which ever one correctly. If the interaction is cancelled by the cancellation object, or by the user then TlsInteractionResultFailed will be returned with an error that contains a IOErrorEnumCancelled error code. Certain implementations may not support immediate cancellation. Since: 2.40
-
gi-gio GI.Gio.Objects.TlsInteraction Run synchronous interaction to ask the user to choose a certificate to use with the connection. In general, tlsInteractionInvokeRequestCertificate should be used instead of this function. Derived subclasses usually implement a certificate selector, although they may also choose to provide a certificate from elsewhere. Alternatively the user may abort this certificate request, which will usually abort the TLS connection. If TlsInteractionResultHandled is returned, then the TlsConnection passed to tlsInteractionRequestCertificate will have had its TlsConnection:certificate filled in. If the interaction is cancelled by the cancellation object, or by the user then TlsInteractionResultFailed will be returned with an error that contains a IOErrorEnumCancelled error code. Certain implementations may not support immediate cancellation. Since: 2.40
-
gi-gio GI.Gio.Objects.TlsInteraction Run asynchronous interaction to ask the user for a certificate to use with the connection. In general, tlsInteractionInvokeRequestCertificate should be used instead of this function. Derived subclasses usually implement a certificate selector, although they may also choose to provide a certificate from elsewhere. callback will be called when the operation completes. Alternatively the user may abort this certificate request, which will usually abort the TLS connection. Since: 2.40
-
gi-gio GI.Gio.Objects.TlsInteraction Complete a request certificate user interaction request. This should be once the tlsInteractionRequestCertificateAsync completion callback is called. If TlsInteractionResultHandled is returned, then the TlsConnection passed to tlsInteractionRequestCertificateAsync will have had its TlsConnection:certificate filled in. If the interaction is cancelled by the cancellation object, or by the user then TlsInteractionResultFailed will be returned with an error that contains a IOErrorEnumCancelled error code. Since: 2.40
iOExtensionPointGetRequiredType :: (HasCallStack, MonadIO m) => IOExtensionPoint -> m GTypegi-gio GI.Gio.Structs.IOExtensionPoint Gets the required type for extensionPoint.