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 <adrien@reblaze.com>

Mirrored from https://github.com/envoyproxy/envoy @ c7c462fa4c10b7a71edd57ab2029619e752f4b2b
pull/626/head
data-plane-api(Azure Pipelines) 2 years ago
parent a4c435c675
commit 3fb46a52ed
  1. 9
      envoy/type/matcher/v3/http_inputs.proto

@ -60,3 +60,12 @@ message HttpResponseTrailerMatchInput {
string header_name = 1 string header_name = 1
[(validate.rules).string = {well_known_regex: HTTP_HEADER_NAME strict: false}]; [(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}];
}

Loading…
Cancel
Save