From: Philippe Antoine Date: Thu, 1 Sep 2022 11:47:16 +0000 (+0200) Subject: doc/http2: suricata.yaml max-streams parameter X-Git-Tag: suricata-7.0.0-beta1~239 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F7839%2Fhead;p=thirdparty%2Fsuricata.git doc/http2: suricata.yaml max-streams parameter Ticket: #4949 --- diff --git a/doc/userguide/configuration/suricata-yaml.rst b/doc/userguide/configuration/suricata-yaml.rst index e98a6d6034..831c59e558 100644 --- a/doc/userguide/configuration/suricata-yaml.rst +++ b/doc/userguide/configuration/suricata-yaml.rst @@ -1727,6 +1727,11 @@ An app-layer event `protocol.too_many_transactions` is triggered when this value The point of this parameter is to find a balance between the completeness of analysis and the resource consumption. +For HTTP2, this parameter is named `max-streams` as an HTTP2 stream will get translated +into one Suricata transaction. This configuration parameter is used whatever the +value of `SETTINGS_MAX_CONCURRENT_STREAMS` negotiated between a client and a server +in a specific flow is. + Engine Logging --------------