Class Server
- All Implemented Interfaces:
Proxy
SoupServer provides a basic implementation of an HTTP server. The
recommended usage of this server is for internal use, tasks like
a mock server for tests, a private service for IPC, etc. It is not
recommended to be exposed to untrusted clients as it may be vulnerable
to denial of service attacks or other exploits.
To begin, create a server using Server(). Add at least one
handler by calling addHandler(java.lang.String, org.gnome.soup.ServerCallback) or
addEarlyHandler(java.lang.String, org.gnome.soup.ServerCallback); the handler will be called to
process any requests underneath the path you pass. (If you want all
requests to go to the same handler, just pass "/" (or null) for
the path.)
When a new connection is accepted (or a new request is started on
an existing persistent connection), the SoupServer will emit
Server::request-started and then begin processing the request
as described below, but note that once the message is assigned a
status-code, then callbacks after that point will be
skipped. Note also that it is not defined when the callbacks happen
relative to various ServerMessage signals.
Once the headers have been read, SoupServer will check if there is
a AuthDomain (qv) covering the Request-URI; if so, and if the
message does not contain suitable authorization, then the
AuthDomain will set a status of Status.UNAUTHORIZED on
the message.
After checking for authorization, SoupServer will look for "early"
handlers (added with addEarlyHandler(java.lang.String, org.gnome.soup.ServerCallback)) matching the
Request-URI. If one is found, it will be run; in particular, this
can be used to connect to signals to do a streaming read of the
request body.
(At this point, if the request headers contain Expect:
100-continue, and a status code has been set, then
SoupServer will skip the remaining steps and return the response.
If the request headers contain Expect:
100-continue and no status code has been set,
SoupServer will return a Status.CONTINUE status before
continuing.)
The server will then read in the response body (if present). At
this point, if there are no handlers at all defined for the
Request-URI, then the server will return Status.NOT_FOUND to
the client.
Otherwise (assuming no previous step assigned a status to the
message) any "normal" handlers (added with
addHandler(java.lang.String, org.gnome.soup.ServerCallback)) for the message's Request-URI will be
run.
Then, if the path has a WebSocket handler registered (and has
not yet been assigned a status), SoupServer will attempt to
validate the WebSocket handshake, filling in the response and
setting a status of Status.SWITCHING_PROTOCOLS or
Status.BAD_REQUEST accordingly.
If the message still has no status code at this point (and has not
been paused with ServerMessage.pause()), then it will be
given a status of Status.INTERNAL_SERVER_ERROR (because at
least one handler ran, but returned without assigning a status).
Finally, the server will emit Server::request-finished (or
Server::request-aborted if an I/O error occurred before
handling was completed).
If you want to handle the special "*" URI (eg, "OPTIONS *"), you must explicitly register a handler for "*"; the default handler will not be used for that case.
If you want to process https connections in addition to (or instead
of) http connections, you can set the Server:tls-certificate
property.
Once the server is set up, make one or more calls to
listen(org.gnome.gio.SocketAddress, java.util.Set<org.gnome.soup.ServerListenOptions>), listenLocal(int, java.util.Set<org.gnome.soup.ServerListenOptions>), or
listenAll(int, java.util.Set<org.gnome.soup.ServerListenOptions>) to tell it where to listen for
connections. (All ports on a SoupServer use the same handlers; if
you need to handle some ports differently, such as returning
different data for http and https, you'll need to create multiple
SoupServers, or else check the passed-in URI in the handler
function.).
SoupServer will begin processing connections as soon as you return
to (or start) the main loop for the current thread-default
GLib.MainContext.
-
Nested Class Summary
Nested ClassesModifier and TypeClassDescriptionstatic classServer.Builder<B extends Server.Builder<B>>Inner class implementing a builder pattern to construct a GObject with properties.static interfaceFunctional interface declaration of theRequestAbortedCallbackcallback.static interfaceFunctional interface declaration of theRequestFinishedCallbackcallback.static interfaceFunctional interface declaration of theRequestReadCallbackcallback.static interfaceFunctional interface declaration of theRequestStartedCallbackcallback.static classNested classes/interfaces inherited from class org.gnome.gobject.GObject
GObject.NotifyCallback, GObject.ObjectClass -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionbooleanacceptIostream(IOStream stream, @Nullable SocketAddress localAddr, @Nullable SocketAddress remoteAddr) Adds a new client stream to theserver.voidaddAuthDomain(AuthDomain authDomain) Adds an authentication domain toserver.voidaddEarlyHandler(@Nullable String path, @Nullable ServerCallback callback) Adds an "early" handler to this Server for requests prefixed bypath.voidaddHandler(@Nullable String path, @Nullable ServerCallback callback) Adds a handler to this Server for requests prefixed bypath.voidaddWebsocketExtension(Type extensionType) Add support for a WebSocket extension of the givenextensionType.voidaddWebsocketHandler(@Nullable String path, @Nullable String origin, @Nullable String @Nullable [] protocols, @Nullable ServerWebsocketCallback callback) Adds a WebSocket handler to this Server for requests prefixed bypath.protected ServerasParent()Returns this instance as if it were its parent type.static Server.Builder<? extends Server.Builder> builder()AServer.Builderobject constructs aServerwith the specified properties.voidCloses and freesserver'slistening sockets.voidemitRequestAborted(@Nullable ServerMessage message) Emits the "request-aborted" signal.voidemitRequestFinished(@Nullable ServerMessage message) Emits the "request-finished" signal.voidemitRequestRead(@Nullable ServerMessage message) Emits the "request-read" signal.voidemitRequestStarted(@Nullable ServerMessage message) Emits the "request-started" signal.Getsserver'slist of listening sockets.static MemoryLayoutThe memory layout of the native struct.Gets the this Server SSL/TLS client authentication mode.@Nullable TlsCertificateGets the this Server SSL/TLS certificate.@Nullable TlsDatabaseGets the this Server SSL/TLS database.static @Nullable TypegetType()Get the GType of the Server classgetUris()Gets a list of URIs corresponding to the interfaces this Server is listening on.booleanisHttps()Checks whether this Server is capable of https.booleanlisten(SocketAddress address, Set<ServerListenOptions> options) Attempts to set up this Server to listen for connections onaddress.booleanlisten(SocketAddress address, ServerListenOptions... options) Attempts to set up this Server to listen for connections onaddress.booleanlistenAll(int port, Set<ServerListenOptions> options) Attempts to set up this Server to listen for connections on all interfaces on the system.booleanlistenAll(int port, ServerListenOptions... options) Attempts to set up this Server to listen for connections on all interfaces on the system.booleanlistenLocal(int port, Set<ServerListenOptions> options) Attempts to set up this Server to listen for connections on "localhost".booleanlistenLocal(int port, ServerListenOptions... options) Attempts to set up this Server to listen for connections on "localhost".booleanlistenSocket(Socket socket, Set<ServerListenOptions> options) Attempts to set up this Server to listen for connections onsocket.booleanlistenSocket(Socket socket, ServerListenOptions... options) Attempts to set up this Server to listen for connections onsocket.Emitted when processing has failed for a message.Emitted when the server has finished writing a response to a request.onRequestRead(Server.RequestReadCallback handler) Emitted when the server has successfully read a request.Emitted when the server has started reading a new request.voidDeprecated.Use soup_server_message_pause() instead.voidremoveAuthDomain(AuthDomain authDomain) RemovesauthDomainfromserver.voidremoveHandler(String path) Removes all handlers (early and normal) registered atpath.voidremoveWebsocketExtension(Type extensionType) Removes support for WebSocket extension of typeextensionType(or any subclass ofextensionType)fromserver.protected voidprotected voidprotected voidrequestRead(ServerMessage msg) protected voidvoidSetsserver'sGTlsAuthenticationModeto use for SSL/TLS client authentication.voidsetTlsCertificate(TlsCertificate certificate) Sets this Server up to do https, using the given SSL/TLScertificate.voidsetTlsDatabase(TlsDatabase tlsDatabase) Setsserver'sGTlsDatabaseto use for validating SSL/TLS client certificates.voidDeprecated.Use soup_server_message_unpause() instead.Methods inherited from class org.gnome.gobject.GObject
addToggleRef, addWeakPointer, bindProperty, bindProperty, bindProperty, bindPropertyFull, bindPropertyFull, bindPropertyWithClosures, bindPropertyWithClosures, compatControl, connect, connect, connect, constructed, disconnect, dispatchPropertiesChanged, dispose, dupData, dupQdata, emit, emitNotify, finalize_, forceFloating, freezeNotify, get, getData, getProperty, getProperty, getProperty, getQdata, getv, interfaceFindProperty, interfaceInstallProperty, interfaceListProperties, isFloating, newInstance, newInstance, newv, notify, notify, notifyByPspec, onNotify, ref, refSink, removeToggleRef, removeWeakPointer, replaceData, replaceQdata, runDispose, set, setData, setDataFull, setProperty, setProperty, setProperty, setQdata, setQdataFull, setv, stealData, stealQdata, takeRef, thawNotify, unref, watchClosure, weakRef, weakUnref, withPropertiesMethods inherited from class org.gnome.gobject.TypeInstance
callParent, callParent, cast, getPrivate, readGClass, writeGClassMethods inherited from class org.javagi.base.ProxyInstance
equals, handle, hashCode
-
Constructor Details
-
Server
Create a Server proxy instance for the provided memory address.- Parameters:
address- the memory address of the native object
-
Server
-
Server
public Server()Creates a new Server.
-
-
Method Details
-
getType
-
getMemoryLayout
The memory layout of the native struct.- Returns:
- the memory layout
-
asParent
Returns this instance as if it were its parent type. This is mostly synonymous to the Javasuperkeyword, but will set the native typeclass function pointers to the parent type. When overriding a native virtual method in Java, "chaining up" withsuper.methodName()doesn't work, because it invokes the overridden function pointer again. To chain up, callasParent().methodName(). This will call the native function pointer of this virtual method in the typeclass of the parent type. -
acceptIostream
public boolean acceptIostream(IOStream stream, @Nullable SocketAddress localAddr, @Nullable SocketAddress remoteAddr) throws GErrorException Adds a new client stream to theserver.- Parameters:
stream- aGIOStreamlocalAddr- the localGSocketAddressassociated with thestreamremoteAddr- the remoteGSocketAddressassociated with thestream- Returns:
trueon success,falseif the stream could not be accepted or any other error occurred (in which caseerrorwill be set).- Throws:
GErrorException- seeGError
-
addAuthDomain
Adds an authentication domain toserver.Each auth domain will have the chance to require authentication for each request that comes in; normally auth domains will require authentication for requests on certain paths that they have been set up to watch, or that meet other criteria set by the caller. If an auth domain determines that a request requires authentication (and the request doesn't contain authentication), this Server will automatically reject the request with an appropriate status (401 Unauthorized or 407 Proxy Authentication Required). If the request used the SoupServer:100-continue Expectation, this Server will reject it before the request body is sent.
- Parameters:
authDomain- aSoupAuthDomain
-
addEarlyHandler
Adds an "early" handler to this Server for requests prefixed bypath.Note that "normal" and "early" handlers are matched up together, so if you add a normal handler for "/foo" and an early handler for "/foo/bar", then a request to "/foo/bar" (or any path below it) will run only the early handler. (But if you add both handlers at the same path, then both will get run.)
For requests under
path(that have not already been assigned a status code by aAuthDomainor a signal handler),callbackwill be invoked after receiving the request headers, but before receiving the request body; the message's method and request-headers properties will be set.Early handlers are generally used for processing requests with request bodies in a streaming fashion. If you determine that the request will contain a message body, normally you would call
MessageBody.setAccumulate(boolean)on the message's request-body to turn off request-body accumulation, and connect to the message'sServerMessage::got-chunksignal to process each chunk as it comes in.To complete the message processing after the full message body has been read, you can either also connect to
ServerMessage::got-body, or else you can register a non-early handler forpathas well. As long as you have not set the status-code by the timeServerMessage::got-bodyis emitted, the non-early handler will be run as well.- Parameters:
path- the toplevel path for the handlercallback- callback to invoke for requests underpath
-
addHandler
Adds a handler to this Server for requests prefixed bypath.If
pathisnullor "/", then this will be the default handler for all requests that don't have a more specific handler. (Note though that if you want to handle requests to the special "*" URI, you must explicitly register a handler for "*"; the default handler will not be used for that case.)For requests under
path(that have not already been assigned a status code by aAuthDomain, an early server handler, or a signal handler),callbackwill be invoked after receiving the request body; theServerMessage's method, request-headers, and request-body properties will be set.After determining what to do with the request, the callback must at a minimum call
ServerMessage.setStatus(int, java.lang.String)on the message to set the response status code. Additionally, it may set response headers and/or fill in the response body.If the callback cannot fully fill in the response before returning (eg, if it needs to wait for information from a database, or another network server), it should call
ServerMessage.pause()to tell this Server to not send the response right away. When the response is ready, callServerMessage.unpause()to cause it to be sent.To send the response body a bit at a time using "chunked" encoding, first call
MessageHeaders.setEncoding(org.gnome.soup.Encoding)to setEncoding.CHUNKEDon the response-headers. Then callMessageBody.append(byte[])(orMessageBody.appendBytes(byte[]))) to append each chunk as it becomes ready, andServerMessage.unpause()to make sure it's running. (The server will automatically pause the message if it is using chunked encoding but no more chunks are available.) When you are done, callMessageBody.complete()to indicate that no more chunks are coming.- Parameters:
path- the toplevel path for the handlercallback- callback to invoke for requests underpath
-
addWebsocketExtension
Add support for a WebSocket extension of the givenextensionType.When a WebSocket client requests an extension of
extensionType,a newWebsocketExtensionof typeextensionTypewill be created to handle the request.Note that
WebsocketExtensionDeflateis supported by default, useremoveWebsocketExtension(org.gnome.glib.Type)if you want to disable it.- Parameters:
extensionType- aGType
-
addWebsocketHandler
public void addWebsocketHandler(@Nullable String path, @Nullable String origin, @Nullable String @Nullable [] protocols, @Nullable ServerWebsocketCallback callback) Adds a WebSocket handler to this Server for requests prefixed bypath.If
pathisnullor "/", then this will be the default handler for all requests that don't have a more specific handler.When a path has a WebSocket handler registered, this Server will check incoming requests for WebSocket handshakes after all other handlers have run (unless some earlier handler has already set a status code on the message), and update the request's status, response headers, and response body accordingly.
If
originis non-null, then only requests containing a matching "Origin" header will be accepted. Ifprotocolsis non-null, then only requests containing a compatible "Sec-WebSocket-Protocols" header will be accepted. More complicated requirements can be handled by adding a normal handler topath,and having it perform whatever checks are needed and setting a failure status code if the handshake should be rejected.- Parameters:
path- the toplevel path for the handlerorigin- the origin of the connectionprotocols- the protocols supported by this handlercallback- callback to invoke for successful WebSocket requests underpath
-
disconnect
public void disconnect()Closes and freesserver'slistening sockets.Note that if there are currently requests in progress on
server,that they will continue to be processed ifserver'sGLib.MainContextis still running.You can call
listen(org.gnome.gio.SocketAddress, java.util.Set<org.gnome.soup.ServerListenOptions>), etc, after calling this function if you want to start listening again. -
getListeners
-
getTlsAuthMode
Gets the this Server SSL/TLS client authentication mode.- Returns:
- a
GTlsAuthenticationMode
-
getTlsCertificate
Gets the this Server SSL/TLS certificate.- Returns:
- a
GTlsCertificateornull
-
getTlsDatabase
Gets the this Server SSL/TLS database.- Returns:
- a
GTlsDatabase
-
getUris
Gets a list of URIs corresponding to the interfaces this Server is listening on.These will contain IP addresses, not hostnames, and will also indicate whether the given listener is http or https.
Note that if you used
listenAll(int, java.util.Set<org.gnome.soup.ServerListenOptions>)the returned URIs will use the addresses0.0.0.0and::, rather than actually returning separate URIs for each interface on the system.- Returns:
- a list of
GUris, which you must free when you are done with it.
-
isHttps
public boolean isHttps()Checks whether this Server is capable of https.In order for a server to run https, you must call
setTlsCertificate(org.gnome.gio.TlsCertificate), or set theServer:tls-certificateproperty, to provide it with a certificate to use.If you are using the deprecated single-listener APIs, then a return value of
trueindicates that theSoupServerserves https exclusively. If you are usinglisten(org.gnome.gio.SocketAddress, java.util.Set<org.gnome.soup.ServerListenOptions>), etc, then atruereturn value merely indicates that the server is able to do https, regardless of whether it actually currently is or not. UsegetUris()to see if it currently has any https listeners.- Returns:
trueif this Server is configured to serve https.
-
listen
public boolean listen(SocketAddress address, Set<ServerListenOptions> options) throws GErrorException Attempts to set up this Server to listen for connections onaddress.If
optionsincludesServerListenOptions.HTTPS, and this Server has been configured for TLS, then this Server will listen for https connections on this port. Otherwise it will listen for plain http.You may call this method (along with the other "listen" methods) any number of times on a server, if you want to listen on multiple ports, or set up both http and https service.
After calling this method, this Server will begin accepting and processing connections as soon as the appropriate
GLib.MainContextis run.Note that this API does not make use of dual IPv4/IPv6 sockets; if
addressis an IPv6 address, it will only accept IPv6 connections. You must configure IPv4 listening separately.- Parameters:
address- the address of the interface to listen onoptions- listening options for this server- Returns:
trueon success,falseifaddresscould not be bound or any other error occurred (in which caseerrorwill be set).- Throws:
GErrorException- seeGError
-
listen
Attempts to set up this Server to listen for connections onaddress.If
optionsincludesServerListenOptions.HTTPS, and this Server has been configured for TLS, then this Server will listen for https connections on this port. Otherwise it will listen for plain http.You may call this method (along with the other "listen" methods) any number of times on a server, if you want to listen on multiple ports, or set up both http and https service.
After calling this method, this Server will begin accepting and processing connections as soon as the appropriate
GLib.MainContextis run.Note that this API does not make use of dual IPv4/IPv6 sockets; if
addressis an IPv6 address, it will only accept IPv6 connections. You must configure IPv4 listening separately.- Parameters:
address- the address of the interface to listen onoptions- listening options for this server- Returns:
trueon success,falseifaddresscould not be bound or any other error occurred (in which caseerrorwill be set).- Throws:
GErrorException- seeGError
-
listenAll
Attempts to set up this Server to listen for connections on all interfaces on the system.That is, it listens on the addresses
0.0.0.0and/or::, depending on whetheroptionsincludesServerListenOptions.IPV4_ONLY,ServerListenOptions.IPV6_ONLY, or neither.) Ifportis specified, this Server will listen on that port. If it is 0, this Server will find an unused port to listen on. (In that case, you can usegetUris()to find out what port it ended up choosing.See
listen(org.gnome.gio.SocketAddress, java.util.Set<org.gnome.soup.ServerListenOptions>)for more details.- Parameters:
port- the port to listen on, or 0options- listening options for this server- Returns:
trueon success,falseifportcould not be bound or any other error occurred (in which caseerrorwill be set).- Throws:
GErrorException- seeGError
-
listenAll
Attempts to set up this Server to listen for connections on all interfaces on the system.That is, it listens on the addresses
0.0.0.0and/or::, depending on whetheroptionsincludesServerListenOptions.IPV4_ONLY,ServerListenOptions.IPV6_ONLY, or neither.) Ifportis specified, this Server will listen on that port. If it is 0, this Server will find an unused port to listen on. (In that case, you can usegetUris()to find out what port it ended up choosing.See
listen(org.gnome.gio.SocketAddress, java.util.Set<org.gnome.soup.ServerListenOptions>)for more details.- Parameters:
port- the port to listen on, or 0options- listening options for this server- Returns:
trueon success,falseifportcould not be bound or any other error occurred (in which caseerrorwill be set).- Throws:
GErrorException- seeGError
-
listenLocal
Attempts to set up this Server to listen for connections on "localhost".That is,
127.0.0.1and/or::1, depending on whetheroptionsincludesServerListenOptions.IPV4_ONLY,ServerListenOptions.IPV6_ONLY, or neither). Ifportis specified, this Server will listen on that port. If it is 0, this Server will find an unused port to listen on. (In that case, you can usegetUris()to find out what port it ended up choosing.See
listen(org.gnome.gio.SocketAddress, java.util.Set<org.gnome.soup.ServerListenOptions>)for more details.- Parameters:
port- the port to listen on, or 0options- listening options for this server- Returns:
trueon success,falseifportcould not be bound or any other error occurred (in which caseerrorwill be set).- Throws:
GErrorException- seeGError
-
listenLocal
Attempts to set up this Server to listen for connections on "localhost".That is,
127.0.0.1and/or::1, depending on whetheroptionsincludesServerListenOptions.IPV4_ONLY,ServerListenOptions.IPV6_ONLY, or neither). Ifportis specified, this Server will listen on that port. If it is 0, this Server will find an unused port to listen on. (In that case, you can usegetUris()to find out what port it ended up choosing.See
listen(org.gnome.gio.SocketAddress, java.util.Set<org.gnome.soup.ServerListenOptions>)for more details.- Parameters:
port- the port to listen on, or 0options- listening options for this server- Returns:
trueon success,falseifportcould not be bound or any other error occurred (in which caseerrorwill be set).- Throws:
GErrorException- seeGError
-
listenSocket
Attempts to set up this Server to listen for connections onsocket.See
listen(org.gnome.gio.SocketAddress, java.util.Set<org.gnome.soup.ServerListenOptions>)for more details.- Parameters:
socket- a listeningGSocketoptions- listening options for this server- Returns:
trueon success,falseif an error occurred (in which caseerrorwill be set).- Throws:
GErrorException- seeGError
-
listenSocket
Attempts to set up this Server to listen for connections onsocket.See
listen(org.gnome.gio.SocketAddress, java.util.Set<org.gnome.soup.ServerListenOptions>)for more details.- Parameters:
socket- a listeningGSocketoptions- listening options for this server- Returns:
trueon success,falseif an error occurred (in which caseerrorwill be set).- Throws:
GErrorException- seeGError
-
pauseMessage
Deprecated.Use soup_server_message_pause() instead.Pauses I/O onmsg.This can be used when you need to return from the server handler without having the full response ready yet. Use
unpauseMessage(org.gnome.soup.ServerMessage)to resume I/O.This must only be called on a
ServerMessagewhich was created by theSoupServerand are currently doing I/O, such as those passed into aServerCallbackor emitted in aServer::request-readsignal.- Parameters:
msg- aSoupServerMessageassociated withserver.
-
removeAuthDomain
RemovesauthDomainfromserver.- Parameters:
authDomain- aSoupAuthDomain
-
removeHandler
Removes all handlers (early and normal) registered atpath.- Parameters:
path- the toplevel path for the handler
-
removeWebsocketExtension
Removes support for WebSocket extension of typeextensionType(or any subclass ofextensionType)fromserver.- Parameters:
extensionType- aGType
-
setTlsAuthMode
Setsserver'sGTlsAuthenticationModeto use for SSL/TLS client authentication.- Parameters:
mode- aGTlsAuthenticationMode
-
setTlsCertificate
Sets this Server up to do https, using the given SSL/TLScertificate.- Parameters:
certificate- aGTlsCertificate
-
setTlsDatabase
Setsserver'sGTlsDatabaseto use for validating SSL/TLS client certificates.- Parameters:
tlsDatabase- aGTlsDatabase
-
unpauseMessage
Deprecated.Use soup_server_message_unpause() instead.Resumes I/O onmsg.Use this to resume after calling
pauseMessage(org.gnome.soup.ServerMessage), or after adding a new chunk to a chunked response.I/O won't actually resume until you return to the main loop.
This must only be called on a
ServerMessagewhich was created by theSoupServerand are currently doing I/O, such as those passed into aServerCallbackor emitted in aServer::request-readsignal.- Parameters:
msg- aSoupServerMessageassociated withserver.
-
requestAborted
-
requestFinished
-
requestRead
-
requestStarted
-
onRequestAborted
public SignalConnection<Server.RequestAbortedCallback> onRequestAborted(Server.RequestAbortedCallback handler) Emitted when processing has failed for a message.This could mean either that it could not be read (if
Server::request-readhas not been emitted for it yet), or that the response could not be written back (ifServer::request-readhas been emitted butServer::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 inServer::request-started.- Parameters:
handler- the signal handler- Returns:
- a signal handler ID to keep track of the signal connection
- See Also:
-
emitRequestAborted
Emits the "request-aborted" signal. SeeonRequestAborted(org.gnome.soup.Server.RequestAbortedCallback). -
onRequestFinished
public SignalConnection<Server.RequestFinishedCallback> onRequestFinished(Server.RequestFinishedCallback handler) Emitted when the server has finished writing a response to a request.- Parameters:
handler- the signal handler- Returns:
- a signal handler ID to keep track of the signal connection
- See Also:
-
emitRequestFinished
Emits the "request-finished" signal. SeeonRequestFinished(org.gnome.soup.Server.RequestFinishedCallback). -
onRequestRead
public SignalConnection<Server.RequestReadCallback> onRequestRead(Server.RequestReadCallback handler) Emitted when the server has successfully read a request.messagewill have all of its request-side information filled in, and if the message was authenticated,clientwill have information about that. This signal is emitted before any (non-early) handlers are called for the message, and if it sets the message'sstatus_code, then normal handler processing will be skipped.- Parameters:
handler- the signal handler- Returns:
- a signal handler ID to keep track of the signal connection
- See Also:
-
emitRequestRead
Emits the "request-read" signal. SeeonRequestRead(org.gnome.soup.Server.RequestReadCallback). -
onRequestStarted
public SignalConnection<Server.RequestStartedCallback> onRequestStarted(Server.RequestStartedCallback handler) Emitted when the server has started reading a new request.messagewill 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
Server::request_read signal. If a response is then sent, the request processing will end with aServer::request-finishedsignal. If a network error occurs, the processing will instead end withServer::request-aborted.- Parameters:
handler- the signal handler- Returns:
- a signal handler ID to keep track of the signal connection
- See Also:
-
emitRequestStarted
Emits the "request-started" signal. SeeonRequestStarted(org.gnome.soup.Server.RequestStartedCallback). -
builder
AServer.Builderobject constructs aServerwith the specified properties. Use the variousset...()methods to set properties, and finish construction withServer.Builder.build().- Returns:
- the builder object
-