HTTP2 Client doesn't work/DefaultChannelPipeline wrongly configure for HTTP2 about reactor-netty

[violetagg]

@kgonia I'm closing this as a duplicate to #3080

[violetagg]

@kgonia Please check this comment #3080 (comment)
Also the presented logs definitely indicate HTTP/2 processing:

For example:

14:26:31.928 [reactor-http-nio-2] DEBUG reactor.netty.http.client.h2 - [id: 0x4eda8039, L:/192.168.1.155:60830 - R:api.binance.com/18.244.93.2:443] INBOUND HEADERS: streamId=3 headers=DefaultHttp2Headers[:status: 200, content-type: application/json;charset=UTF-8, content-length: 2254, date: Sun, 24 Mar 2024 13:26:32 GMT, server: nginx, vary: Accept-Encoding, x-mbx-uuid: 207b09f5-6713-466b-8fe2-3139efdde31c, x-mbx-used-weight: 20, x-mbx-used-weight-1m: 20, strict-transport-security: max-age=31536000; includeSubdomains, x-frame-options: SAMEORIGIN, x-xss-protection: 1; mode=block, x-content-type-options: nosniff, content-security-policy: default-src 'self', x-content-security-policy: default-src 'self', x-webkit-csp: default-src 'self', cache-control: no-cache, no-store, must-revalidate, pragma: no-cache, expires: 0, access-control-allow-origin: *, access-control-allow-methods: GET, HEAD, OPTIONS, x-cache: Miss from cloudfront, via: 1.1 e72c603b74b2c0164af9caa73c5fcb4c.cloudfront.net (CloudFront), x-amz-cf-pop: WAW51-P3, x-amz-cf-id: Pm3z6UEnMaT9sYonxiCD2ToYMqQHoL1FOG7n-rrNFKfK1eai5NDXnw==] padding=0 endStream=false