Config

Configure the server to use HttpServerExpectContinueHandler to send a 100 HttpResponse if necessary.

Attempts to avoid context switching between thread pools by executing requests within the server's IO thread-pool (e.g., Netty's EventLoop) until the first async/blocking boundary.

Enabling this setting can improve performance for short-lived CPU-bound tasks, but can also lead to degraded performance if the request handler performs CPU-heavy work prior to the first async boundary.

'''WARNING:''' Do not use this mode if the ZIO executor is configured to use virtual threads!

Configure the server to listen on the provided hostname and port.

Configure the server to listen on the provided InetAddress and port.

Configure the server to listen on the provided InetSocketAddress.

Disables streaming of request bodies. Payloads larger than maxContentLength will be rejected

Enables streaming request bodies

Enables hybrid request streaming

Configure the server to use netty's HttpServerKeepAliveHandler to close persistent connections when enable is true (@see HttpServerKeepAliveHandler).

Log a warning in case of fatal errors when an error response cannot be sent back to the client

Configure the server to use maxHeaderSize value when encode/decode headers.

Configure the server to listen on an available open port

Configure the server to listen on the provided port.

Soft cap on the bytes the server will buffer from a streamed request body before the route handler starts consuming it. The cap may be overshot by up to one HttpContent chunk: the chunk that crosses the threshold is appended to the buffer before reads stop. Once the threshold is reached, Netty's TCP back-pressure kicks in and the client is paused until the handler calls request.body.asStream (or similar) and begins reading. Prevents heap exhaustion when an async handler defers consuming the body and the client uploads faster than the handler can connect. Applies when RequestStreaming.Enabled is configured, and also with RequestStreaming.Hybrid for request bodies that exceed the aggregated threshold and are therefore handled as streamed bodies.

Configure the server to use netty's HttpContentDecompressor to decompress Http requests (@see HttpContentDecompressor).

Enables or disables request body streaming

Configure the new server with netty's HttpContentCompressor to compress Http responses (@see <a href = "https://netty.io/4.1/api/io/netty/handler/codec/http/HttpContentCompressor.html"HttpContentCompressor).

Sets the maximum number of connection requests that will be queued before being rejected

Configure the server with the following ssl options.

Configure the server to enable/disable TCP_NODELAY. TCP_NODELAY disables Nagle's algorithm, which reduces latency for small messages.