Yes Envoy should be relaying the grpc-timeout header to the backend and should have the same sematics.
On Wednesday, March 25, 2020 at 4:13:41 PM UTC-7 [email protected] wrote: > 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 > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/f304e7f4-d77e-4bb2-bcac-a8dad9a2731e%40googlegroups.com.
