I use the HTTP2 ":authority" header for routing gRPC requests from a nginx gateway to various gRPC servers, along the lines of https://github.com/grpc/grpc/issues/14900
So far I have not used any credentials but I wish to do so soon. However, I notice that in the documentation of the DialOptions.WithAuthority() call, there is the following statement: // :authority pseudo-header. This value only works with WithInsecure and has no // effect if TransportCredentials are present. // WithAuthority returns a DialOption that specifies the value to be used as the I am probably missing something obvious here but what is the relation between the ":authority" header and the transport credentials? Is my routing somehow incompatible with the use of proper channel credentials? Cheers, Sander -- 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/85b1974e-f961-4c65-9601-77ea4c2401d0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
