Setting :authority headers returns Metadata key ":authority" contains illegal characters

[mikhainin]

Hi there, The issue claimed to be resolved but it still isn't possible to use it. Same thing happens on MacOS, bloomrpc version 1.5.2 (1.5.2.240) (and on master branch)

[palcalde]

Hi! is this still a problem? I'm unable to add the :authority header into metadata and I needed to route my requests to the GRPC server.

I've tried with backslash to escape but it doesn't work either

[smnbbrv]

This is actually an issue, because it does not allow to call grpc servers behind proxies...

E.g. Gloo explicitly points to authority pseudo-header in their documentation.

https://docs.solo.io/gloo-edge/latest/guides/traffic_management/destination_types/grpc/

[mmohaveri]

I'm using version 1.5.2 and have the exact same issue when connecting to an API behind a proxy (gloo edge proxy)

[levischuckeats]

I also hit this issue.

[mccauli]

+1, same issue

[codingknees]

+1 same issue

[kseniacold]

This probably would not work with metadata at all - based on this comment: in grpc/node:

You can't directly set the :authority header because gRPC internally handles HTTP2 protocol pseudo-headers. You can modify the authority for an entire client by setting the option "grpc.default_authority" at client construction,

Looks it should be initialized with the client creation.