We normally recommend using a proxy that supports HTTP/2 to the backend, like nghttpx and derivatives (Enjoy, Istio). If that's not possible, then the solutions tend to involve something that looks like grpc-web.
If the proxy you are already using supports HTTP/1.1 trailers, it should be possible to use nghttpx to up-convert back to HTTP/2, but I've not tried that out. On Thu, Aug 31, 2017 at 7:11 AM, <[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/ms > gid/grpc-io/997fd992-dd4e-40d9-bb72-c4f61d0eebbe%40googlegroups.com > <https://groups.google.com/d/msgid/grpc-io/997fd992-dd4e-40d9-bb72-c4f61d0eebbe%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CA%2B4M1oOUXCmcz4dhnhmVDCWzbBcX%2B-OUhS%2Bu8T4aCWD%2B_kuW6w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
