Class TcpProxy.TunnelingConfig.Builder
java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderT>
com.google.protobuf.GeneratedMessageV3.Builder<TcpProxy.TunnelingConfig.Builder>
io.envoyproxy.envoy.extensions.filters.network.tcp_proxy.v3.TcpProxy.TunnelingConfig.Builder
- All Implemented Interfaces:
com.google.protobuf.Message.Builder,com.google.protobuf.MessageLite.Builder,com.google.protobuf.MessageLiteOrBuilder,com.google.protobuf.MessageOrBuilder,TcpProxy.TunnelingConfigOrBuilder,Cloneable
- Enclosing class:
- TcpProxy.TunnelingConfig
public static final class TcpProxy.TunnelingConfig.Builder
extends com.google.protobuf.GeneratedMessageV3.Builder<TcpProxy.TunnelingConfig.Builder>
implements TcpProxy.TunnelingConfigOrBuilder
Configuration for tunneling TCP over other transports or application layers. Tunneling is supported over HTTP/1.1 and HTTP/2. The upstream protocol is determined by the cluster configuration. [#next-free-field: 10]Protobuf type
envoy.extensions.filters.network.tcp_proxy.v3.TcpProxy.TunnelingConfig-
Method Summary
Modifier and TypeMethodDescriptionaddAllHeadersToAdd(Iterable<? extends HeaderValueOption> values) Additional request headers to send to the upstream proxy.addHeadersToAdd(int index, HeaderValueOption value) Additional request headers to send to the upstream proxy.addHeadersToAdd(int index, HeaderValueOption.Builder builderForValue) Additional request headers to send to the upstream proxy.addHeadersToAdd(HeaderValueOption value) Additional request headers to send to the upstream proxy.addHeadersToAdd(HeaderValueOption.Builder builderForValue) Additional request headers to send to the upstream proxy.Additional request headers to send to the upstream proxy.addHeadersToAddBuilder(int index) Additional request headers to send to the upstream proxy.addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value) build()clear()clearField(com.google.protobuf.Descriptors.FieldDescriptor field) Additional request headers to send to the upstream proxy.The hostname to send in the synthesized CONNECT headers to the upstream proxy.clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof) The path used with the POST method.Save response headers to the downstream connection's filter state for consumption by network filters.Save response trailers to the downstream connection's filter state for consumption by network filters.The configuration of the request ID extension used for generation, validation, and associated tracing operations when tunneling.The request header name to use for emitting the generated request ID on the tunneling HTTP request.The dynamic metadata key to use when storing the generated request ID.Use the ``POST`` method instead of the ``CONNECT`` method to tunnel the TCP stream.clone()static final com.google.protobuf.Descriptors.Descriptorcom.google.protobuf.Descriptors.DescriptorgetHeadersToAdd(int index) Additional request headers to send to the upstream proxy.getHeadersToAddBuilder(int index) Additional request headers to send to the upstream proxy.Additional request headers to send to the upstream proxy.intAdditional request headers to send to the upstream proxy.Additional request headers to send to the upstream proxy.getHeadersToAddOrBuilder(int index) Additional request headers to send to the upstream proxy.List<? extends HeaderValueOptionOrBuilder>Additional request headers to send to the upstream proxy.The hostname to send in the synthesized CONNECT headers to the upstream proxy.com.google.protobuf.ByteStringThe hostname to send in the synthesized CONNECT headers to the upstream proxy.The path used with the POST method.com.google.protobuf.ByteStringThe path used with the POST method.booleanSave response headers to the downstream connection's filter state for consumption by network filters.booleanSave response trailers to the downstream connection's filter state for consumption by network filters.The configuration of the request ID extension used for generation, validation, and associated tracing operations when tunneling.The configuration of the request ID extension used for generation, validation, and associated tracing operations when tunneling.The configuration of the request ID extension used for generation, validation, and associated tracing operations when tunneling.The request header name to use for emitting the generated request ID on the tunneling HTTP request.com.google.protobuf.ByteStringThe request header name to use for emitting the generated request ID on the tunneling HTTP request.The dynamic metadata key to use when storing the generated request ID.com.google.protobuf.ByteStringThe dynamic metadata key to use when storing the generated request ID.booleanUse the ``POST`` method instead of the ``CONNECT`` method to tunnel the TCP stream.booleanThe configuration of the request ID extension used for generation, validation, and associated tracing operations when tunneling.protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTablefinal booleanmergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) mergeFrom(com.google.protobuf.Message other) The configuration of the request ID extension used for generation, validation, and associated tracing operations when tunneling.mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) removeHeadersToAdd(int index) Additional request headers to send to the upstream proxy.setHeadersToAdd(int index, HeaderValueOption value) Additional request headers to send to the upstream proxy.setHeadersToAdd(int index, HeaderValueOption.Builder builderForValue) Additional request headers to send to the upstream proxy.setHostname(String value) The hostname to send in the synthesized CONNECT headers to the upstream proxy.setHostnameBytes(com.google.protobuf.ByteString value) The hostname to send in the synthesized CONNECT headers to the upstream proxy.setPostPath(String value) The path used with the POST method.setPostPathBytes(com.google.protobuf.ByteString value) The path used with the POST method.setPropagateResponseHeaders(boolean value) Save response headers to the downstream connection's filter state for consumption by network filters.setPropagateResponseTrailers(boolean value) Save response trailers to the downstream connection's filter state for consumption by network filters.setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value) The configuration of the request ID extension used for generation, validation, and associated tracing operations when tunneling.setRequestIdExtension(RequestIDExtension.Builder builderForValue) The configuration of the request ID extension used for generation, validation, and associated tracing operations when tunneling.setRequestIdHeader(String value) The request header name to use for emitting the generated request ID on the tunneling HTTP request.setRequestIdHeaderBytes(com.google.protobuf.ByteString value) The request header name to use for emitting the generated request ID on the tunneling HTTP request.setRequestIdMetadataKey(String value) The dynamic metadata key to use when storing the generated request ID.setRequestIdMetadataKeyBytes(com.google.protobuf.ByteString value) The dynamic metadata key to use when storing the generated request ID.setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) setUsePost(boolean value) Use the ``POST`` method instead of the ``CONNECT`` method to tunnel the TCP stream.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<TcpProxy.TunnelingConfig.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<TcpProxy.TunnelingConfig.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<TcpProxy.TunnelingConfig.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<TcpProxy.TunnelingConfig.Builder>
-
setField
public TcpProxy.TunnelingConfig.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<TcpProxy.TunnelingConfig.Builder>
-
clearField
public TcpProxy.TunnelingConfig.Builder clearField(com.google.protobuf.Descriptors.FieldDescriptor field) - Specified by:
clearFieldin interfacecom.google.protobuf.Message.Builder- Overrides:
clearFieldin classcom.google.protobuf.GeneratedMessageV3.Builder<TcpProxy.TunnelingConfig.Builder>
-
clearOneof
public TcpProxy.TunnelingConfig.Builder clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof) - Specified by:
clearOneofin interfacecom.google.protobuf.Message.Builder- Overrides:
clearOneofin classcom.google.protobuf.GeneratedMessageV3.Builder<TcpProxy.TunnelingConfig.Builder>
-
setRepeatedField
public TcpProxy.TunnelingConfig.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<TcpProxy.TunnelingConfig.Builder>
-
addRepeatedField
public TcpProxy.TunnelingConfig.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<TcpProxy.TunnelingConfig.Builder>
-
mergeFrom
- Specified by:
mergeFromin interfacecom.google.protobuf.Message.Builder- Overrides:
mergeFromin classcom.google.protobuf.AbstractMessage.Builder<TcpProxy.TunnelingConfig.Builder>
-
mergeFrom
-
isInitialized
public final boolean isInitialized()- Specified by:
isInitializedin interfacecom.google.protobuf.MessageLiteOrBuilder- Overrides:
isInitializedin classcom.google.protobuf.GeneratedMessageV3.Builder<TcpProxy.TunnelingConfig.Builder>
-
mergeFrom
public TcpProxy.TunnelingConfig.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<TcpProxy.TunnelingConfig.Builder>- Throws:
IOException
-
getHostname
The hostname to send in the synthesized CONNECT headers to the upstream proxy. This field evaluates command operators if present; otherwise, the value is used as-is. For example, dynamically set the hostname using downstream SNI: .. code-block:: yaml tunneling_config: hostname: "%REQUESTED_SERVER_NAME%:443" For example, dynamically set the hostname using dynamic metadata: .. code-block:: yaml tunneling_config: hostname: "%DYNAMIC_METADATA(tunnel:address)%"string hostname = 1 [(.validate.rules) = { ... }- Specified by:
getHostnamein interfaceTcpProxy.TunnelingConfigOrBuilder- Returns:
- The hostname.
-
getHostnameBytes
public com.google.protobuf.ByteString getHostnameBytes()The hostname to send in the synthesized CONNECT headers to the upstream proxy. This field evaluates command operators if present; otherwise, the value is used as-is. For example, dynamically set the hostname using downstream SNI: .. code-block:: yaml tunneling_config: hostname: "%REQUESTED_SERVER_NAME%:443" For example, dynamically set the hostname using dynamic metadata: .. code-block:: yaml tunneling_config: hostname: "%DYNAMIC_METADATA(tunnel:address)%"string hostname = 1 [(.validate.rules) = { ... }- Specified by:
getHostnameBytesin interfaceTcpProxy.TunnelingConfigOrBuilder- Returns:
- The bytes for hostname.
-
setHostname
The hostname to send in the synthesized CONNECT headers to the upstream proxy. This field evaluates command operators if present; otherwise, the value is used as-is. For example, dynamically set the hostname using downstream SNI: .. code-block:: yaml tunneling_config: hostname: "%REQUESTED_SERVER_NAME%:443" For example, dynamically set the hostname using dynamic metadata: .. code-block:: yaml tunneling_config: hostname: "%DYNAMIC_METADATA(tunnel:address)%"string hostname = 1 [(.validate.rules) = { ... }- Parameters:
value- The hostname to set.- Returns:
- This builder for chaining.
-
clearHostname
The hostname to send in the synthesized CONNECT headers to the upstream proxy. This field evaluates command operators if present; otherwise, the value is used as-is. For example, dynamically set the hostname using downstream SNI: .. code-block:: yaml tunneling_config: hostname: "%REQUESTED_SERVER_NAME%:443" For example, dynamically set the hostname using dynamic metadata: .. code-block:: yaml tunneling_config: hostname: "%DYNAMIC_METADATA(tunnel:address)%"string hostname = 1 [(.validate.rules) = { ... }- Returns:
- This builder for chaining.
-
setHostnameBytes
The hostname to send in the synthesized CONNECT headers to the upstream proxy. This field evaluates command operators if present; otherwise, the value is used as-is. For example, dynamically set the hostname using downstream SNI: .. code-block:: yaml tunneling_config: hostname: "%REQUESTED_SERVER_NAME%:443" For example, dynamically set the hostname using dynamic metadata: .. code-block:: yaml tunneling_config: hostname: "%DYNAMIC_METADATA(tunnel:address)%"string hostname = 1 [(.validate.rules) = { ... }- Parameters:
value- The bytes for hostname to set.- Returns:
- This builder for chaining.
-
getUsePost
public boolean getUsePost()Use the ``POST`` method instead of the ``CONNECT`` method to tunnel the TCP stream. The ``protocol: bytestream`` header is not set for HTTP/2 to comply with the specification. The upstream proxy is expected to interpret the POST payload as raw TCP.
bool use_post = 2;- Specified by:
getUsePostin interfaceTcpProxy.TunnelingConfigOrBuilder- Returns:
- The usePost.
-
setUsePost
Use the ``POST`` method instead of the ``CONNECT`` method to tunnel the TCP stream. The ``protocol: bytestream`` header is not set for HTTP/2 to comply with the specification. The upstream proxy is expected to interpret the POST payload as raw TCP.
bool use_post = 2;- Parameters:
value- The usePost to set.- Returns:
- This builder for chaining.
-
clearUsePost
Use the ``POST`` method instead of the ``CONNECT`` method to tunnel the TCP stream. The ``protocol: bytestream`` header is not set for HTTP/2 to comply with the specification. The upstream proxy is expected to interpret the POST payload as raw TCP.
bool use_post = 2;- Returns:
- This builder for chaining.
-
getHeadersToAddList
Additional request headers to send to the upstream proxy. This is mainly used to trigger the upstream to convert POST requests back to CONNECT requests. Neither ``:``-prefixed pseudo-headers like ``:path`` nor the ``host`` header can be overridden.
repeated .envoy.config.core.v3.HeaderValueOption headers_to_add = 3 [(.validate.rules) = { ... }- Specified by:
getHeadersToAddListin interfaceTcpProxy.TunnelingConfigOrBuilder
-
getHeadersToAddCount
public int getHeadersToAddCount()Additional request headers to send to the upstream proxy. This is mainly used to trigger the upstream to convert POST requests back to CONNECT requests. Neither ``:``-prefixed pseudo-headers like ``:path`` nor the ``host`` header can be overridden.
repeated .envoy.config.core.v3.HeaderValueOption headers_to_add = 3 [(.validate.rules) = { ... }- Specified by:
getHeadersToAddCountin interfaceTcpProxy.TunnelingConfigOrBuilder
-
getHeadersToAdd
Additional request headers to send to the upstream proxy. This is mainly used to trigger the upstream to convert POST requests back to CONNECT requests. Neither ``:``-prefixed pseudo-headers like ``:path`` nor the ``host`` header can be overridden.
repeated .envoy.config.core.v3.HeaderValueOption headers_to_add = 3 [(.validate.rules) = { ... }- Specified by:
getHeadersToAddin interfaceTcpProxy.TunnelingConfigOrBuilder
-
setHeadersToAdd
Additional request headers to send to the upstream proxy. This is mainly used to trigger the upstream to convert POST requests back to CONNECT requests. Neither ``:``-prefixed pseudo-headers like ``:path`` nor the ``host`` header can be overridden.
repeated .envoy.config.core.v3.HeaderValueOption headers_to_add = 3 [(.validate.rules) = { ... } -
setHeadersToAdd
public TcpProxy.TunnelingConfig.Builder setHeadersToAdd(int index, HeaderValueOption.Builder builderForValue) Additional request headers to send to the upstream proxy. This is mainly used to trigger the upstream to convert POST requests back to CONNECT requests. Neither ``:``-prefixed pseudo-headers like ``:path`` nor the ``host`` header can be overridden.
repeated .envoy.config.core.v3.HeaderValueOption headers_to_add = 3 [(.validate.rules) = { ... } -
addHeadersToAdd
Additional request headers to send to the upstream proxy. This is mainly used to trigger the upstream to convert POST requests back to CONNECT requests. Neither ``:``-prefixed pseudo-headers like ``:path`` nor the ``host`` header can be overridden.
repeated .envoy.config.core.v3.HeaderValueOption headers_to_add = 3 [(.validate.rules) = { ... } -
addHeadersToAdd
Additional request headers to send to the upstream proxy. This is mainly used to trigger the upstream to convert POST requests back to CONNECT requests. Neither ``:``-prefixed pseudo-headers like ``:path`` nor the ``host`` header can be overridden.
repeated .envoy.config.core.v3.HeaderValueOption headers_to_add = 3 [(.validate.rules) = { ... } -
addHeadersToAdd
Additional request headers to send to the upstream proxy. This is mainly used to trigger the upstream to convert POST requests back to CONNECT requests. Neither ``:``-prefixed pseudo-headers like ``:path`` nor the ``host`` header can be overridden.
repeated .envoy.config.core.v3.HeaderValueOption headers_to_add = 3 [(.validate.rules) = { ... } -
addHeadersToAdd
public TcpProxy.TunnelingConfig.Builder addHeadersToAdd(int index, HeaderValueOption.Builder builderForValue) Additional request headers to send to the upstream proxy. This is mainly used to trigger the upstream to convert POST requests back to CONNECT requests. Neither ``:``-prefixed pseudo-headers like ``:path`` nor the ``host`` header can be overridden.
repeated .envoy.config.core.v3.HeaderValueOption headers_to_add = 3 [(.validate.rules) = { ... } -
addAllHeadersToAdd
public TcpProxy.TunnelingConfig.Builder addAllHeadersToAdd(Iterable<? extends HeaderValueOption> values) Additional request headers to send to the upstream proxy. This is mainly used to trigger the upstream to convert POST requests back to CONNECT requests. Neither ``:``-prefixed pseudo-headers like ``:path`` nor the ``host`` header can be overridden.
repeated .envoy.config.core.v3.HeaderValueOption headers_to_add = 3 [(.validate.rules) = { ... } -
clearHeadersToAdd
Additional request headers to send to the upstream proxy. This is mainly used to trigger the upstream to convert POST requests back to CONNECT requests. Neither ``:``-prefixed pseudo-headers like ``:path`` nor the ``host`` header can be overridden.
repeated .envoy.config.core.v3.HeaderValueOption headers_to_add = 3 [(.validate.rules) = { ... } -
removeHeadersToAdd
Additional request headers to send to the upstream proxy. This is mainly used to trigger the upstream to convert POST requests back to CONNECT requests. Neither ``:``-prefixed pseudo-headers like ``:path`` nor the ``host`` header can be overridden.
repeated .envoy.config.core.v3.HeaderValueOption headers_to_add = 3 [(.validate.rules) = { ... } -
getHeadersToAddBuilder
Additional request headers to send to the upstream proxy. This is mainly used to trigger the upstream to convert POST requests back to CONNECT requests. Neither ``:``-prefixed pseudo-headers like ``:path`` nor the ``host`` header can be overridden.
repeated .envoy.config.core.v3.HeaderValueOption headers_to_add = 3 [(.validate.rules) = { ... } -
getHeadersToAddOrBuilder
Additional request headers to send to the upstream proxy. This is mainly used to trigger the upstream to convert POST requests back to CONNECT requests. Neither ``:``-prefixed pseudo-headers like ``:path`` nor the ``host`` header can be overridden.
repeated .envoy.config.core.v3.HeaderValueOption headers_to_add = 3 [(.validate.rules) = { ... }- Specified by:
getHeadersToAddOrBuilderin interfaceTcpProxy.TunnelingConfigOrBuilder
-
getHeadersToAddOrBuilderList
Additional request headers to send to the upstream proxy. This is mainly used to trigger the upstream to convert POST requests back to CONNECT requests. Neither ``:``-prefixed pseudo-headers like ``:path`` nor the ``host`` header can be overridden.
repeated .envoy.config.core.v3.HeaderValueOption headers_to_add = 3 [(.validate.rules) = { ... }- Specified by:
getHeadersToAddOrBuilderListin interfaceTcpProxy.TunnelingConfigOrBuilder
-
addHeadersToAddBuilder
Additional request headers to send to the upstream proxy. This is mainly used to trigger the upstream to convert POST requests back to CONNECT requests. Neither ``:``-prefixed pseudo-headers like ``:path`` nor the ``host`` header can be overridden.
repeated .envoy.config.core.v3.HeaderValueOption headers_to_add = 3 [(.validate.rules) = { ... } -
addHeadersToAddBuilder
Additional request headers to send to the upstream proxy. This is mainly used to trigger the upstream to convert POST requests back to CONNECT requests. Neither ``:``-prefixed pseudo-headers like ``:path`` nor the ``host`` header can be overridden.
repeated .envoy.config.core.v3.HeaderValueOption headers_to_add = 3 [(.validate.rules) = { ... } -
getHeadersToAddBuilderList
Additional request headers to send to the upstream proxy. This is mainly used to trigger the upstream to convert POST requests back to CONNECT requests. Neither ``:``-prefixed pseudo-headers like ``:path`` nor the ``host`` header can be overridden.
repeated .envoy.config.core.v3.HeaderValueOption headers_to_add = 3 [(.validate.rules) = { ... } -
getPropagateResponseHeaders
public boolean getPropagateResponseHeaders()Save response headers to the downstream connection's filter state for consumption by network filters. The filter state key is ``envoy.tcp_proxy.propagate_response_headers``.
bool propagate_response_headers = 4;- Specified by:
getPropagateResponseHeadersin interfaceTcpProxy.TunnelingConfigOrBuilder- Returns:
- The propagateResponseHeaders.
-
setPropagateResponseHeaders
Save response headers to the downstream connection's filter state for consumption by network filters. The filter state key is ``envoy.tcp_proxy.propagate_response_headers``.
bool propagate_response_headers = 4;- Parameters:
value- The propagateResponseHeaders to set.- Returns:
- This builder for chaining.
-
clearPropagateResponseHeaders
Save response headers to the downstream connection's filter state for consumption by network filters. The filter state key is ``envoy.tcp_proxy.propagate_response_headers``.
bool propagate_response_headers = 4;- Returns:
- This builder for chaining.
-
getPostPath
The path used with the POST method. The default path is ``/``. If this field is specified and :ref:`use_post field <envoy_v3_api_field_extensions.filters.network.tcp_proxy.v3.TcpProxy.TunnelingConfig.use_post>` is not set to true, the configuration will be rejected.
string post_path = 5;- Specified by:
getPostPathin interfaceTcpProxy.TunnelingConfigOrBuilder- Returns:
- The postPath.
-
getPostPathBytes
public com.google.protobuf.ByteString getPostPathBytes()The path used with the POST method. The default path is ``/``. If this field is specified and :ref:`use_post field <envoy_v3_api_field_extensions.filters.network.tcp_proxy.v3.TcpProxy.TunnelingConfig.use_post>` is not set to true, the configuration will be rejected.
string post_path = 5;- Specified by:
getPostPathBytesin interfaceTcpProxy.TunnelingConfigOrBuilder- Returns:
- The bytes for postPath.
-
setPostPath
The path used with the POST method. The default path is ``/``. If this field is specified and :ref:`use_post field <envoy_v3_api_field_extensions.filters.network.tcp_proxy.v3.TcpProxy.TunnelingConfig.use_post>` is not set to true, the configuration will be rejected.
string post_path = 5;- Parameters:
value- The postPath to set.- Returns:
- This builder for chaining.
-
clearPostPath
The path used with the POST method. The default path is ``/``. If this field is specified and :ref:`use_post field <envoy_v3_api_field_extensions.filters.network.tcp_proxy.v3.TcpProxy.TunnelingConfig.use_post>` is not set to true, the configuration will be rejected.
string post_path = 5;- Returns:
- This builder for chaining.
-
setPostPathBytes
The path used with the POST method. The default path is ``/``. If this field is specified and :ref:`use_post field <envoy_v3_api_field_extensions.filters.network.tcp_proxy.v3.TcpProxy.TunnelingConfig.use_post>` is not set to true, the configuration will be rejected.
string post_path = 5;- Parameters:
value- The bytes for postPath to set.- Returns:
- This builder for chaining.
-
getPropagateResponseTrailers
public boolean getPropagateResponseTrailers()Save response trailers to the downstream connection's filter state for consumption by network filters. The filter state key is ``envoy.tcp_proxy.propagate_response_trailers``.
bool propagate_response_trailers = 6;- Specified by:
getPropagateResponseTrailersin interfaceTcpProxy.TunnelingConfigOrBuilder- Returns:
- The propagateResponseTrailers.
-
setPropagateResponseTrailers
Save response trailers to the downstream connection's filter state for consumption by network filters. The filter state key is ``envoy.tcp_proxy.propagate_response_trailers``.
bool propagate_response_trailers = 6;- Parameters:
value- The propagateResponseTrailers to set.- Returns:
- This builder for chaining.
-
clearPropagateResponseTrailers
Save response trailers to the downstream connection's filter state for consumption by network filters. The filter state key is ``envoy.tcp_proxy.propagate_response_trailers``.
bool propagate_response_trailers = 6;- Returns:
- This builder for chaining.
-
hasRequestIdExtension
public boolean hasRequestIdExtension()The configuration of the request ID extension used for generation, validation, and associated tracing operations when tunneling. If this field is set, a request ID is generated using the specified extension. If this field is not set, no request ID is generated. When a request ID is generated, it is also stored in the downstream connection's dynamic metadata under the namespace ``envoy.filters.network.tcp_proxy`` with the key ``tunnel_request_id`` to allow emission from TCP proxy access logs via the ``%DYNAMIC_METADATA(envoy.filters.network.tcp_proxy:tunnel_request_id)%`` formatter. [#extension-category: envoy.request_id]
.envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension request_id_extension = 7;- Specified by:
hasRequestIdExtensionin interfaceTcpProxy.TunnelingConfigOrBuilder- Returns:
- Whether the requestIdExtension field is set.
-
getRequestIdExtension
The configuration of the request ID extension used for generation, validation, and associated tracing operations when tunneling. If this field is set, a request ID is generated using the specified extension. If this field is not set, no request ID is generated. When a request ID is generated, it is also stored in the downstream connection's dynamic metadata under the namespace ``envoy.filters.network.tcp_proxy`` with the key ``tunnel_request_id`` to allow emission from TCP proxy access logs via the ``%DYNAMIC_METADATA(envoy.filters.network.tcp_proxy:tunnel_request_id)%`` formatter. [#extension-category: envoy.request_id]
.envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension request_id_extension = 7;- Specified by:
getRequestIdExtensionin interfaceTcpProxy.TunnelingConfigOrBuilder- Returns:
- The requestIdExtension.
-
setRequestIdExtension
The configuration of the request ID extension used for generation, validation, and associated tracing operations when tunneling. If this field is set, a request ID is generated using the specified extension. If this field is not set, no request ID is generated. When a request ID is generated, it is also stored in the downstream connection's dynamic metadata under the namespace ``envoy.filters.network.tcp_proxy`` with the key ``tunnel_request_id`` to allow emission from TCP proxy access logs via the ``%DYNAMIC_METADATA(envoy.filters.network.tcp_proxy:tunnel_request_id)%`` formatter. [#extension-category: envoy.request_id]
.envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension request_id_extension = 7; -
setRequestIdExtension
public TcpProxy.TunnelingConfig.Builder setRequestIdExtension(RequestIDExtension.Builder builderForValue) The configuration of the request ID extension used for generation, validation, and associated tracing operations when tunneling. If this field is set, a request ID is generated using the specified extension. If this field is not set, no request ID is generated. When a request ID is generated, it is also stored in the downstream connection's dynamic metadata under the namespace ``envoy.filters.network.tcp_proxy`` with the key ``tunnel_request_id`` to allow emission from TCP proxy access logs via the ``%DYNAMIC_METADATA(envoy.filters.network.tcp_proxy:tunnel_request_id)%`` formatter. [#extension-category: envoy.request_id]
.envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension request_id_extension = 7; -
mergeRequestIdExtension
The configuration of the request ID extension used for generation, validation, and associated tracing operations when tunneling. If this field is set, a request ID is generated using the specified extension. If this field is not set, no request ID is generated. When a request ID is generated, it is also stored in the downstream connection's dynamic metadata under the namespace ``envoy.filters.network.tcp_proxy`` with the key ``tunnel_request_id`` to allow emission from TCP proxy access logs via the ``%DYNAMIC_METADATA(envoy.filters.network.tcp_proxy:tunnel_request_id)%`` formatter. [#extension-category: envoy.request_id]
.envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension request_id_extension = 7; -
clearRequestIdExtension
The configuration of the request ID extension used for generation, validation, and associated tracing operations when tunneling. If this field is set, a request ID is generated using the specified extension. If this field is not set, no request ID is generated. When a request ID is generated, it is also stored in the downstream connection's dynamic metadata under the namespace ``envoy.filters.network.tcp_proxy`` with the key ``tunnel_request_id`` to allow emission from TCP proxy access logs via the ``%DYNAMIC_METADATA(envoy.filters.network.tcp_proxy:tunnel_request_id)%`` formatter. [#extension-category: envoy.request_id]
.envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension request_id_extension = 7; -
getRequestIdExtensionBuilder
The configuration of the request ID extension used for generation, validation, and associated tracing operations when tunneling. If this field is set, a request ID is generated using the specified extension. If this field is not set, no request ID is generated. When a request ID is generated, it is also stored in the downstream connection's dynamic metadata under the namespace ``envoy.filters.network.tcp_proxy`` with the key ``tunnel_request_id`` to allow emission from TCP proxy access logs via the ``%DYNAMIC_METADATA(envoy.filters.network.tcp_proxy:tunnel_request_id)%`` formatter. [#extension-category: envoy.request_id]
.envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension request_id_extension = 7; -
getRequestIdExtensionOrBuilder
The configuration of the request ID extension used for generation, validation, and associated tracing operations when tunneling. If this field is set, a request ID is generated using the specified extension. If this field is not set, no request ID is generated. When a request ID is generated, it is also stored in the downstream connection's dynamic metadata under the namespace ``envoy.filters.network.tcp_proxy`` with the key ``tunnel_request_id`` to allow emission from TCP proxy access logs via the ``%DYNAMIC_METADATA(envoy.filters.network.tcp_proxy:tunnel_request_id)%`` formatter. [#extension-category: envoy.request_id]
.envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension request_id_extension = 7;- Specified by:
getRequestIdExtensionOrBuilderin interfaceTcpProxy.TunnelingConfigOrBuilder
-
getRequestIdHeader
The request header name to use for emitting the generated request ID on the tunneling HTTP request. If not specified or set to an empty string, the default header name ``x-request-id`` is used. .. note:: This setting does not alter the internal request ID handling elsewhere in Envoy and only controls the header emitted on the tunneling request.
string request_id_header = 8;- Specified by:
getRequestIdHeaderin interfaceTcpProxy.TunnelingConfigOrBuilder- Returns:
- The requestIdHeader.
-
getRequestIdHeaderBytes
public com.google.protobuf.ByteString getRequestIdHeaderBytes()The request header name to use for emitting the generated request ID on the tunneling HTTP request. If not specified or set to an empty string, the default header name ``x-request-id`` is used. .. note:: This setting does not alter the internal request ID handling elsewhere in Envoy and only controls the header emitted on the tunneling request.
string request_id_header = 8;- Specified by:
getRequestIdHeaderBytesin interfaceTcpProxy.TunnelingConfigOrBuilder- Returns:
- The bytes for requestIdHeader.
-
setRequestIdHeader
The request header name to use for emitting the generated request ID on the tunneling HTTP request. If not specified or set to an empty string, the default header name ``x-request-id`` is used. .. note:: This setting does not alter the internal request ID handling elsewhere in Envoy and only controls the header emitted on the tunneling request.
string request_id_header = 8;- Parameters:
value- The requestIdHeader to set.- Returns:
- This builder for chaining.
-
clearRequestIdHeader
The request header name to use for emitting the generated request ID on the tunneling HTTP request. If not specified or set to an empty string, the default header name ``x-request-id`` is used. .. note:: This setting does not alter the internal request ID handling elsewhere in Envoy and only controls the header emitted on the tunneling request.
string request_id_header = 8;- Returns:
- This builder for chaining.
-
setRequestIdHeaderBytes
public TcpProxy.TunnelingConfig.Builder setRequestIdHeaderBytes(com.google.protobuf.ByteString value) The request header name to use for emitting the generated request ID on the tunneling HTTP request. If not specified or set to an empty string, the default header name ``x-request-id`` is used. .. note:: This setting does not alter the internal request ID handling elsewhere in Envoy and only controls the header emitted on the tunneling request.
string request_id_header = 8;- Parameters:
value- The bytes for requestIdHeader to set.- Returns:
- This builder for chaining.
-
getRequestIdMetadataKey
The dynamic metadata key to use when storing the generated request ID. The metadata is stored under the namespace ``envoy.filters.network.tcp_proxy``. If not specified or set to an empty string, the default key ``tunnel_request_id`` is used. This enables customizing the key used by access log formatters such as ``%DYNAMIC_METADATA(envoy.filters.network.tcp_proxy:<key>)%``.
string request_id_metadata_key = 9;- Specified by:
getRequestIdMetadataKeyin interfaceTcpProxy.TunnelingConfigOrBuilder- Returns:
- The requestIdMetadataKey.
-
getRequestIdMetadataKeyBytes
public com.google.protobuf.ByteString getRequestIdMetadataKeyBytes()The dynamic metadata key to use when storing the generated request ID. The metadata is stored under the namespace ``envoy.filters.network.tcp_proxy``. If not specified or set to an empty string, the default key ``tunnel_request_id`` is used. This enables customizing the key used by access log formatters such as ``%DYNAMIC_METADATA(envoy.filters.network.tcp_proxy:<key>)%``.
string request_id_metadata_key = 9;- Specified by:
getRequestIdMetadataKeyBytesin interfaceTcpProxy.TunnelingConfigOrBuilder- Returns:
- The bytes for requestIdMetadataKey.
-
setRequestIdMetadataKey
The dynamic metadata key to use when storing the generated request ID. The metadata is stored under the namespace ``envoy.filters.network.tcp_proxy``. If not specified or set to an empty string, the default key ``tunnel_request_id`` is used. This enables customizing the key used by access log formatters such as ``%DYNAMIC_METADATA(envoy.filters.network.tcp_proxy:<key>)%``.
string request_id_metadata_key = 9;- Parameters:
value- The requestIdMetadataKey to set.- Returns:
- This builder for chaining.
-
clearRequestIdMetadataKey
The dynamic metadata key to use when storing the generated request ID. The metadata is stored under the namespace ``envoy.filters.network.tcp_proxy``. If not specified or set to an empty string, the default key ``tunnel_request_id`` is used. This enables customizing the key used by access log formatters such as ``%DYNAMIC_METADATA(envoy.filters.network.tcp_proxy:<key>)%``.
string request_id_metadata_key = 9;- Returns:
- This builder for chaining.
-
setRequestIdMetadataKeyBytes
public TcpProxy.TunnelingConfig.Builder setRequestIdMetadataKeyBytes(com.google.protobuf.ByteString value) The dynamic metadata key to use when storing the generated request ID. The metadata is stored under the namespace ``envoy.filters.network.tcp_proxy``. If not specified or set to an empty string, the default key ``tunnel_request_id`` is used. This enables customizing the key used by access log formatters such as ``%DYNAMIC_METADATA(envoy.filters.network.tcp_proxy:<key>)%``.
string request_id_metadata_key = 9;- Parameters:
value- The bytes for requestIdMetadataKey to set.- Returns:
- This builder for chaining.
-
setUnknownFields
public final TcpProxy.TunnelingConfig.Builder setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) - Specified by:
setUnknownFieldsin interfacecom.google.protobuf.Message.Builder- Overrides:
setUnknownFieldsin classcom.google.protobuf.GeneratedMessageV3.Builder<TcpProxy.TunnelingConfig.Builder>
-
mergeUnknownFields
public final TcpProxy.TunnelingConfig.Builder mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) - Specified by:
mergeUnknownFieldsin interfacecom.google.protobuf.Message.Builder- Overrides:
mergeUnknownFieldsin classcom.google.protobuf.GeneratedMessageV3.Builder<TcpProxy.TunnelingConfig.Builder>
-