Package io.envoyproxy.envoy.extensions.filters.network.dubbo_proxy.v3

Interface MethodMatch.ParameterMatchSpecifierOrBuilder

All Superinterfaces:
com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder
All Known Implementing Classes:
MethodMatch.ParameterMatchSpecifier, MethodMatch.ParameterMatchSpecifier.Builder
Enclosing class:
MethodMatch
public static interface MethodMatch.ParameterMatchSpecifierOrBuilder extends com.google.protobuf.MessageOrBuilder

  • Method Summary

    Modifier and Type
    Method
    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
    hasExactMatch()
    If specified, header match will be performed based on the value of the header.
    boolean
    hasRangeMatch()
    If specified, header match will be performed based on range.

    Methods inherited from interface com.google.protobuf.MessageLiteOrBuilder

    isInitialized

    Methods inherited from interface com.google.protobuf.MessageOrBuilder

    findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof

  • Method Details

    • hasExactMatch

      boolean hasExactMatch()
       If specified, header match will be performed based on the value of the header.
      string exact_match = 3;
      Returns:
      Whether the exactMatch field is set.

    • getExactMatch

      String getExactMatch()
       If specified, header match will be performed based on the value of the header.
      string exact_match = 3;
      Returns:
      The exactMatch.

    • getExactMatchBytes

      com.google.protobuf.ByteString getExactMatchBytes()
       If specified, header match will be performed based on the value of the header.
      string exact_match = 3;
      Returns:
      The bytes for exactMatch.

    • hasRangeMatch

      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;
      Returns:
      Whether the rangeMatch field is set.

    • getRangeMatch

      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;
      Returns:
      The rangeMatch.

    • getRangeMatchOrBuilder

      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;

    • getParameterMatchSpecifierCase

      MethodMatch.ParameterMatchSpecifier.ParameterMatchSpecifierCase getParameterMatchSpecifierCase()