Get desktop application:
View/edit binary Protocol Buffers messages
HTTP generic body match configuration. List of text strings and hex strings to be located in HTTP body. All specified strings must be found in the HTTP body for positive match. The search may be limited to specified number of bytes from the body start. .. attention:: Searching for patterns in HTTP body is potentially cpu intensive. For each specified pattern, http body is scanned byte by byte to find a match. If multiple patterns are specified, the process is repeated for each pattern. If location of a pattern is known, ``bytes_limit`` should be specified to scan only part of the http body.
Used in:
Limits search to specified number of bytes - default zero (no limit - match entire captured buffer).
List of patterns to match.
Used in:
Text string to be located in HTTP body.
Sequence of bytes to be located in HTTP body.
HTTP headers match configuration.
Used in:
HTTP headers to match.
Match configuration. This is a recursive structure which allows complex nested match configurations to be built using various logical operators. [#next-free-field: 11]
Used in:
,A set that describes a logical OR. If any member of the set matches, the match configuration matches.
A set that describes a logical AND. If all members of the set match, the match configuration matches.
A negation match. The match configuration will match if the negated match condition matches.
The match configuration will always match.
HTTP request headers match configuration.
HTTP request trailers match configuration.
HTTP response headers match configuration.
HTTP response trailers match configuration.
HTTP request generic body match configuration.
HTTP response generic body match configuration.
A set of match configurations used for logical operations.
Used in:
The list of rules that make up the set.
A matcher, which may traverse a matching tree in order to result in a match action. During matching, the tree will be traversed until a match is found, or if no match is found the action specified by the most specific on_no_match will be evaluated. As an on_no_match might result in another matching tree being evaluated, this process might repeat several times until the final OnMatch (or no match) is decided. .. note:: Please use the syntactically equivalent :ref:`matching API <envoy_v3_api_msg_.xds.type.matcher.v3.Matcher>`
Used in:
,A linear list of matchers to evaluate.
A match tree to evaluate.
Optional OnMatch to use if the matcher failed. If specified, the OnMatch is used, and the matcher is considered to have matched. If not specified, the matcher is considered not to have matched.
A linear list of field matchers. The field matchers are evaluated in order, and the first match wins.
Used in:
A list of matchers. First match wins.
An individual matcher.
Used in:
Determines if the match succeeds.
What to do if the match succeeds.
Predicate to determine if a match is successful.
Used in:
,A single predicate to evaluate.
A list of predicates to be OR-ed together.
A list of predicates to be AND-ed together.
The invert of a predicate
A list of two or more matchers. Used to allow using a list within a oneof.
Used in:
Predicate for a single input field.
Used in:
Protocol-specific specification of input field to match on. [#extension-category: envoy.matching.common_inputs]
Built-in string matcher.
Extension for custom matching logic. [#extension-category: envoy.matching.input_matchers]
Used in:
Protocol-specific specification of input field to match on.
Exact or prefix match maps in which to look up the input value. If the lookup succeeds, the match is considered successful, and the corresponding OnMatch is used.
Longest matching prefix wins.
Extension for custom matching logic.
A map of configured matchers. Used to allow using a map within a oneof.
Used in:
What to do if a match is successful.
Used in:
, ,Nested matcher to evaluate. If the nested matcher does not match and does not specify on_no_match, then this matcher is considered not to have matched, even if a predicate at this level or above returned true.
Protocol-specific action to take.