Get desktop application:
View/edit binary Protocol Buffers messages
Used to match request host of the generic downstream request. Only applicable if a host provided by the application protocol. This is same with the ServiceMatchInput and this should be preferred over ServiceMatchInput.
(message has no fields)
Used to match an arbitrary key-value pair for headers, trailers or properties.
Used in:
The key name to match on.
The key value pattern.
Used to match request method of the generic downstream request. Only applicable if a method provided by the application protocol.
(message has no fields)
Used to match request path of the generic downstream request. Only applicable if a path provided by the application protocol.
(message has no fields)
Used to match an arbitrary property of the generic downstream request. These properties are populated by the codecs of application protocols.
The property name to match on.
Used to match an whole generic downstream request.
(message has no fields)
Custom matcher to match on the generic downstream request. This is used to match multiple fields of the downstream request and avoid complex combinations of HostMatchInput, PathMatchInput, MethodMatchInput and PropertyMatchInput.
Optional host pattern to match on. If not specified, any host will match.
Optional path pattern to match on. If not specified, any path will match.
Optional method pattern to match on. If not specified, any method will match.
Optional arbitrary properties to match on. If not specified, any properties will match. The key is the property name and the value is the property value to match on.
Used to match request service of the downstream request. Only applicable if a service provided by the application protocol. This is deprecated and should be replaced by HostMatchInput. This is kept for backward compatibility.
(message has no fields)