Paul Ogilby
Paul Ogilby
https://github.com/envoyproxy/envoy/issues/21910 is also relevant here I think.
@abeyad wdyt from an API view?
Assigning to Greg for non-google senior maintainer + socket expertise. Greg, if you are overloaded, please let me know and I can assign to someone else. /assign @ggreenway
You can also use the `response_headers_to_remove` field on Route Configuration: https://github.com/envoyproxy/envoy/blob/1e68b78b9f26e4d93b01faae257158b3ec54798a/api/envoy/config/route/v3/route.proto#L66
yes; I believe that gRPC will put the ORCA metrics in trailers generally. and the `response_headers_to_remove` only removes response headers, not response trailers.
yurp, that API doesn't exist today. would be a welcome addition if you'd like to open a PR?
if we're doing `response_trailers_to_remove` we might as well do all the other `*_trailers_to_*` API fields. @envoyproxy/api-shepherds sound reasonable?
On the response path the router filter goes first: Request path: Filter A --> Fitler B --> Router --> upstream Response path: Filter A
I think you need request trailer mutations and response trailers mutations (separately) ``` repeated config.common.mutation_rules.v3.HeaderMutation response_trailer_mutations = 4; repeated config.common.mutation_rules.v3.HeaderMutation request_trailer_mutations = 5; ``` added to https://github.com/envoyproxy/envoy/blob/f2a1a61901d7b7ed3a7ced176fd0540859ef5d9c/api/envoy/extensions/filters/http/header_mutation/v3/header_mutation.proto#L19. Definitely these can...