Http2Config (webserver.http2) Configuration

Duration

Outbound flow control blocking timeout configured as java.time.Duration or text in ISO-8601 format. Blocking timeout defines an interval to wait for the outbound window size changes(incoming window updates). Default value is PT15S.

See ISO_8601 Durations

int

This setting indicates the sender’s maximum window size in bytes for stream-level flow control. Default and maximum value is 2³¹-1 = 2147483647 bytes. This setting affects the window size of HTTP/2 connection. Any value greater than 2147483647 causes an error. Any value smaller than initial window size causes an error. See RFC 9113 section 6.9.1 for details.

long

Maximum number of concurrent streams that the server will allow. Defaults to 8192. This limit is directional: it applies to the number of streams that the sender permits the receiver to create. It is recommended that this value be no smaller than 100 to not unnecessarily limit parallelism See RFC 9113 section 6.5.2 for details.

int

Maximum number of consecutive empty frames allowed on connection.

int

The size of the largest frame payload that the sender is willing to receive in bytes. Default value is 16384 and maximum value is 2²⁴-1 = 16777215 bytes. See RFC 9113 section 6.5.2 for details.

long

The maximum field section size that the sender is prepared to accept in bytes. See RFC 9113 section 6.5.2 for details. Default is 8192.

int

Maximum number of rapid resets(stream RST sent by client before any data have been sent by server). When reached within rapidResetCheckPeriod(), GOAWAY is sent to client and connection is closed. Default value is 50.

Duration

Period for counting rapid resets(stream RST sent by client before any data have been sent by server). Default value is PT10S.

See ISO_8601 Durations

RequestedUriDiscoveryContext

Requested URI discovery settings.

boolean

Whether to send error message over HTTP to client. Defaults to false, as exception message may contain internal information that could be used as an attack vector. Use with care and in cases where both server and clients are under your full control (such as for testing).

boolean

If set to false, any path is accepted (even containing illegal characters).