nizarm 14e856ac72 Correctly handle client side http2 upgrades when Http2FrameCodec …(9495) (#9501) ... Motivation: In the release (4.1.37) we introduced Http2MultiplexHandler as a replacement of Http2MultiplexCodec. This did split the frame parsing from the multiplexing to allow a more flexible way to handle frames and to make the code cleaner. Unfortunally we did miss to special handle this in Http2ClientUpgradeCodec and so did not correctly add Http2MultiplexHandler to the pipeline before calling Http2FrameCodec.onHttpClientUpgrade(...). This did lead to the situation that we did not correctly receive the event on the Http2MultiplexHandler and so did not correctly created the Http2StreamChannel for the upgrade stream. Because of this we ended up with an NPE if a frame was dispatched to the upgrade stream later on. Modifications: - Correctly add Http2MultiplexHandler to the pipeline before calling Http2FrameCodec.onHttpClientUpgrade(...) Result: Fixes #9495.		2019-08-23 18:51:57 +02:00
..
src	Correctly handle client side http2 upgrades when Http2FrameCodec …(9495) (#9501)	2019-08-23 18:51:57 +02:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2019-08-13 17:16:42 +00:00