Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
Configuration source specifier. In case of ``api_config_source`` only aggregated ``api_type`` is supported.
The name of the multiple route configuration. This allows to use different multiple route configurations. Tells which multiple route configuration should be fetched from the configuration source. Leave unspecified is also valid and means the unnamed multiple route configuration.
DubboFilter configures a Dubbo filter.
Used in:
The name of the filter to instantiate. The name must match a supported filter.
Filter specific configuration which depends on the filter being instantiated. See the supported filters for further documentation.
[#next-free-field: 8]
The human readable prefix to use when emitting statistics.
Configure the protocol used.
Configure the serialization protocol used.
The route table for the connection manager is static and is specified in this property. .. note:: This field is deprecated. Please use ``drds`` or ``multiple_route_config`` first.
Use xDS to fetch the route configuration. It is invalid to define both ``route_config`` and ``drds``.
A list of individual Dubbo filters that make up the filter chain for requests made to the Dubbo proxy. Order matters as the filters are processed sequentially. For backwards compatibility, if no dubbo_filters are specified, a default Dubbo router filter (``envoy.filters.dubbo.router``) is used.
Used in:
The name of the method.
Method parameter definition. The key is the parameter index, starting from 0. The value is the parameter matching type.
The parameter matching type.
Used in:
If specified, header match will be performed based on the value of the header.
If specified, header match will be performed based on range. The rule will match if the request header value is within this range. The entire request header value must represent an integer in base 10 notation: consisting of an optional plus or minus sign followed by a sequence of digits. The rule will not match if the header value does not represent an integer. Match will fail for empty values, floating point numbers or if only a subsequence of the header value is an integer. Examples: * For range [-10,0), route will match for header value -1, but not for 0, "somestring", 10.9, "-1somestring"
Used in:
The name of the named route configurations. This name is used in asynchronous route discovery.
The route table of the dubbo connection manager.
Dubbo Protocol types supported by Envoy.
Used in:
the default protocol.
Used in:
Route matching parameters.
Route request to some upstream cluster.
Used in:
Indicates the upstream cluster to which the request should be routed.
Multiple upstream clusters can be specified for a given route. The request is routed to one of the upstream clusters based on weights assigned to each cluster. Currently ClusterWeight only supports the name and weight fields.
Optional endpoint metadata match criteria used by the subset load balancer. Only endpoints in the upstream cluster with metadata matching what is set in this field will be considered for load balancing. The filter name should be specified as ``envoy.lb``.
[#next-free-field: 6]
Used in:
,The name of the route configuration. Reserved for future use in asynchronous route discovery.
The interface name of the service. Wildcard interface are supported in the suffix or prefix form. e.g. ``*.methods.add`` will match ``com.dev.methods.add``, ``com.prod.methods.add``, etc. ``com.dev.methods.*`` will match ``com.dev.methods.add``, ``com.dev.methods.update``, etc. Special wildcard ``*`` matching any interface. .. note:: The wildcard will not match the empty string. e.g. ``*.methods.add`` will match ``com.dev.methods.add`` but not ``.methods.add``.
Which group does the interface belong to.
The version number of the interface.
The list of routes that will be matched, in order, against incoming requests. The first route that matches will be used.
Used in:
Method level routing matching.
Specifies a set of headers that the route should match on. The router will check the request’s headers against all the specified headers in the route config. A match will happen if all the headers in the route are present in the request with the same values (or based on presence if the value field is not in the config).
Dubbo Serialization types supported by Envoy.
Used in:
the default serialization protocol.