类 VirtualServiceOuterClass.HTTPMatchRequest.Builder
java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>
com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>
istio.networking.v1alpha3.VirtualServiceOuterClass.HTTPMatchRequest.Builder
- 所有已实现的接口:
com.google.protobuf.Message.Builder,com.google.protobuf.MessageLite.Builder,com.google.protobuf.MessageLiteOrBuilder,com.google.protobuf.MessageOrBuilder,VirtualServiceOuterClass.HTTPMatchRequestOrBuilder,Cloneable
public static final class VirtualServiceOuterClass.HTTPMatchRequest.Builder
extends com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>
implements VirtualServiceOuterClass.HTTPMatchRequestOrBuilder
HttpMatchRequest specifies a set of criterion to be met in order for the
rule to be applied to the HTTP request. For example, the following
restricts the rule to match only requests where the URL path
starts with /ratings/v2/ and the request contains a custom `end-user` header
with value `jason`.
{{<tabset category-name="example">}}
{{<tab name="v1alpha3" category-value="v1alpha3">}}
```yaml
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
name: ratings-route
spec:
hosts:
- ratings.prod.svc.cluster.local
http:
- match:
- headers:
end-user:
exact: jason
uri:
prefix: "/ratings/v2/"
ignoreUriCase: true
route:
- destination:
host: ratings.prod.svc.cluster.local
```
{{</tab>}}
{{<tab name="v1beta1" category-value="v1beta1">}}
```yaml
apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
name: ratings-route
spec:
hosts:
- ratings.prod.svc.cluster.local
http:
- match:
- headers:
end-user:
exact: jason
uri:
prefix: "/ratings/v2/"
ignoreUriCase: true
route:
- destination:
host: ratings.prod.svc.cluster.local
```
{{</tab>}}
{{</tabset>}}
HTTPMatchRequest CANNOT be empty.
**Note:** No regex string match can be set when delegate VirtualService is specified.
Protobuf type istio.networking.v1alpha3.HTTPMatchRequest-
方法概要
修饰符和类型方法说明addAllGateways(Iterable<String> values) Names of gateways where the rule should be applied.addGateways(String value) Names of gateways where the rule should be applied.addGatewaysBytes(com.google.protobuf.ByteString value) Names of gateways where the rule should be applied.addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value) build()clear()HTTP Authority values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchclearField(com.google.protobuf.Descriptors.FieldDescriptor field) Names of gateways where the rule should be applied.Flag to specify whether the URI matching should be case-insensitive.HTTP Method values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchThe name assigned to a match.clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof) Specifies the ports on the host that is being addressed.URI Scheme values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchSource namespace constraining the applicability of a rule to workloads in that namespace.clearUri()URI to match values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match **Note:** Case-insensitive matching could be enabled via the `ignore_uri_case` flag.clone()booleancontainsHeaders(String key) The header keys must be lowercase and use hyphen as the separator, e.g.booleanQuery parameters for matching.booleanOne or more labels that constrain the applicability of a rule to workloads with the given labels.booleanwithoutHeader has the same syntax with the header, but has opposite meaning.HTTP Authority values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchHTTP Authority values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchHTTP Authority values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchstatic final com.google.protobuf.Descriptors.Descriptorcom.google.protobuf.Descriptors.DescriptorgetGateways(int index) Names of gateways where the rule should be applied.com.google.protobuf.ByteStringgetGatewaysBytes(int index) Names of gateways where the rule should be applied.intNames of gateways where the rule should be applied.com.google.protobuf.ProtocolStringListNames of gateways where the rule should be applied.已过时。intThe header keys must be lowercase and use hyphen as the separator, e.g.The header keys must be lowercase and use hyphen as the separator, e.g.getHeadersOrDefault(String key, VirtualServiceOuterClass.StringMatch defaultValue) The header keys must be lowercase and use hyphen as the separator, e.g.getHeadersOrThrow(String key) The header keys must be lowercase and use hyphen as the separator, e.g.booleanFlag to specify whether the URI matching should be case-insensitive.HTTP Method values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchHTTP Method values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchHTTP Method values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match已过时。已过时。已过时。已过时。getName()The name assigned to a match.com.google.protobuf.ByteStringThe name assigned to a match.intgetPort()Specifies the ports on the host that is being addressed.已过时。intQuery parameters for matching.Query parameters for matching.getQueryParamsOrDefault(String key, VirtualServiceOuterClass.StringMatch defaultValue) Query parameters for matching.Query parameters for matching.URI Scheme values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchURI Scheme values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchURI Scheme values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match已过时。intOne or more labels that constrain the applicability of a rule to workloads with the given labels.One or more labels that constrain the applicability of a rule to workloads with the given labels.getSourceLabelsOrDefault(String key, String defaultValue) One or more labels that constrain the applicability of a rule to workloads with the given labels.One or more labels that constrain the applicability of a rule to workloads with the given labels.Source namespace constraining the applicability of a rule to workloads in that namespace.com.google.protobuf.ByteStringSource namespace constraining the applicability of a rule to workloads in that namespace.getUri()URI to match values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match **Note:** Case-insensitive matching could be enabled via the `ignore_uri_case` flag.URI to match values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match **Note:** Case-insensitive matching could be enabled via the `ignore_uri_case` flag.URI to match values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match **Note:** Case-insensitive matching could be enabled via the `ignore_uri_case` flag.已过时。intwithoutHeader has the same syntax with the header, but has opposite meaning.withoutHeader has the same syntax with the header, but has opposite meaning.getWithoutHeadersOrDefault(String key, VirtualServiceOuterClass.StringMatch defaultValue) withoutHeader has the same syntax with the header, but has opposite meaning.withoutHeader has the same syntax with the header, but has opposite meaning.booleanHTTP Authority values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchbooleanHTTP Method values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchbooleanURI Scheme values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchbooleanhasUri()URI to match values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match **Note:** Case-insensitive matching could be enabled via the `ignore_uri_case` flag.protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTableprotected com.google.protobuf.MapFieldReflectionAccessorinternalGetMapFieldReflection(int number) protected com.google.protobuf.MapFieldReflectionAccessorinternalGetMutableMapFieldReflection(int number) final booleanHTTP Authority values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchmergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) mergeFrom(com.google.protobuf.Message other) HTTP Method values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchURI Scheme values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchmergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) URI to match values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match **Note:** Case-insensitive matching could be enabled via the `ignore_uri_case` flag.The header keys must be lowercase and use hyphen as the separator, e.g.Query parameters for matching.putAllSourceLabels(Map<String, String> values) One or more labels that constrain the applicability of a rule to workloads with the given labels.withoutHeader has the same syntax with the header, but has opposite meaning.putHeaders(String key, VirtualServiceOuterClass.StringMatch value) The header keys must be lowercase and use hyphen as the separator, e.g.The header keys must be lowercase and use hyphen as the separator, e.g.putQueryParams(String key, VirtualServiceOuterClass.StringMatch value) Query parameters for matching.Query parameters for matching.putSourceLabels(String key, String value) One or more labels that constrain the applicability of a rule to workloads with the given labels.withoutHeader has the same syntax with the header, but has opposite meaning.withoutHeader has the same syntax with the header, but has opposite meaning.removeHeaders(String key) The header keys must be lowercase and use hyphen as the separator, e.g.removeQueryParams(String key) Query parameters for matching.removeSourceLabels(String key) One or more labels that constrain the applicability of a rule to workloads with the given labels.withoutHeader has the same syntax with the header, but has opposite meaning.HTTP Authority values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchsetAuthority(VirtualServiceOuterClass.StringMatch.Builder builderForValue) HTTP Authority values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchsetGateways(int index, String value) Names of gateways where the rule should be applied.setIgnoreUriCase(boolean value) Flag to specify whether the URI matching should be case-insensitive.HTTP Method values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchsetMethod(VirtualServiceOuterClass.StringMatch.Builder builderForValue) HTTP Method values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchThe name assigned to a match.setNameBytes(com.google.protobuf.ByteString value) The name assigned to a match.setPort(int value) Specifies the ports on the host that is being addressed.setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value) URI Scheme values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchsetScheme(VirtualServiceOuterClass.StringMatch.Builder builderForValue) URI Scheme values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based matchsetSourceNamespace(String value) Source namespace constraining the applicability of a rule to workloads in that namespace.setSourceNamespaceBytes(com.google.protobuf.ByteString value) Source namespace constraining the applicability of a rule to workloads in that namespace.setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) URI to match values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match **Note:** Case-insensitive matching could be enabled via the `ignore_uri_case` flag.setUri(VirtualServiceOuterClass.StringMatch.Builder builderForValue) URI to match values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match **Note:** Case-insensitive matching could be enabled via the `ignore_uri_case` flag.从类继承的方法 com.google.protobuf.GeneratedMessageV3.Builder
getAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, getUnknownFieldSetBuilder, hasField, hasOneof, internalGetMapField, internalGetMutableMapField, isClean, markClean, mergeUnknownLengthDelimitedField, mergeUnknownVarintField, newBuilderForField, onBuilt, onChanged, parseUnknownField, setUnknownFieldSetBuilder, setUnknownFieldsProto3从类继承的方法 com.google.protobuf.AbstractMessage.Builder
findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toString从类继承的方法 com.google.protobuf.AbstractMessageLite.Builder
addAll, addAll, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, newUninitializedMessageException从接口继承的方法 com.google.protobuf.Message.Builder
mergeDelimitedFrom, mergeDelimitedFrom从接口继承的方法 com.google.protobuf.MessageLite.Builder
mergeFrom从接口继承的方法 com.google.protobuf.MessageOrBuilder
findInitializationErrors, getAllFields, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
-
方法详细资料
-
getDescriptor
public static final com.google.protobuf.Descriptors.Descriptor getDescriptor() -
internalGetMapFieldReflection
protected com.google.protobuf.MapFieldReflectionAccessor internalGetMapFieldReflection(int number) - 覆盖:
internalGetMapFieldReflection在类中com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>
-
internalGetMutableMapFieldReflection
protected com.google.protobuf.MapFieldReflectionAccessor internalGetMutableMapFieldReflection(int number) - 覆盖:
internalGetMutableMapFieldReflection在类中com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>
-
internalGetFieldAccessorTable
protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()- 指定者:
internalGetFieldAccessorTable在类中com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>
-
clear
- 指定者:
clear在接口中com.google.protobuf.Message.Builder- 指定者:
clear在接口中com.google.protobuf.MessageLite.Builder- 覆盖:
clear在类中com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>
-
getDescriptorForType
public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()- 指定者:
getDescriptorForType在接口中com.google.protobuf.Message.Builder- 指定者:
getDescriptorForType在接口中com.google.protobuf.MessageOrBuilder- 覆盖:
getDescriptorForType在类中com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>
-
getDefaultInstanceForType
- 指定者:
getDefaultInstanceForType在接口中com.google.protobuf.MessageLiteOrBuilder- 指定者:
getDefaultInstanceForType在接口中com.google.protobuf.MessageOrBuilder
-
build
- 指定者:
build在接口中com.google.protobuf.Message.Builder- 指定者:
build在接口中com.google.protobuf.MessageLite.Builder
-
buildPartial
- 指定者:
buildPartial在接口中com.google.protobuf.Message.Builder- 指定者:
buildPartial在接口中com.google.protobuf.MessageLite.Builder
-
clone
- 指定者:
clone在接口中com.google.protobuf.Message.Builder- 指定者:
clone在接口中com.google.protobuf.MessageLite.Builder- 覆盖:
clone在类中com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>
-
setField
public VirtualServiceOuterClass.HTTPMatchRequest.Builder setField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value) - 指定者:
setField在接口中com.google.protobuf.Message.Builder- 覆盖:
setField在类中com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>
-
clearField
public VirtualServiceOuterClass.HTTPMatchRequest.Builder clearField(com.google.protobuf.Descriptors.FieldDescriptor field) - 指定者:
clearField在接口中com.google.protobuf.Message.Builder- 覆盖:
clearField在类中com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>
-
clearOneof
public VirtualServiceOuterClass.HTTPMatchRequest.Builder clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof) - 指定者:
clearOneof在接口中com.google.protobuf.Message.Builder- 覆盖:
clearOneof在类中com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>
-
setRepeatedField
public VirtualServiceOuterClass.HTTPMatchRequest.Builder setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value) - 指定者:
setRepeatedField在接口中com.google.protobuf.Message.Builder- 覆盖:
setRepeatedField在类中com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>
-
addRepeatedField
public VirtualServiceOuterClass.HTTPMatchRequest.Builder addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value) - 指定者:
addRepeatedField在接口中com.google.protobuf.Message.Builder- 覆盖:
addRepeatedField在类中com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>
-
mergeFrom
public VirtualServiceOuterClass.HTTPMatchRequest.Builder mergeFrom(com.google.protobuf.Message other) - 指定者:
mergeFrom在接口中com.google.protobuf.Message.Builder- 覆盖:
mergeFrom在类中com.google.protobuf.AbstractMessage.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>
-
mergeFrom
public VirtualServiceOuterClass.HTTPMatchRequest.Builder mergeFrom(VirtualServiceOuterClass.HTTPMatchRequest other) -
isInitialized
public final boolean isInitialized()- 指定者:
isInitialized在接口中com.google.protobuf.MessageLiteOrBuilder- 覆盖:
isInitialized在类中com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>
-
mergeFrom
public VirtualServiceOuterClass.HTTPMatchRequest.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException - 指定者:
mergeFrom在接口中com.google.protobuf.Message.Builder- 指定者:
mergeFrom在接口中com.google.protobuf.MessageLite.Builder- 覆盖:
mergeFrom在类中com.google.protobuf.AbstractMessage.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>- 抛出:
IOException
-
getName
The name assigned to a match. The match's name will be concatenated with the parent route's name and will be logged in the access logs for requests matching this route.
string name = 11;- 指定者:
getName在接口中VirtualServiceOuterClass.HTTPMatchRequestOrBuilder- 返回:
- The name.
-
getNameBytes
public com.google.protobuf.ByteString getNameBytes()The name assigned to a match. The match's name will be concatenated with the parent route's name and will be logged in the access logs for requests matching this route.
string name = 11;- 指定者:
getNameBytes在接口中VirtualServiceOuterClass.HTTPMatchRequestOrBuilder- 返回:
- The bytes for name.
-
setName
The name assigned to a match. The match's name will be concatenated with the parent route's name and will be logged in the access logs for requests matching this route.
string name = 11;- 参数:
value- The name to set.- 返回:
- This builder for chaining.
-
clearName
The name assigned to a match. The match's name will be concatenated with the parent route's name and will be logged in the access logs for requests matching this route.
string name = 11;- 返回:
- This builder for chaining.
-
setNameBytes
public VirtualServiceOuterClass.HTTPMatchRequest.Builder setNameBytes(com.google.protobuf.ByteString value) The name assigned to a match. The match's name will be concatenated with the parent route's name and will be logged in the access logs for requests matching this route.
string name = 11;- 参数:
value- The bytes for name to set.- 返回:
- This builder for chaining.
-
hasUri
public boolean hasUri()URI to match values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match **Note:** Case-insensitive matching could be enabled via the `ignore_uri_case` flag.
.istio.networking.v1alpha3.StringMatch uri = 1;- 指定者:
hasUri在接口中VirtualServiceOuterClass.HTTPMatchRequestOrBuilder- 返回:
- Whether the uri field is set.
-
getUri
URI to match values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match **Note:** Case-insensitive matching could be enabled via the `ignore_uri_case` flag.
.istio.networking.v1alpha3.StringMatch uri = 1;- 指定者:
getUri在接口中VirtualServiceOuterClass.HTTPMatchRequestOrBuilder- 返回:
- The uri.
-
setUri
public VirtualServiceOuterClass.HTTPMatchRequest.Builder setUri(VirtualServiceOuterClass.StringMatch value) URI to match values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match **Note:** Case-insensitive matching could be enabled via the `ignore_uri_case` flag.
.istio.networking.v1alpha3.StringMatch uri = 1; -
setUri
public VirtualServiceOuterClass.HTTPMatchRequest.Builder setUri(VirtualServiceOuterClass.StringMatch.Builder builderForValue) URI to match values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match **Note:** Case-insensitive matching could be enabled via the `ignore_uri_case` flag.
.istio.networking.v1alpha3.StringMatch uri = 1; -
mergeUri
public VirtualServiceOuterClass.HTTPMatchRequest.Builder mergeUri(VirtualServiceOuterClass.StringMatch value) URI to match values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match **Note:** Case-insensitive matching could be enabled via the `ignore_uri_case` flag.
.istio.networking.v1alpha3.StringMatch uri = 1; -
clearUri
URI to match values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match **Note:** Case-insensitive matching could be enabled via the `ignore_uri_case` flag.
.istio.networking.v1alpha3.StringMatch uri = 1; -
getUriBuilder
URI to match values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match **Note:** Case-insensitive matching could be enabled via the `ignore_uri_case` flag.
.istio.networking.v1alpha3.StringMatch uri = 1; -
getUriOrBuilder
URI to match values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match **Note:** Case-insensitive matching could be enabled via the `ignore_uri_case` flag.
.istio.networking.v1alpha3.StringMatch uri = 1; -
hasScheme
public boolean hasScheme()URI Scheme values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch scheme = 2;- 指定者:
hasScheme在接口中VirtualServiceOuterClass.HTTPMatchRequestOrBuilder- 返回:
- Whether the scheme field is set.
-
getScheme
URI Scheme values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch scheme = 2;- 指定者:
getScheme在接口中VirtualServiceOuterClass.HTTPMatchRequestOrBuilder- 返回:
- The scheme.
-
setScheme
public VirtualServiceOuterClass.HTTPMatchRequest.Builder setScheme(VirtualServiceOuterClass.StringMatch value) URI Scheme values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch scheme = 2; -
setScheme
public VirtualServiceOuterClass.HTTPMatchRequest.Builder setScheme(VirtualServiceOuterClass.StringMatch.Builder builderForValue) URI Scheme values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch scheme = 2; -
mergeScheme
public VirtualServiceOuterClass.HTTPMatchRequest.Builder mergeScheme(VirtualServiceOuterClass.StringMatch value) URI Scheme values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch scheme = 2; -
clearScheme
URI Scheme values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch scheme = 2; -
getSchemeBuilder
URI Scheme values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch scheme = 2; -
getSchemeOrBuilder
URI Scheme values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch scheme = 2; -
hasMethod
public boolean hasMethod()HTTP Method values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch method = 3;- 指定者:
hasMethod在接口中VirtualServiceOuterClass.HTTPMatchRequestOrBuilder- 返回:
- Whether the method field is set.
-
getMethod
HTTP Method values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch method = 3;- 指定者:
getMethod在接口中VirtualServiceOuterClass.HTTPMatchRequestOrBuilder- 返回:
- The method.
-
setMethod
public VirtualServiceOuterClass.HTTPMatchRequest.Builder setMethod(VirtualServiceOuterClass.StringMatch value) HTTP Method values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch method = 3; -
setMethod
public VirtualServiceOuterClass.HTTPMatchRequest.Builder setMethod(VirtualServiceOuterClass.StringMatch.Builder builderForValue) HTTP Method values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch method = 3; -
mergeMethod
public VirtualServiceOuterClass.HTTPMatchRequest.Builder mergeMethod(VirtualServiceOuterClass.StringMatch value) HTTP Method values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch method = 3; -
clearMethod
HTTP Method values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch method = 3; -
getMethodBuilder
HTTP Method values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch method = 3; -
getMethodOrBuilder
HTTP Method values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch method = 3; -
hasAuthority
public boolean hasAuthority()HTTP Authority values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch authority = 4;- 指定者:
hasAuthority在接口中VirtualServiceOuterClass.HTTPMatchRequestOrBuilder- 返回:
- Whether the authority field is set.
-
getAuthority
HTTP Authority values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch authority = 4;- 指定者:
getAuthority在接口中VirtualServiceOuterClass.HTTPMatchRequestOrBuilder- 返回:
- The authority.
-
setAuthority
public VirtualServiceOuterClass.HTTPMatchRequest.Builder setAuthority(VirtualServiceOuterClass.StringMatch value) HTTP Authority values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch authority = 4; -
setAuthority
public VirtualServiceOuterClass.HTTPMatchRequest.Builder setAuthority(VirtualServiceOuterClass.StringMatch.Builder builderForValue) HTTP Authority values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch authority = 4; -
mergeAuthority
public VirtualServiceOuterClass.HTTPMatchRequest.Builder mergeAuthority(VirtualServiceOuterClass.StringMatch value) HTTP Authority values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch authority = 4; -
clearAuthority
HTTP Authority values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch authority = 4; -
getAuthorityBuilder
HTTP Authority values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch authority = 4; -
getAuthorityOrBuilder
HTTP Authority values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match
.istio.networking.v1alpha3.StringMatch authority = 4; -
getHeadersCount
public int getHeadersCount()The header keys must be lowercase and use hyphen as the separator, e.g. _x-request-id_. Header values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match If the value is empty and only the name of header is specfied, presence of the header is checked. **Note:** The keys `uri`, `scheme`, `method`, and `authority` will be ignored.
map<string, .istio.networking.v1alpha3.StringMatch> headers = 5; -
containsHeaders
The header keys must be lowercase and use hyphen as the separator, e.g. _x-request-id_. Header values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match If the value is empty and only the name of header is specfied, presence of the header is checked. **Note:** The keys `uri`, `scheme`, `method`, and `authority` will be ignored.
map<string, .istio.networking.v1alpha3.StringMatch> headers = 5; -
getHeaders
已过时。UsegetHeadersMap()instead. -
getHeadersMap
The header keys must be lowercase and use hyphen as the separator, e.g. _x-request-id_. Header values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match If the value is empty and only the name of header is specfied, presence of the header is checked. **Note:** The keys `uri`, `scheme`, `method`, and `authority` will be ignored.
map<string, .istio.networking.v1alpha3.StringMatch> headers = 5; -
getHeadersOrDefault
public VirtualServiceOuterClass.StringMatch getHeadersOrDefault(String key, VirtualServiceOuterClass.StringMatch defaultValue) The header keys must be lowercase and use hyphen as the separator, e.g. _x-request-id_. Header values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match If the value is empty and only the name of header is specfied, presence of the header is checked. **Note:** The keys `uri`, `scheme`, `method`, and `authority` will be ignored.
map<string, .istio.networking.v1alpha3.StringMatch> headers = 5; -
getHeadersOrThrow
The header keys must be lowercase and use hyphen as the separator, e.g. _x-request-id_. Header values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match If the value is empty and only the name of header is specfied, presence of the header is checked. **Note:** The keys `uri`, `scheme`, `method`, and `authority` will be ignored.
map<string, .istio.networking.v1alpha3.StringMatch> headers = 5; -
clearHeaders
-
removeHeaders
The header keys must be lowercase and use hyphen as the separator, e.g. _x-request-id_. Header values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match If the value is empty and only the name of header is specfied, presence of the header is checked. **Note:** The keys `uri`, `scheme`, `method`, and `authority` will be ignored.
map<string, .istio.networking.v1alpha3.StringMatch> headers = 5; -
getMutableHeaders
已过时。Use alternate mutation accessors instead. -
putHeaders
public VirtualServiceOuterClass.HTTPMatchRequest.Builder putHeaders(String key, VirtualServiceOuterClass.StringMatch value) The header keys must be lowercase and use hyphen as the separator, e.g. _x-request-id_. Header values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match If the value is empty and only the name of header is specfied, presence of the header is checked. **Note:** The keys `uri`, `scheme`, `method`, and `authority` will be ignored.
map<string, .istio.networking.v1alpha3.StringMatch> headers = 5; -
putAllHeaders
public VirtualServiceOuterClass.HTTPMatchRequest.Builder putAllHeaders(Map<String, VirtualServiceOuterClass.StringMatch> values) The header keys must be lowercase and use hyphen as the separator, e.g. _x-request-id_. Header values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match If the value is empty and only the name of header is specfied, presence of the header is checked. **Note:** The keys `uri`, `scheme`, `method`, and `authority` will be ignored.
map<string, .istio.networking.v1alpha3.StringMatch> headers = 5; -
putHeadersBuilderIfAbsent
The header keys must be lowercase and use hyphen as the separator, e.g. _x-request-id_. Header values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for ECMAscript style regex-based match If the value is empty and only the name of header is specfied, presence of the header is checked. **Note:** The keys `uri`, `scheme`, `method`, and `authority` will be ignored.
map<string, .istio.networking.v1alpha3.StringMatch> headers = 5; -
getPort
public int getPort()Specifies the ports on the host that is being addressed. Many services only expose a single port or label ports with the protocols they support, in these cases it is not required to explicitly select the port.
uint32 port = 6;- 指定者:
getPort在接口中VirtualServiceOuterClass.HTTPMatchRequestOrBuilder- 返回:
- The port.
-
setPort
Specifies the ports on the host that is being addressed. Many services only expose a single port or label ports with the protocols they support, in these cases it is not required to explicitly select the port.
uint32 port = 6;- 参数:
value- The port to set.- 返回:
- This builder for chaining.
-
clearPort
Specifies the ports on the host that is being addressed. Many services only expose a single port or label ports with the protocols they support, in these cases it is not required to explicitly select the port.
uint32 port = 6;- 返回:
- This builder for chaining.
-
getSourceLabelsCount
public int getSourceLabelsCount()One or more labels that constrain the applicability of a rule to workloads with the given labels. If the VirtualService has a list of gateways specified in the top-level `gateways` field, it must include the reserved gateway `mesh` for this field to be applicable.
map<string, string> source_labels = 7; -
containsSourceLabels
One or more labels that constrain the applicability of a rule to workloads with the given labels. If the VirtualService has a list of gateways specified in the top-level `gateways` field, it must include the reserved gateway `mesh` for this field to be applicable.
map<string, string> source_labels = 7; -
getSourceLabels
已过时。UsegetSourceLabelsMap()instead. -
getSourceLabelsMap
One or more labels that constrain the applicability of a rule to workloads with the given labels. If the VirtualService has a list of gateways specified in the top-level `gateways` field, it must include the reserved gateway `mesh` for this field to be applicable.
map<string, string> source_labels = 7; -
getSourceLabelsOrDefault
One or more labels that constrain the applicability of a rule to workloads with the given labels. If the VirtualService has a list of gateways specified in the top-level `gateways` field, it must include the reserved gateway `mesh` for this field to be applicable.
map<string, string> source_labels = 7; -
getSourceLabelsOrThrow
One or more labels that constrain the applicability of a rule to workloads with the given labels. If the VirtualService has a list of gateways specified in the top-level `gateways` field, it must include the reserved gateway `mesh` for this field to be applicable.
map<string, string> source_labels = 7; -
clearSourceLabels
-
removeSourceLabels
One or more labels that constrain the applicability of a rule to workloads with the given labels. If the VirtualService has a list of gateways specified in the top-level `gateways` field, it must include the reserved gateway `mesh` for this field to be applicable.
map<string, string> source_labels = 7; -
getMutableSourceLabels
已过时。Use alternate mutation accessors instead. -
putSourceLabels
One or more labels that constrain the applicability of a rule to workloads with the given labels. If the VirtualService has a list of gateways specified in the top-level `gateways` field, it must include the reserved gateway `mesh` for this field to be applicable.
map<string, string> source_labels = 7; -
putAllSourceLabels
public VirtualServiceOuterClass.HTTPMatchRequest.Builder putAllSourceLabels(Map<String, String> values) One or more labels that constrain the applicability of a rule to workloads with the given labels. If the VirtualService has a list of gateways specified in the top-level `gateways` field, it must include the reserved gateway `mesh` for this field to be applicable.
map<string, string> source_labels = 7; -
getGatewaysList
public com.google.protobuf.ProtocolStringList getGatewaysList()Names of gateways where the rule should be applied. Gateway names in the top-level `gateways` field of the VirtualService (if any) are overridden. The gateway match is independent of sourceLabels.
repeated string gateways = 8;- 指定者:
getGatewaysList在接口中VirtualServiceOuterClass.HTTPMatchRequestOrBuilder- 返回:
- A list containing the gateways.
-
getGatewaysCount
public int getGatewaysCount()Names of gateways where the rule should be applied. Gateway names in the top-level `gateways` field of the VirtualService (if any) are overridden. The gateway match is independent of sourceLabels.
repeated string gateways = 8;- 指定者:
getGatewaysCount在接口中VirtualServiceOuterClass.HTTPMatchRequestOrBuilder- 返回:
- The count of gateways.
-
getGateways
Names of gateways where the rule should be applied. Gateway names in the top-level `gateways` field of the VirtualService (if any) are overridden. The gateway match is independent of sourceLabels.
repeated string gateways = 8;- 指定者:
getGateways在接口中VirtualServiceOuterClass.HTTPMatchRequestOrBuilder- 参数:
index- The index of the element to return.- 返回:
- The gateways at the given index.
-
getGatewaysBytes
public com.google.protobuf.ByteString getGatewaysBytes(int index) Names of gateways where the rule should be applied. Gateway names in the top-level `gateways` field of the VirtualService (if any) are overridden. The gateway match is independent of sourceLabels.
repeated string gateways = 8;- 指定者:
getGatewaysBytes在接口中VirtualServiceOuterClass.HTTPMatchRequestOrBuilder- 参数:
index- The index of the value to return.- 返回:
- The bytes of the gateways at the given index.
-
setGateways
Names of gateways where the rule should be applied. Gateway names in the top-level `gateways` field of the VirtualService (if any) are overridden. The gateway match is independent of sourceLabels.
repeated string gateways = 8;- 参数:
index- The index to set the value at.value- The gateways to set.- 返回:
- This builder for chaining.
-
addGateways
Names of gateways where the rule should be applied. Gateway names in the top-level `gateways` field of the VirtualService (if any) are overridden. The gateway match is independent of sourceLabels.
repeated string gateways = 8;- 参数:
value- The gateways to add.- 返回:
- This builder for chaining.
-
addAllGateways
Names of gateways where the rule should be applied. Gateway names in the top-level `gateways` field of the VirtualService (if any) are overridden. The gateway match is independent of sourceLabels.
repeated string gateways = 8;- 参数:
values- The gateways to add.- 返回:
- This builder for chaining.
-
clearGateways
Names of gateways where the rule should be applied. Gateway names in the top-level `gateways` field of the VirtualService (if any) are overridden. The gateway match is independent of sourceLabels.
repeated string gateways = 8;- 返回:
- This builder for chaining.
-
addGatewaysBytes
public VirtualServiceOuterClass.HTTPMatchRequest.Builder addGatewaysBytes(com.google.protobuf.ByteString value) Names of gateways where the rule should be applied. Gateway names in the top-level `gateways` field of the VirtualService (if any) are overridden. The gateway match is independent of sourceLabels.
repeated string gateways = 8;- 参数:
value- The bytes of the gateways to add.- 返回:
- This builder for chaining.
-
getQueryParamsCount
public int getQueryParamsCount()Query parameters for matching. Ex: - For a query parameter like "?key=true", the map key would be "key" and the string match could be defined as `exact: "true"`. - For a query parameter like "?key", the map key would be "key" and the string match could be defined as `exact: ""`. - For a query parameter like "?key=123", the map key would be "key" and the string match could be defined as `regex: "\d+$"`. Note that this configuration will only match values like "123" but not "a123" or "123a". **Note:** `prefix` matching is currently not supported.
map<string, .istio.networking.v1alpha3.StringMatch> query_params = 9; -
containsQueryParams
Query parameters for matching. Ex: - For a query parameter like "?key=true", the map key would be "key" and the string match could be defined as `exact: "true"`. - For a query parameter like "?key", the map key would be "key" and the string match could be defined as `exact: ""`. - For a query parameter like "?key=123", the map key would be "key" and the string match could be defined as `regex: "\d+$"`. Note that this configuration will only match values like "123" but not "a123" or "123a". **Note:** `prefix` matching is currently not supported.
map<string, .istio.networking.v1alpha3.StringMatch> query_params = 9; -
getQueryParams
已过时。UsegetQueryParamsMap()instead. -
getQueryParamsMap
Query parameters for matching. Ex: - For a query parameter like "?key=true", the map key would be "key" and the string match could be defined as `exact: "true"`. - For a query parameter like "?key", the map key would be "key" and the string match could be defined as `exact: ""`. - For a query parameter like "?key=123", the map key would be "key" and the string match could be defined as `regex: "\d+$"`. Note that this configuration will only match values like "123" but not "a123" or "123a". **Note:** `prefix` matching is currently not supported.
map<string, .istio.networking.v1alpha3.StringMatch> query_params = 9; -
getQueryParamsOrDefault
public VirtualServiceOuterClass.StringMatch getQueryParamsOrDefault(String key, VirtualServiceOuterClass.StringMatch defaultValue) Query parameters for matching. Ex: - For a query parameter like "?key=true", the map key would be "key" and the string match could be defined as `exact: "true"`. - For a query parameter like "?key", the map key would be "key" and the string match could be defined as `exact: ""`. - For a query parameter like "?key=123", the map key would be "key" and the string match could be defined as `regex: "\d+$"`. Note that this configuration will only match values like "123" but not "a123" or "123a". **Note:** `prefix` matching is currently not supported.
map<string, .istio.networking.v1alpha3.StringMatch> query_params = 9; -
getQueryParamsOrThrow
Query parameters for matching. Ex: - For a query parameter like "?key=true", the map key would be "key" and the string match could be defined as `exact: "true"`. - For a query parameter like "?key", the map key would be "key" and the string match could be defined as `exact: ""`. - For a query parameter like "?key=123", the map key would be "key" and the string match could be defined as `regex: "\d+$"`. Note that this configuration will only match values like "123" but not "a123" or "123a". **Note:** `prefix` matching is currently not supported.
map<string, .istio.networking.v1alpha3.StringMatch> query_params = 9; -
clearQueryParams
-
removeQueryParams
Query parameters for matching. Ex: - For a query parameter like "?key=true", the map key would be "key" and the string match could be defined as `exact: "true"`. - For a query parameter like "?key", the map key would be "key" and the string match could be defined as `exact: ""`. - For a query parameter like "?key=123", the map key would be "key" and the string match could be defined as `regex: "\d+$"`. Note that this configuration will only match values like "123" but not "a123" or "123a". **Note:** `prefix` matching is currently not supported.
map<string, .istio.networking.v1alpha3.StringMatch> query_params = 9; -
getMutableQueryParams
已过时。Use alternate mutation accessors instead. -
putQueryParams
public VirtualServiceOuterClass.HTTPMatchRequest.Builder putQueryParams(String key, VirtualServiceOuterClass.StringMatch value) Query parameters for matching. Ex: - For a query parameter like "?key=true", the map key would be "key" and the string match could be defined as `exact: "true"`. - For a query parameter like "?key", the map key would be "key" and the string match could be defined as `exact: ""`. - For a query parameter like "?key=123", the map key would be "key" and the string match could be defined as `regex: "\d+$"`. Note that this configuration will only match values like "123" but not "a123" or "123a". **Note:** `prefix` matching is currently not supported.
map<string, .istio.networking.v1alpha3.StringMatch> query_params = 9; -
putAllQueryParams
public VirtualServiceOuterClass.HTTPMatchRequest.Builder putAllQueryParams(Map<String, VirtualServiceOuterClass.StringMatch> values) Query parameters for matching. Ex: - For a query parameter like "?key=true", the map key would be "key" and the string match could be defined as `exact: "true"`. - For a query parameter like "?key", the map key would be "key" and the string match could be defined as `exact: ""`. - For a query parameter like "?key=123", the map key would be "key" and the string match could be defined as `regex: "\d+$"`. Note that this configuration will only match values like "123" but not "a123" or "123a". **Note:** `prefix` matching is currently not supported.
map<string, .istio.networking.v1alpha3.StringMatch> query_params = 9; -
putQueryParamsBuilderIfAbsent
Query parameters for matching. Ex: - For a query parameter like "?key=true", the map key would be "key" and the string match could be defined as `exact: "true"`. - For a query parameter like "?key", the map key would be "key" and the string match could be defined as `exact: ""`. - For a query parameter like "?key=123", the map key would be "key" and the string match could be defined as `regex: "\d+$"`. Note that this configuration will only match values like "123" but not "a123" or "123a". **Note:** `prefix` matching is currently not supported.
map<string, .istio.networking.v1alpha3.StringMatch> query_params = 9; -
getIgnoreUriCase
public boolean getIgnoreUriCase()Flag to specify whether the URI matching should be case-insensitive. **Note:** The case will be ignored only in the case of `exact` and `prefix` URI matches.
bool ignore_uri_case = 10;- 指定者:
getIgnoreUriCase在接口中VirtualServiceOuterClass.HTTPMatchRequestOrBuilder- 返回:
- The ignoreUriCase.
-
setIgnoreUriCase
Flag to specify whether the URI matching should be case-insensitive. **Note:** The case will be ignored only in the case of `exact` and `prefix` URI matches.
bool ignore_uri_case = 10;- 参数:
value- The ignoreUriCase to set.- 返回:
- This builder for chaining.
-
clearIgnoreUriCase
Flag to specify whether the URI matching should be case-insensitive. **Note:** The case will be ignored only in the case of `exact` and `prefix` URI matches.
bool ignore_uri_case = 10;- 返回:
- This builder for chaining.
-
getWithoutHeadersCount
public int getWithoutHeadersCount()withoutHeader has the same syntax with the header, but has opposite meaning. If a header is matched with a matching rule among withoutHeader, the traffic becomes not matched one.
map<string, .istio.networking.v1alpha3.StringMatch> without_headers = 12; -
containsWithoutHeaders
withoutHeader has the same syntax with the header, but has opposite meaning. If a header is matched with a matching rule among withoutHeader, the traffic becomes not matched one.
map<string, .istio.networking.v1alpha3.StringMatch> without_headers = 12; -
getWithoutHeaders
已过时。UsegetWithoutHeadersMap()instead. -
getWithoutHeadersMap
withoutHeader has the same syntax with the header, but has opposite meaning. If a header is matched with a matching rule among withoutHeader, the traffic becomes not matched one.
map<string, .istio.networking.v1alpha3.StringMatch> without_headers = 12; -
getWithoutHeadersOrDefault
public VirtualServiceOuterClass.StringMatch getWithoutHeadersOrDefault(String key, VirtualServiceOuterClass.StringMatch defaultValue) withoutHeader has the same syntax with the header, but has opposite meaning. If a header is matched with a matching rule among withoutHeader, the traffic becomes not matched one.
map<string, .istio.networking.v1alpha3.StringMatch> without_headers = 12; -
getWithoutHeadersOrThrow
withoutHeader has the same syntax with the header, but has opposite meaning. If a header is matched with a matching rule among withoutHeader, the traffic becomes not matched one.
map<string, .istio.networking.v1alpha3.StringMatch> without_headers = 12; -
clearWithoutHeaders
-
removeWithoutHeaders
withoutHeader has the same syntax with the header, but has opposite meaning. If a header is matched with a matching rule among withoutHeader, the traffic becomes not matched one.
map<string, .istio.networking.v1alpha3.StringMatch> without_headers = 12; -
getMutableWithoutHeaders
已过时。Use alternate mutation accessors instead. -
putWithoutHeaders
public VirtualServiceOuterClass.HTTPMatchRequest.Builder putWithoutHeaders(String key, VirtualServiceOuterClass.StringMatch value) withoutHeader has the same syntax with the header, but has opposite meaning. If a header is matched with a matching rule among withoutHeader, the traffic becomes not matched one.
map<string, .istio.networking.v1alpha3.StringMatch> without_headers = 12; -
putAllWithoutHeaders
public VirtualServiceOuterClass.HTTPMatchRequest.Builder putAllWithoutHeaders(Map<String, VirtualServiceOuterClass.StringMatch> values) withoutHeader has the same syntax with the header, but has opposite meaning. If a header is matched with a matching rule among withoutHeader, the traffic becomes not matched one.
map<string, .istio.networking.v1alpha3.StringMatch> without_headers = 12; -
putWithoutHeadersBuilderIfAbsent
withoutHeader has the same syntax with the header, but has opposite meaning. If a header is matched with a matching rule among withoutHeader, the traffic becomes not matched one.
map<string, .istio.networking.v1alpha3.StringMatch> without_headers = 12; -
getSourceNamespace
Source namespace constraining the applicability of a rule to workloads in that namespace. If the VirtualService has a list of gateways specified in the top-level `gateways` field, it must include the reserved gateway `mesh` for this field to be applicable.
string source_namespace = 13;- 指定者:
getSourceNamespace在接口中VirtualServiceOuterClass.HTTPMatchRequestOrBuilder- 返回:
- The sourceNamespace.
-
getSourceNamespaceBytes
public com.google.protobuf.ByteString getSourceNamespaceBytes()Source namespace constraining the applicability of a rule to workloads in that namespace. If the VirtualService has a list of gateways specified in the top-level `gateways` field, it must include the reserved gateway `mesh` for this field to be applicable.
string source_namespace = 13;- 指定者:
getSourceNamespaceBytes在接口中VirtualServiceOuterClass.HTTPMatchRequestOrBuilder- 返回:
- The bytes for sourceNamespace.
-
setSourceNamespace
Source namespace constraining the applicability of a rule to workloads in that namespace. If the VirtualService has a list of gateways specified in the top-level `gateways` field, it must include the reserved gateway `mesh` for this field to be applicable.
string source_namespace = 13;- 参数:
value- The sourceNamespace to set.- 返回:
- This builder for chaining.
-
clearSourceNamespace
Source namespace constraining the applicability of a rule to workloads in that namespace. If the VirtualService has a list of gateways specified in the top-level `gateways` field, it must include the reserved gateway `mesh` for this field to be applicable.
string source_namespace = 13;- 返回:
- This builder for chaining.
-
setSourceNamespaceBytes
public VirtualServiceOuterClass.HTTPMatchRequest.Builder setSourceNamespaceBytes(com.google.protobuf.ByteString value) Source namespace constraining the applicability of a rule to workloads in that namespace. If the VirtualService has a list of gateways specified in the top-level `gateways` field, it must include the reserved gateway `mesh` for this field to be applicable.
string source_namespace = 13;- 参数:
value- The bytes for sourceNamespace to set.- 返回:
- This builder for chaining.
-
setUnknownFields
public final VirtualServiceOuterClass.HTTPMatchRequest.Builder setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) - 指定者:
setUnknownFields在接口中com.google.protobuf.Message.Builder- 覆盖:
setUnknownFields在类中com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>
-
mergeUnknownFields
public final VirtualServiceOuterClass.HTTPMatchRequest.Builder mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) - 指定者:
mergeUnknownFields在接口中com.google.protobuf.Message.Builder- 覆盖:
mergeUnknownFields在类中com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.HTTPMatchRequest.Builder>
-