From daea3904e5aab6a4ad4a17c6bf3b18df8265ee4e Mon Sep 17 00:00:00 2001 From: "data-plane-api(Azure Pipelines)" Date: Tue, 25 Apr 2023 15:15:03 +0000 Subject: [PATCH] [CER] Traverse per route filter hierarchy till match is found. (#26767) * [CER] Traverse per route filter hierarchy till match is found. Mirrored from https://github.com/envoyproxy/envoy @ f63220bdeda9336ce54584e044141eb963d3cb27 --- .../filters/http/custom_response/v3/custom_response.proto | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/envoy/extensions/filters/http/custom_response/v3/custom_response.proto b/envoy/extensions/filters/http/custom_response/v3/custom_response.proto index 0c9d2a83..8f2c1c2b 100644 --- a/envoy/extensions/filters/http/custom_response/v3/custom_response.proto +++ b/envoy/extensions/filters/http/custom_response/v3/custom_response.proto @@ -21,7 +21,8 @@ option (xds.annotations.v3.file_status).work_in_progress = true; // The filter configuration is a collection of custom response // policies in a matcher tree. The configuration can be defined at the filter, -// virtual host or route level. The most specific configuration will apply. +// virtual host or route level. The response will be matched against the most +// specific to the least specific config, till a match is found. message CustomResponse { // Matcher to match against the original response to select a // :ref:`Custom Response Policy `