Support for End-to-End HTTP/2 (gRPC) for
Support for End-to-End HTTP/2 (gRPC) for Actor Container URLs
The Problem:
I am building a high-performance Rust Actor using gRPC (Tonic) for internal data ingestion.
The Load Balancer appears to downgrade the connection to HTTP/1.1 when communicating with the Actor container.
This causes standard gRPC servers (like tonic in Rust or grpc-go) to crash immediately with Protocol Errors (HTTP 464) because they require an HTTP/2 transport layer.
The Request:
Please add an option in the actor.json or Input configuration to enable End-to-End HTTP/2 (or gRPC mode) for the Container Web Server.
The Problem:
I am building a high-performance Rust Actor using gRPC (Tonic) for internal data ingestion.
The Load Balancer appears to downgrade the connection to HTTP/1.1 when communicating with the Actor container.
This causes standard gRPC servers (like tonic in Rust or grpc-go) to crash immediately with Protocol Errors (HTTP 464) because they require an HTTP/2 transport layer.
The Request:
Please add an option in the actor.json or Input configuration to enable End-to-End HTTP/2 (or gRPC mode) for the Container Web Server.
