Configuration
Configuration for the NettyApplicationEngine
Properties
User-provided function to configure Netty's ChannelPipeline
User-provided function to configure Netty's ServerBootstrap
If set to true, adds Netty's io.netty.handler.flush.FlushConsolidationHandler as the first handler in the channel pipeline. It batches back-to-back flush() calls (for example, from pipelined responses) into a single transport write, which can improve throughput under concurrent load at the cost of slightly delaying individual flushes.
If set to true and enableHttp2 is set to true, enables HTTP/2 protocol without TLS (h2c) for unencrypted connectors. SSL connectors are unaffected and continue to negotiate HTTP/2 via ALPN when enableHttp2 is true, so this flag can be combined with an SSL connector to serve both HTTP/2 over TLS and h2c from the same server.
If set to true, enables HTTP/2 protocol for Netty engine
User-provided function to configure Netty's HttpServerCodec
The maximum length of the content or each chunk
The maximum length of all headers. If the sum of the length of each header exceeds this value, a TooLongFrameException will be raised.
The url limit including query parameters
Timeout in seconds for reading requests from client, "0" is infinite.
Timeout in seconds for sending responses to client
Number of concurrently running requests from the same http pipeline
All tasks use a common event group, and call dispatchers wrap this event group without thread pinning. This setting reduces some overhead in scheduling at the expense of the safety provided by segregating the work and call groups.
If set to true, enables TCP keep alive for connections so all dead client connections will be discarded. The timeout period is configured by the system so configure your host accordingly.