Get desktop application:
View/edit binary Protocol Buffers messages
The list of rules to apply to requests.
Used in:
field name to log
field id to match
next node of the field selector
[#next-free-field: 6]
Used in:
The namespace — if this is empty, the filter's namespace will be used.
The key to use within the namespace.
The value to pair with the given key. When used for on_present case, if value is non-empty it'll be used instead of the field value. If both are empty, the field value is used as-is. When used for on_missing case, a non-empty value must be provided.
If present, the header's value will be matched and substituted with this. If there is no match or substitution, the field value is used as-is. This is only used for on_present.
The value's type — defaults to string.
A Rule defines what metadata to apply when a field is present or missing. [#next-free-field: 6]
Used in:
If specified, the route must exactly match the request method name. As a special case, an empty string matches any request method name.
If specified, the route must have the service name as the request method name prefix. As a special case, an empty string matches any service name. Only relevant when service multiplexing.
Specifies that a match will be performed on the value of a field.
If the field is present, apply this metadata KeyValuePair.
If the field is missing, apply this metadata KeyValuePair. The value in the KeyValuePair must be set, since it'll be used in lieu of the missing field value.
Used in: