Jetty version
9.4.x
Description
Apparently, Chrome sends a lot of PRIORITY frames even for simple-ish pages, causing jetty.http2.rateControl.maxEventsPerSecond=20 to be tripped quite frequently, which closes the connection and causes the failure of in-flight requests, which results in images/javascripts to not be downloaded with the consequent page rendering glitches.
The value should be probably be defaulted at 50.
Jetty version
9.4.x
Description
Apparently, Chrome sends a lot of
PRIORITYframes even for simple-ish pages, causingjetty.http2.rateControl.maxEventsPerSecond=20to be tripped quite frequently, which closes the connection and causes the failure of in-flight requests, which results in images/javascripts to not be downloaded with the consequent page rendering glitches.The value should be probably be defaulted at 50.