On Sat, Sep 3, 2016 at 6:16 PM, <[email protected]> wrote: > 1) With plaintext GRPC on the backend, ALB fails because it tries to > upgrade from HTTP/1.1 which grpc-java does not support. >
Yep. It isn't supported. The first request being HTTP/1 makes things... weird. For those following along at home, this issue <https://github.com/grpc/grpc-java/issues/2228> is now tracking plaintext upgrade. > 2) With TLS GRPC on the backend, ALB seems to fail for the same reason > (TLS/ALPN negotiation succeeds but protocol is not HTTP/2). > That sounds like it doesn't support HTTP/2. I wouldn't be surprised if it didn't support HTTP/2 to the backend. Clients could be HTTP/2, but then it would convert it to HTTP/1.1. This is the same state as with Google Cloud Load Balancer and nginx. Amazon's blog post <https://aws.amazon.com/blogs/aws/new-aws-application-load-balancer/> also doesn't make it clear. Since TLS doesn't work, I'd assume it doesn't support plaintext as well; if you stand up a test plaintext HTTP/1.1 server you won't see an "Upgrade: h2c" header. -- 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%2B4M1oMjebZXd55w5ttG5_OMYvsfdB%2Btd6vgA6FUasfubCvBGQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
