gRPC Uses the trailer frame to send the status code, and is required. Any HTTP2/HTTP1.1 translation will need a mechanism to include the status code in the trailer.
On Thursday, March 15, 2018 at 8:08:37 AM UTC-7, yz wrote: > > We tested gRPC on ALB for the past week, we have found out following facts: > ``` > 1. ALB will translate HTTP2 to HTTP 1.1, with the protobuf translated into > chunked-encoding request body. And this body can be decoded on the upstream > server; > 2. ALB end the stream with a data frame without adding a trailer header > frame, which is the gRPC client expecting. So the Go client library will > just throw an error. > ``` > From rfc7540, the trailer frame is not required, but it seems that the > gRPC client requires it? > If so, is there a workaround for 2? > > Thank you very much! > -- 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/22b6d0f6-36ec-4cac-ab9e-fd57cf7bda8f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
