We sort of have this situation, since we use Google App Engine, and its load balancer and URLFetch service only support HTTP/1.1. We used the PRPC implementation described here, which is a mapping of the simple unary gRPC requests to an HTTP/1.1 protocol: http://nodir.io/post/138899670556/prpc. We used the Go implementation from the Chrome tools repository, and wrote our own client and server, which were relatively simple but absolutely do not support all of gRPC's features.
The "better" approach might be to look at the grpc-web work, and possibly just run the grpcwebproxy. See: https://github.com/improbable-eng/grpc-web I think that will also have the problem that if your clients aren't Go or Javascript, you will need to implement the protocol yourself. Good luck and hope this helps, Evan On Thursday, August 31, 2017 at 10:11:33 AM UTC-4, [email protected] wrote: > > What are common solutions getting gRPC app running when there is a > requirement to run through a some sort of proxy which does not support > HTTP/2 toward origin, rather towards client side. > > > Were you people got this kind of setup done somehow? > > > The setup via proxy would create a flow similar to this: > > > Client <--- HTTP/2 ---> Proxy <--- HTTP/1.1 ---> gRPC Server. > > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/23035b75-99e0-443d-8960-08f9e6c6e89a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
