👾 Enable ALPN and support HTTP/1.1 in transport.rs

[Rnbsov]

Updated transport.rs to enable ALPN for protocol negotiation and support both HTTP/1.1 and HTTP/2.

• With a modern gRPC server: Uses HTTP/2 (faster, multiplexing, bidirectional streaming)
• With an HTTP/1.1-only server: Falls back to HTTP/1.1 automatically
• Backward compatible: Doesn't break existing HTTP/2 connections

closes: https://feedback.yaak.app/p/grpc-testing-over-http11

[gschier]

I'm not sure what this change does since gRPC only works over http/2. Can you add more detail on what this is doing, exactly?

[gschier]

Closing this for now, to keep things tidy, but can re-open if needed.

[Rnbsov]

nodeJs server plugins ecosystem doesn't yet support http/2

I'm using connectRpc and I can't test my api with yaak

https://connectrpc.com/docs/node/server-plugins

[Rnbsov]

@gschier more precisely, express and Next.js doesn't support http/2

https://connectrpc.com/docs/node/server-plugins#protocol-support-in-express

[gschier]

I still don't understand @Rnbsov. Did you test that this change actually lets you interact with a connectRPC API successfully?

The gRPC library that Yaak uses (tonic) ONLY supports the official http/2 gRPC protocol. If connectRPC is running over http/1.1 then it shouldn't be able to work.