package envoy.config.filter.network.dubbo_proxy.v2alpha1
Get desktop application:
View/edit binary Protocol Buffers messages
message
dubbo_proxy.proto:59DubboFilter configures a Dubbo filter.
Used in:
string name = 1
The name of the filter to instantiate. The name must match a supported filter.
optional config = 2
Filter specific configuration which depends on the filter being instantiated. See the supported filters for further documentation.
message
dubbo_proxy.proto:38[#next-free-field: 6]
string stat_prefix = 1
The human readable prefix to use when emitting statistics.
ProtocolType protocol_type = 2
Configure the protocol used.
SerializationType serialization_type = 3
Configure the serialization protocol used.
repeated route_config = 4
The route table for the connection manager is static and is specified in this property.
repeated dubbo_filters = 5
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.
message
route.proto:77Used in:
optional name = 1
The name of the method.
map<uint32, > params_match = 2
Method parameter definition. The key is the parameter index, starting from 0. The value is the parameter matching type.
message
route.proto:79The parameter matching type.
Used in:
oneof parameter_match_specifier
string exact_match = 3
If specified, header match will be performed based on the value of the header.
range_match = 4
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"
Dubbo Protocol types supported by Envoy.
Used in:
Dubbo = 0
the default protocol.
message
route.proto:43Used in:
optional match = 1
Route matching parameters.
optional route = 2
Route request to some upstream cluster.
message
route.proto:62Used in:
oneof cluster_specifier
string cluster = 1
Indicates the upstream cluster to which the request should be routed.
weighted_clusters = 2
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.
message
route.proto:25[#next-free-field: 6]
Used in:
string name = 1
The name of the route configuration. Reserved for future use in asynchronous route discovery.
string interface = 2
The interface name of the service.
string group = 3
Which group does the interface belong to.
string version = 4
The version number of the interface.
repeated routes = 5
The list of routes that will be matched, in order, against incoming requests. The first route that matches will be used.
message
route.proto:51Used in:
optional method = 1
Method level routing matching.
repeated headers = 2
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:
Hessian2 = 0
the default serialization protocol.