metadata "grpc-timeout" question

[Sumukh Shivaprakash]

I have noticed that the client timeout that is passed in the rpc call is propagated to the server using the above metadata.

In c++, when I get the call context and query the deadline(), I am guessing it provides the same by using the value from the above header? 

Additionally, I am using grpc transcoding from REST via Envoy. If I set the same header in a REST request from a HTTP 1.1 client, can I get assume that the server will behave similar wrt the deadline aspect when compared to a native grpc client call?

Thanks,

Sumukh

[stanle...@google.com]

Yes Envoy should be relaying the grpc-timeout header to the backend and should have the same sematics.

[Sumukh Shivaprakash]

Thank you.

I see a request id in the client which gets printed when grpc client gets an error from the server. How can we access this request id on the server?