Right now the tonic_web layer requires that the upstream service returns a http::Response<BoxBody> and it only accepts http::Request<hyper::Body>. It could be made generic over the request/response body so it could be used in more contexts—for example you could implement the tonic-web layer as a reverse proxy.
Feature Request
Right now the tonic_web layer requires that the upstream service returns a
http::Response<BoxBody>
and it only acceptshttp::Request<hyper::Body>
. It could be made generic over the request/response body so it could be used in more contexts—for example you could implement the tonic-web layer as a reverse proxy.Motivation
I want to proxy a Python gRPC service with tonic-web. The lack of flexibility means I can't just stick tonic-web in front of a
hyper::Client
to proxy the upstream.