Class AwsRequestSigning.Builder
java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderT>
com.google.protobuf.GeneratedMessageV3.Builder<AwsRequestSigning.Builder>
io.envoyproxy.envoy.extensions.filters.http.aws_request_signing.v3.AwsRequestSigning.Builder
- All Implemented Interfaces:
com.google.protobuf.Message.Builder,com.google.protobuf.MessageLite.Builder,com.google.protobuf.MessageLiteOrBuilder,com.google.protobuf.MessageOrBuilder,AwsRequestSigningOrBuilder,Cloneable
- Enclosing class:
- AwsRequestSigning
public static final class AwsRequestSigning.Builder
extends com.google.protobuf.GeneratedMessageV3.Builder<AwsRequestSigning.Builder>
implements AwsRequestSigningOrBuilder
Top level configuration for the AWS request signing filter. [#next-free-field: 10]Protobuf type
envoy.extensions.filters.http.aws_request_signing.v3.AwsRequestSigning-
Method Summary
Modifier and TypeMethodDescriptionaddAllMatchExcludedHeaders(Iterable<? extends StringMatcher> values) A list of request header string matchers that will be excluded from signing.addAllMatchIncludedHeaders(Iterable<? extends StringMatcher> values) A list of request header string matchers that will be included during signing.addMatchExcludedHeaders(int index, StringMatcher value) A list of request header string matchers that will be excluded from signing.addMatchExcludedHeaders(int index, StringMatcher.Builder builderForValue) A list of request header string matchers that will be excluded from signing.A list of request header string matchers that will be excluded from signing.addMatchExcludedHeaders(StringMatcher.Builder builderForValue) A list of request header string matchers that will be excluded from signing.A list of request header string matchers that will be excluded from signing.addMatchExcludedHeadersBuilder(int index) A list of request header string matchers that will be excluded from signing.addMatchIncludedHeaders(int index, StringMatcher value) A list of request header string matchers that will be included during signing.addMatchIncludedHeaders(int index, StringMatcher.Builder builderForValue) A list of request header string matchers that will be included during signing.A list of request header string matchers that will be included during signing.addMatchIncludedHeaders(StringMatcher.Builder builderForValue) A list of request header string matchers that will be included during signing.A list of request header string matchers that will be included during signing.addMatchIncludedHeadersBuilder(int index) A list of request header string matchers that will be included during signing.addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value) build()clear()The credential provider for signing the request.clearField(com.google.protobuf.Descriptors.FieldDescriptor field) Indicates that before signing headers, the host header will be swapped with this value.A list of request header string matchers that will be excluded from signing.A list of request header string matchers that will be included during signing.clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof) If set, use the query string to store output of SigV4 or SigV4A calculation, rather than HTTP headers.Optional region string.The `service namespace <https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#genref-aws-service-namespaces>`_ of the HTTP endpoint.Optional Signing algorithm specifier, either ``AWS_SIGV4`` or ``AWS_SIGV4A``, defaulting to ``AWS_SIGV4``.Instead of buffering the request to calculate the payload hash, use the literal string ``UNSIGNED-PAYLOAD`` to calculate the payload hash.clone()The credential provider for signing the request.The credential provider for signing the request.The credential provider for signing the request.static final com.google.protobuf.Descriptors.Descriptorcom.google.protobuf.Descriptors.DescriptorIndicates that before signing headers, the host header will be swapped with this value.com.google.protobuf.ByteStringIndicates that before signing headers, the host header will be swapped with this value.getMatchExcludedHeaders(int index) A list of request header string matchers that will be excluded from signing.getMatchExcludedHeadersBuilder(int index) A list of request header string matchers that will be excluded from signing.A list of request header string matchers that will be excluded from signing.intA list of request header string matchers that will be excluded from signing.A list of request header string matchers that will be excluded from signing.getMatchExcludedHeadersOrBuilder(int index) A list of request header string matchers that will be excluded from signing.List<? extends StringMatcherOrBuilder>A list of request header string matchers that will be excluded from signing.getMatchIncludedHeaders(int index) A list of request header string matchers that will be included during signing.getMatchIncludedHeadersBuilder(int index) A list of request header string matchers that will be included during signing.A list of request header string matchers that will be included during signing.intA list of request header string matchers that will be included during signing.A list of request header string matchers that will be included during signing.getMatchIncludedHeadersOrBuilder(int index) A list of request header string matchers that will be included during signing.List<? extends StringMatcherOrBuilder>A list of request header string matchers that will be included during signing.If set, use the query string to store output of SigV4 or SigV4A calculation, rather than HTTP headers.If set, use the query string to store output of SigV4 or SigV4A calculation, rather than HTTP headers.If set, use the query string to store output of SigV4 or SigV4A calculation, rather than HTTP headers.Optional region string.com.google.protobuf.ByteStringOptional region string.The `service namespace <https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#genref-aws-service-namespaces>`_ of the HTTP endpoint.com.google.protobuf.ByteStringThe `service namespace <https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#genref-aws-service-namespaces>`_ of the HTTP endpoint.Optional Signing algorithm specifier, either ``AWS_SIGV4`` or ``AWS_SIGV4A``, defaulting to ``AWS_SIGV4``.intOptional Signing algorithm specifier, either ``AWS_SIGV4`` or ``AWS_SIGV4A``, defaulting to ``AWS_SIGV4``.booleanInstead of buffering the request to calculate the payload hash, use the literal string ``UNSIGNED-PAYLOAD`` to calculate the payload hash.booleanThe credential provider for signing the request.booleanIf set, use the query string to store output of SigV4 or SigV4A calculation, rather than HTTP headers.protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTablefinal booleanThe credential provider for signing the request.mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) mergeFrom(com.google.protobuf.Message other) mergeFrom(AwsRequestSigning other) If set, use the query string to store output of SigV4 or SigV4A calculation, rather than HTTP headers.mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) removeMatchExcludedHeaders(int index) A list of request header string matchers that will be excluded from signing.removeMatchIncludedHeaders(int index) A list of request header string matchers that will be included during signing.The credential provider for signing the request.setCredentialProvider(AwsCredentialProvider.Builder builderForValue) The credential provider for signing the request.setHostRewrite(String value) Indicates that before signing headers, the host header will be swapped with this value.setHostRewriteBytes(com.google.protobuf.ByteString value) Indicates that before signing headers, the host header will be swapped with this value.setMatchExcludedHeaders(int index, StringMatcher value) A list of request header string matchers that will be excluded from signing.setMatchExcludedHeaders(int index, StringMatcher.Builder builderForValue) A list of request header string matchers that will be excluded from signing.setMatchIncludedHeaders(int index, StringMatcher value) A list of request header string matchers that will be included during signing.setMatchIncludedHeaders(int index, StringMatcher.Builder builderForValue) A list of request header string matchers that will be included during signing.If set, use the query string to store output of SigV4 or SigV4A calculation, rather than HTTP headers.setQueryString(AwsRequestSigning.QueryString.Builder builderForValue) If set, use the query string to store output of SigV4 or SigV4A calculation, rather than HTTP headers.Optional region string.setRegionBytes(com.google.protobuf.ByteString value) Optional region string.setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value) setServiceName(String value) The `service namespace <https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#genref-aws-service-namespaces>`_ of the HTTP endpoint.setServiceNameBytes(com.google.protobuf.ByteString value) The `service namespace <https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#genref-aws-service-namespaces>`_ of the HTTP endpoint.Optional Signing algorithm specifier, either ``AWS_SIGV4`` or ``AWS_SIGV4A``, defaulting to ``AWS_SIGV4``.setSigningAlgorithmValue(int value) Optional Signing algorithm specifier, either ``AWS_SIGV4`` or ``AWS_SIGV4A``, defaulting to ``AWS_SIGV4``.setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) setUseUnsignedPayload(boolean value) Instead of buffering the request to calculate the payload hash, use the literal string ``UNSIGNED-PAYLOAD`` to calculate the payload hash.Methods inherited from class com.google.protobuf.GeneratedMessageV3.Builder
getAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, getUnknownFieldSetBuilder, hasField, hasOneof, internalGetMapField, internalGetMapFieldReflection, internalGetMutableMapField, internalGetMutableMapFieldReflection, isClean, markClean, mergeUnknownLengthDelimitedField, mergeUnknownVarintField, newBuilderForField, onBuilt, onChanged, parseUnknownField, setUnknownFieldSetBuilder, setUnknownFieldsProto3Methods inherited from class com.google.protobuf.AbstractMessage.Builder
findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toStringMethods inherited from class com.google.protobuf.AbstractMessageLite.Builder
addAll, addAll, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, newUninitializedMessageExceptionMethods inherited from class java.lang.Object
equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitMethods inherited from interface com.google.protobuf.Message.Builder
mergeDelimitedFrom, mergeDelimitedFromMethods inherited from interface com.google.protobuf.MessageLite.Builder
mergeFromMethods inherited from interface com.google.protobuf.MessageOrBuilder
findInitializationErrors, getAllFields, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
-
Method Details
-
getDescriptor
public static final com.google.protobuf.Descriptors.Descriptor getDescriptor() -
internalGetFieldAccessorTable
protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()- Specified by:
internalGetFieldAccessorTablein classcom.google.protobuf.GeneratedMessageV3.Builder<AwsRequestSigning.Builder>
-
clear
- Specified by:
clearin interfacecom.google.protobuf.Message.Builder- Specified by:
clearin interfacecom.google.protobuf.MessageLite.Builder- Overrides:
clearin classcom.google.protobuf.GeneratedMessageV3.Builder<AwsRequestSigning.Builder>
-
getDescriptorForType
public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()- Specified by:
getDescriptorForTypein interfacecom.google.protobuf.Message.Builder- Specified by:
getDescriptorForTypein interfacecom.google.protobuf.MessageOrBuilder- Overrides:
getDescriptorForTypein classcom.google.protobuf.GeneratedMessageV3.Builder<AwsRequestSigning.Builder>
-
getDefaultInstanceForType
- Specified by:
getDefaultInstanceForTypein interfacecom.google.protobuf.MessageLiteOrBuilder- Specified by:
getDefaultInstanceForTypein interfacecom.google.protobuf.MessageOrBuilder
-
build
- Specified by:
buildin interfacecom.google.protobuf.Message.Builder- Specified by:
buildin interfacecom.google.protobuf.MessageLite.Builder
-
buildPartial
- Specified by:
buildPartialin interfacecom.google.protobuf.Message.Builder- Specified by:
buildPartialin interfacecom.google.protobuf.MessageLite.Builder
-
clone
- Specified by:
clonein interfacecom.google.protobuf.Message.Builder- Specified by:
clonein interfacecom.google.protobuf.MessageLite.Builder- Overrides:
clonein classcom.google.protobuf.GeneratedMessageV3.Builder<AwsRequestSigning.Builder>
-
setField
public AwsRequestSigning.Builder setField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value) - Specified by:
setFieldin interfacecom.google.protobuf.Message.Builder- Overrides:
setFieldin classcom.google.protobuf.GeneratedMessageV3.Builder<AwsRequestSigning.Builder>
-
clearField
- Specified by:
clearFieldin interfacecom.google.protobuf.Message.Builder- Overrides:
clearFieldin classcom.google.protobuf.GeneratedMessageV3.Builder<AwsRequestSigning.Builder>
-
clearOneof
- Specified by:
clearOneofin interfacecom.google.protobuf.Message.Builder- Overrides:
clearOneofin classcom.google.protobuf.GeneratedMessageV3.Builder<AwsRequestSigning.Builder>
-
setRepeatedField
public AwsRequestSigning.Builder setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value) - Specified by:
setRepeatedFieldin interfacecom.google.protobuf.Message.Builder- Overrides:
setRepeatedFieldin classcom.google.protobuf.GeneratedMessageV3.Builder<AwsRequestSigning.Builder>
-
addRepeatedField
public AwsRequestSigning.Builder addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value) - Specified by:
addRepeatedFieldin interfacecom.google.protobuf.Message.Builder- Overrides:
addRepeatedFieldin classcom.google.protobuf.GeneratedMessageV3.Builder<AwsRequestSigning.Builder>
-
mergeFrom
- Specified by:
mergeFromin interfacecom.google.protobuf.Message.Builder- Overrides:
mergeFromin classcom.google.protobuf.AbstractMessage.Builder<AwsRequestSigning.Builder>
-
mergeFrom
-
isInitialized
public final boolean isInitialized()- Specified by:
isInitializedin interfacecom.google.protobuf.MessageLiteOrBuilder- Overrides:
isInitializedin classcom.google.protobuf.GeneratedMessageV3.Builder<AwsRequestSigning.Builder>
-
mergeFrom
public AwsRequestSigning.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException - Specified by:
mergeFromin interfacecom.google.protobuf.Message.Builder- Specified by:
mergeFromin interfacecom.google.protobuf.MessageLite.Builder- Overrides:
mergeFromin classcom.google.protobuf.AbstractMessage.Builder<AwsRequestSigning.Builder>- Throws:
IOException
-
getServiceName
The `service namespace <https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#genref-aws-service-namespaces>`_ of the HTTP endpoint. Example: s3
string service_name = 1 [(.validate.rules) = { ... }- Specified by:
getServiceNamein interfaceAwsRequestSigningOrBuilder- Returns:
- The serviceName.
-
getServiceNameBytes
public com.google.protobuf.ByteString getServiceNameBytes()The `service namespace <https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#genref-aws-service-namespaces>`_ of the HTTP endpoint. Example: s3
string service_name = 1 [(.validate.rules) = { ... }- Specified by:
getServiceNameBytesin interfaceAwsRequestSigningOrBuilder- Returns:
- The bytes for serviceName.
-
setServiceName
The `service namespace <https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#genref-aws-service-namespaces>`_ of the HTTP endpoint. Example: s3
string service_name = 1 [(.validate.rules) = { ... }- Parameters:
value- The serviceName to set.- Returns:
- This builder for chaining.
-
clearServiceName
The `service namespace <https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#genref-aws-service-namespaces>`_ of the HTTP endpoint. Example: s3
string service_name = 1 [(.validate.rules) = { ... }- Returns:
- This builder for chaining.
-
setServiceNameBytes
The `service namespace <https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#genref-aws-service-namespaces>`_ of the HTTP endpoint. Example: s3
string service_name = 1 [(.validate.rules) = { ... }- Parameters:
value- The bytes for serviceName to set.- Returns:
- This builder for chaining.
-
getRegion
Optional region string. If region is not provided, the region will be retrieved from the environment or AWS configuration files. See :ref:`config_http_filters_aws_request_signing_region` for more details. When signing_algorithm is set to ``AWS_SIGV4`` the region is a standard AWS `region <https://docs.aws.amazon.com/general/latest/gr/rande.html>`_ string for the service hosting the HTTP endpoint. Example: ``us-west-2`` When signing_algorithm is set to ``AWS_SIGV4A`` the region is used as a region set. A region set is a comma separated list of AWS regions, such as ``us-east-1,us-east-2`` or wildcard ``*`` or even region strings containing wildcards such as ``us-east-*`` Example: ``'*'`` By configuring a region set, a SigV4A signed request can be sent to multiple regions, rather than being valid for only a single region destination.
string region = 2;- Specified by:
getRegionin interfaceAwsRequestSigningOrBuilder- Returns:
- The region.
-
getRegionBytes
public com.google.protobuf.ByteString getRegionBytes()Optional region string. If region is not provided, the region will be retrieved from the environment or AWS configuration files. See :ref:`config_http_filters_aws_request_signing_region` for more details. When signing_algorithm is set to ``AWS_SIGV4`` the region is a standard AWS `region <https://docs.aws.amazon.com/general/latest/gr/rande.html>`_ string for the service hosting the HTTP endpoint. Example: ``us-west-2`` When signing_algorithm is set to ``AWS_SIGV4A`` the region is used as a region set. A region set is a comma separated list of AWS regions, such as ``us-east-1,us-east-2`` or wildcard ``*`` or even region strings containing wildcards such as ``us-east-*`` Example: ``'*'`` By configuring a region set, a SigV4A signed request can be sent to multiple regions, rather than being valid for only a single region destination.
string region = 2;- Specified by:
getRegionBytesin interfaceAwsRequestSigningOrBuilder- Returns:
- The bytes for region.
-
setRegion
Optional region string. If region is not provided, the region will be retrieved from the environment or AWS configuration files. See :ref:`config_http_filters_aws_request_signing_region` for more details. When signing_algorithm is set to ``AWS_SIGV4`` the region is a standard AWS `region <https://docs.aws.amazon.com/general/latest/gr/rande.html>`_ string for the service hosting the HTTP endpoint. Example: ``us-west-2`` When signing_algorithm is set to ``AWS_SIGV4A`` the region is used as a region set. A region set is a comma separated list of AWS regions, such as ``us-east-1,us-east-2`` or wildcard ``*`` or even region strings containing wildcards such as ``us-east-*`` Example: ``'*'`` By configuring a region set, a SigV4A signed request can be sent to multiple regions, rather than being valid for only a single region destination.
string region = 2;- Parameters:
value- The region to set.- Returns:
- This builder for chaining.
-
clearRegion
Optional region string. If region is not provided, the region will be retrieved from the environment or AWS configuration files. See :ref:`config_http_filters_aws_request_signing_region` for more details. When signing_algorithm is set to ``AWS_SIGV4`` the region is a standard AWS `region <https://docs.aws.amazon.com/general/latest/gr/rande.html>`_ string for the service hosting the HTTP endpoint. Example: ``us-west-2`` When signing_algorithm is set to ``AWS_SIGV4A`` the region is used as a region set. A region set is a comma separated list of AWS regions, such as ``us-east-1,us-east-2`` or wildcard ``*`` or even region strings containing wildcards such as ``us-east-*`` Example: ``'*'`` By configuring a region set, a SigV4A signed request can be sent to multiple regions, rather than being valid for only a single region destination.
string region = 2;- Returns:
- This builder for chaining.
-
setRegionBytes
Optional region string. If region is not provided, the region will be retrieved from the environment or AWS configuration files. See :ref:`config_http_filters_aws_request_signing_region` for more details. When signing_algorithm is set to ``AWS_SIGV4`` the region is a standard AWS `region <https://docs.aws.amazon.com/general/latest/gr/rande.html>`_ string for the service hosting the HTTP endpoint. Example: ``us-west-2`` When signing_algorithm is set to ``AWS_SIGV4A`` the region is used as a region set. A region set is a comma separated list of AWS regions, such as ``us-east-1,us-east-2`` or wildcard ``*`` or even region strings containing wildcards such as ``us-east-*`` Example: ``'*'`` By configuring a region set, a SigV4A signed request can be sent to multiple regions, rather than being valid for only a single region destination.
string region = 2;- Parameters:
value- The bytes for region to set.- Returns:
- This builder for chaining.
-
getHostRewrite
Indicates that before signing headers, the host header will be swapped with this value. If not set or empty, the original host header value will be used and no rewrite will happen. .. note:: This rewrite affects both signing and host header forwarding. However, this option shouldn't be used with :ref:`HCM host rewrite <envoy_v3_api_field_config.route.v3.RouteAction.host_rewrite_literal>` given that the value set here would be used for signing whereas the value set in the HCM would be used for host header forwarding which is not the desired outcome.string host_rewrite = 3;- Specified by:
getHostRewritein interfaceAwsRequestSigningOrBuilder- Returns:
- The hostRewrite.
-
getHostRewriteBytes
public com.google.protobuf.ByteString getHostRewriteBytes()Indicates that before signing headers, the host header will be swapped with this value. If not set or empty, the original host header value will be used and no rewrite will happen. .. note:: This rewrite affects both signing and host header forwarding. However, this option shouldn't be used with :ref:`HCM host rewrite <envoy_v3_api_field_config.route.v3.RouteAction.host_rewrite_literal>` given that the value set here would be used for signing whereas the value set in the HCM would be used for host header forwarding which is not the desired outcome.string host_rewrite = 3;- Specified by:
getHostRewriteBytesin interfaceAwsRequestSigningOrBuilder- Returns:
- The bytes for hostRewrite.
-
setHostRewrite
Indicates that before signing headers, the host header will be swapped with this value. If not set or empty, the original host header value will be used and no rewrite will happen. .. note:: This rewrite affects both signing and host header forwarding. However, this option shouldn't be used with :ref:`HCM host rewrite <envoy_v3_api_field_config.route.v3.RouteAction.host_rewrite_literal>` given that the value set here would be used for signing whereas the value set in the HCM would be used for host header forwarding which is not the desired outcome.string host_rewrite = 3;- Parameters:
value- The hostRewrite to set.- Returns:
- This builder for chaining.
-
clearHostRewrite
Indicates that before signing headers, the host header will be swapped with this value. If not set or empty, the original host header value will be used and no rewrite will happen. .. note:: This rewrite affects both signing and host header forwarding. However, this option shouldn't be used with :ref:`HCM host rewrite <envoy_v3_api_field_config.route.v3.RouteAction.host_rewrite_literal>` given that the value set here would be used for signing whereas the value set in the HCM would be used for host header forwarding which is not the desired outcome.string host_rewrite = 3;- Returns:
- This builder for chaining.
-
setHostRewriteBytes
Indicates that before signing headers, the host header will be swapped with this value. If not set or empty, the original host header value will be used and no rewrite will happen. .. note:: This rewrite affects both signing and host header forwarding. However, this option shouldn't be used with :ref:`HCM host rewrite <envoy_v3_api_field_config.route.v3.RouteAction.host_rewrite_literal>` given that the value set here would be used for signing whereas the value set in the HCM would be used for host header forwarding which is not the desired outcome.string host_rewrite = 3;- Parameters:
value- The bytes for hostRewrite to set.- Returns:
- This builder for chaining.
-
getUseUnsignedPayload
public boolean getUseUnsignedPayload()Instead of buffering the request to calculate the payload hash, use the literal string ``UNSIGNED-PAYLOAD`` to calculate the payload hash. Not all services support this option. See the `S3 <https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-header-based-auth.html>`_ policy for details.
bool use_unsigned_payload = 4;- Specified by:
getUseUnsignedPayloadin interfaceAwsRequestSigningOrBuilder- Returns:
- The useUnsignedPayload.
-
setUseUnsignedPayload
Instead of buffering the request to calculate the payload hash, use the literal string ``UNSIGNED-PAYLOAD`` to calculate the payload hash. Not all services support this option. See the `S3 <https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-header-based-auth.html>`_ policy for details.
bool use_unsigned_payload = 4;- Parameters:
value- The useUnsignedPayload to set.- Returns:
- This builder for chaining.
-
clearUseUnsignedPayload
Instead of buffering the request to calculate the payload hash, use the literal string ``UNSIGNED-PAYLOAD`` to calculate the payload hash. Not all services support this option. See the `S3 <https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-header-based-auth.html>`_ policy for details.
bool use_unsigned_payload = 4;- Returns:
- This builder for chaining.
-
getMatchExcludedHeadersList
A list of request header string matchers that will be excluded from signing. The excluded header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). Example: .. code-block:: yaml match_excluded_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will not be signed.
repeated .envoy.type.matcher.v3.StringMatcher match_excluded_headers = 5;- Specified by:
getMatchExcludedHeadersListin interfaceAwsRequestSigningOrBuilder
-
getMatchExcludedHeadersCount
public int getMatchExcludedHeadersCount()A list of request header string matchers that will be excluded from signing. The excluded header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). Example: .. code-block:: yaml match_excluded_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will not be signed.
repeated .envoy.type.matcher.v3.StringMatcher match_excluded_headers = 5;- Specified by:
getMatchExcludedHeadersCountin interfaceAwsRequestSigningOrBuilder
-
getMatchExcludedHeaders
A list of request header string matchers that will be excluded from signing. The excluded header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). Example: .. code-block:: yaml match_excluded_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will not be signed.
repeated .envoy.type.matcher.v3.StringMatcher match_excluded_headers = 5;- Specified by:
getMatchExcludedHeadersin interfaceAwsRequestSigningOrBuilder
-
setMatchExcludedHeaders
A list of request header string matchers that will be excluded from signing. The excluded header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). Example: .. code-block:: yaml match_excluded_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will not be signed.
repeated .envoy.type.matcher.v3.StringMatcher match_excluded_headers = 5; -
setMatchExcludedHeaders
public AwsRequestSigning.Builder setMatchExcludedHeaders(int index, StringMatcher.Builder builderForValue) A list of request header string matchers that will be excluded from signing. The excluded header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). Example: .. code-block:: yaml match_excluded_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will not be signed.
repeated .envoy.type.matcher.v3.StringMatcher match_excluded_headers = 5; -
addMatchExcludedHeaders
A list of request header string matchers that will be excluded from signing. The excluded header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). Example: .. code-block:: yaml match_excluded_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will not be signed.
repeated .envoy.type.matcher.v3.StringMatcher match_excluded_headers = 5; -
addMatchExcludedHeaders
A list of request header string matchers that will be excluded from signing. The excluded header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). Example: .. code-block:: yaml match_excluded_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will not be signed.
repeated .envoy.type.matcher.v3.StringMatcher match_excluded_headers = 5; -
addMatchExcludedHeaders
A list of request header string matchers that will be excluded from signing. The excluded header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). Example: .. code-block:: yaml match_excluded_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will not be signed.
repeated .envoy.type.matcher.v3.StringMatcher match_excluded_headers = 5; -
addMatchExcludedHeaders
public AwsRequestSigning.Builder addMatchExcludedHeaders(int index, StringMatcher.Builder builderForValue) A list of request header string matchers that will be excluded from signing. The excluded header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). Example: .. code-block:: yaml match_excluded_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will not be signed.
repeated .envoy.type.matcher.v3.StringMatcher match_excluded_headers = 5; -
addAllMatchExcludedHeaders
public AwsRequestSigning.Builder addAllMatchExcludedHeaders(Iterable<? extends StringMatcher> values) A list of request header string matchers that will be excluded from signing. The excluded header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). Example: .. code-block:: yaml match_excluded_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will not be signed.
repeated .envoy.type.matcher.v3.StringMatcher match_excluded_headers = 5; -
clearMatchExcludedHeaders
A list of request header string matchers that will be excluded from signing. The excluded header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). Example: .. code-block:: yaml match_excluded_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will not be signed.
repeated .envoy.type.matcher.v3.StringMatcher match_excluded_headers = 5; -
removeMatchExcludedHeaders
A list of request header string matchers that will be excluded from signing. The excluded header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). Example: .. code-block:: yaml match_excluded_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will not be signed.
repeated .envoy.type.matcher.v3.StringMatcher match_excluded_headers = 5; -
getMatchExcludedHeadersBuilder
A list of request header string matchers that will be excluded from signing. The excluded header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). Example: .. code-block:: yaml match_excluded_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will not be signed.
repeated .envoy.type.matcher.v3.StringMatcher match_excluded_headers = 5; -
getMatchExcludedHeadersOrBuilder
A list of request header string matchers that will be excluded from signing. The excluded header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). Example: .. code-block:: yaml match_excluded_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will not be signed.
repeated .envoy.type.matcher.v3.StringMatcher match_excluded_headers = 5;- Specified by:
getMatchExcludedHeadersOrBuilderin interfaceAwsRequestSigningOrBuilder
-
getMatchExcludedHeadersOrBuilderList
A list of request header string matchers that will be excluded from signing. The excluded header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). Example: .. code-block:: yaml match_excluded_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will not be signed.
repeated .envoy.type.matcher.v3.StringMatcher match_excluded_headers = 5;- Specified by:
getMatchExcludedHeadersOrBuilderListin interfaceAwsRequestSigningOrBuilder
-
addMatchExcludedHeadersBuilder
A list of request header string matchers that will be excluded from signing. The excluded header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). Example: .. code-block:: yaml match_excluded_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will not be signed.
repeated .envoy.type.matcher.v3.StringMatcher match_excluded_headers = 5; -
addMatchExcludedHeadersBuilder
A list of request header string matchers that will be excluded from signing. The excluded header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). Example: .. code-block:: yaml match_excluded_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will not be signed.
repeated .envoy.type.matcher.v3.StringMatcher match_excluded_headers = 5; -
getMatchExcludedHeadersBuilderList
A list of request header string matchers that will be excluded from signing. The excluded header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). Example: .. code-block:: yaml match_excluded_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will not be signed.
repeated .envoy.type.matcher.v3.StringMatcher match_excluded_headers = 5; -
getSigningAlgorithmValue
public int getSigningAlgorithmValue()Optional Signing algorithm specifier, either ``AWS_SIGV4`` or ``AWS_SIGV4A``, defaulting to ``AWS_SIGV4``.
.envoy.extensions.filters.http.aws_request_signing.v3.AwsRequestSigning.SigningAlgorithm signing_algorithm = 6;- Specified by:
getSigningAlgorithmValuein interfaceAwsRequestSigningOrBuilder- Returns:
- The enum numeric value on the wire for signingAlgorithm.
-
setSigningAlgorithmValue
Optional Signing algorithm specifier, either ``AWS_SIGV4`` or ``AWS_SIGV4A``, defaulting to ``AWS_SIGV4``.
.envoy.extensions.filters.http.aws_request_signing.v3.AwsRequestSigning.SigningAlgorithm signing_algorithm = 6;- Parameters:
value- The enum numeric value on the wire for signingAlgorithm to set.- Returns:
- This builder for chaining.
-
getSigningAlgorithm
Optional Signing algorithm specifier, either ``AWS_SIGV4`` or ``AWS_SIGV4A``, defaulting to ``AWS_SIGV4``.
.envoy.extensions.filters.http.aws_request_signing.v3.AwsRequestSigning.SigningAlgorithm signing_algorithm = 6;- Specified by:
getSigningAlgorithmin interfaceAwsRequestSigningOrBuilder- Returns:
- The signingAlgorithm.
-
setSigningAlgorithm
Optional Signing algorithm specifier, either ``AWS_SIGV4`` or ``AWS_SIGV4A``, defaulting to ``AWS_SIGV4``.
.envoy.extensions.filters.http.aws_request_signing.v3.AwsRequestSigning.SigningAlgorithm signing_algorithm = 6;- Parameters:
value- The signingAlgorithm to set.- Returns:
- This builder for chaining.
-
clearSigningAlgorithm
Optional Signing algorithm specifier, either ``AWS_SIGV4`` or ``AWS_SIGV4A``, defaulting to ``AWS_SIGV4``.
.envoy.extensions.filters.http.aws_request_signing.v3.AwsRequestSigning.SigningAlgorithm signing_algorithm = 6;- Returns:
- This builder for chaining.
-
hasQueryString
public boolean hasQueryString()If set, use the query string to store output of SigV4 or SigV4A calculation, rather than HTTP headers. The ``Authorization`` header will not be modified if ``query_string`` is configured. Example: query_string: {}.envoy.extensions.filters.http.aws_request_signing.v3.AwsRequestSigning.QueryString query_string = 7;- Specified by:
hasQueryStringin interfaceAwsRequestSigningOrBuilder- Returns:
- Whether the queryString field is set.
-
getQueryString
If set, use the query string to store output of SigV4 or SigV4A calculation, rather than HTTP headers. The ``Authorization`` header will not be modified if ``query_string`` is configured. Example: query_string: {}.envoy.extensions.filters.http.aws_request_signing.v3.AwsRequestSigning.QueryString query_string = 7;- Specified by:
getQueryStringin interfaceAwsRequestSigningOrBuilder- Returns:
- The queryString.
-
setQueryString
If set, use the query string to store output of SigV4 or SigV4A calculation, rather than HTTP headers. The ``Authorization`` header will not be modified if ``query_string`` is configured. Example: query_string: {}.envoy.extensions.filters.http.aws_request_signing.v3.AwsRequestSigning.QueryString query_string = 7; -
setQueryString
public AwsRequestSigning.Builder setQueryString(AwsRequestSigning.QueryString.Builder builderForValue) If set, use the query string to store output of SigV4 or SigV4A calculation, rather than HTTP headers. The ``Authorization`` header will not be modified if ``query_string`` is configured. Example: query_string: {}.envoy.extensions.filters.http.aws_request_signing.v3.AwsRequestSigning.QueryString query_string = 7; -
mergeQueryString
If set, use the query string to store output of SigV4 or SigV4A calculation, rather than HTTP headers. The ``Authorization`` header will not be modified if ``query_string`` is configured. Example: query_string: {}.envoy.extensions.filters.http.aws_request_signing.v3.AwsRequestSigning.QueryString query_string = 7; -
clearQueryString
If set, use the query string to store output of SigV4 or SigV4A calculation, rather than HTTP headers. The ``Authorization`` header will not be modified if ``query_string`` is configured. Example: query_string: {}.envoy.extensions.filters.http.aws_request_signing.v3.AwsRequestSigning.QueryString query_string = 7; -
getQueryStringBuilder
If set, use the query string to store output of SigV4 or SigV4A calculation, rather than HTTP headers. The ``Authorization`` header will not be modified if ``query_string`` is configured. Example: query_string: {}.envoy.extensions.filters.http.aws_request_signing.v3.AwsRequestSigning.QueryString query_string = 7; -
getQueryStringOrBuilder
If set, use the query string to store output of SigV4 or SigV4A calculation, rather than HTTP headers. The ``Authorization`` header will not be modified if ``query_string`` is configured. Example: query_string: {}.envoy.extensions.filters.http.aws_request_signing.v3.AwsRequestSigning.QueryString query_string = 7;- Specified by:
getQueryStringOrBuilderin interfaceAwsRequestSigningOrBuilder
-
hasCredentialProvider
public boolean hasCredentialProvider()The credential provider for signing the request. This is optional and if not set, it will be retrieved using the procedure described in :ref:`config_http_filters_aws_request_signing`.
.envoy.extensions.common.aws.v3.AwsCredentialProvider credential_provider = 8;- Specified by:
hasCredentialProviderin interfaceAwsRequestSigningOrBuilder- Returns:
- Whether the credentialProvider field is set.
-
getCredentialProvider
The credential provider for signing the request. This is optional and if not set, it will be retrieved using the procedure described in :ref:`config_http_filters_aws_request_signing`.
.envoy.extensions.common.aws.v3.AwsCredentialProvider credential_provider = 8;- Specified by:
getCredentialProviderin interfaceAwsRequestSigningOrBuilder- Returns:
- The credentialProvider.
-
setCredentialProvider
The credential provider for signing the request. This is optional and if not set, it will be retrieved using the procedure described in :ref:`config_http_filters_aws_request_signing`.
.envoy.extensions.common.aws.v3.AwsCredentialProvider credential_provider = 8; -
setCredentialProvider
public AwsRequestSigning.Builder setCredentialProvider(AwsCredentialProvider.Builder builderForValue) The credential provider for signing the request. This is optional and if not set, it will be retrieved using the procedure described in :ref:`config_http_filters_aws_request_signing`.
.envoy.extensions.common.aws.v3.AwsCredentialProvider credential_provider = 8; -
mergeCredentialProvider
The credential provider for signing the request. This is optional and if not set, it will be retrieved using the procedure described in :ref:`config_http_filters_aws_request_signing`.
.envoy.extensions.common.aws.v3.AwsCredentialProvider credential_provider = 8; -
clearCredentialProvider
The credential provider for signing the request. This is optional and if not set, it will be retrieved using the procedure described in :ref:`config_http_filters_aws_request_signing`.
.envoy.extensions.common.aws.v3.AwsCredentialProvider credential_provider = 8; -
getCredentialProviderBuilder
The credential provider for signing the request. This is optional and if not set, it will be retrieved using the procedure described in :ref:`config_http_filters_aws_request_signing`.
.envoy.extensions.common.aws.v3.AwsCredentialProvider credential_provider = 8; -
getCredentialProviderOrBuilder
The credential provider for signing the request. This is optional and if not set, it will be retrieved using the procedure described in :ref:`config_http_filters_aws_request_signing`.
.envoy.extensions.common.aws.v3.AwsCredentialProvider credential_provider = 8;- Specified by:
getCredentialProviderOrBuilderin interfaceAwsRequestSigningOrBuilder
-
getMatchIncludedHeadersList
A list of request header string matchers that will be included during signing. The included header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). match_included_headers takes precedence over match_excluded_headers - if match_included_headers is set, only those headers will be signed and match_excluded_headers will be ignored. Required headers for signing such as ``host`` will always be signed regardless of this setting. The required headers are determined via ``CanonicalHeaders`` section in the AWS documentation `here <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html#create-canonical-request>`_. Example: .. code-block:: yaml match_included_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will be signed and all other headers will be excluded from signing except required headers.
repeated .envoy.type.matcher.v3.StringMatcher match_included_headers = 9;- Specified by:
getMatchIncludedHeadersListin interfaceAwsRequestSigningOrBuilder
-
getMatchIncludedHeadersCount
public int getMatchIncludedHeadersCount()A list of request header string matchers that will be included during signing. The included header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). match_included_headers takes precedence over match_excluded_headers - if match_included_headers is set, only those headers will be signed and match_excluded_headers will be ignored. Required headers for signing such as ``host`` will always be signed regardless of this setting. The required headers are determined via ``CanonicalHeaders`` section in the AWS documentation `here <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html#create-canonical-request>`_. Example: .. code-block:: yaml match_included_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will be signed and all other headers will be excluded from signing except required headers.
repeated .envoy.type.matcher.v3.StringMatcher match_included_headers = 9;- Specified by:
getMatchIncludedHeadersCountin interfaceAwsRequestSigningOrBuilder
-
getMatchIncludedHeaders
A list of request header string matchers that will be included during signing. The included header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). match_included_headers takes precedence over match_excluded_headers - if match_included_headers is set, only those headers will be signed and match_excluded_headers will be ignored. Required headers for signing such as ``host`` will always be signed regardless of this setting. The required headers are determined via ``CanonicalHeaders`` section in the AWS documentation `here <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html#create-canonical-request>`_. Example: .. code-block:: yaml match_included_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will be signed and all other headers will be excluded from signing except required headers.
repeated .envoy.type.matcher.v3.StringMatcher match_included_headers = 9;- Specified by:
getMatchIncludedHeadersin interfaceAwsRequestSigningOrBuilder
-
setMatchIncludedHeaders
A list of request header string matchers that will be included during signing. The included header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). match_included_headers takes precedence over match_excluded_headers - if match_included_headers is set, only those headers will be signed and match_excluded_headers will be ignored. Required headers for signing such as ``host`` will always be signed regardless of this setting. The required headers are determined via ``CanonicalHeaders`` section in the AWS documentation `here <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html#create-canonical-request>`_. Example: .. code-block:: yaml match_included_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will be signed and all other headers will be excluded from signing except required headers.
repeated .envoy.type.matcher.v3.StringMatcher match_included_headers = 9; -
setMatchIncludedHeaders
public AwsRequestSigning.Builder setMatchIncludedHeaders(int index, StringMatcher.Builder builderForValue) A list of request header string matchers that will be included during signing. The included header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). match_included_headers takes precedence over match_excluded_headers - if match_included_headers is set, only those headers will be signed and match_excluded_headers will be ignored. Required headers for signing such as ``host`` will always be signed regardless of this setting. The required headers are determined via ``CanonicalHeaders`` section in the AWS documentation `here <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html#create-canonical-request>`_. Example: .. code-block:: yaml match_included_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will be signed and all other headers will be excluded from signing except required headers.
repeated .envoy.type.matcher.v3.StringMatcher match_included_headers = 9; -
addMatchIncludedHeaders
A list of request header string matchers that will be included during signing. The included header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). match_included_headers takes precedence over match_excluded_headers - if match_included_headers is set, only those headers will be signed and match_excluded_headers will be ignored. Required headers for signing such as ``host`` will always be signed regardless of this setting. The required headers are determined via ``CanonicalHeaders`` section in the AWS documentation `here <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html#create-canonical-request>`_. Example: .. code-block:: yaml match_included_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will be signed and all other headers will be excluded from signing except required headers.
repeated .envoy.type.matcher.v3.StringMatcher match_included_headers = 9; -
addMatchIncludedHeaders
A list of request header string matchers that will be included during signing. The included header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). match_included_headers takes precedence over match_excluded_headers - if match_included_headers is set, only those headers will be signed and match_excluded_headers will be ignored. Required headers for signing such as ``host`` will always be signed regardless of this setting. The required headers are determined via ``CanonicalHeaders`` section in the AWS documentation `here <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html#create-canonical-request>`_. Example: .. code-block:: yaml match_included_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will be signed and all other headers will be excluded from signing except required headers.
repeated .envoy.type.matcher.v3.StringMatcher match_included_headers = 9; -
addMatchIncludedHeaders
A list of request header string matchers that will be included during signing. The included header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). match_included_headers takes precedence over match_excluded_headers - if match_included_headers is set, only those headers will be signed and match_excluded_headers will be ignored. Required headers for signing such as ``host`` will always be signed regardless of this setting. The required headers are determined via ``CanonicalHeaders`` section in the AWS documentation `here <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html#create-canonical-request>`_. Example: .. code-block:: yaml match_included_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will be signed and all other headers will be excluded from signing except required headers.
repeated .envoy.type.matcher.v3.StringMatcher match_included_headers = 9; -
addMatchIncludedHeaders
public AwsRequestSigning.Builder addMatchIncludedHeaders(int index, StringMatcher.Builder builderForValue) A list of request header string matchers that will be included during signing. The included header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). match_included_headers takes precedence over match_excluded_headers - if match_included_headers is set, only those headers will be signed and match_excluded_headers will be ignored. Required headers for signing such as ``host`` will always be signed regardless of this setting. The required headers are determined via ``CanonicalHeaders`` section in the AWS documentation `here <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html#create-canonical-request>`_. Example: .. code-block:: yaml match_included_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will be signed and all other headers will be excluded from signing except required headers.
repeated .envoy.type.matcher.v3.StringMatcher match_included_headers = 9; -
addAllMatchIncludedHeaders
public AwsRequestSigning.Builder addAllMatchIncludedHeaders(Iterable<? extends StringMatcher> values) A list of request header string matchers that will be included during signing. The included header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). match_included_headers takes precedence over match_excluded_headers - if match_included_headers is set, only those headers will be signed and match_excluded_headers will be ignored. Required headers for signing such as ``host`` will always be signed regardless of this setting. The required headers are determined via ``CanonicalHeaders`` section in the AWS documentation `here <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html#create-canonical-request>`_. Example: .. code-block:: yaml match_included_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will be signed and all other headers will be excluded from signing except required headers.
repeated .envoy.type.matcher.v3.StringMatcher match_included_headers = 9; -
clearMatchIncludedHeaders
A list of request header string matchers that will be included during signing. The included header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). match_included_headers takes precedence over match_excluded_headers - if match_included_headers is set, only those headers will be signed and match_excluded_headers will be ignored. Required headers for signing such as ``host`` will always be signed regardless of this setting. The required headers are determined via ``CanonicalHeaders`` section in the AWS documentation `here <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html#create-canonical-request>`_. Example: .. code-block:: yaml match_included_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will be signed and all other headers will be excluded from signing except required headers.
repeated .envoy.type.matcher.v3.StringMatcher match_included_headers = 9; -
removeMatchIncludedHeaders
A list of request header string matchers that will be included during signing. The included header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). match_included_headers takes precedence over match_excluded_headers - if match_included_headers is set, only those headers will be signed and match_excluded_headers will be ignored. Required headers for signing such as ``host`` will always be signed regardless of this setting. The required headers are determined via ``CanonicalHeaders`` section in the AWS documentation `here <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html#create-canonical-request>`_. Example: .. code-block:: yaml match_included_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will be signed and all other headers will be excluded from signing except required headers.
repeated .envoy.type.matcher.v3.StringMatcher match_included_headers = 9; -
getMatchIncludedHeadersBuilder
A list of request header string matchers that will be included during signing. The included header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). match_included_headers takes precedence over match_excluded_headers - if match_included_headers is set, only those headers will be signed and match_excluded_headers will be ignored. Required headers for signing such as ``host`` will always be signed regardless of this setting. The required headers are determined via ``CanonicalHeaders`` section in the AWS documentation `here <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html#create-canonical-request>`_. Example: .. code-block:: yaml match_included_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will be signed and all other headers will be excluded from signing except required headers.
repeated .envoy.type.matcher.v3.StringMatcher match_included_headers = 9; -
getMatchIncludedHeadersOrBuilder
A list of request header string matchers that will be included during signing. The included header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). match_included_headers takes precedence over match_excluded_headers - if match_included_headers is set, only those headers will be signed and match_excluded_headers will be ignored. Required headers for signing such as ``host`` will always be signed regardless of this setting. The required headers are determined via ``CanonicalHeaders`` section in the AWS documentation `here <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html#create-canonical-request>`_. Example: .. code-block:: yaml match_included_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will be signed and all other headers will be excluded from signing except required headers.
repeated .envoy.type.matcher.v3.StringMatcher match_included_headers = 9;- Specified by:
getMatchIncludedHeadersOrBuilderin interfaceAwsRequestSigningOrBuilder
-
getMatchIncludedHeadersOrBuilderList
A list of request header string matchers that will be included during signing. The included header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). match_included_headers takes precedence over match_excluded_headers - if match_included_headers is set, only those headers will be signed and match_excluded_headers will be ignored. Required headers for signing such as ``host`` will always be signed regardless of this setting. The required headers are determined via ``CanonicalHeaders`` section in the AWS documentation `here <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html#create-canonical-request>`_. Example: .. code-block:: yaml match_included_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will be signed and all other headers will be excluded from signing except required headers.
repeated .envoy.type.matcher.v3.StringMatcher match_included_headers = 9;- Specified by:
getMatchIncludedHeadersOrBuilderListin interfaceAwsRequestSigningOrBuilder
-
addMatchIncludedHeadersBuilder
A list of request header string matchers that will be included during signing. The included header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). match_included_headers takes precedence over match_excluded_headers - if match_included_headers is set, only those headers will be signed and match_excluded_headers will be ignored. Required headers for signing such as ``host`` will always be signed regardless of this setting. The required headers are determined via ``CanonicalHeaders`` section in the AWS documentation `here <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html#create-canonical-request>`_. Example: .. code-block:: yaml match_included_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will be signed and all other headers will be excluded from signing except required headers.
repeated .envoy.type.matcher.v3.StringMatcher match_included_headers = 9; -
addMatchIncludedHeadersBuilder
A list of request header string matchers that will be included during signing. The included header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). match_included_headers takes precedence over match_excluded_headers - if match_included_headers is set, only those headers will be signed and match_excluded_headers will be ignored. Required headers for signing such as ``host`` will always be signed regardless of this setting. The required headers are determined via ``CanonicalHeaders`` section in the AWS documentation `here <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html#create-canonical-request>`_. Example: .. code-block:: yaml match_included_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will be signed and all other headers will be excluded from signing except required headers.
repeated .envoy.type.matcher.v3.StringMatcher match_included_headers = 9; -
getMatchIncludedHeadersBuilderList
A list of request header string matchers that will be included during signing. The included header can be matched by any patterns defined in the StringMatcher proto (e.g. exact string, prefix, regex, etc). match_included_headers takes precedence over match_excluded_headers - if match_included_headers is set, only those headers will be signed and match_excluded_headers will be ignored. Required headers for signing such as ``host`` will always be signed regardless of this setting. The required headers are determined via ``CanonicalHeaders`` section in the AWS documentation `here <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv-create-signed-request.html#create-canonical-request>`_. Example: .. code-block:: yaml match_included_headers: - prefix: x-envoy - exact: foo - exact: bar When applied, all headers that start with ``x-envoy`` and headers ``foo`` and ``bar`` will be signed and all other headers will be excluded from signing except required headers.
repeated .envoy.type.matcher.v3.StringMatcher match_included_headers = 9; -
setUnknownFields
public final AwsRequestSigning.Builder setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) - Specified by:
setUnknownFieldsin interfacecom.google.protobuf.Message.Builder- Overrides:
setUnknownFieldsin classcom.google.protobuf.GeneratedMessageV3.Builder<AwsRequestSigning.Builder>
-
mergeUnknownFields
public final AwsRequestSigning.Builder mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) - Specified by:
mergeUnknownFieldsin interfacecom.google.protobuf.Message.Builder- Overrides:
mergeUnknownFieldsin classcom.google.protobuf.GeneratedMessageV3.Builder<AwsRequestSigning.Builder>
-