Header mutation filter configuration (proto)

This extension has the qualified name envoy.filters.http.header_mutation


This extension is functional but has not had substantial production burn time, use only with this caveat.

This extension has an unknown security posture and should only be used in deployments where both the downstream and upstream are trusted.


This extension extends and can be used with the following extension categories:

This extension must be configured with one of the following type URLs:


[extensions.filters.http.header_mutation.v3.Mutations proto]

  "request_mutations": [],
  "response_mutations": []

(repeated config.common.mutation_rules.v3.HeaderMutation) The request mutations are applied before the request is forwarded to the upstream cluster.


(repeated config.common.mutation_rules.v3.HeaderMutation) The response mutations are applied before the response is sent to the downstream client.


[extensions.filters.http.header_mutation.v3.HeaderMutationPerRoute proto]

Per route configuration for the header mutation filter.

  "mutations": {...}



[extensions.filters.http.header_mutation.v3.HeaderMutation proto]

Configuration for the header mutation filter. The mutation rules in the filter configuration will always be applied first and then the per-route mutation rules, if both are specified.

  "mutations": {...},
  "most_specific_header_mutations_wins": ...



(bool) If per route HeaderMutationPerRoute config is configured at multiple route levels, header mutations at all specified levels are evaluated. By default, the order is from most specific (i.e. route entry level) to least specific (i.e. route configuration level). Later header mutations may override earlier mutations.

This order can be reversed by setting this field to true. In other words, most specific level mutation is evaluated last.