Class RouteMatch.Builder
java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<RouteMatch.Builder>
com.google.protobuf.GeneratedMessage.Builder<RouteMatch.Builder>
io.envoyproxy.envoy.config.route.v3.RouteMatch.Builder
- All Implemented Interfaces:
com.google.protobuf.Message.Builder
,com.google.protobuf.MessageLite.Builder
,com.google.protobuf.MessageLiteOrBuilder
,com.google.protobuf.MessageOrBuilder
,RouteMatchOrBuilder
,Cloneable
- Enclosing class:
RouteMatch
public static final class RouteMatch.Builder
extends com.google.protobuf.GeneratedMessage.Builder<RouteMatch.Builder>
implements RouteMatchOrBuilder
[#next-free-field: 16]Protobuf type
envoy.config.route.v3.RouteMatch
-
Field Summary
FieldsModifier and TypeFieldDescriptionprivate int
private com.google.protobuf.BoolValue
private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.BoolValue, com.google.protobuf.BoolValue.Builder, com.google.protobuf.BoolValueOrBuilder> private com.google.protobuf.SingleFieldBuilder
<RouteMatch.ConnectMatcher, RouteMatch.ConnectMatcher.Builder, RouteMatch.ConnectMatcherOrBuilder> private List
<MetadataMatcher> private com.google.protobuf.RepeatedFieldBuilder
<MetadataMatcher, MetadataMatcher.Builder, MetadataMatcherOrBuilder> private RouteMatch.GrpcRouteMatchOptions
private com.google.protobuf.SingleFieldBuilder
<RouteMatch.GrpcRouteMatchOptions, RouteMatch.GrpcRouteMatchOptions.Builder, RouteMatch.GrpcRouteMatchOptionsOrBuilder> private List
<HeaderMatcher> private com.google.protobuf.RepeatedFieldBuilder
<HeaderMatcher, HeaderMatcher.Builder, HeaderMatcherOrBuilder> private com.google.protobuf.SingleFieldBuilder
<TypedExtensionConfig, TypedExtensionConfig.Builder, TypedExtensionConfigOrBuilder> private Object
private int
private List
<QueryParameterMatcher> private com.google.protobuf.RepeatedFieldBuilder
<QueryParameterMatcher, QueryParameterMatcher.Builder, QueryParameterMatcherOrBuilder> private RuntimeFractionalPercent
private com.google.protobuf.SingleFieldBuilder
<RuntimeFractionalPercent, RuntimeFractionalPercent.Builder, RuntimeFractionalPercentOrBuilder> private com.google.protobuf.SingleFieldBuilder
<RegexMatcher, RegexMatcher.Builder, RegexMatcherOrBuilder> private com.google.protobuf.SingleFieldBuilder
<RouteMatch.TlsContextMatchOptions, RouteMatch.TlsContextMatchOptions.Builder, RouteMatch.TlsContextMatchOptionsOrBuilder> -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionaddAllDynamicMetadata
(Iterable<? extends MetadataMatcher> values) Specifies a set of dynamic metadata matchers on which the route should match.addAllHeaders
(Iterable<? extends HeaderMatcher> values) Specifies a set of headers that the route should match on.addAllQueryParameters
(Iterable<? extends QueryParameterMatcher> values) Specifies a set of URL query parameters on which the route should match.addDynamicMetadata
(int index, MetadataMatcher value) Specifies a set of dynamic metadata matchers on which the route should match.addDynamicMetadata
(int index, MetadataMatcher.Builder builderForValue) Specifies a set of dynamic metadata matchers on which the route should match.Specifies a set of dynamic metadata matchers on which the route should match.addDynamicMetadata
(MetadataMatcher.Builder builderForValue) Specifies a set of dynamic metadata matchers on which the route should match.Specifies a set of dynamic metadata matchers on which the route should match.addDynamicMetadataBuilder
(int index) Specifies a set of dynamic metadata matchers on which the route should match.addHeaders
(int index, HeaderMatcher value) Specifies a set of headers that the route should match on.addHeaders
(int index, HeaderMatcher.Builder builderForValue) Specifies a set of headers that the route should match on.addHeaders
(HeaderMatcher value) Specifies a set of headers that the route should match on.addHeaders
(HeaderMatcher.Builder builderForValue) Specifies a set of headers that the route should match on.Specifies a set of headers that the route should match on.addHeadersBuilder
(int index) Specifies a set of headers that the route should match on.addQueryParameters
(int index, QueryParameterMatcher value) Specifies a set of URL query parameters on which the route should match.addQueryParameters
(int index, QueryParameterMatcher.Builder builderForValue) Specifies a set of URL query parameters on which the route should match.Specifies a set of URL query parameters on which the route should match.addQueryParameters
(QueryParameterMatcher.Builder builderForValue) Specifies a set of URL query parameters on which the route should match.Specifies a set of URL query parameters on which the route should match.addQueryParametersBuilder
(int index) Specifies a set of URL query parameters on which the route should match.build()
private void
buildPartial0
(RouteMatch result) private void
buildPartialOneofs
(RouteMatch result) private void
buildPartialRepeatedFields
(RouteMatch result) clear()
Indicates that prefix/path matching should be case sensitive.If this is used as the matcher, the matcher will only match CONNECT or CONNECT-UDP requests.Specifies a set of dynamic metadata matchers on which the route should match.If specified, only gRPC requests will be matched.Specifies a set of headers that the route should match on.If specified, the route is an exact path rule meaning that the path must exactly match the ``:path`` header once the query string is removed.[#extension-category: envoy.path.match]If specified, the route is a path-separated prefix rule meaning that the ``:path`` header (without the query string) must either exactly match the ``path_separated_prefix`` or have it as a prefix, followed by ``/`` For example, ``/api/dev`` would match ``/api/dev``, ``/api/dev/``, ``/api/dev/v1``, and ``/api/dev?param=true`` but would not match ``/api/developer`` Expect the value to not contain ``?`` or ``#`` and not to end in ``/``If specified, the route is a prefix rule meaning that the prefix must match the beginning of the ``:path`` header.Specifies a set of URL query parameters on which the route should match.Indicates that the route should additionally match on a runtime key.If specified, the route is a regular expression rule meaning that the regex must match the ``:path`` header once the query string is removed.If specified, the client tls context will be matched against the defined match options.private void
private void
private void
com.google.protobuf.BoolValue
Indicates that prefix/path matching should be case sensitive.com.google.protobuf.BoolValue.Builder
Indicates that prefix/path matching should be case sensitive.com.google.protobuf.BoolValueOrBuilder
Indicates that prefix/path matching should be case sensitive.If this is used as the matcher, the matcher will only match CONNECT or CONNECT-UDP requests.If this is used as the matcher, the matcher will only match CONNECT or CONNECT-UDP requests.If this is used as the matcher, the matcher will only match CONNECT or CONNECT-UDP requests.static final com.google.protobuf.Descriptors.Descriptor
com.google.protobuf.Descriptors.Descriptor
getDynamicMetadata
(int index) Specifies a set of dynamic metadata matchers on which the route should match.getDynamicMetadataBuilder
(int index) Specifies a set of dynamic metadata matchers on which the route should match.Specifies a set of dynamic metadata matchers on which the route should match.int
Specifies a set of dynamic metadata matchers on which the route should match.Specifies a set of dynamic metadata matchers on which the route should match.getDynamicMetadataOrBuilder
(int index) Specifies a set of dynamic metadata matchers on which the route should match.List
<? extends MetadataMatcherOrBuilder> Specifies a set of dynamic metadata matchers on which the route should match.getGrpc()
If specified, only gRPC requests will be matched.If specified, only gRPC requests will be matched.If specified, only gRPC requests will be matched.getHeaders
(int index) Specifies a set of headers that the route should match on.getHeadersBuilder
(int index) Specifies a set of headers that the route should match on.Specifies a set of headers that the route should match on.int
Specifies a set of headers that the route should match on.Specifies a set of headers that the route should match on.getHeadersOrBuilder
(int index) Specifies a set of headers that the route should match on.List
<? extends HeaderMatcherOrBuilder> Specifies a set of headers that the route should match on.getPath()
If specified, the route is an exact path rule meaning that the path must exactly match the ``:path`` header once the query string is removed.com.google.protobuf.ByteString
If specified, the route is an exact path rule meaning that the path must exactly match the ``:path`` header once the query string is removed.[#extension-category: envoy.path.match][#extension-category: envoy.path.match][#extension-category: envoy.path.match]If specified, the route is a path-separated prefix rule meaning that the ``:path`` header (without the query string) must either exactly match the ``path_separated_prefix`` or have it as a prefix, followed by ``/`` For example, ``/api/dev`` would match ``/api/dev``, ``/api/dev/``, ``/api/dev/v1``, and ``/api/dev?param=true`` but would not match ``/api/developer`` Expect the value to not contain ``?`` or ``#`` and not to end in ``/``com.google.protobuf.ByteString
If specified, the route is a path-separated prefix rule meaning that the ``:path`` header (without the query string) must either exactly match the ``path_separated_prefix`` or have it as a prefix, followed by ``/`` For example, ``/api/dev`` would match ``/api/dev``, ``/api/dev/``, ``/api/dev/v1``, and ``/api/dev?param=true`` but would not match ``/api/developer`` Expect the value to not contain ``?`` or ``#`` and not to end in ``/``If specified, the route is a prefix rule meaning that the prefix must match the beginning of the ``:path`` header.com.google.protobuf.ByteString
If specified, the route is a prefix rule meaning that the prefix must match the beginning of the ``:path`` header.getQueryParameters
(int index) Specifies a set of URL query parameters on which the route should match.getQueryParametersBuilder
(int index) Specifies a set of URL query parameters on which the route should match.Specifies a set of URL query parameters on which the route should match.int
Specifies a set of URL query parameters on which the route should match.Specifies a set of URL query parameters on which the route should match.getQueryParametersOrBuilder
(int index) Specifies a set of URL query parameters on which the route should match.List
<? extends QueryParameterMatcherOrBuilder> Specifies a set of URL query parameters on which the route should match.Indicates that the route should additionally match on a runtime key.Indicates that the route should additionally match on a runtime key.Indicates that the route should additionally match on a runtime key.If specified, the route is a regular expression rule meaning that the regex must match the ``:path`` header once the query string is removed.If specified, the route is a regular expression rule meaning that the regex must match the ``:path`` header once the query string is removed.If specified, the route is a regular expression rule meaning that the regex must match the ``:path`` header once the query string is removed.If specified, the client tls context will be matched against the defined match options.If specified, the client tls context will be matched against the defined match options.If specified, the client tls context will be matched against the defined match options.boolean
Indicates that prefix/path matching should be case sensitive.boolean
If this is used as the matcher, the matcher will only match CONNECT or CONNECT-UDP requests.boolean
hasGrpc()
If specified, only gRPC requests will be matched.boolean
hasPath()
If specified, the route is an exact path rule meaning that the path must exactly match the ``:path`` header once the query string is removed.boolean
[#extension-category: envoy.path.match]boolean
If specified, the route is a path-separated prefix rule meaning that the ``:path`` header (without the query string) must either exactly match the ``path_separated_prefix`` or have it as a prefix, followed by ``/`` For example, ``/api/dev`` would match ``/api/dev``, ``/api/dev/``, ``/api/dev/v1``, and ``/api/dev?param=true`` but would not match ``/api/developer`` Expect the value to not contain ``?`` or ``#`` and not to end in ``/``boolean
If specified, the route is a prefix rule meaning that the prefix must match the beginning of the ``:path`` header.boolean
Indicates that the route should additionally match on a runtime key.boolean
If specified, the route is a regular expression rule meaning that the regex must match the ``:path`` header once the query string is removed.boolean
If specified, the client tls context will be matched against the defined match options.private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.BoolValue, com.google.protobuf.BoolValue.Builder, com.google.protobuf.BoolValueOrBuilder> Indicates that prefix/path matching should be case sensitive.private com.google.protobuf.SingleFieldBuilder
<RouteMatch.ConnectMatcher, RouteMatch.ConnectMatcher.Builder, RouteMatch.ConnectMatcherOrBuilder> If this is used as the matcher, the matcher will only match CONNECT or CONNECT-UDP requests.private com.google.protobuf.RepeatedFieldBuilder
<MetadataMatcher, MetadataMatcher.Builder, MetadataMatcherOrBuilder> protected com.google.protobuf.GeneratedMessage.FieldAccessorTable
private com.google.protobuf.SingleFieldBuilder
<RouteMatch.GrpcRouteMatchOptions, RouteMatch.GrpcRouteMatchOptions.Builder, RouteMatch.GrpcRouteMatchOptionsOrBuilder> If specified, only gRPC requests will be matched.private com.google.protobuf.RepeatedFieldBuilder
<HeaderMatcher, HeaderMatcher.Builder, HeaderMatcherOrBuilder> private com.google.protobuf.SingleFieldBuilder
<TypedExtensionConfig, TypedExtensionConfig.Builder, TypedExtensionConfigOrBuilder> [#extension-category: envoy.path.match]private com.google.protobuf.RepeatedFieldBuilder
<QueryParameterMatcher, QueryParameterMatcher.Builder, QueryParameterMatcherOrBuilder> private com.google.protobuf.SingleFieldBuilder
<RuntimeFractionalPercent, RuntimeFractionalPercent.Builder, RuntimeFractionalPercentOrBuilder> Indicates that the route should additionally match on a runtime key.private com.google.protobuf.SingleFieldBuilder
<RegexMatcher, RegexMatcher.Builder, RegexMatcherOrBuilder> If specified, the route is a regular expression rule meaning that the regex must match the ``:path`` header once the query string is removed.private com.google.protobuf.SingleFieldBuilder
<RouteMatch.TlsContextMatchOptions, RouteMatch.TlsContextMatchOptions.Builder, RouteMatch.TlsContextMatchOptionsOrBuilder> If specified, the client tls context will be matched against the defined match options.final boolean
private void
mergeCaseSensitive
(com.google.protobuf.BoolValue value) Indicates that prefix/path matching should be case sensitive.If this is used as the matcher, the matcher will only match CONNECT or CONNECT-UDP requests.mergeFrom
(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) mergeFrom
(com.google.protobuf.Message other) mergeFrom
(RouteMatch other) If specified, only gRPC requests will be matched.[#extension-category: envoy.path.match]Indicates that the route should additionally match on a runtime key.mergeSafeRegex
(RegexMatcher value) If specified, the route is a regular expression rule meaning that the regex must match the ``:path`` header once the query string is removed.If specified, the client tls context will be matched against the defined match options.removeDynamicMetadata
(int index) Specifies a set of dynamic metadata matchers on which the route should match.removeHeaders
(int index) Specifies a set of headers that the route should match on.removeQueryParameters
(int index) Specifies a set of URL query parameters on which the route should match.setCaseSensitive
(com.google.protobuf.BoolValue value) Indicates that prefix/path matching should be case sensitive.setCaseSensitive
(com.google.protobuf.BoolValue.Builder builderForValue) Indicates that prefix/path matching should be case sensitive.If this is used as the matcher, the matcher will only match CONNECT or CONNECT-UDP requests.setConnectMatcher
(RouteMatch.ConnectMatcher.Builder builderForValue) If this is used as the matcher, the matcher will only match CONNECT or CONNECT-UDP requests.setDynamicMetadata
(int index, MetadataMatcher value) Specifies a set of dynamic metadata matchers on which the route should match.setDynamicMetadata
(int index, MetadataMatcher.Builder builderForValue) Specifies a set of dynamic metadata matchers on which the route should match.If specified, only gRPC requests will be matched.setGrpc
(RouteMatch.GrpcRouteMatchOptions.Builder builderForValue) If specified, only gRPC requests will be matched.setHeaders
(int index, HeaderMatcher value) Specifies a set of headers that the route should match on.setHeaders
(int index, HeaderMatcher.Builder builderForValue) Specifies a set of headers that the route should match on.If specified, the route is an exact path rule meaning that the path must exactly match the ``:path`` header once the query string is removed.setPathBytes
(com.google.protobuf.ByteString value) If specified, the route is an exact path rule meaning that the path must exactly match the ``:path`` header once the query string is removed.[#extension-category: envoy.path.match]setPathMatchPolicy
(TypedExtensionConfig.Builder builderForValue) [#extension-category: envoy.path.match]setPathSeparatedPrefix
(String value) If specified, the route is a path-separated prefix rule meaning that the ``:path`` header (without the query string) must either exactly match the ``path_separated_prefix`` or have it as a prefix, followed by ``/`` For example, ``/api/dev`` would match ``/api/dev``, ``/api/dev/``, ``/api/dev/v1``, and ``/api/dev?param=true`` but would not match ``/api/developer`` Expect the value to not contain ``?`` or ``#`` and not to end in ``/``setPathSeparatedPrefixBytes
(com.google.protobuf.ByteString value) If specified, the route is a path-separated prefix rule meaning that the ``:path`` header (without the query string) must either exactly match the ``path_separated_prefix`` or have it as a prefix, followed by ``/`` For example, ``/api/dev`` would match ``/api/dev``, ``/api/dev/``, ``/api/dev/v1``, and ``/api/dev?param=true`` but would not match ``/api/developer`` Expect the value to not contain ``?`` or ``#`` and not to end in ``/``If specified, the route is a prefix rule meaning that the prefix must match the beginning of the ``:path`` header.setPrefixBytes
(com.google.protobuf.ByteString value) If specified, the route is a prefix rule meaning that the prefix must match the beginning of the ``:path`` header.setQueryParameters
(int index, QueryParameterMatcher value) Specifies a set of URL query parameters on which the route should match.setQueryParameters
(int index, QueryParameterMatcher.Builder builderForValue) Specifies a set of URL query parameters on which the route should match.Indicates that the route should additionally match on a runtime key.setRuntimeFraction
(RuntimeFractionalPercent.Builder builderForValue) Indicates that the route should additionally match on a runtime key.setSafeRegex
(RegexMatcher value) If specified, the route is a regular expression rule meaning that the regex must match the ``:path`` header once the query string is removed.setSafeRegex
(RegexMatcher.Builder builderForValue) If specified, the route is a regular expression rule meaning that the regex must match the ``:path`` header once the query string is removed.If specified, the client tls context will be matched against the defined match options.setTlsContext
(RouteMatch.TlsContextMatchOptions.Builder builderForValue) If specified, the client tls context will be matched against the defined match options.Methods inherited from class com.google.protobuf.GeneratedMessage.Builder
addRepeatedField, clearField, clearOneof, clone, getAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, getUnknownFieldSetBuilder, hasField, hasOneof, internalGetMapField, internalGetMapFieldReflection, internalGetMutableMapField, internalGetMutableMapFieldReflection, isClean, markClean, mergeUnknownFields, mergeUnknownLengthDelimitedField, mergeUnknownVarintField, newBuilderForField, onBuilt, onChanged, parseUnknownField, setField, setRepeatedField, setUnknownFields, setUnknownFieldSetBuilder, setUnknownFieldsProto3
Methods inherited from class com.google.protobuf.AbstractMessage.Builder
findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toString
Methods inherited from class com.google.protobuf.AbstractMessageLite.Builder
addAll, addAll, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, newUninitializedMessageException
Methods inherited from class java.lang.Object
equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
Methods inherited from interface com.google.protobuf.Message.Builder
mergeDelimitedFrom, mergeDelimitedFrom
Methods inherited from interface com.google.protobuf.MessageLite.Builder
mergeFrom
Methods inherited from interface com.google.protobuf.MessageOrBuilder
findInitializationErrors, getAllFields, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
-
Field Details
-
pathSpecifierCase_
private int pathSpecifierCase_ -
pathSpecifier_
-
bitField0_
private int bitField0_ -
safeRegexBuilder_
private com.google.protobuf.SingleFieldBuilder<RegexMatcher,RegexMatcher.Builder, safeRegexBuilder_RegexMatcherOrBuilder> -
connectMatcherBuilder_
private com.google.protobuf.SingleFieldBuilder<RouteMatch.ConnectMatcher,RouteMatch.ConnectMatcher.Builder, connectMatcherBuilder_RouteMatch.ConnectMatcherOrBuilder> -
pathMatchPolicyBuilder_
private com.google.protobuf.SingleFieldBuilder<TypedExtensionConfig,TypedExtensionConfig.Builder, pathMatchPolicyBuilder_TypedExtensionConfigOrBuilder> -
caseSensitive_
private com.google.protobuf.BoolValue caseSensitive_ -
caseSensitiveBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder, caseSensitiveBuilder_com.google.protobuf.BoolValueOrBuilder> -
runtimeFraction_
-
runtimeFractionBuilder_
private com.google.protobuf.SingleFieldBuilder<RuntimeFractionalPercent,RuntimeFractionalPercent.Builder, runtimeFractionBuilder_RuntimeFractionalPercentOrBuilder> -
headers_
-
headersBuilder_
private com.google.protobuf.RepeatedFieldBuilder<HeaderMatcher,HeaderMatcher.Builder, headersBuilder_HeaderMatcherOrBuilder> -
queryParameters_
-
queryParametersBuilder_
private com.google.protobuf.RepeatedFieldBuilder<QueryParameterMatcher,QueryParameterMatcher.Builder, queryParametersBuilder_QueryParameterMatcherOrBuilder> -
grpc_
-
grpcBuilder_
private com.google.protobuf.SingleFieldBuilder<RouteMatch.GrpcRouteMatchOptions,RouteMatch.GrpcRouteMatchOptions.Builder, grpcBuilder_RouteMatch.GrpcRouteMatchOptionsOrBuilder> -
tlsContext_
-
tlsContextBuilder_
private com.google.protobuf.SingleFieldBuilder<RouteMatch.TlsContextMatchOptions,RouteMatch.TlsContextMatchOptions.Builder, tlsContextBuilder_RouteMatch.TlsContextMatchOptionsOrBuilder> -
dynamicMetadata_
-
dynamicMetadataBuilder_
private com.google.protobuf.RepeatedFieldBuilder<MetadataMatcher,MetadataMatcher.Builder, dynamicMetadataBuilder_MetadataMatcherOrBuilder>
-
-
Constructor Details
-
Builder
private Builder() -
Builder
private Builder(com.google.protobuf.AbstractMessage.BuilderParent parent)
-
-
Method Details
-
getDescriptor
public static final com.google.protobuf.Descriptors.Descriptor getDescriptor() -
internalGetFieldAccessorTable
protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()- Specified by:
internalGetFieldAccessorTable
in classcom.google.protobuf.GeneratedMessage.Builder<RouteMatch.Builder>
-
maybeForceBuilderInitialization
private void maybeForceBuilderInitialization() -
clear
- Specified by:
clear
in interfacecom.google.protobuf.Message.Builder
- Specified by:
clear
in interfacecom.google.protobuf.MessageLite.Builder
- Overrides:
clear
in classcom.google.protobuf.GeneratedMessage.Builder<RouteMatch.Builder>
-
getDescriptorForType
public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()- Specified by:
getDescriptorForType
in interfacecom.google.protobuf.Message.Builder
- Specified by:
getDescriptorForType
in interfacecom.google.protobuf.MessageOrBuilder
- Overrides:
getDescriptorForType
in classcom.google.protobuf.GeneratedMessage.Builder<RouteMatch.Builder>
-
getDefaultInstanceForType
- Specified by:
getDefaultInstanceForType
in interfacecom.google.protobuf.MessageLiteOrBuilder
- Specified by:
getDefaultInstanceForType
in interfacecom.google.protobuf.MessageOrBuilder
-
build
- Specified by:
build
in interfacecom.google.protobuf.Message.Builder
- Specified by:
build
in interfacecom.google.protobuf.MessageLite.Builder
-
buildPartial
- Specified by:
buildPartial
in interfacecom.google.protobuf.Message.Builder
- Specified by:
buildPartial
in interfacecom.google.protobuf.MessageLite.Builder
-
buildPartialRepeatedFields
-
buildPartial0
-
buildPartialOneofs
-
mergeFrom
- Specified by:
mergeFrom
in interfacecom.google.protobuf.Message.Builder
- Overrides:
mergeFrom
in classcom.google.protobuf.AbstractMessage.Builder<RouteMatch.Builder>
-
mergeFrom
-
isInitialized
public final boolean isInitialized()- Specified by:
isInitialized
in interfacecom.google.protobuf.MessageLiteOrBuilder
- Overrides:
isInitialized
in classcom.google.protobuf.GeneratedMessage.Builder<RouteMatch.Builder>
-
mergeFrom
public RouteMatch.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException - Specified by:
mergeFrom
in interfacecom.google.protobuf.Message.Builder
- Specified by:
mergeFrom
in interfacecom.google.protobuf.MessageLite.Builder
- Overrides:
mergeFrom
in classcom.google.protobuf.AbstractMessage.Builder<RouteMatch.Builder>
- Throws:
IOException
-
getPathSpecifierCase
- Specified by:
getPathSpecifierCase
in interfaceRouteMatchOrBuilder
-
clearPathSpecifier
-
hasPrefix
public boolean hasPrefix()If specified, the route is a prefix rule meaning that the prefix must match the beginning of the ``:path`` header.
string prefix = 1;
- Specified by:
hasPrefix
in interfaceRouteMatchOrBuilder
- Returns:
- Whether the prefix field is set.
-
getPrefix
If specified, the route is a prefix rule meaning that the prefix must match the beginning of the ``:path`` header.
string prefix = 1;
- Specified by:
getPrefix
in interfaceRouteMatchOrBuilder
- Returns:
- The prefix.
-
getPrefixBytes
public com.google.protobuf.ByteString getPrefixBytes()If specified, the route is a prefix rule meaning that the prefix must match the beginning of the ``:path`` header.
string prefix = 1;
- Specified by:
getPrefixBytes
in interfaceRouteMatchOrBuilder
- Returns:
- The bytes for prefix.
-
setPrefix
If specified, the route is a prefix rule meaning that the prefix must match the beginning of the ``:path`` header.
string prefix = 1;
- Parameters:
value
- The prefix to set.- Returns:
- This builder for chaining.
-
clearPrefix
If specified, the route is a prefix rule meaning that the prefix must match the beginning of the ``:path`` header.
string prefix = 1;
- Returns:
- This builder for chaining.
-
setPrefixBytes
If specified, the route is a prefix rule meaning that the prefix must match the beginning of the ``:path`` header.
string prefix = 1;
- Parameters:
value
- The bytes for prefix to set.- Returns:
- This builder for chaining.
-
hasPath
public boolean hasPath()If specified, the route is an exact path rule meaning that the path must exactly match the ``:path`` header once the query string is removed.
string path = 2;
- Specified by:
hasPath
in interfaceRouteMatchOrBuilder
- Returns:
- Whether the path field is set.
-
getPath
If specified, the route is an exact path rule meaning that the path must exactly match the ``:path`` header once the query string is removed.
string path = 2;
- Specified by:
getPath
in interfaceRouteMatchOrBuilder
- Returns:
- The path.
-
getPathBytes
public com.google.protobuf.ByteString getPathBytes()If specified, the route is an exact path rule meaning that the path must exactly match the ``:path`` header once the query string is removed.
string path = 2;
- Specified by:
getPathBytes
in interfaceRouteMatchOrBuilder
- Returns:
- The bytes for path.
-
setPath
If specified, the route is an exact path rule meaning that the path must exactly match the ``:path`` header once the query string is removed.
string path = 2;
- Parameters:
value
- The path to set.- Returns:
- This builder for chaining.
-
clearPath
If specified, the route is an exact path rule meaning that the path must exactly match the ``:path`` header once the query string is removed.
string path = 2;
- Returns:
- This builder for chaining.
-
setPathBytes
If specified, the route is an exact path rule meaning that the path must exactly match the ``:path`` header once the query string is removed.
string path = 2;
- Parameters:
value
- The bytes for path to set.- Returns:
- This builder for chaining.
-
hasSafeRegex
public boolean hasSafeRegex()If specified, the route is a regular expression rule meaning that the regex must match the ``:path`` header once the query string is removed. The entire path (without the query string) must match the regex. The rule will not match if only a subsequence of the ``:path`` header matches the regex. [#next-major-version: In the v3 API we should redo how path specification works such that we utilize StringMatcher, and additionally have consistent options around whether we strip query strings, do a case sensitive match, etc. In the interim it will be too disruptive to deprecate the existing options. We should even consider whether we want to do away with path_specifier entirely and just rely on a set of header matchers which can already match on :path, etc. The issue with that is it is unclear how to generically deal with query string stripping. This needs more thought.]
.envoy.type.matcher.v3.RegexMatcher safe_regex = 10 [(.validate.rules) = { ... }
- Specified by:
hasSafeRegex
in interfaceRouteMatchOrBuilder
- Returns:
- Whether the safeRegex field is set.
-
getSafeRegex
If specified, the route is a regular expression rule meaning that the regex must match the ``:path`` header once the query string is removed. The entire path (without the query string) must match the regex. The rule will not match if only a subsequence of the ``:path`` header matches the regex. [#next-major-version: In the v3 API we should redo how path specification works such that we utilize StringMatcher, and additionally have consistent options around whether we strip query strings, do a case sensitive match, etc. In the interim it will be too disruptive to deprecate the existing options. We should even consider whether we want to do away with path_specifier entirely and just rely on a set of header matchers which can already match on :path, etc. The issue with that is it is unclear how to generically deal with query string stripping. This needs more thought.]
.envoy.type.matcher.v3.RegexMatcher safe_regex = 10 [(.validate.rules) = { ... }
- Specified by:
getSafeRegex
in interfaceRouteMatchOrBuilder
- Returns:
- The safeRegex.
-
setSafeRegex
If specified, the route is a regular expression rule meaning that the regex must match the ``:path`` header once the query string is removed. The entire path (without the query string) must match the regex. The rule will not match if only a subsequence of the ``:path`` header matches the regex. [#next-major-version: In the v3 API we should redo how path specification works such that we utilize StringMatcher, and additionally have consistent options around whether we strip query strings, do a case sensitive match, etc. In the interim it will be too disruptive to deprecate the existing options. We should even consider whether we want to do away with path_specifier entirely and just rely on a set of header matchers which can already match on :path, etc. The issue with that is it is unclear how to generically deal with query string stripping. This needs more thought.]
.envoy.type.matcher.v3.RegexMatcher safe_regex = 10 [(.validate.rules) = { ... }
-
setSafeRegex
If specified, the route is a regular expression rule meaning that the regex must match the ``:path`` header once the query string is removed. The entire path (without the query string) must match the regex. The rule will not match if only a subsequence of the ``:path`` header matches the regex. [#next-major-version: In the v3 API we should redo how path specification works such that we utilize StringMatcher, and additionally have consistent options around whether we strip query strings, do a case sensitive match, etc. In the interim it will be too disruptive to deprecate the existing options. We should even consider whether we want to do away with path_specifier entirely and just rely on a set of header matchers which can already match on :path, etc. The issue with that is it is unclear how to generically deal with query string stripping. This needs more thought.]
.envoy.type.matcher.v3.RegexMatcher safe_regex = 10 [(.validate.rules) = { ... }
-
mergeSafeRegex
If specified, the route is a regular expression rule meaning that the regex must match the ``:path`` header once the query string is removed. The entire path (without the query string) must match the regex. The rule will not match if only a subsequence of the ``:path`` header matches the regex. [#next-major-version: In the v3 API we should redo how path specification works such that we utilize StringMatcher, and additionally have consistent options around whether we strip query strings, do a case sensitive match, etc. In the interim it will be too disruptive to deprecate the existing options. We should even consider whether we want to do away with path_specifier entirely and just rely on a set of header matchers which can already match on :path, etc. The issue with that is it is unclear how to generically deal with query string stripping. This needs more thought.]
.envoy.type.matcher.v3.RegexMatcher safe_regex = 10 [(.validate.rules) = { ... }
-
clearSafeRegex
If specified, the route is a regular expression rule meaning that the regex must match the ``:path`` header once the query string is removed. The entire path (without the query string) must match the regex. The rule will not match if only a subsequence of the ``:path`` header matches the regex. [#next-major-version: In the v3 API we should redo how path specification works such that we utilize StringMatcher, and additionally have consistent options around whether we strip query strings, do a case sensitive match, etc. In the interim it will be too disruptive to deprecate the existing options. We should even consider whether we want to do away with path_specifier entirely and just rely on a set of header matchers which can already match on :path, etc. The issue with that is it is unclear how to generically deal with query string stripping. This needs more thought.]
.envoy.type.matcher.v3.RegexMatcher safe_regex = 10 [(.validate.rules) = { ... }
-
getSafeRegexBuilder
If specified, the route is a regular expression rule meaning that the regex must match the ``:path`` header once the query string is removed. The entire path (without the query string) must match the regex. The rule will not match if only a subsequence of the ``:path`` header matches the regex. [#next-major-version: In the v3 API we should redo how path specification works such that we utilize StringMatcher, and additionally have consistent options around whether we strip query strings, do a case sensitive match, etc. In the interim it will be too disruptive to deprecate the existing options. We should even consider whether we want to do away with path_specifier entirely and just rely on a set of header matchers which can already match on :path, etc. The issue with that is it is unclear how to generically deal with query string stripping. This needs more thought.]
.envoy.type.matcher.v3.RegexMatcher safe_regex = 10 [(.validate.rules) = { ... }
-
getSafeRegexOrBuilder
If specified, the route is a regular expression rule meaning that the regex must match the ``:path`` header once the query string is removed. The entire path (without the query string) must match the regex. The rule will not match if only a subsequence of the ``:path`` header matches the regex. [#next-major-version: In the v3 API we should redo how path specification works such that we utilize StringMatcher, and additionally have consistent options around whether we strip query strings, do a case sensitive match, etc. In the interim it will be too disruptive to deprecate the existing options. We should even consider whether we want to do away with path_specifier entirely and just rely on a set of header matchers which can already match on :path, etc. The issue with that is it is unclear how to generically deal with query string stripping. This needs more thought.]
.envoy.type.matcher.v3.RegexMatcher safe_regex = 10 [(.validate.rules) = { ... }
- Specified by:
getSafeRegexOrBuilder
in interfaceRouteMatchOrBuilder
-
internalGetSafeRegexFieldBuilder
private com.google.protobuf.SingleFieldBuilder<RegexMatcher,RegexMatcher.Builder, internalGetSafeRegexFieldBuilder()RegexMatcherOrBuilder> If specified, the route is a regular expression rule meaning that the regex must match the ``:path`` header once the query string is removed. The entire path (without the query string) must match the regex. The rule will not match if only a subsequence of the ``:path`` header matches the regex. [#next-major-version: In the v3 API we should redo how path specification works such that we utilize StringMatcher, and additionally have consistent options around whether we strip query strings, do a case sensitive match, etc. In the interim it will be too disruptive to deprecate the existing options. We should even consider whether we want to do away with path_specifier entirely and just rely on a set of header matchers which can already match on :path, etc. The issue with that is it is unclear how to generically deal with query string stripping. This needs more thought.]
.envoy.type.matcher.v3.RegexMatcher safe_regex = 10 [(.validate.rules) = { ... }
-
hasConnectMatcher
public boolean hasConnectMatcher()If this is used as the matcher, the matcher will only match CONNECT or CONNECT-UDP requests. Note that this will not match other Extended CONNECT requests (WebSocket and the like) as they are normalized in Envoy as HTTP/1.1 style upgrades. This is the only way to match CONNECT requests for HTTP/1.1. For HTTP/2 and HTTP/3, where Extended CONNECT requests may have a path, the path matchers will work if there is a path present. Note that CONNECT support is currently considered alpha in Envoy. [#comment: TODO(htuch): Replace the above comment with an alpha tag.]
.envoy.config.route.v3.RouteMatch.ConnectMatcher connect_matcher = 12;
- Specified by:
hasConnectMatcher
in interfaceRouteMatchOrBuilder
- Returns:
- Whether the connectMatcher field is set.
-
getConnectMatcher
If this is used as the matcher, the matcher will only match CONNECT or CONNECT-UDP requests. Note that this will not match other Extended CONNECT requests (WebSocket and the like) as they are normalized in Envoy as HTTP/1.1 style upgrades. This is the only way to match CONNECT requests for HTTP/1.1. For HTTP/2 and HTTP/3, where Extended CONNECT requests may have a path, the path matchers will work if there is a path present. Note that CONNECT support is currently considered alpha in Envoy. [#comment: TODO(htuch): Replace the above comment with an alpha tag.]
.envoy.config.route.v3.RouteMatch.ConnectMatcher connect_matcher = 12;
- Specified by:
getConnectMatcher
in interfaceRouteMatchOrBuilder
- Returns:
- The connectMatcher.
-
setConnectMatcher
If this is used as the matcher, the matcher will only match CONNECT or CONNECT-UDP requests. Note that this will not match other Extended CONNECT requests (WebSocket and the like) as they are normalized in Envoy as HTTP/1.1 style upgrades. This is the only way to match CONNECT requests for HTTP/1.1. For HTTP/2 and HTTP/3, where Extended CONNECT requests may have a path, the path matchers will work if there is a path present. Note that CONNECT support is currently considered alpha in Envoy. [#comment: TODO(htuch): Replace the above comment with an alpha tag.]
.envoy.config.route.v3.RouteMatch.ConnectMatcher connect_matcher = 12;
-
setConnectMatcher
If this is used as the matcher, the matcher will only match CONNECT or CONNECT-UDP requests. Note that this will not match other Extended CONNECT requests (WebSocket and the like) as they are normalized in Envoy as HTTP/1.1 style upgrades. This is the only way to match CONNECT requests for HTTP/1.1. For HTTP/2 and HTTP/3, where Extended CONNECT requests may have a path, the path matchers will work if there is a path present. Note that CONNECT support is currently considered alpha in Envoy. [#comment: TODO(htuch): Replace the above comment with an alpha tag.]
.envoy.config.route.v3.RouteMatch.ConnectMatcher connect_matcher = 12;
-
mergeConnectMatcher
If this is used as the matcher, the matcher will only match CONNECT or CONNECT-UDP requests. Note that this will not match other Extended CONNECT requests (WebSocket and the like) as they are normalized in Envoy as HTTP/1.1 style upgrades. This is the only way to match CONNECT requests for HTTP/1.1. For HTTP/2 and HTTP/3, where Extended CONNECT requests may have a path, the path matchers will work if there is a path present. Note that CONNECT support is currently considered alpha in Envoy. [#comment: TODO(htuch): Replace the above comment with an alpha tag.]
.envoy.config.route.v3.RouteMatch.ConnectMatcher connect_matcher = 12;
-
clearConnectMatcher
If this is used as the matcher, the matcher will only match CONNECT or CONNECT-UDP requests. Note that this will not match other Extended CONNECT requests (WebSocket and the like) as they are normalized in Envoy as HTTP/1.1 style upgrades. This is the only way to match CONNECT requests for HTTP/1.1. For HTTP/2 and HTTP/3, where Extended CONNECT requests may have a path, the path matchers will work if there is a path present. Note that CONNECT support is currently considered alpha in Envoy. [#comment: TODO(htuch): Replace the above comment with an alpha tag.]
.envoy.config.route.v3.RouteMatch.ConnectMatcher connect_matcher = 12;
-
getConnectMatcherBuilder
If this is used as the matcher, the matcher will only match CONNECT or CONNECT-UDP requests. Note that this will not match other Extended CONNECT requests (WebSocket and the like) as they are normalized in Envoy as HTTP/1.1 style upgrades. This is the only way to match CONNECT requests for HTTP/1.1. For HTTP/2 and HTTP/3, where Extended CONNECT requests may have a path, the path matchers will work if there is a path present. Note that CONNECT support is currently considered alpha in Envoy. [#comment: TODO(htuch): Replace the above comment with an alpha tag.]
.envoy.config.route.v3.RouteMatch.ConnectMatcher connect_matcher = 12;
-
getConnectMatcherOrBuilder
If this is used as the matcher, the matcher will only match CONNECT or CONNECT-UDP requests. Note that this will not match other Extended CONNECT requests (WebSocket and the like) as they are normalized in Envoy as HTTP/1.1 style upgrades. This is the only way to match CONNECT requests for HTTP/1.1. For HTTP/2 and HTTP/3, where Extended CONNECT requests may have a path, the path matchers will work if there is a path present. Note that CONNECT support is currently considered alpha in Envoy. [#comment: TODO(htuch): Replace the above comment with an alpha tag.]
.envoy.config.route.v3.RouteMatch.ConnectMatcher connect_matcher = 12;
- Specified by:
getConnectMatcherOrBuilder
in interfaceRouteMatchOrBuilder
-
internalGetConnectMatcherFieldBuilder
private com.google.protobuf.SingleFieldBuilder<RouteMatch.ConnectMatcher,RouteMatch.ConnectMatcher.Builder, internalGetConnectMatcherFieldBuilder()RouteMatch.ConnectMatcherOrBuilder> If this is used as the matcher, the matcher will only match CONNECT or CONNECT-UDP requests. Note that this will not match other Extended CONNECT requests (WebSocket and the like) as they are normalized in Envoy as HTTP/1.1 style upgrades. This is the only way to match CONNECT requests for HTTP/1.1. For HTTP/2 and HTTP/3, where Extended CONNECT requests may have a path, the path matchers will work if there is a path present. Note that CONNECT support is currently considered alpha in Envoy. [#comment: TODO(htuch): Replace the above comment with an alpha tag.]
.envoy.config.route.v3.RouteMatch.ConnectMatcher connect_matcher = 12;
-
hasPathSeparatedPrefix
public boolean hasPathSeparatedPrefix()If specified, the route is a path-separated prefix rule meaning that the ``:path`` header (without the query string) must either exactly match the ``path_separated_prefix`` or have it as a prefix, followed by ``/`` For example, ``/api/dev`` would match ``/api/dev``, ``/api/dev/``, ``/api/dev/v1``, and ``/api/dev?param=true`` but would not match ``/api/developer`` Expect the value to not contain ``?`` or ``#`` and not to end in ``/``
string path_separated_prefix = 14 [(.validate.rules) = { ... }
- Specified by:
hasPathSeparatedPrefix
in interfaceRouteMatchOrBuilder
- Returns:
- Whether the pathSeparatedPrefix field is set.
-
getPathSeparatedPrefix
If specified, the route is a path-separated prefix rule meaning that the ``:path`` header (without the query string) must either exactly match the ``path_separated_prefix`` or have it as a prefix, followed by ``/`` For example, ``/api/dev`` would match ``/api/dev``, ``/api/dev/``, ``/api/dev/v1``, and ``/api/dev?param=true`` but would not match ``/api/developer`` Expect the value to not contain ``?`` or ``#`` and not to end in ``/``
string path_separated_prefix = 14 [(.validate.rules) = { ... }
- Specified by:
getPathSeparatedPrefix
in interfaceRouteMatchOrBuilder
- Returns:
- The pathSeparatedPrefix.
-
getPathSeparatedPrefixBytes
public com.google.protobuf.ByteString getPathSeparatedPrefixBytes()If specified, the route is a path-separated prefix rule meaning that the ``:path`` header (without the query string) must either exactly match the ``path_separated_prefix`` or have it as a prefix, followed by ``/`` For example, ``/api/dev`` would match ``/api/dev``, ``/api/dev/``, ``/api/dev/v1``, and ``/api/dev?param=true`` but would not match ``/api/developer`` Expect the value to not contain ``?`` or ``#`` and not to end in ``/``
string path_separated_prefix = 14 [(.validate.rules) = { ... }
- Specified by:
getPathSeparatedPrefixBytes
in interfaceRouteMatchOrBuilder
- Returns:
- The bytes for pathSeparatedPrefix.
-
setPathSeparatedPrefix
If specified, the route is a path-separated prefix rule meaning that the ``:path`` header (without the query string) must either exactly match the ``path_separated_prefix`` or have it as a prefix, followed by ``/`` For example, ``/api/dev`` would match ``/api/dev``, ``/api/dev/``, ``/api/dev/v1``, and ``/api/dev?param=true`` but would not match ``/api/developer`` Expect the value to not contain ``?`` or ``#`` and not to end in ``/``
string path_separated_prefix = 14 [(.validate.rules) = { ... }
- Parameters:
value
- The pathSeparatedPrefix to set.- Returns:
- This builder for chaining.
-
clearPathSeparatedPrefix
If specified, the route is a path-separated prefix rule meaning that the ``:path`` header (without the query string) must either exactly match the ``path_separated_prefix`` or have it as a prefix, followed by ``/`` For example, ``/api/dev`` would match ``/api/dev``, ``/api/dev/``, ``/api/dev/v1``, and ``/api/dev?param=true`` but would not match ``/api/developer`` Expect the value to not contain ``?`` or ``#`` and not to end in ``/``
string path_separated_prefix = 14 [(.validate.rules) = { ... }
- Returns:
- This builder for chaining.
-
setPathSeparatedPrefixBytes
If specified, the route is a path-separated prefix rule meaning that the ``:path`` header (without the query string) must either exactly match the ``path_separated_prefix`` or have it as a prefix, followed by ``/`` For example, ``/api/dev`` would match ``/api/dev``, ``/api/dev/``, ``/api/dev/v1``, and ``/api/dev?param=true`` but would not match ``/api/developer`` Expect the value to not contain ``?`` or ``#`` and not to end in ``/``
string path_separated_prefix = 14 [(.validate.rules) = { ... }
- Parameters:
value
- The bytes for pathSeparatedPrefix to set.- Returns:
- This builder for chaining.
-
hasPathMatchPolicy
public boolean hasPathMatchPolicy()[#extension-category: envoy.path.match]
.envoy.config.core.v3.TypedExtensionConfig path_match_policy = 15;
- Specified by:
hasPathMatchPolicy
in interfaceRouteMatchOrBuilder
- Returns:
- Whether the pathMatchPolicy field is set.
-
getPathMatchPolicy
[#extension-category: envoy.path.match]
.envoy.config.core.v3.TypedExtensionConfig path_match_policy = 15;
- Specified by:
getPathMatchPolicy
in interfaceRouteMatchOrBuilder
- Returns:
- The pathMatchPolicy.
-
setPathMatchPolicy
[#extension-category: envoy.path.match]
.envoy.config.core.v3.TypedExtensionConfig path_match_policy = 15;
-
setPathMatchPolicy
[#extension-category: envoy.path.match]
.envoy.config.core.v3.TypedExtensionConfig path_match_policy = 15;
-
mergePathMatchPolicy
[#extension-category: envoy.path.match]
.envoy.config.core.v3.TypedExtensionConfig path_match_policy = 15;
-
clearPathMatchPolicy
[#extension-category: envoy.path.match]
.envoy.config.core.v3.TypedExtensionConfig path_match_policy = 15;
-
getPathMatchPolicyBuilder
[#extension-category: envoy.path.match]
.envoy.config.core.v3.TypedExtensionConfig path_match_policy = 15;
-
getPathMatchPolicyOrBuilder
[#extension-category: envoy.path.match]
.envoy.config.core.v3.TypedExtensionConfig path_match_policy = 15;
- Specified by:
getPathMatchPolicyOrBuilder
in interfaceRouteMatchOrBuilder
-
internalGetPathMatchPolicyFieldBuilder
private com.google.protobuf.SingleFieldBuilder<TypedExtensionConfig,TypedExtensionConfig.Builder, internalGetPathMatchPolicyFieldBuilder()TypedExtensionConfigOrBuilder> [#extension-category: envoy.path.match]
.envoy.config.core.v3.TypedExtensionConfig path_match_policy = 15;
-
hasCaseSensitive
public boolean hasCaseSensitive()Indicates that prefix/path matching should be case sensitive. The default is true. Ignored for safe_regex matching.
.google.protobuf.BoolValue case_sensitive = 4;
- Specified by:
hasCaseSensitive
in interfaceRouteMatchOrBuilder
- Returns:
- Whether the caseSensitive field is set.
-
getCaseSensitive
public com.google.protobuf.BoolValue getCaseSensitive()Indicates that prefix/path matching should be case sensitive. The default is true. Ignored for safe_regex matching.
.google.protobuf.BoolValue case_sensitive = 4;
- Specified by:
getCaseSensitive
in interfaceRouteMatchOrBuilder
- Returns:
- The caseSensitive.
-
setCaseSensitive
Indicates that prefix/path matching should be case sensitive. The default is true. Ignored for safe_regex matching.
.google.protobuf.BoolValue case_sensitive = 4;
-
setCaseSensitive
Indicates that prefix/path matching should be case sensitive. The default is true. Ignored for safe_regex matching.
.google.protobuf.BoolValue case_sensitive = 4;
-
mergeCaseSensitive
Indicates that prefix/path matching should be case sensitive. The default is true. Ignored for safe_regex matching.
.google.protobuf.BoolValue case_sensitive = 4;
-
clearCaseSensitive
Indicates that prefix/path matching should be case sensitive. The default is true. Ignored for safe_regex matching.
.google.protobuf.BoolValue case_sensitive = 4;
-
getCaseSensitiveBuilder
public com.google.protobuf.BoolValue.Builder getCaseSensitiveBuilder()Indicates that prefix/path matching should be case sensitive. The default is true. Ignored for safe_regex matching.
.google.protobuf.BoolValue case_sensitive = 4;
-
getCaseSensitiveOrBuilder
public com.google.protobuf.BoolValueOrBuilder getCaseSensitiveOrBuilder()Indicates that prefix/path matching should be case sensitive. The default is true. Ignored for safe_regex matching.
.google.protobuf.BoolValue case_sensitive = 4;
- Specified by:
getCaseSensitiveOrBuilder
in interfaceRouteMatchOrBuilder
-
internalGetCaseSensitiveFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder, internalGetCaseSensitiveFieldBuilder()com.google.protobuf.BoolValueOrBuilder> Indicates that prefix/path matching should be case sensitive. The default is true. Ignored for safe_regex matching.
.google.protobuf.BoolValue case_sensitive = 4;
-
hasRuntimeFraction
public boolean hasRuntimeFraction()Indicates that the route should additionally match on a runtime key. Every time the route is considered for a match, it must also fall under the percentage of matches indicated by this field. For some fraction N/D, a random number in the range [0,D) is selected. If the number is <= the value of the numerator N, or if the key is not present, the default value, the router continues to evaluate the remaining match criteria. A runtime_fraction route configuration can be used to roll out route changes in a gradual manner without full code/config deploys. Refer to the :ref:`traffic shifting <config_http_conn_man_route_table_traffic_splitting_shift>` docs for additional documentation. .. note:: Parsing this field is implemented such that the runtime key's data may be represented as a FractionalPercent proto represented as JSON/YAML and may also be represented as an integer with the assumption that the value is an integral percentage out of 100. For instance, a runtime key lookup returning the value "42" would parse as a FractionalPercent whose numerator is 42 and denominator is HUNDRED. This preserves legacy semantics.
.envoy.config.core.v3.RuntimeFractionalPercent runtime_fraction = 9;
- Specified by:
hasRuntimeFraction
in interfaceRouteMatchOrBuilder
- Returns:
- Whether the runtimeFraction field is set.
-
getRuntimeFraction
Indicates that the route should additionally match on a runtime key. Every time the route is considered for a match, it must also fall under the percentage of matches indicated by this field. For some fraction N/D, a random number in the range [0,D) is selected. If the number is <= the value of the numerator N, or if the key is not present, the default value, the router continues to evaluate the remaining match criteria. A runtime_fraction route configuration can be used to roll out route changes in a gradual manner without full code/config deploys. Refer to the :ref:`traffic shifting <config_http_conn_man_route_table_traffic_splitting_shift>` docs for additional documentation. .. note:: Parsing this field is implemented such that the runtime key's data may be represented as a FractionalPercent proto represented as JSON/YAML and may also be represented as an integer with the assumption that the value is an integral percentage out of 100. For instance, a runtime key lookup returning the value "42" would parse as a FractionalPercent whose numerator is 42 and denominator is HUNDRED. This preserves legacy semantics.
.envoy.config.core.v3.RuntimeFractionalPercent runtime_fraction = 9;
- Specified by:
getRuntimeFraction
in interfaceRouteMatchOrBuilder
- Returns:
- The runtimeFraction.
-
setRuntimeFraction
Indicates that the route should additionally match on a runtime key. Every time the route is considered for a match, it must also fall under the percentage of matches indicated by this field. For some fraction N/D, a random number in the range [0,D) is selected. If the number is <= the value of the numerator N, or if the key is not present, the default value, the router continues to evaluate the remaining match criteria. A runtime_fraction route configuration can be used to roll out route changes in a gradual manner without full code/config deploys. Refer to the :ref:`traffic shifting <config_http_conn_man_route_table_traffic_splitting_shift>` docs for additional documentation. .. note:: Parsing this field is implemented such that the runtime key's data may be represented as a FractionalPercent proto represented as JSON/YAML and may also be represented as an integer with the assumption that the value is an integral percentage out of 100. For instance, a runtime key lookup returning the value "42" would parse as a FractionalPercent whose numerator is 42 and denominator is HUNDRED. This preserves legacy semantics.
.envoy.config.core.v3.RuntimeFractionalPercent runtime_fraction = 9;
-
setRuntimeFraction
Indicates that the route should additionally match on a runtime key. Every time the route is considered for a match, it must also fall under the percentage of matches indicated by this field. For some fraction N/D, a random number in the range [0,D) is selected. If the number is <= the value of the numerator N, or if the key is not present, the default value, the router continues to evaluate the remaining match criteria. A runtime_fraction route configuration can be used to roll out route changes in a gradual manner without full code/config deploys. Refer to the :ref:`traffic shifting <config_http_conn_man_route_table_traffic_splitting_shift>` docs for additional documentation. .. note:: Parsing this field is implemented such that the runtime key's data may be represented as a FractionalPercent proto represented as JSON/YAML and may also be represented as an integer with the assumption that the value is an integral percentage out of 100. For instance, a runtime key lookup returning the value "42" would parse as a FractionalPercent whose numerator is 42 and denominator is HUNDRED. This preserves legacy semantics.
.envoy.config.core.v3.RuntimeFractionalPercent runtime_fraction = 9;
-
mergeRuntimeFraction
Indicates that the route should additionally match on a runtime key. Every time the route is considered for a match, it must also fall under the percentage of matches indicated by this field. For some fraction N/D, a random number in the range [0,D) is selected. If the number is <= the value of the numerator N, or if the key is not present, the default value, the router continues to evaluate the remaining match criteria. A runtime_fraction route configuration can be used to roll out route changes in a gradual manner without full code/config deploys. Refer to the :ref:`traffic shifting <config_http_conn_man_route_table_traffic_splitting_shift>` docs for additional documentation. .. note:: Parsing this field is implemented such that the runtime key's data may be represented as a FractionalPercent proto represented as JSON/YAML and may also be represented as an integer with the assumption that the value is an integral percentage out of 100. For instance, a runtime key lookup returning the value "42" would parse as a FractionalPercent whose numerator is 42 and denominator is HUNDRED. This preserves legacy semantics.
.envoy.config.core.v3.RuntimeFractionalPercent runtime_fraction = 9;
-
clearRuntimeFraction
Indicates that the route should additionally match on a runtime key. Every time the route is considered for a match, it must also fall under the percentage of matches indicated by this field. For some fraction N/D, a random number in the range [0,D) is selected. If the number is <= the value of the numerator N, or if the key is not present, the default value, the router continues to evaluate the remaining match criteria. A runtime_fraction route configuration can be used to roll out route changes in a gradual manner without full code/config deploys. Refer to the :ref:`traffic shifting <config_http_conn_man_route_table_traffic_splitting_shift>` docs for additional documentation. .. note:: Parsing this field is implemented such that the runtime key's data may be represented as a FractionalPercent proto represented as JSON/YAML and may also be represented as an integer with the assumption that the value is an integral percentage out of 100. For instance, a runtime key lookup returning the value "42" would parse as a FractionalPercent whose numerator is 42 and denominator is HUNDRED. This preserves legacy semantics.
.envoy.config.core.v3.RuntimeFractionalPercent runtime_fraction = 9;
-
getRuntimeFractionBuilder
Indicates that the route should additionally match on a runtime key. Every time the route is considered for a match, it must also fall under the percentage of matches indicated by this field. For some fraction N/D, a random number in the range [0,D) is selected. If the number is <= the value of the numerator N, or if the key is not present, the default value, the router continues to evaluate the remaining match criteria. A runtime_fraction route configuration can be used to roll out route changes in a gradual manner without full code/config deploys. Refer to the :ref:`traffic shifting <config_http_conn_man_route_table_traffic_splitting_shift>` docs for additional documentation. .. note:: Parsing this field is implemented such that the runtime key's data may be represented as a FractionalPercent proto represented as JSON/YAML and may also be represented as an integer with the assumption that the value is an integral percentage out of 100. For instance, a runtime key lookup returning the value "42" would parse as a FractionalPercent whose numerator is 42 and denominator is HUNDRED. This preserves legacy semantics.
.envoy.config.core.v3.RuntimeFractionalPercent runtime_fraction = 9;
-
getRuntimeFractionOrBuilder
Indicates that the route should additionally match on a runtime key. Every time the route is considered for a match, it must also fall under the percentage of matches indicated by this field. For some fraction N/D, a random number in the range [0,D) is selected. If the number is <= the value of the numerator N, or if the key is not present, the default value, the router continues to evaluate the remaining match criteria. A runtime_fraction route configuration can be used to roll out route changes in a gradual manner without full code/config deploys. Refer to the :ref:`traffic shifting <config_http_conn_man_route_table_traffic_splitting_shift>` docs for additional documentation. .. note:: Parsing this field is implemented such that the runtime key's data may be represented as a FractionalPercent proto represented as JSON/YAML and may also be represented as an integer with the assumption that the value is an integral percentage out of 100. For instance, a runtime key lookup returning the value "42" would parse as a FractionalPercent whose numerator is 42 and denominator is HUNDRED. This preserves legacy semantics.
.envoy.config.core.v3.RuntimeFractionalPercent runtime_fraction = 9;
- Specified by:
getRuntimeFractionOrBuilder
in interfaceRouteMatchOrBuilder
-
internalGetRuntimeFractionFieldBuilder
private com.google.protobuf.SingleFieldBuilder<RuntimeFractionalPercent,RuntimeFractionalPercent.Builder, internalGetRuntimeFractionFieldBuilder()RuntimeFractionalPercentOrBuilder> Indicates that the route should additionally match on a runtime key. Every time the route is considered for a match, it must also fall under the percentage of matches indicated by this field. For some fraction N/D, a random number in the range [0,D) is selected. If the number is <= the value of the numerator N, or if the key is not present, the default value, the router continues to evaluate the remaining match criteria. A runtime_fraction route configuration can be used to roll out route changes in a gradual manner without full code/config deploys. Refer to the :ref:`traffic shifting <config_http_conn_man_route_table_traffic_splitting_shift>` docs for additional documentation. .. note:: Parsing this field is implemented such that the runtime key's data may be represented as a FractionalPercent proto represented as JSON/YAML and may also be represented as an integer with the assumption that the value is an integral percentage out of 100. For instance, a runtime key lookup returning the value "42" would parse as a FractionalPercent whose numerator is 42 and denominator is HUNDRED. This preserves legacy semantics.
.envoy.config.core.v3.RuntimeFractionalPercent runtime_fraction = 9;
-
ensureHeadersIsMutable
private void ensureHeadersIsMutable() -
getHeadersList
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).
repeated .envoy.config.route.v3.HeaderMatcher headers = 6;
- Specified by:
getHeadersList
in interfaceRouteMatchOrBuilder
-
getHeadersCount
public int getHeadersCount()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).
repeated .envoy.config.route.v3.HeaderMatcher headers = 6;
- Specified by:
getHeadersCount
in interfaceRouteMatchOrBuilder
-
getHeaders
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).
repeated .envoy.config.route.v3.HeaderMatcher headers = 6;
- Specified by:
getHeaders
in interfaceRouteMatchOrBuilder
-
setHeaders
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).
repeated .envoy.config.route.v3.HeaderMatcher headers = 6;
-
setHeaders
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).
repeated .envoy.config.route.v3.HeaderMatcher headers = 6;
-
addHeaders
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).
repeated .envoy.config.route.v3.HeaderMatcher headers = 6;
-
addHeaders
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).
repeated .envoy.config.route.v3.HeaderMatcher headers = 6;
-
addHeaders
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).
repeated .envoy.config.route.v3.HeaderMatcher headers = 6;
-
addHeaders
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).
repeated .envoy.config.route.v3.HeaderMatcher headers = 6;
-
addAllHeaders
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).
repeated .envoy.config.route.v3.HeaderMatcher headers = 6;
-
clearHeaders
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).
repeated .envoy.config.route.v3.HeaderMatcher headers = 6;
-
removeHeaders
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).
repeated .envoy.config.route.v3.HeaderMatcher headers = 6;
-
getHeadersBuilder
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).
repeated .envoy.config.route.v3.HeaderMatcher headers = 6;
-
getHeadersOrBuilder
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).
repeated .envoy.config.route.v3.HeaderMatcher headers = 6;
- Specified by:
getHeadersOrBuilder
in interfaceRouteMatchOrBuilder
-
getHeadersOrBuilderList
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).
repeated .envoy.config.route.v3.HeaderMatcher headers = 6;
- Specified by:
getHeadersOrBuilderList
in interfaceRouteMatchOrBuilder
-
addHeadersBuilder
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).
repeated .envoy.config.route.v3.HeaderMatcher headers = 6;
-
addHeadersBuilder
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).
repeated .envoy.config.route.v3.HeaderMatcher headers = 6;
-
getHeadersBuilderList
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).
repeated .envoy.config.route.v3.HeaderMatcher headers = 6;
-
internalGetHeadersFieldBuilder
private com.google.protobuf.RepeatedFieldBuilder<HeaderMatcher,HeaderMatcher.Builder, internalGetHeadersFieldBuilder()HeaderMatcherOrBuilder> -
ensureQueryParametersIsMutable
private void ensureQueryParametersIsMutable() -
getQueryParametersList
Specifies a set of URL query parameters on which the route should match. The router will check the query string from the ``path`` header against all the specified query parameters. If the number of specified query parameters is nonzero, they all must match the ``path`` header's query string for a match to occur. In the event query parameters are repeated, only the first value for each key will be considered. .. note:: If query parameters are used to pass request message fields when `grpc_json_transcoder <https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter>`_ is used, the transcoded message fields maybe different. The query parameters are url encoded, but the message fields are not. For example, if a query parameter is "foo%20bar", the message field will be "foo bar".
repeated .envoy.config.route.v3.QueryParameterMatcher query_parameters = 7;
- Specified by:
getQueryParametersList
in interfaceRouteMatchOrBuilder
-
getQueryParametersCount
public int getQueryParametersCount()Specifies a set of URL query parameters on which the route should match. The router will check the query string from the ``path`` header against all the specified query parameters. If the number of specified query parameters is nonzero, they all must match the ``path`` header's query string for a match to occur. In the event query parameters are repeated, only the first value for each key will be considered. .. note:: If query parameters are used to pass request message fields when `grpc_json_transcoder <https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter>`_ is used, the transcoded message fields maybe different. The query parameters are url encoded, but the message fields are not. For example, if a query parameter is "foo%20bar", the message field will be "foo bar".
repeated .envoy.config.route.v3.QueryParameterMatcher query_parameters = 7;
- Specified by:
getQueryParametersCount
in interfaceRouteMatchOrBuilder
-
getQueryParameters
Specifies a set of URL query parameters on which the route should match. The router will check the query string from the ``path`` header against all the specified query parameters. If the number of specified query parameters is nonzero, they all must match the ``path`` header's query string for a match to occur. In the event query parameters are repeated, only the first value for each key will be considered. .. note:: If query parameters are used to pass request message fields when `grpc_json_transcoder <https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter>`_ is used, the transcoded message fields maybe different. The query parameters are url encoded, but the message fields are not. For example, if a query parameter is "foo%20bar", the message field will be "foo bar".
repeated .envoy.config.route.v3.QueryParameterMatcher query_parameters = 7;
- Specified by:
getQueryParameters
in interfaceRouteMatchOrBuilder
-
setQueryParameters
Specifies a set of URL query parameters on which the route should match. The router will check the query string from the ``path`` header against all the specified query parameters. If the number of specified query parameters is nonzero, they all must match the ``path`` header's query string for a match to occur. In the event query parameters are repeated, only the first value for each key will be considered. .. note:: If query parameters are used to pass request message fields when `grpc_json_transcoder <https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter>`_ is used, the transcoded message fields maybe different. The query parameters are url encoded, but the message fields are not. For example, if a query parameter is "foo%20bar", the message field will be "foo bar".
repeated .envoy.config.route.v3.QueryParameterMatcher query_parameters = 7;
-
setQueryParameters
public RouteMatch.Builder setQueryParameters(int index, QueryParameterMatcher.Builder builderForValue) Specifies a set of URL query parameters on which the route should match. The router will check the query string from the ``path`` header against all the specified query parameters. If the number of specified query parameters is nonzero, they all must match the ``path`` header's query string for a match to occur. In the event query parameters are repeated, only the first value for each key will be considered. .. note:: If query parameters are used to pass request message fields when `grpc_json_transcoder <https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter>`_ is used, the transcoded message fields maybe different. The query parameters are url encoded, but the message fields are not. For example, if a query parameter is "foo%20bar", the message field will be "foo bar".
repeated .envoy.config.route.v3.QueryParameterMatcher query_parameters = 7;
-
addQueryParameters
Specifies a set of URL query parameters on which the route should match. The router will check the query string from the ``path`` header against all the specified query parameters. If the number of specified query parameters is nonzero, they all must match the ``path`` header's query string for a match to occur. In the event query parameters are repeated, only the first value for each key will be considered. .. note:: If query parameters are used to pass request message fields when `grpc_json_transcoder <https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter>`_ is used, the transcoded message fields maybe different. The query parameters are url encoded, but the message fields are not. For example, if a query parameter is "foo%20bar", the message field will be "foo bar".
repeated .envoy.config.route.v3.QueryParameterMatcher query_parameters = 7;
-
addQueryParameters
Specifies a set of URL query parameters on which the route should match. The router will check the query string from the ``path`` header against all the specified query parameters. If the number of specified query parameters is nonzero, they all must match the ``path`` header's query string for a match to occur. In the event query parameters are repeated, only the first value for each key will be considered. .. note:: If query parameters are used to pass request message fields when `grpc_json_transcoder <https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter>`_ is used, the transcoded message fields maybe different. The query parameters are url encoded, but the message fields are not. For example, if a query parameter is "foo%20bar", the message field will be "foo bar".
repeated .envoy.config.route.v3.QueryParameterMatcher query_parameters = 7;
-
addQueryParameters
Specifies a set of URL query parameters on which the route should match. The router will check the query string from the ``path`` header against all the specified query parameters. If the number of specified query parameters is nonzero, they all must match the ``path`` header's query string for a match to occur. In the event query parameters are repeated, only the first value for each key will be considered. .. note:: If query parameters are used to pass request message fields when `grpc_json_transcoder <https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter>`_ is used, the transcoded message fields maybe different. The query parameters are url encoded, but the message fields are not. For example, if a query parameter is "foo%20bar", the message field will be "foo bar".
repeated .envoy.config.route.v3.QueryParameterMatcher query_parameters = 7;
-
addQueryParameters
public RouteMatch.Builder addQueryParameters(int index, QueryParameterMatcher.Builder builderForValue) Specifies a set of URL query parameters on which the route should match. The router will check the query string from the ``path`` header against all the specified query parameters. If the number of specified query parameters is nonzero, they all must match the ``path`` header's query string for a match to occur. In the event query parameters are repeated, only the first value for each key will be considered. .. note:: If query parameters are used to pass request message fields when `grpc_json_transcoder <https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter>`_ is used, the transcoded message fields maybe different. The query parameters are url encoded, but the message fields are not. For example, if a query parameter is "foo%20bar", the message field will be "foo bar".
repeated .envoy.config.route.v3.QueryParameterMatcher query_parameters = 7;
-
addAllQueryParameters
Specifies a set of URL query parameters on which the route should match. The router will check the query string from the ``path`` header against all the specified query parameters. If the number of specified query parameters is nonzero, they all must match the ``path`` header's query string for a match to occur. In the event query parameters are repeated, only the first value for each key will be considered. .. note:: If query parameters are used to pass request message fields when `grpc_json_transcoder <https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter>`_ is used, the transcoded message fields maybe different. The query parameters are url encoded, but the message fields are not. For example, if a query parameter is "foo%20bar", the message field will be "foo bar".
repeated .envoy.config.route.v3.QueryParameterMatcher query_parameters = 7;
-
clearQueryParameters
Specifies a set of URL query parameters on which the route should match. The router will check the query string from the ``path`` header against all the specified query parameters. If the number of specified query parameters is nonzero, they all must match the ``path`` header's query string for a match to occur. In the event query parameters are repeated, only the first value for each key will be considered. .. note:: If query parameters are used to pass request message fields when `grpc_json_transcoder <https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter>`_ is used, the transcoded message fields maybe different. The query parameters are url encoded, but the message fields are not. For example, if a query parameter is "foo%20bar", the message field will be "foo bar".
repeated .envoy.config.route.v3.QueryParameterMatcher query_parameters = 7;
-
removeQueryParameters
Specifies a set of URL query parameters on which the route should match. The router will check the query string from the ``path`` header against all the specified query parameters. If the number of specified query parameters is nonzero, they all must match the ``path`` header's query string for a match to occur. In the event query parameters are repeated, only the first value for each key will be considered. .. note:: If query parameters are used to pass request message fields when `grpc_json_transcoder <https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter>`_ is used, the transcoded message fields maybe different. The query parameters are url encoded, but the message fields are not. For example, if a query parameter is "foo%20bar", the message field will be "foo bar".
repeated .envoy.config.route.v3.QueryParameterMatcher query_parameters = 7;
-
getQueryParametersBuilder
Specifies a set of URL query parameters on which the route should match. The router will check the query string from the ``path`` header against all the specified query parameters. If the number of specified query parameters is nonzero, they all must match the ``path`` header's query string for a match to occur. In the event query parameters are repeated, only the first value for each key will be considered. .. note:: If query parameters are used to pass request message fields when `grpc_json_transcoder <https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter>`_ is used, the transcoded message fields maybe different. The query parameters are url encoded, but the message fields are not. For example, if a query parameter is "foo%20bar", the message field will be "foo bar".
repeated .envoy.config.route.v3.QueryParameterMatcher query_parameters = 7;
-
getQueryParametersOrBuilder
Specifies a set of URL query parameters on which the route should match. The router will check the query string from the ``path`` header against all the specified query parameters. If the number of specified query parameters is nonzero, they all must match the ``path`` header's query string for a match to occur. In the event query parameters are repeated, only the first value for each key will be considered. .. note:: If query parameters are used to pass request message fields when `grpc_json_transcoder <https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter>`_ is used, the transcoded message fields maybe different. The query parameters are url encoded, but the message fields are not. For example, if a query parameter is "foo%20bar", the message field will be "foo bar".
repeated .envoy.config.route.v3.QueryParameterMatcher query_parameters = 7;
- Specified by:
getQueryParametersOrBuilder
in interfaceRouteMatchOrBuilder
-
getQueryParametersOrBuilderList
Specifies a set of URL query parameters on which the route should match. The router will check the query string from the ``path`` header against all the specified query parameters. If the number of specified query parameters is nonzero, they all must match the ``path`` header's query string for a match to occur. In the event query parameters are repeated, only the first value for each key will be considered. .. note:: If query parameters are used to pass request message fields when `grpc_json_transcoder <https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter>`_ is used, the transcoded message fields maybe different. The query parameters are url encoded, but the message fields are not. For example, if a query parameter is "foo%20bar", the message field will be "foo bar".
repeated .envoy.config.route.v3.QueryParameterMatcher query_parameters = 7;
- Specified by:
getQueryParametersOrBuilderList
in interfaceRouteMatchOrBuilder
-
addQueryParametersBuilder
Specifies a set of URL query parameters on which the route should match. The router will check the query string from the ``path`` header against all the specified query parameters. If the number of specified query parameters is nonzero, they all must match the ``path`` header's query string for a match to occur. In the event query parameters are repeated, only the first value for each key will be considered. .. note:: If query parameters are used to pass request message fields when `grpc_json_transcoder <https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter>`_ is used, the transcoded message fields maybe different. The query parameters are url encoded, but the message fields are not. For example, if a query parameter is "foo%20bar", the message field will be "foo bar".
repeated .envoy.config.route.v3.QueryParameterMatcher query_parameters = 7;
-
addQueryParametersBuilder
Specifies a set of URL query parameters on which the route should match. The router will check the query string from the ``path`` header against all the specified query parameters. If the number of specified query parameters is nonzero, they all must match the ``path`` header's query string for a match to occur. In the event query parameters are repeated, only the first value for each key will be considered. .. note:: If query parameters are used to pass request message fields when `grpc_json_transcoder <https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter>`_ is used, the transcoded message fields maybe different. The query parameters are url encoded, but the message fields are not. For example, if a query parameter is "foo%20bar", the message field will be "foo bar".
repeated .envoy.config.route.v3.QueryParameterMatcher query_parameters = 7;
-
getQueryParametersBuilderList
Specifies a set of URL query parameters on which the route should match. The router will check the query string from the ``path`` header against all the specified query parameters. If the number of specified query parameters is nonzero, they all must match the ``path`` header's query string for a match to occur. In the event query parameters are repeated, only the first value for each key will be considered. .. note:: If query parameters are used to pass request message fields when `grpc_json_transcoder <https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter>`_ is used, the transcoded message fields maybe different. The query parameters are url encoded, but the message fields are not. For example, if a query parameter is "foo%20bar", the message field will be "foo bar".
repeated .envoy.config.route.v3.QueryParameterMatcher query_parameters = 7;
-
internalGetQueryParametersFieldBuilder
private com.google.protobuf.RepeatedFieldBuilder<QueryParameterMatcher,QueryParameterMatcher.Builder, internalGetQueryParametersFieldBuilder()QueryParameterMatcherOrBuilder> -
hasGrpc
public boolean hasGrpc()If specified, only gRPC requests will be matched. The router will check that the content-type header has a application/grpc or one of the various application/grpc+ values.
.envoy.config.route.v3.RouteMatch.GrpcRouteMatchOptions grpc = 8;
- Specified by:
hasGrpc
in interfaceRouteMatchOrBuilder
- Returns:
- Whether the grpc field is set.
-
getGrpc
If specified, only gRPC requests will be matched. The router will check that the content-type header has a application/grpc or one of the various application/grpc+ values.
.envoy.config.route.v3.RouteMatch.GrpcRouteMatchOptions grpc = 8;
- Specified by:
getGrpc
in interfaceRouteMatchOrBuilder
- Returns:
- The grpc.
-
setGrpc
If specified, only gRPC requests will be matched. The router will check that the content-type header has a application/grpc or one of the various application/grpc+ values.
.envoy.config.route.v3.RouteMatch.GrpcRouteMatchOptions grpc = 8;
-
setGrpc
If specified, only gRPC requests will be matched. The router will check that the content-type header has a application/grpc or one of the various application/grpc+ values.
.envoy.config.route.v3.RouteMatch.GrpcRouteMatchOptions grpc = 8;
-
mergeGrpc
If specified, only gRPC requests will be matched. The router will check that the content-type header has a application/grpc or one of the various application/grpc+ values.
.envoy.config.route.v3.RouteMatch.GrpcRouteMatchOptions grpc = 8;
-
clearGrpc
If specified, only gRPC requests will be matched. The router will check that the content-type header has a application/grpc or one of the various application/grpc+ values.
.envoy.config.route.v3.RouteMatch.GrpcRouteMatchOptions grpc = 8;
-
getGrpcBuilder
If specified, only gRPC requests will be matched. The router will check that the content-type header has a application/grpc or one of the various application/grpc+ values.
.envoy.config.route.v3.RouteMatch.GrpcRouteMatchOptions grpc = 8;
-
getGrpcOrBuilder
If specified, only gRPC requests will be matched. The router will check that the content-type header has a application/grpc or one of the various application/grpc+ values.
.envoy.config.route.v3.RouteMatch.GrpcRouteMatchOptions grpc = 8;
- Specified by:
getGrpcOrBuilder
in interfaceRouteMatchOrBuilder
-
internalGetGrpcFieldBuilder
private com.google.protobuf.SingleFieldBuilder<RouteMatch.GrpcRouteMatchOptions,RouteMatch.GrpcRouteMatchOptions.Builder, internalGetGrpcFieldBuilder()RouteMatch.GrpcRouteMatchOptionsOrBuilder> If specified, only gRPC requests will be matched. The router will check that the content-type header has a application/grpc or one of the various application/grpc+ values.
.envoy.config.route.v3.RouteMatch.GrpcRouteMatchOptions grpc = 8;
-
hasTlsContext
public boolean hasTlsContext()If specified, the client tls context will be matched against the defined match options. [#next-major-version: unify with RBAC]
.envoy.config.route.v3.RouteMatch.TlsContextMatchOptions tls_context = 11;
- Specified by:
hasTlsContext
in interfaceRouteMatchOrBuilder
- Returns:
- Whether the tlsContext field is set.
-
getTlsContext
If specified, the client tls context will be matched against the defined match options. [#next-major-version: unify with RBAC]
.envoy.config.route.v3.RouteMatch.TlsContextMatchOptions tls_context = 11;
- Specified by:
getTlsContext
in interfaceRouteMatchOrBuilder
- Returns:
- The tlsContext.
-
setTlsContext
If specified, the client tls context will be matched against the defined match options. [#next-major-version: unify with RBAC]
.envoy.config.route.v3.RouteMatch.TlsContextMatchOptions tls_context = 11;
-
setTlsContext
If specified, the client tls context will be matched against the defined match options. [#next-major-version: unify with RBAC]
.envoy.config.route.v3.RouteMatch.TlsContextMatchOptions tls_context = 11;
-
mergeTlsContext
If specified, the client tls context will be matched against the defined match options. [#next-major-version: unify with RBAC]
.envoy.config.route.v3.RouteMatch.TlsContextMatchOptions tls_context = 11;
-
clearTlsContext
If specified, the client tls context will be matched against the defined match options. [#next-major-version: unify with RBAC]
.envoy.config.route.v3.RouteMatch.TlsContextMatchOptions tls_context = 11;
-
getTlsContextBuilder
If specified, the client tls context will be matched against the defined match options. [#next-major-version: unify with RBAC]
.envoy.config.route.v3.RouteMatch.TlsContextMatchOptions tls_context = 11;
-
getTlsContextOrBuilder
If specified, the client tls context will be matched against the defined match options. [#next-major-version: unify with RBAC]
.envoy.config.route.v3.RouteMatch.TlsContextMatchOptions tls_context = 11;
- Specified by:
getTlsContextOrBuilder
in interfaceRouteMatchOrBuilder
-
internalGetTlsContextFieldBuilder
private com.google.protobuf.SingleFieldBuilder<RouteMatch.TlsContextMatchOptions,RouteMatch.TlsContextMatchOptions.Builder, internalGetTlsContextFieldBuilder()RouteMatch.TlsContextMatchOptionsOrBuilder> If specified, the client tls context will be matched against the defined match options. [#next-major-version: unify with RBAC]
.envoy.config.route.v3.RouteMatch.TlsContextMatchOptions tls_context = 11;
-
ensureDynamicMetadataIsMutable
private void ensureDynamicMetadataIsMutable() -
getDynamicMetadataList
Specifies a set of dynamic metadata matchers on which the route should match. The router will check the dynamic metadata against all the specified dynamic metadata matchers. If the number of specified dynamic metadata matchers is nonzero, they all must match the dynamic metadata for a match to occur.
repeated .envoy.type.matcher.v3.MetadataMatcher dynamic_metadata = 13;
- Specified by:
getDynamicMetadataList
in interfaceRouteMatchOrBuilder
-
getDynamicMetadataCount
public int getDynamicMetadataCount()Specifies a set of dynamic metadata matchers on which the route should match. The router will check the dynamic metadata against all the specified dynamic metadata matchers. If the number of specified dynamic metadata matchers is nonzero, they all must match the dynamic metadata for a match to occur.
repeated .envoy.type.matcher.v3.MetadataMatcher dynamic_metadata = 13;
- Specified by:
getDynamicMetadataCount
in interfaceRouteMatchOrBuilder
-
getDynamicMetadata
Specifies a set of dynamic metadata matchers on which the route should match. The router will check the dynamic metadata against all the specified dynamic metadata matchers. If the number of specified dynamic metadata matchers is nonzero, they all must match the dynamic metadata for a match to occur.
repeated .envoy.type.matcher.v3.MetadataMatcher dynamic_metadata = 13;
- Specified by:
getDynamicMetadata
in interfaceRouteMatchOrBuilder
-
setDynamicMetadata
Specifies a set of dynamic metadata matchers on which the route should match. The router will check the dynamic metadata against all the specified dynamic metadata matchers. If the number of specified dynamic metadata matchers is nonzero, they all must match the dynamic metadata for a match to occur.
repeated .envoy.type.matcher.v3.MetadataMatcher dynamic_metadata = 13;
-
setDynamicMetadata
Specifies a set of dynamic metadata matchers on which the route should match. The router will check the dynamic metadata against all the specified dynamic metadata matchers. If the number of specified dynamic metadata matchers is nonzero, they all must match the dynamic metadata for a match to occur.
repeated .envoy.type.matcher.v3.MetadataMatcher dynamic_metadata = 13;
-
addDynamicMetadata
Specifies a set of dynamic metadata matchers on which the route should match. The router will check the dynamic metadata against all the specified dynamic metadata matchers. If the number of specified dynamic metadata matchers is nonzero, they all must match the dynamic metadata for a match to occur.
repeated .envoy.type.matcher.v3.MetadataMatcher dynamic_metadata = 13;
-
addDynamicMetadata
Specifies a set of dynamic metadata matchers on which the route should match. The router will check the dynamic metadata against all the specified dynamic metadata matchers. If the number of specified dynamic metadata matchers is nonzero, they all must match the dynamic metadata for a match to occur.
repeated .envoy.type.matcher.v3.MetadataMatcher dynamic_metadata = 13;
-
addDynamicMetadata
Specifies a set of dynamic metadata matchers on which the route should match. The router will check the dynamic metadata against all the specified dynamic metadata matchers. If the number of specified dynamic metadata matchers is nonzero, they all must match the dynamic metadata for a match to occur.
repeated .envoy.type.matcher.v3.MetadataMatcher dynamic_metadata = 13;
-
addDynamicMetadata
Specifies a set of dynamic metadata matchers on which the route should match. The router will check the dynamic metadata against all the specified dynamic metadata matchers. If the number of specified dynamic metadata matchers is nonzero, they all must match the dynamic metadata for a match to occur.
repeated .envoy.type.matcher.v3.MetadataMatcher dynamic_metadata = 13;
-
addAllDynamicMetadata
Specifies a set of dynamic metadata matchers on which the route should match. The router will check the dynamic metadata against all the specified dynamic metadata matchers. If the number of specified dynamic metadata matchers is nonzero, they all must match the dynamic metadata for a match to occur.
repeated .envoy.type.matcher.v3.MetadataMatcher dynamic_metadata = 13;
-
clearDynamicMetadata
Specifies a set of dynamic metadata matchers on which the route should match. The router will check the dynamic metadata against all the specified dynamic metadata matchers. If the number of specified dynamic metadata matchers is nonzero, they all must match the dynamic metadata for a match to occur.
repeated .envoy.type.matcher.v3.MetadataMatcher dynamic_metadata = 13;
-
removeDynamicMetadata
Specifies a set of dynamic metadata matchers on which the route should match. The router will check the dynamic metadata against all the specified dynamic metadata matchers. If the number of specified dynamic metadata matchers is nonzero, they all must match the dynamic metadata for a match to occur.
repeated .envoy.type.matcher.v3.MetadataMatcher dynamic_metadata = 13;
-
getDynamicMetadataBuilder
Specifies a set of dynamic metadata matchers on which the route should match. The router will check the dynamic metadata against all the specified dynamic metadata matchers. If the number of specified dynamic metadata matchers is nonzero, they all must match the dynamic metadata for a match to occur.
repeated .envoy.type.matcher.v3.MetadataMatcher dynamic_metadata = 13;
-
getDynamicMetadataOrBuilder
Specifies a set of dynamic metadata matchers on which the route should match. The router will check the dynamic metadata against all the specified dynamic metadata matchers. If the number of specified dynamic metadata matchers is nonzero, they all must match the dynamic metadata for a match to occur.
repeated .envoy.type.matcher.v3.MetadataMatcher dynamic_metadata = 13;
- Specified by:
getDynamicMetadataOrBuilder
in interfaceRouteMatchOrBuilder
-
getDynamicMetadataOrBuilderList
Specifies a set of dynamic metadata matchers on which the route should match. The router will check the dynamic metadata against all the specified dynamic metadata matchers. If the number of specified dynamic metadata matchers is nonzero, they all must match the dynamic metadata for a match to occur.
repeated .envoy.type.matcher.v3.MetadataMatcher dynamic_metadata = 13;
- Specified by:
getDynamicMetadataOrBuilderList
in interfaceRouteMatchOrBuilder
-
addDynamicMetadataBuilder
Specifies a set of dynamic metadata matchers on which the route should match. The router will check the dynamic metadata against all the specified dynamic metadata matchers. If the number of specified dynamic metadata matchers is nonzero, they all must match the dynamic metadata for a match to occur.
repeated .envoy.type.matcher.v3.MetadataMatcher dynamic_metadata = 13;
-
addDynamicMetadataBuilder
Specifies a set of dynamic metadata matchers on which the route should match. The router will check the dynamic metadata against all the specified dynamic metadata matchers. If the number of specified dynamic metadata matchers is nonzero, they all must match the dynamic metadata for a match to occur.
repeated .envoy.type.matcher.v3.MetadataMatcher dynamic_metadata = 13;
-
getDynamicMetadataBuilderList
Specifies a set of dynamic metadata matchers on which the route should match. The router will check the dynamic metadata against all the specified dynamic metadata matchers. If the number of specified dynamic metadata matchers is nonzero, they all must match the dynamic metadata for a match to occur.
repeated .envoy.type.matcher.v3.MetadataMatcher dynamic_metadata = 13;
-
internalGetDynamicMetadataFieldBuilder
private com.google.protobuf.RepeatedFieldBuilder<MetadataMatcher,MetadataMatcher.Builder, internalGetDynamicMetadataFieldBuilder()MetadataMatcherOrBuilder>
-