From 78814130c7427236bf222824f03d813be00f9694 Mon Sep 17 00:00:00 2001 From: Tianyu <72890320+tyxia@users.noreply.github.com> Date: Fri, 5 Jan 2024 10:22:56 -0500 Subject: [PATCH] route: Clarify the `most_specific_header_mutations_wins` (#31658) Signed-off-by: tyxia --- api/envoy/config/route/v3/route.proto | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/api/envoy/config/route/v3/route.proto b/api/envoy/config/route/v3/route.proto index 0d5867d00714..c4d507d22b01 100644 --- a/api/envoy/config/route/v3/route.proto +++ b/api/envoy/config/route/v3/route.proto @@ -82,14 +82,11 @@ message RouteConfiguration { (validate.rules).repeated = {items {string {well_known_regex: HTTP_HEADER_NAME strict: false}}} ]; - // By default, headers that should be added/removed are evaluated from most to least specific: - // - // * route level - // * virtual host level - // * connection manager level - // - // To allow setting overrides at the route or virtual host level, this order can be reversed - // by setting this option to true. Defaults to false. + // Headers mutations at all levels are evaluated, if specified. 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. // bool most_specific_header_mutations_wins = 10;