SignalRun Firstrequest-SignalRun Firstrequest-Emitted when the server has finished writing a response to a request.
SignalRun Firstrequest-Emitted when the server has successfully read a request.
message will have all of its request-side information
filled in, and if the message was authenticated, client
will have information about that. This signal is emitted
before any (non-early) handlers are called for the message,
and if it sets the message's status_code, then normal
handler processing will be skipped.
SignalRun Firstrequest-Emitted when the server has started reading a new request.
message will be completely blank; not even the
Request-Line will have been read yet. About the only thing
you can usefully do with it is connect to its signals.
If the request is read successfully, this will eventually
be followed by a [signal@Server::request_read signal]. If a
response is then sent, the request processing will end with
a Soup.Server::request-finished signal. If a network error
occurs, the processing will instead end with
Soup.Server::request-aborted.
SignalDetailedActionRun FirstnotifyThe 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.
Emitted when processing has failed for a message.
This could mean either that it could not be read (if
Soup.Server::request-readhas not been emitted for it yet), or that the response could not be written back (ifSoup.Server::request-readhas been emitted butSoup.Server::request-finishedhas not been).messageis in an undefined state when this signal is emitted; the signal exists primarily to allow the server to free any state that it may have allocated inSoup.Server::request-started.