Closed pomo-mondreganto closed 1 month ago
any progress?
Also will be useful in my use case, since I'm using pingora behind other proxy (ingress traefik) which supports h2c connections to services.
Also will be useful in my use case, since I'm using pingora behind other proxy (ingress traefik) which supports h2c connections to services.
pingora is better than ingress? how about use hyper?
Pingora "too customizable" for use as ingress.I don't want to recompile whole router to add a service or write my own ingress controller. Waiting for river for this.
Right now we are open to having support for the feature but haven't been able to prioritize it yet.
We've added support for server h2c in our latest sync, an example is here.
Switching protocols is todo, all downstream plaintext will go over H2 when this setting is enabled.
Downstream TLS -> Upstream plaintext doesn't need the h2c
server setting, you only need to specify the min and max peer version is h2.
What is the problem your feature solves, or the need it fulfills?
It's currently impossible to use this project as TLS termination edge proxy in front of a cluster of non-TLS gRPC services.
Describe the solution you'd like
Non-TLS gRPC is basically http/2 without tls, so it'd be convenient if pingora supported h2c for both upstream and downstream connections.
Describe alternatives you've considered
It's currently non-feasible to implement such proxying with pingora, as it entails writing h2c protocol parsing.
Additional context
Most oss proxies support this feature (e.g. envoy, nginx).