public static interface MethodMatch.ParameterMatchSpecifierOrBuilder
extends com.google.protobuf.MessageOrBuilder
| Modifier and Type | Method and Description |
|---|---|
String |
getExactMatch()
If specified, header match will be performed based on the value of the header.
|
com.google.protobuf.ByteString |
getExactMatchBytes()
If specified, header match will be performed based on the value of the header.
|
MethodMatch.ParameterMatchSpecifier.ParameterMatchSpecifierCase |
getParameterMatchSpecifierCase() |
Int64Range |
getRangeMatch()
If specified, header match will be performed based on range.
|
Int64RangeOrBuilder |
getRangeMatchOrBuilder()
If specified, header match will be performed based on range.
|
boolean |
hasRangeMatch()
If specified, header match will be performed based on range.
|
findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneofString getExactMatch()
If specified, header match will be performed based on the value of the header.
string exact_match = 3;com.google.protobuf.ByteString getExactMatchBytes()
If specified, header match will be performed based on the value of the header.
string exact_match = 3;boolean hasRangeMatch()
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"
.envoy.type.v3.Int64Range range_match = 4;Int64Range getRangeMatch()
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"
.envoy.type.v3.Int64Range range_match = 4;Int64RangeOrBuilder getRangeMatchOrBuilder()
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"
.envoy.type.v3.Int64Range range_match = 4;MethodMatch.ParameterMatchSpecifier.ParameterMatchSpecifierCase getParameterMatchSpecifierCase()
Copyright © 2018–2021 The Envoy Project. All rights reserved.