I don't think any implementation is providing that header at this point. That would also explain why it isn't defined for responses.
On Wed, Mar 22, 2017 at 1:15 PM, Martin G <[email protected]> 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/d8b35ca3-ee1a-4c92-aae1-c80d881ed184%40googlegroups.com > <https://groups.google.com/d/msgid/grpc-io/d8b35ca3-ee1a-4c92-aae1-c80d881ed184%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CA%2B4M1oO%3D8TK6ip_DhaMS4fB4q6ALk1ULPewe9UDXOay-DhAbwg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
