Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
5.1
-
None
Description
I originally reported this to the Jetty project but they have identified that the problem is in HttpCore's AbstractH2StreamMultiplexer. Jetty 10 has added support for SETTINGS_ENABLE_CONNECT_PROTOCOL. When consuming the settings frame, AbstractH2StreamMultiplexer consumes the code but, as it has no H2Param for it, it does not consume the value. This partial consumption results in an failure later on.
The problem can be reproduced using this sample project.