From 3fb46a52ed2841003a3ca1a4db61087be7b0d248 Mon Sep 17 00:00:00 2001 From: "data-plane-api(Azure Pipelines)" Date: Mon, 13 Feb 2023 23:08:44 +0000 Subject: [PATCH] Http input matcher on query parameters (#24627) Risk Level: Medium Testing: Unit test that verifies the documented behavior is correct Docs Changes: API documentation added Release Notes: N/A Platform Specific Features: N/A Signed-off-by: Adrien Guinet Mirrored from https://github.com/envoyproxy/envoy @ c7c462fa4c10b7a71edd57ab2029619e752f4b2b --- envoy/type/matcher/v3/http_inputs.proto | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/envoy/type/matcher/v3/http_inputs.proto b/envoy/type/matcher/v3/http_inputs.proto index 27e29bf1..c90199eb 100644 --- a/envoy/type/matcher/v3/http_inputs.proto +++ b/envoy/type/matcher/v3/http_inputs.proto @@ -60,3 +60,12 @@ message HttpResponseTrailerMatchInput { string header_name = 1 [(validate.rules).string = {well_known_regex: HTTP_HEADER_NAME strict: false}]; } + +// Match input indicates that matching should be done on a specific query parameter. +// The resulting input string will be the first query parameter for the value +// 'query_param'. +// [#extension: envoy.matching.inputs.query_params] +message HttpRequestQueryParamMatchInput { + // The query parameter to match on. + string query_param = 1 [(validate.rules).string = {min_len: 1}]; +}