HTTP protocol handling configuration
Maximum size of HTTP request in megabytes. Defaults to 4MB.
Maximum size the initial line. Defaults to 4096 characters.
Maximum size of HTTP headers. Defaults to 8192 bytes.
Maximum size of HTTP chunks. Defaults to 8192 bytes.
Flag to indicate if we want to aggregate chunks. If
false, your processor actors must be
able to handle
Minimum number of bytes before HTTP content will be compressed if requested
by the client. Set to
-1 to turn off compression for all files;
0 to make all content compressible.
Maximum number of bytes before HTTP content will be not be compressed if requested by the client. Defaults to 1MB otherwise too much CPU maybe taken up for compression.
Support SPDY protocol or not. Defaults to
Creates a new channel pipeline for each Netty channel (network connection)
Handler used with SPDY that performs protocol negotiation.
Handles incoming HTTP messages from Netty
Path to server private key store file (server certificates)
Password to access server private key store file.
Path to key store file for trusted remote public keys (client certificates). This is optional.
Password to access the key store for trusted remote public keys (client certificates). This is optional.
Manages reading key stores and trust stores for TLS/SSL connections
TCP IP configuration as per Netty.
Disable Nagle's algorithm. Defaults to
true if not supplied.
Set a hint the size of the underlying buffers for outgoing network I/O.
Get the size of the buffer actually used by the platform when receiving in data on this socket.
Turn on socket keep-alive. Defaults to
false if not supplied.
Enable reuse address for a socket and not throw an "already bind exception" The default value is JVM specific.
Specify a linger-on-close timeout.
Sets the type-of-service or traffic class field in the IP header for a TCP or UDP socket. \ The default value is JVM specific.
The number of requests that can be queued. Useful in managing sudden bursts in requests. If take an example with a socket server invoker that has max pool set to 300, accept threads is 2, and backlog is 200, will be able to make 502 concurrent client calls. The 503rd client request will get an exception immediately. However, this does not mean all 502 requests will be guaranteed to be processed, only the first 300 (as they have server threads available to do the processing). If 202 of the server threads finish processing their requests from their initial client connections and the connection is released before the timeout for the other 202 that are waiting (200 for backlog and 2 for accept thread), then they will be processed (of course this is a request by request determination).
Configuration for web server activity logs.
Socko Web Server
Web server configuration
Human friendly name of this server. Defaults to
Hostname or IP address to bind.
0.0.0.0 will bind to all addresses.
You can also specify comma separated hostnames/ip address like
IP port number to bind to. Defaults to
If a connection is idle for this duration, it will be closed. The default is
which indicates NO timeout and idle connections will NOT be closed.
Dumps request and response data to the debug logger. To see the output, you need to
set the logging level for
io.netty.handler.logging.LoggingHandler to debug. The default is
Optional web log configuration. If
None, web log events will NOT be generated.
SSL protocol configuration. If
None, then SSL will not be turned on.
HTTP protocol configuration. Defaults to an instance of org.mashupbots.socko.webserver.HttpConfig with default settings.
TCP IP protocol configuration. Defaults to an instance of org.mashupbots.socko.webserver.TcpConfig with default settings.
Manages all web socket connections