fix: Added additional jetty configuration options

[niloc132]

Deployments can now specify max h2 streams per connection and max request header size.

Set the configuration property http2.maxConcurrentStreams to the number of streams to allow for a given h2 connection.

Set the configuration property http.maxHeaderRequestSize to the max number of bytes to allow in HTTP request headers.

Fixes #5934
Fixes #6021

[devinrsmith]

Awesome. Please update the description / merge message with the config property names.

Do we know if there is a technical reason why jetty uses the "low" default of 128 for maxConcurrentStreams? We may want to consider setting a higher value by default, but happy to consider that separately.

[niloc132]

Do we know if there is a technical reason why jetty uses the "low" default of 128 for maxConcurrentStreams? We may want to consider setting a higher value by default, but happy to consider that separately.

jetty/jetty.project@5073ba4 is this commit where this was changed from -1 to 128, there isn't a lot of specific detail there.

The http2 spec itself says this should be not less than 100 - I suspect they just took a power of two higher than 100.

SETTINGS_MAX_CONCURRENT_STREAMS (0x3):

Indicates the maximum number of concurrent streams that the sender will allow. This limit is directional: it applies to the number of streams that the sender permits the receiver to create. Initially, there is no limit to this value. It is recommended that this value be no smaller than 100, so as to not unnecessarily limit parallelism.