FWIW, the response can only really include the header in the beginning (i.e. Server Headers) and not the end (i.e. trailers). If you want to open an issue on Github it can be prioritized. That said, I don't know of any use cases for it. Most clients/servers either know the type of response to expect, or don't care and treat them as opaque bytes.
On Wednesday, March 22, 2017 at 1:15:58 PM UTC-7, Martin G wrote: > > Hello, > > According to the wire specification ( > http://www.grpc.io/docs/guides/wire.html) the request can carry an > optional Message-Type in the headers which indicates the fully qualified > proto name > of the message in the payload. I am using grpc-java and it doesn't seem to > send this header. Is there a way to enable it? Also, is it intentional that > the response can't carry this header? > I think it would be useful for debugging purposes when the response could > also carry this header. > > Regards > -- 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/f24dd2a1-7195-457d-aad6-a74e1f0bab9b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
