[grpc-io] [Help] use self-signed cert on Android

I am trying to make gRPC over TLS working on Android using a self-signed cert. The code is as following: InputStream testCA = new ByteArrayInputStream(CA.getBytes("UTF8")); > mChannel = ZnzGrpcChannelBuilder.build(mHost, mPort, null, true, testCA, > "alpn"); > GRPCDummyServerGrpc.GRPCDummyServer

[grpc-io] Why the trailer frame is needed for gRPC? Any luck on making it work with Amazon ALB?

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 t

[grpc-io] Why the trailer frame are required in gRPC? Any success on using gRPC with Amazon ALB?

We tested gRPC on ALB for the past week, we have found out following facts: ``` 1. HTTP2 will be translated 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 t

Re: [grpc-io] Re: Using gRPC on AWS

How to use ALB at Layer 3? it only supports HTTP/HTTPS? On Saturday, January 21, 2017 at 2:19:46 AM UTC+8, Louis Ryan wrote: > > Alternatively use ELB/ALB at Layer-3 but put your own HTTP2 compliant > proxy behind it (Envoy, nghttpx, Linkerd, Traefik, ...) > > I know Lyft does this in productio

[grpc-io] gRPC over TLS using AWS NLB?

We are trying to use public facing gRPC on AWS. We know that one solution is to use AWS ELB and do SSL offloading on ELB. But we are more inclined to use the new NLB which does not support SSL termination. Hence we have to manage the certificates on the backend servers. Is there a good practice

[grpc-io] question about keepalive

I just found out that keepalive has been implemented in the go server and Android SDK, but not on iOS, am I right with this? If so, now we can not use go server keepalive feature because iOS does not support this. Any plans to implement it in the near future? -- *Grab is hiring. Learn more at

Re: [grpc-io] Is gRPC golang server able to catch the client disconnecting event and do something accordingly?

On Tue, Jan 23, 2018 at 3:44 AM, 'yz' via grpc.io > wrote: > >> We are implementing authentication on gRPC Golang server. When a client >> connect to the server, it needs to send the token to the server to >> authenticate itself, and the server will save the a

[grpc-io] Re: Is there a way for gRPC server - Go server specifically, to close the the client stream/connection?

Thanks Menghan for the suggestion, but seems it does not fit our scenario well. I noticed that and the cred config is server-wise. What we want to achieve is to do the auth in an interceptor, so that it is configurable per endpoint on the server. On Thursday, January 25, 2018 at 3:17:18 AM U

[grpc-io] Re: Is there a way for gRPC server - Go server specifically, to close the the client stream/connection?

Another thing I want to mention is that the clients might not be as friendly as you think, which means that it will not behave as you expected. If the auth failed, the client do not have to "go away", they can still try to send more requests to the server for bad purposes. It will give the ap

[grpc-io] Re: Is there a way for gRPC server - Go server specifically, to close the the client stream/connection?

Thanks for your answer, but I do not get why auth has to be per-RPC. If the client connect to the server and has been authed for the first time, the server should know that the connection has been authenticated, and there is no need to authenticate this RPC again. Actually, I think it will be mu

[grpc-io] Is gRPC golang server able to catch the client disconnecting event and do something accordingly?

We are implementing authentication on gRPC Golang server. When a client connect to the server, it needs to send the token to the server to authenticate itself, and the server will save the auth info. When the client disconnect, the server should remove the auth info. But I could not find a way

Re: [grpc-io] (golang) Detecting a dead client

My concern is that if the client connection is closed, no matter gracefully or not, the application layer might need to do some cleaning according to the event, e.g., to remove authentication information from the server. Haven't find a way to do that. On Thursday, October 29, 2015 at 1:56:11 AM

[grpc-io] Is there a way for gRPC server - Go server specifically, to close the the client stream/connection?

I am trying to implement some auth mechanism on go gRPC server. When the auth failed, ideally, the driver should be able to close the client connection. But seems that the ServerStream does not offer an interface to do that. Is it possible to do it in golang? -- *Grab is hiring. Learn more at

[grpc-io] Re: What is the minimum android/iOS version that gRPC support?

Thanks for your detailed answer on Android, Eric. Need to know the answer on iOS too, so we can make a decision whether to use it on our App. On Wednesday, January 17, 2018 at 12:50:31 PM UTC+8, yz wrote: > > I did not find it on the gRPC website. Does anyone have a clue? > -- *Grab is hiring.

[grpc-io] What is the minimum android/iOS version that gRPC support?

I did not find it on the gRPC website. Does anyone have a clue? -- *Grab is hiring. Learn more at **https://grab.careers * By communicating with Grab Inc and/or its subsidiaries, associate companies and jointly controlled entities (“Grab Group”), you are deemed to have