You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
setting :authority in initial_metadata creates two :authority values #199
gRPC's initial metadata is supplemental metadata that's encoded as HTTP headers, but those shouldn't be used as HTTP headers, and you cannot use it to override HTTP headers.
Having said that, it looks that Envoy implementation has a bug that allows setting two :authority values, which it concatenates.
Also, answering your original question, I think you should be able to configure :authority in upstream-cluster's configuration in Envoy using the Endpoint's hostname field.
I've tried to see if in the cluster definition under load_assignment setting hostname in endpoint as you mentioned, but it doesn't seem to use that value in the authority header
Activity
PiotrSikora commentedon Jun 8, 2023
gRPC's initial metadata is supplemental metadata that's encoded as HTTP headers, but those shouldn't be used as HTTP headers, and you cannot use it to override HTTP headers.
Having said that, it looks that Envoy implementation has a bug that allows setting two
:authorityvalues, which it concatenates.Could you open issue there? Thanks! cc @mpwarres
PiotrSikora commentedon Jun 9, 2023
Also, answering your original question, I think you should be able to configure
:authorityinupstream-cluster'sconfiguration in Envoy using the Endpoint'shostnamefield.collinlee commentedon Jun 13, 2023
I've tried to see if in the cluster definition under load_assignment setting hostname in endpoint as you mentioned, but it doesn't seem to use that value in the authority header