From: Remi Gacogne Date: Mon, 6 Sep 2021 15:44:34 +0000 (+0200) Subject: dnsdist: The number of concurrent streams is hardcoded in libh2o X-Git-Tag: dnsdist-1.7.0-alpha1~23^2~12 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=8960ccec7f349d9d971bc218074a1ba3c3b20d07;p=thirdparty%2Fpdns.git dnsdist: The number of concurrent streams is hardcoded in libh2o --- diff --git a/pdns/dnsdistdist/doh.cc b/pdns/dnsdistdist/doh.cc index 4441fea264..e90077db4e 100644 --- a/pdns/dnsdistdist/doh.cc +++ b/pdns/dnsdistdist/doh.cc @@ -201,7 +201,13 @@ struct DOHServerConfig h2o_config_init(&h2o_config); h2o_config.http2.idle_timeout = idleTimeout * 1000; - // perhaps we should make h2o_config.http2.max_concurrent_requests_per_connection configurable (default is 100) + /* if you came here for a way to make the number of concurrent streams (concurrent requests per connection) + configurable, or even just bigger, I have bad news for you. + h2o_config.http2.max_concurrent_requests_per_connection (default of 100) is capped by + H2O_HTTP2_SETTINGS_HOST.max_concurrent_streams which is not configurable. Even if decided to change the + hard-coded value, libh2o's author warns that there might be parts of the code where the stream ID is stored + in 8 bits, making 256 a hard value: https://github.com/h2o/h2o/issues/805 + */ } DOHServerConfig(const DOHServerConfig&) = delete; DOHServerConfig& operator=(const DOHServerConfig&) = delete;