Interface

Soup-3.0 ▶ Soup ▶ ServerMessage ▶ SignalSignatures

interface SignalSignatures {
    "accept-certificate": (
        arg0: Gio.TlsCertificate,
        arg1: Gio.TlsCertificateFlags,
    ) => boolean | void;
    connected: () => void;
    disconnected: () => void;
    finished: () => void;
    "got-body": () => void;
    "got-chunk": (arg0: GLib.Bytes) => void;
    "got-headers": () => void;
    notify: (arg0: GObject.ParamSpec) => void;
    "notify::tls-peer-certificate": (pspec: GObject.ParamSpec) => void;
    "notify::tls-peer-certificate-errors": (pspec: GObject.ParamSpec) => void;
    "wrote-body": () => void;
    "wrote-body-data": (arg0: number) => void;
    "wrote-chunk": () => void;
    "wrote-headers": () => void;
    "wrote-informational": () => void;
}

Hierarchy (View Summary)

Index

Properties

accept-certificate connected disconnected finished got-body got-chunk got-headers notify::tls-peer-certificate notify::tls-peer-certificate-errors wrote-body wrote-body-data wrote-chunk wrote-headers wrote-informational

Properties - Inherited from GObject

notify

Properties

"accept-certificate": (
    arg0: Gio.TlsCertificate,
    arg1: Gio.TlsCertificateFlags,
) => boolean | void

Emitted during the msg's connection TLS handshake after client TLS certificate has been received. You can return true to accept tls_certificate despite tls_errors.

connected: () => void

Emitted when the msg's socket is connected and the TLS handshake completed.

disconnected: () => void

Emitted when the msg's socket is disconnected.

finished: () => void

Emitted when all HTTP processing is finished for a message. (After Soup.ServerMessage::wrote-body).

SignalRun Lastgot-body

"got-body": () => void

Emitted after receiving the complete request body.

"got-chunk": (arg0: GLib.Bytes) => void

Emitted after receiving a chunk of a message body.

Note that "chunk" in this context means any subpiece of the body, not necessarily the specific HTTP 1.1 chunks sent by the other side.

"got-headers": () => void

Emitted after receiving the Request-Line and request headers.

"notify::tls-peer-certificate": (pspec: GObject.ParamSpec) => void
"notify::tls-peer-certificate-errors": (pspec: GObject.ParamSpec) => void

SignalRun Lastwrote-body

"wrote-body": () => void

Emitted immediately after writing the complete response body for a message.

SignalRun Lastwrote-body-data

"wrote-body-data": (arg0: number) => void

Emitted immediately after writing a portion of the message body to the network.

"wrote-chunk": () => void

Emitted immediately after writing a body chunk for a message.

Note that this signal is not parallel to Soup.ServerMessage::got-chunk; it is emitted only when a complete chunk (added with MessageBody.append or MessageBody.append_bytes has been written. To get more useful continuous progress information, use Soup.ServerMessage::wrote-body-data.

"wrote-headers": () => void

Emitted immediately after writing the response headers for a message.

"wrote-informational": () => void

Emitted immediately after writing a 1xx (Informational) response.

Properties - Inherited from GObject

notify: (arg0: GObject.ParamSpec) => void

The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with GObject.ParamFlags.EXPLICIT_NOTIFY, then any call to g_object_set_property() results in ::notify being emitted, even if the new value is the same as the old. If they did pass GObject.ParamFlags.EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this:

g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

It is important to note that you must use [canonical parameter names][class@GObject.ParamSpec#parameter-names] as detail strings for the notify signal.