Class HttpConnectionManager.Builder
java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<HttpConnectionManager.Builder>
com.google.protobuf.GeneratedMessage.Builder<HttpConnectionManager.Builder>
io.envoyproxy.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.Builder
- All Implemented Interfaces:
com.google.protobuf.Message.Builder
,com.google.protobuf.MessageLite.Builder
,com.google.protobuf.MessageLiteOrBuilder
,com.google.protobuf.MessageOrBuilder
,HttpConnectionManagerOrBuilder
,Cloneable
- Enclosing class:
HttpConnectionManager
public static final class HttpConnectionManager.Builder
extends com.google.protobuf.GeneratedMessage.Builder<HttpConnectionManager.Builder>
implements HttpConnectionManagerOrBuilder
[#next-free-field: 58]Protobuf type
envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
-
Field Summary
FieldsModifier and TypeFieldDescriptionprivate com.google.protobuf.RepeatedFieldBuilder
<AccessLog, AccessLog.Builder, AccessLogOrBuilder> private com.google.protobuf.Duration
private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.Duration, com.google.protobuf.Duration.Builder, com.google.protobuf.DurationOrBuilder> private com.google.protobuf.SingleFieldBuilder
<HttpConnectionManager.HcmAccessLogOptions, HttpConnectionManager.HcmAccessLogOptions.Builder, HttpConnectionManager.HcmAccessLogOptionsOrBuilder> private com.google.protobuf.BoolValue
private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.BoolValue, com.google.protobuf.BoolValue.Builder, com.google.protobuf.BoolValueOrBuilder> private com.google.protobuf.BoolValue
private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.BoolValue, com.google.protobuf.BoolValue.Builder, com.google.protobuf.BoolValueOrBuilder> private boolean
private boolean
private boolean
private int
private int
private int
private HttpProtocolOptions
private com.google.protobuf.SingleFieldBuilder
<HttpProtocolOptions, HttpProtocolOptions.Builder, HttpProtocolOptionsOrBuilder> private com.google.protobuf.Duration
private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.Duration, com.google.protobuf.Duration.Builder, com.google.protobuf.DurationOrBuilder> private com.google.protobuf.Duration
private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.Duration, com.google.protobuf.Duration.Builder, com.google.protobuf.DurationOrBuilder> private List
<TypedExtensionConfig> private com.google.protobuf.RepeatedFieldBuilder
<TypedExtensionConfig, TypedExtensionConfig.Builder, TypedExtensionConfigOrBuilder> private boolean
private int
private com.google.protobuf.BoolValue
private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.BoolValue, com.google.protobuf.BoolValue.Builder, com.google.protobuf.BoolValueOrBuilder> private Http2ProtocolOptions
private com.google.protobuf.SingleFieldBuilder
<Http2ProtocolOptions, Http2ProtocolOptions.Builder, Http2ProtocolOptionsOrBuilder> private Http3ProtocolOptions
private com.google.protobuf.SingleFieldBuilder
<Http3ProtocolOptions, Http3ProtocolOptions.Builder, Http3ProtocolOptionsOrBuilder> private List
<HttpFilter> private com.google.protobuf.RepeatedFieldBuilder
<HttpFilter, HttpFilter.Builder, HttpFilterOrBuilder> private Http1ProtocolOptions
private com.google.protobuf.SingleFieldBuilder
<Http1ProtocolOptions, Http1ProtocolOptions.Builder, Http1ProtocolOptionsOrBuilder> private com.google.protobuf.SingleFieldBuilder
<HttpConnectionManager.InternalAddressConfig, HttpConnectionManager.InternalAddressConfig.Builder, HttpConnectionManager.InternalAddressConfigOrBuilder> private LocalReplyConfig
private com.google.protobuf.SingleFieldBuilder
<LocalReplyConfig, LocalReplyConfig.Builder, LocalReplyConfigOrBuilder> private com.google.protobuf.UInt32Value
private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.UInt32Value, com.google.protobuf.UInt32Value.Builder, com.google.protobuf.UInt32ValueOrBuilder> private boolean
private com.google.protobuf.BoolValue
private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.BoolValue, com.google.protobuf.BoolValue.Builder, com.google.protobuf.BoolValueOrBuilder> private List
<TypedExtensionConfig> private com.google.protobuf.RepeatedFieldBuilder
<TypedExtensionConfig, TypedExtensionConfig.Builder, TypedExtensionConfigOrBuilder> private com.google.protobuf.SingleFieldBuilder
<HttpConnectionManager.PathNormalizationOptions, HttpConnectionManager.PathNormalizationOptions.Builder, HttpConnectionManager.PathNormalizationOptionsOrBuilder> private int
private boolean
private boolean
private com.google.protobuf.SingleFieldBuilder
<HttpConnectionManager.ProxyStatusConfig, HttpConnectionManager.ProxyStatusConfig.Builder, HttpConnectionManager.ProxyStatusConfigOrBuilder> private com.google.protobuf.SingleFieldBuilder
<Rds, Rds.Builder, RdsOrBuilder> private boolean
private com.google.protobuf.Duration
private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.Duration, com.google.protobuf.Duration.Builder, com.google.protobuf.DurationOrBuilder> private RequestIDExtension
private com.google.protobuf.SingleFieldBuilder
<RequestIDExtension, RequestIDExtension.Builder, RequestIDExtensionOrBuilder> private com.google.protobuf.Duration
private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.Duration, com.google.protobuf.Duration.Builder, com.google.protobuf.DurationOrBuilder> private com.google.protobuf.SingleFieldBuilder
<RouteConfiguration, RouteConfiguration.Builder, RouteConfigurationOrBuilder> private Object
private int
private SchemeHeaderTransformation
private com.google.protobuf.SingleFieldBuilder
<SchemeHeaderTransformation, SchemeHeaderTransformation.Builder, SchemeHeaderTransformationOrBuilder> private com.google.protobuf.SingleFieldBuilder
<ScopedRoutes, ScopedRoutes.Builder, ScopedRoutesOrBuilder> private int
private Object
private com.google.protobuf.SingleFieldBuilder
<HttpConnectionManager.SetCurrentClientCertDetails, HttpConnectionManager.SetCurrentClientCertDetails.Builder, HttpConnectionManager.SetCurrentClientCertDetailsOrBuilder> private boolean
private Object
private com.google.protobuf.BoolValue
private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.BoolValue, com.google.protobuf.BoolValue.Builder, com.google.protobuf.BoolValueOrBuilder> private com.google.protobuf.Duration
private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.Duration, com.google.protobuf.Duration.Builder, com.google.protobuf.DurationOrBuilder> private boolean
private Object
private int
private boolean
private HttpConnectionManager.Tracing
private com.google.protobuf.SingleFieldBuilder
<HttpConnectionManager.Tracing, HttpConnectionManager.Tracing.Builder, HttpConnectionManager.TracingOrBuilder> private TypedExtensionConfig
private com.google.protobuf.SingleFieldBuilder
<TypedExtensionConfig, TypedExtensionConfig.Builder, TypedExtensionConfigOrBuilder> private List
<HttpConnectionManager.UpgradeConfig> private com.google.protobuf.RepeatedFieldBuilder
<HttpConnectionManager.UpgradeConfig, HttpConnectionManager.UpgradeConfig.Builder, HttpConnectionManager.UpgradeConfigOrBuilder> private com.google.protobuf.BoolValue
private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.BoolValue, com.google.protobuf.BoolValue.Builder, com.google.protobuf.BoolValueOrBuilder> private Object
private int
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionaddAccessLog
(int index, AccessLog value) Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.addAccessLog
(int index, AccessLog.Builder builderForValue) Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.addAccessLog
(AccessLog value) Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.addAccessLog
(AccessLog.Builder builderForValue) Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.addAccessLogBuilder
(int index) Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.addAllAccessLog
(Iterable<? extends AccessLog> values) Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.addAllEarlyHeaderMutationExtensions
(Iterable<? extends TypedExtensionConfig> values) The configuration for the early header mutation extensions.addAllHttpFilters
(Iterable<? extends HttpFilter> values) A list of individual HTTP filters that make up the filter chain for requests made to the connection manager.addAllOriginalIpDetectionExtensions
(Iterable<? extends TypedExtensionConfig> values) The configuration for the original IP detection extensions.addAllUpgradeConfigs
(Iterable<? extends HttpConnectionManager.UpgradeConfig> values) repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
addEarlyHeaderMutationExtensions
(int index, TypedExtensionConfig value) The configuration for the early header mutation extensions.addEarlyHeaderMutationExtensions
(int index, TypedExtensionConfig.Builder builderForValue) The configuration for the early header mutation extensions.The configuration for the early header mutation extensions.addEarlyHeaderMutationExtensions
(TypedExtensionConfig.Builder builderForValue) The configuration for the early header mutation extensions.The configuration for the early header mutation extensions.addEarlyHeaderMutationExtensionsBuilder
(int index) The configuration for the early header mutation extensions.addHttpFilters
(int index, HttpFilter value) A list of individual HTTP filters that make up the filter chain for requests made to the connection manager.addHttpFilters
(int index, HttpFilter.Builder builderForValue) A list of individual HTTP filters that make up the filter chain for requests made to the connection manager.addHttpFilters
(HttpFilter value) A list of individual HTTP filters that make up the filter chain for requests made to the connection manager.addHttpFilters
(HttpFilter.Builder builderForValue) A list of individual HTTP filters that make up the filter chain for requests made to the connection manager.A list of individual HTTP filters that make up the filter chain for requests made to the connection manager.addHttpFiltersBuilder
(int index) A list of individual HTTP filters that make up the filter chain for requests made to the connection manager.addOriginalIpDetectionExtensions
(int index, TypedExtensionConfig value) The configuration for the original IP detection extensions.addOriginalIpDetectionExtensions
(int index, TypedExtensionConfig.Builder builderForValue) The configuration for the original IP detection extensions.The configuration for the original IP detection extensions.addOriginalIpDetectionExtensions
(TypedExtensionConfig.Builder builderForValue) The configuration for the original IP detection extensions.The configuration for the original IP detection extensions.addOriginalIpDetectionExtensionsBuilder
(int index) The configuration for the original IP detection extensions.addUpgradeConfigs
(int index, HttpConnectionManager.UpgradeConfig value) repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
addUpgradeConfigs
(int index, HttpConnectionManager.UpgradeConfig.Builder builderForValue) repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
addUpgradeConfigs
(HttpConnectionManager.UpgradeConfig.Builder builderForValue) repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
addUpgradeConfigsBuilder
(int index) repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
build()
private void
buildPartial0
(HttpConnectionManager result) private void
buildPartial1
(HttpConnectionManager result) private void
private void
clear()
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.Deprecated.Additional access log options for HTTP connection manager.Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state.Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent` and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers.If set, Envoy will always set :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header in response.Append the :ref:`config_http_conn_man_headers_x-envoy-local-overloaded` HTTP header in the scenario where the Overload Manager has been triggered.Append the ``x-forwarded-port`` header with the port value client used to connect to Envoy.Supplies the type of codec that the connection manager should use.Additional settings for HTTP requests handled by the connection manager.The delayed close timeout is for downstream connections managed by the HTTP connection manager.The time that Envoy will wait between sending an HTTP/2 “shutdown notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame.The configuration for the early header mutation extensions.Deprecated.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.flush_access_log_on_new_request is deprecated.How to handle the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` (XFCC) HTTP header.Whether the connection manager will generate the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if it does not exist.Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.Additional HTTP/3 settings that are passed directly to the HTTP/3 codec.A list of individual HTTP filters that make up the filter chain for requests made to the connection manager.Additional HTTP/1 settings that are passed to the HTTP/1 codec.Configures what network addresses are considered internal for stats and header sanitation purposes.The configuration to customize local reply returned by Envoy.The maximum request headers size for incoming connections.Determines if adjacent slashes in the path are merged into one before any processing of requests by HTTP filters or routing.Should paths be normalized according to RFC 3986 before any processing of requests by HTTP filters or routing? This affects the upstream ``:path`` header as well.The configuration for the original IP detection extensions.[#not-implemented-hide:] Path normalization configuration.Action to take when request URL path contains escaped slash sequences (%2F, %2f, %5C and %5c).Whether the connection manager will keep the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if passed for a request that is edge (Edge request is the request from external clients to front Envoy) and not reset it, which is the current Envoy behaviour.If proxy_100_continue is true, Envoy will proxy incoming "Expect: 100-continue" headers upstream, and forward "100 Continue" responses downstream.Proxy-Status HTTP response header configuration.clearRds()
The connection manager’s route table will be dynamically loaded via the RDS API.If :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` is true and represent_ipv4_remote_address_as_ipv4_mapped_ipv6 is true and the remote address is an IPv4 address, the address will be mapped to IPv6 before it is appended to ``x-forwarded-for``.The amount of time that Envoy will wait for the request headers to be received.The configuration of the request ID extension.The amount of time that Envoy will wait for the entire request to be received.The route table for the connection manager is static and is specified in this property.Allows for explicit transformation of the :scheme header on the request path.A route table will be dynamically assigned to each request based on request attributes (e.g., the value of a header).Defines the action to be applied to the Server header on the response path.An optional override that the connection manager will write to the server header in responses.This field is valid only when :ref:`forward_client_cert_details <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>` is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS.If set, Envoy will not append the remote address to the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header.The human readable prefix to use when emitting statistics for the connection manager.Governs Envoy's behavior when receiving invalid HTTP from downstream.The stream idle timeout for connections managed by the connection manager.Determines if the port part should be removed from host/authority header before any processing of request by HTTP filters or routing.Determines if the port part should be removed from host/authority header before any processing of request by HTTP filters or routing.Determines if trailing dot of the host should be removed from host/authority header before any processing of request by HTTP filters or routing.Presence of the object defines whether the connection manager emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider <envoy_v3_api_msg_config.trace.v3.Tracing>`.Configuration options for Header Validation (UHV).repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
If set to true, the connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers.clearVia()
Via header value to append to request and response headers.The number of additional ingress proxy hops from the right side of the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header to trust when determining the origin client's IP address.private void
private void
private void
private void
private void
getAccessLog
(int index) Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.getAccessLogBuilder
(int index) Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.int
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.com.google.protobuf.Duration
Deprecated.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.access_log_flush_interval is deprecated.com.google.protobuf.Duration.Builder
Deprecated.com.google.protobuf.DurationOrBuilder
Deprecated.Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.Additional access log options for HTTP connection manager.Additional access log options for HTTP connection manager.Additional access log options for HTTP connection manager.getAccessLogOrBuilder
(int index) Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.List
<? extends AccessLogOrBuilder> Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.com.google.protobuf.BoolValue
Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state.com.google.protobuf.BoolValue.Builder
Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state.com.google.protobuf.BoolValueOrBuilder
Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state.com.google.protobuf.BoolValue
Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent` and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers.com.google.protobuf.BoolValue.Builder
Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent` and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers.com.google.protobuf.BoolValueOrBuilder
Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent` and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers.boolean
If set, Envoy will always set :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header in response.boolean
Append the :ref:`config_http_conn_man_headers_x-envoy-local-overloaded` HTTP header in the scenario where the Overload Manager has been triggered.boolean
Append the ``x-forwarded-port`` header with the port value client used to connect to Envoy.Supplies the type of codec that the connection manager should use.int
Supplies the type of codec that the connection manager should use.Additional settings for HTTP requests handled by the connection manager.Additional settings for HTTP requests handled by the connection manager.Additional settings for HTTP requests handled by the connection manager.com.google.protobuf.Duration
The delayed close timeout is for downstream connections managed by the HTTP connection manager.com.google.protobuf.Duration.Builder
The delayed close timeout is for downstream connections managed by the HTTP connection manager.com.google.protobuf.DurationOrBuilder
The delayed close timeout is for downstream connections managed by the HTTP connection manager.static final com.google.protobuf.Descriptors.Descriptor
com.google.protobuf.Descriptors.Descriptor
com.google.protobuf.Duration
The time that Envoy will wait between sending an HTTP/2 “shutdown notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame.com.google.protobuf.Duration.Builder
The time that Envoy will wait between sending an HTTP/2 “shutdown notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame.com.google.protobuf.DurationOrBuilder
The time that Envoy will wait between sending an HTTP/2 “shutdown notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame.getEarlyHeaderMutationExtensions
(int index) The configuration for the early header mutation extensions.getEarlyHeaderMutationExtensionsBuilder
(int index) The configuration for the early header mutation extensions.The configuration for the early header mutation extensions.int
The configuration for the early header mutation extensions.The configuration for the early header mutation extensions.getEarlyHeaderMutationExtensionsOrBuilder
(int index) The configuration for the early header mutation extensions.List
<? extends TypedExtensionConfigOrBuilder> The configuration for the early header mutation extensions.boolean
Deprecated.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.flush_access_log_on_new_request is deprecated.How to handle the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` (XFCC) HTTP header.int
How to handle the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` (XFCC) HTTP header.com.google.protobuf.BoolValue
Whether the connection manager will generate the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if it does not exist.com.google.protobuf.BoolValue.Builder
Whether the connection manager will generate the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if it does not exist.com.google.protobuf.BoolValueOrBuilder
Whether the connection manager will generate the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if it does not exist.Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.Additional HTTP/3 settings that are passed directly to the HTTP/3 codec.Additional HTTP/3 settings that are passed directly to the HTTP/3 codec.Additional HTTP/3 settings that are passed directly to the HTTP/3 codec.getHttpFilters
(int index) A list of individual HTTP filters that make up the filter chain for requests made to the connection manager.getHttpFiltersBuilder
(int index) A list of individual HTTP filters that make up the filter chain for requests made to the connection manager.A list of individual HTTP filters that make up the filter chain for requests made to the connection manager.int
A list of individual HTTP filters that make up the filter chain for requests made to the connection manager.A list of individual HTTP filters that make up the filter chain for requests made to the connection manager.getHttpFiltersOrBuilder
(int index) A list of individual HTTP filters that make up the filter chain for requests made to the connection manager.List
<? extends HttpFilterOrBuilder> A list of individual HTTP filters that make up the filter chain for requests made to the connection manager.Additional HTTP/1 settings that are passed to the HTTP/1 codec.Additional HTTP/1 settings that are passed to the HTTP/1 codec.Additional HTTP/1 settings that are passed to the HTTP/1 codec.Configures what network addresses are considered internal for stats and header sanitation purposes.Configures what network addresses are considered internal for stats and header sanitation purposes.Configures what network addresses are considered internal for stats and header sanitation purposes.The configuration to customize local reply returned by Envoy.The configuration to customize local reply returned by Envoy.The configuration to customize local reply returned by Envoy.com.google.protobuf.UInt32Value
The maximum request headers size for incoming connections.com.google.protobuf.UInt32Value.Builder
The maximum request headers size for incoming connections.com.google.protobuf.UInt32ValueOrBuilder
The maximum request headers size for incoming connections.boolean
Determines if adjacent slashes in the path are merged into one before any processing of requests by HTTP filters or routing.com.google.protobuf.BoolValue
Should paths be normalized according to RFC 3986 before any processing of requests by HTTP filters or routing? This affects the upstream ``:path`` header as well.com.google.protobuf.BoolValue.Builder
Should paths be normalized according to RFC 3986 before any processing of requests by HTTP filters or routing? This affects the upstream ``:path`` header as well.com.google.protobuf.BoolValueOrBuilder
Should paths be normalized according to RFC 3986 before any processing of requests by HTTP filters or routing? This affects the upstream ``:path`` header as well.getOriginalIpDetectionExtensions
(int index) The configuration for the original IP detection extensions.getOriginalIpDetectionExtensionsBuilder
(int index) The configuration for the original IP detection extensions.The configuration for the original IP detection extensions.int
The configuration for the original IP detection extensions.The configuration for the original IP detection extensions.getOriginalIpDetectionExtensionsOrBuilder
(int index) The configuration for the original IP detection extensions.List
<? extends TypedExtensionConfigOrBuilder> The configuration for the original IP detection extensions.[#not-implemented-hide:] Path normalization configuration.[#not-implemented-hide:] Path normalization configuration.[#not-implemented-hide:] Path normalization configuration.Action to take when request URL path contains escaped slash sequences (%2F, %2f, %5C and %5c).int
Action to take when request URL path contains escaped slash sequences (%2F, %2f, %5C and %5c).boolean
Whether the connection manager will keep the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if passed for a request that is edge (Edge request is the request from external clients to front Envoy) and not reset it, which is the current Envoy behaviour.boolean
If proxy_100_continue is true, Envoy will proxy incoming "Expect: 100-continue" headers upstream, and forward "100 Continue" responses downstream.Proxy-Status HTTP response header configuration.Proxy-Status HTTP response header configuration.Proxy-Status HTTP response header configuration.getRds()
The connection manager’s route table will be dynamically loaded via the RDS API.The connection manager’s route table will be dynamically loaded via the RDS API.The connection manager’s route table will be dynamically loaded via the RDS API.boolean
If :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` is true and represent_ipv4_remote_address_as_ipv4_mapped_ipv6 is true and the remote address is an IPv4 address, the address will be mapped to IPv6 before it is appended to ``x-forwarded-for``.com.google.protobuf.Duration
The amount of time that Envoy will wait for the request headers to be received.com.google.protobuf.Duration.Builder
The amount of time that Envoy will wait for the request headers to be received.com.google.protobuf.DurationOrBuilder
The amount of time that Envoy will wait for the request headers to be received.The configuration of the request ID extension.The configuration of the request ID extension.The configuration of the request ID extension.com.google.protobuf.Duration
The amount of time that Envoy will wait for the entire request to be received.com.google.protobuf.Duration.Builder
The amount of time that Envoy will wait for the entire request to be received.com.google.protobuf.DurationOrBuilder
The amount of time that Envoy will wait for the entire request to be received.The route table for the connection manager is static and is specified in this property.The route table for the connection manager is static and is specified in this property.The route table for the connection manager is static and is specified in this property.Allows for explicit transformation of the :scheme header on the request path.Allows for explicit transformation of the :scheme header on the request path.Allows for explicit transformation of the :scheme header on the request path.A route table will be dynamically assigned to each request based on request attributes (e.g., the value of a header).A route table will be dynamically assigned to each request based on request attributes (e.g., the value of a header).A route table will be dynamically assigned to each request based on request attributes (e.g., the value of a header).Defines the action to be applied to the Server header on the response path.int
Defines the action to be applied to the Server header on the response path.An optional override that the connection manager will write to the server header in responses.com.google.protobuf.ByteString
An optional override that the connection manager will write to the server header in responses.This field is valid only when :ref:`forward_client_cert_details <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>` is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS.This field is valid only when :ref:`forward_client_cert_details <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>` is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS.This field is valid only when :ref:`forward_client_cert_details <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>` is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS.boolean
If set, Envoy will not append the remote address to the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header.The human readable prefix to use when emitting statistics for the connection manager.com.google.protobuf.ByteString
The human readable prefix to use when emitting statistics for the connection manager.com.google.protobuf.BoolValue
Governs Envoy's behavior when receiving invalid HTTP from downstream.com.google.protobuf.BoolValue.Builder
Governs Envoy's behavior when receiving invalid HTTP from downstream.com.google.protobuf.BoolValueOrBuilder
Governs Envoy's behavior when receiving invalid HTTP from downstream.com.google.protobuf.Duration
The stream idle timeout for connections managed by the connection manager.com.google.protobuf.Duration.Builder
The stream idle timeout for connections managed by the connection manager.com.google.protobuf.DurationOrBuilder
The stream idle timeout for connections managed by the connection manager.boolean
Determines if the port part should be removed from host/authority header before any processing of request by HTTP filters or routing.boolean
Determines if the port part should be removed from host/authority header before any processing of request by HTTP filters or routing.boolean
Determines if trailing dot of the host should be removed from host/authority header before any processing of request by HTTP filters or routing.Presence of the object defines whether the connection manager emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider <envoy_v3_api_msg_config.trace.v3.Tracing>`.Presence of the object defines whether the connection manager emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider <envoy_v3_api_msg_config.trace.v3.Tracing>`.Presence of the object defines whether the connection manager emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider <envoy_v3_api_msg_config.trace.v3.Tracing>`.Configuration options for Header Validation (UHV).Configuration options for Header Validation (UHV).Configuration options for Header Validation (UHV).getUpgradeConfigs
(int index) repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
getUpgradeConfigsBuilder
(int index) repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
int
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
getUpgradeConfigsOrBuilder
(int index) repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
List
<? extends HttpConnectionManager.UpgradeConfigOrBuilder> repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
com.google.protobuf.BoolValue
If set to true, the connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers.com.google.protobuf.BoolValue.Builder
If set to true, the connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers.com.google.protobuf.BoolValueOrBuilder
If set to true, the connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers.getVia()
Via header value to append to request and response headers.com.google.protobuf.ByteString
Via header value to append to request and response headers.int
The number of additional ingress proxy hops from the right side of the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header to trust when determining the origin client's IP address.boolean
Deprecated.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.access_log_flush_interval is deprecated.boolean
Additional access log options for HTTP connection manager.boolean
Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state.boolean
Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent` and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers.boolean
Additional settings for HTTP requests handled by the connection manager.boolean
The delayed close timeout is for downstream connections managed by the HTTP connection manager.boolean
The time that Envoy will wait between sending an HTTP/2 “shutdown notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame.boolean
Whether the connection manager will generate the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if it does not exist.boolean
Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.boolean
Additional HTTP/3 settings that are passed directly to the HTTP/3 codec.boolean
Additional HTTP/1 settings that are passed to the HTTP/1 codec.boolean
Configures what network addresses are considered internal for stats and header sanitation purposes.boolean
The configuration to customize local reply returned by Envoy.boolean
The maximum request headers size for incoming connections.boolean
Should paths be normalized according to RFC 3986 before any processing of requests by HTTP filters or routing? This affects the upstream ``:path`` header as well.boolean
[#not-implemented-hide:] Path normalization configuration.boolean
Proxy-Status HTTP response header configuration.boolean
hasRds()
The connection manager’s route table will be dynamically loaded via the RDS API.boolean
The amount of time that Envoy will wait for the request headers to be received.boolean
The configuration of the request ID extension.boolean
The amount of time that Envoy will wait for the entire request to be received.boolean
The route table for the connection manager is static and is specified in this property.boolean
Allows for explicit transformation of the :scheme header on the request path.boolean
A route table will be dynamically assigned to each request based on request attributes (e.g., the value of a header).boolean
This field is valid only when :ref:`forward_client_cert_details <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>` is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS.boolean
Governs Envoy's behavior when receiving invalid HTTP from downstream.boolean
The stream idle timeout for connections managed by the connection manager.boolean
Determines if the port part should be removed from host/authority header before any processing of request by HTTP filters or routing.boolean
Presence of the object defines whether the connection manager emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider <envoy_v3_api_msg_config.trace.v3.Tracing>`.boolean
Configuration options for Header Validation (UHV).boolean
If set to true, the connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers.private com.google.protobuf.RepeatedFieldBuilder
<AccessLog, AccessLog.Builder, AccessLogOrBuilder> private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.Duration, com.google.protobuf.Duration.Builder, com.google.protobuf.DurationOrBuilder> ..private com.google.protobuf.SingleFieldBuilder
<HttpConnectionManager.HcmAccessLogOptions, HttpConnectionManager.HcmAccessLogOptions.Builder, HttpConnectionManager.HcmAccessLogOptionsOrBuilder> Additional access log options for HTTP connection manager.private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.BoolValue, com.google.protobuf.BoolValue.Builder, com.google.protobuf.BoolValueOrBuilder> Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state.private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.BoolValue, com.google.protobuf.BoolValue.Builder, com.google.protobuf.BoolValueOrBuilder> Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent` and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers.private com.google.protobuf.SingleFieldBuilder
<HttpProtocolOptions, HttpProtocolOptions.Builder, HttpProtocolOptionsOrBuilder> Additional settings for HTTP requests handled by the connection manager.private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.Duration, com.google.protobuf.Duration.Builder, com.google.protobuf.DurationOrBuilder> The delayed close timeout is for downstream connections managed by the HTTP connection manager.private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.Duration, com.google.protobuf.Duration.Builder, com.google.protobuf.DurationOrBuilder> The time that Envoy will wait between sending an HTTP/2 “shutdown notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame.private com.google.protobuf.RepeatedFieldBuilder
<TypedExtensionConfig, TypedExtensionConfig.Builder, TypedExtensionConfigOrBuilder> protected com.google.protobuf.GeneratedMessage.FieldAccessorTable
private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.BoolValue, com.google.protobuf.BoolValue.Builder, com.google.protobuf.BoolValueOrBuilder> Whether the connection manager will generate the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if it does not exist.private com.google.protobuf.SingleFieldBuilder
<Http2ProtocolOptions, Http2ProtocolOptions.Builder, Http2ProtocolOptionsOrBuilder> Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.private com.google.protobuf.SingleFieldBuilder
<Http3ProtocolOptions, Http3ProtocolOptions.Builder, Http3ProtocolOptionsOrBuilder> Additional HTTP/3 settings that are passed directly to the HTTP/3 codec.private com.google.protobuf.RepeatedFieldBuilder
<HttpFilter, HttpFilter.Builder, HttpFilterOrBuilder> private com.google.protobuf.SingleFieldBuilder
<Http1ProtocolOptions, Http1ProtocolOptions.Builder, Http1ProtocolOptionsOrBuilder> Additional HTTP/1 settings that are passed to the HTTP/1 codec.private com.google.protobuf.SingleFieldBuilder
<HttpConnectionManager.InternalAddressConfig, HttpConnectionManager.InternalAddressConfig.Builder, HttpConnectionManager.InternalAddressConfigOrBuilder> Configures what network addresses are considered internal for stats and header sanitation purposes.private com.google.protobuf.SingleFieldBuilder
<LocalReplyConfig, LocalReplyConfig.Builder, LocalReplyConfigOrBuilder> The configuration to customize local reply returned by Envoy.private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.UInt32Value, com.google.protobuf.UInt32Value.Builder, com.google.protobuf.UInt32ValueOrBuilder> The maximum request headers size for incoming connections.private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.BoolValue, com.google.protobuf.BoolValue.Builder, com.google.protobuf.BoolValueOrBuilder> Should paths be normalized according to RFC 3986 before any processing of requests by HTTP filters or routing? This affects the upstream ``:path`` header as well.private com.google.protobuf.RepeatedFieldBuilder
<TypedExtensionConfig, TypedExtensionConfig.Builder, TypedExtensionConfigOrBuilder> private com.google.protobuf.SingleFieldBuilder
<HttpConnectionManager.PathNormalizationOptions, HttpConnectionManager.PathNormalizationOptions.Builder, HttpConnectionManager.PathNormalizationOptionsOrBuilder> [#not-implemented-hide:] Path normalization configuration.private com.google.protobuf.SingleFieldBuilder
<HttpConnectionManager.ProxyStatusConfig, HttpConnectionManager.ProxyStatusConfig.Builder, HttpConnectionManager.ProxyStatusConfigOrBuilder> Proxy-Status HTTP response header configuration.private com.google.protobuf.SingleFieldBuilder
<Rds, Rds.Builder, RdsOrBuilder> The connection manager’s route table will be dynamically loaded via the RDS API.private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.Duration, com.google.protobuf.Duration.Builder, com.google.protobuf.DurationOrBuilder> The amount of time that Envoy will wait for the request headers to be received.private com.google.protobuf.SingleFieldBuilder
<RequestIDExtension, RequestIDExtension.Builder, RequestIDExtensionOrBuilder> The configuration of the request ID extension.private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.Duration, com.google.protobuf.Duration.Builder, com.google.protobuf.DurationOrBuilder> The amount of time that Envoy will wait for the entire request to be received.private com.google.protobuf.SingleFieldBuilder
<RouteConfiguration, RouteConfiguration.Builder, RouteConfigurationOrBuilder> The route table for the connection manager is static and is specified in this property.private com.google.protobuf.SingleFieldBuilder
<SchemeHeaderTransformation, SchemeHeaderTransformation.Builder, SchemeHeaderTransformationOrBuilder> Allows for explicit transformation of the :scheme header on the request path.private com.google.protobuf.SingleFieldBuilder
<ScopedRoutes, ScopedRoutes.Builder, ScopedRoutesOrBuilder> A route table will be dynamically assigned to each request based on request attributes (e.g., the value of a header).private com.google.protobuf.SingleFieldBuilder
<HttpConnectionManager.SetCurrentClientCertDetails, HttpConnectionManager.SetCurrentClientCertDetails.Builder, HttpConnectionManager.SetCurrentClientCertDetailsOrBuilder> This field is valid only when :ref:`forward_client_cert_details <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>` is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS.private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.BoolValue, com.google.protobuf.BoolValue.Builder, com.google.protobuf.BoolValueOrBuilder> Governs Envoy's behavior when receiving invalid HTTP from downstream.private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.Duration, com.google.protobuf.Duration.Builder, com.google.protobuf.DurationOrBuilder> The stream idle timeout for connections managed by the connection manager.private com.google.protobuf.SingleFieldBuilder
<HttpConnectionManager.Tracing, HttpConnectionManager.Tracing.Builder, HttpConnectionManager.TracingOrBuilder> Presence of the object defines whether the connection manager emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider <envoy_v3_api_msg_config.trace.v3.Tracing>`.private com.google.protobuf.SingleFieldBuilder
<TypedExtensionConfig, TypedExtensionConfig.Builder, TypedExtensionConfigOrBuilder> Configuration options for Header Validation (UHV).private com.google.protobuf.RepeatedFieldBuilder
<HttpConnectionManager.UpgradeConfig, HttpConnectionManager.UpgradeConfig.Builder, HttpConnectionManager.UpgradeConfigOrBuilder> private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.BoolValue, com.google.protobuf.BoolValue.Builder, com.google.protobuf.BoolValueOrBuilder> If set to true, the connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers.final boolean
private void
mergeAccessLogFlushInterval
(com.google.protobuf.Duration value) Deprecated.Additional access log options for HTTP connection manager.mergeAddProxyProtocolConnectionState
(com.google.protobuf.BoolValue value) Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state.mergeAddUserAgent
(com.google.protobuf.BoolValue value) Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent` and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers.Additional settings for HTTP requests handled by the connection manager.mergeDelayedCloseTimeout
(com.google.protobuf.Duration value) The delayed close timeout is for downstream connections managed by the HTTP connection manager.mergeDrainTimeout
(com.google.protobuf.Duration value) The time that Envoy will wait between sending an HTTP/2 “shutdown notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame.mergeFrom
(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) mergeFrom
(com.google.protobuf.Message other) mergeFrom
(HttpConnectionManager other) mergeGenerateRequestId
(com.google.protobuf.BoolValue value) Whether the connection manager will generate the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if it does not exist.Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.Additional HTTP/3 settings that are passed directly to the HTTP/3 codec.Additional HTTP/1 settings that are passed to the HTTP/1 codec.Configures what network addresses are considered internal for stats and header sanitation purposes.The configuration to customize local reply returned by Envoy.mergeMaxRequestHeadersKb
(com.google.protobuf.UInt32Value value) The maximum request headers size for incoming connections.mergeNormalizePath
(com.google.protobuf.BoolValue value) Should paths be normalized according to RFC 3986 before any processing of requests by HTTP filters or routing? This affects the upstream ``:path`` header as well.[#not-implemented-hide:] Path normalization configuration.Proxy-Status HTTP response header configuration.The connection manager’s route table will be dynamically loaded via the RDS API.mergeRequestHeadersTimeout
(com.google.protobuf.Duration value) The amount of time that Envoy will wait for the request headers to be received.The configuration of the request ID extension.mergeRequestTimeout
(com.google.protobuf.Duration value) The amount of time that Envoy will wait for the entire request to be received.The route table for the connection manager is static and is specified in this property.Allows for explicit transformation of the :scheme header on the request path.mergeScopedRoutes
(ScopedRoutes value) A route table will be dynamically assigned to each request based on request attributes (e.g., the value of a header).This field is valid only when :ref:`forward_client_cert_details <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>` is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS.mergeStreamErrorOnInvalidHttpMessage
(com.google.protobuf.BoolValue value) Governs Envoy's behavior when receiving invalid HTTP from downstream.mergeStreamIdleTimeout
(com.google.protobuf.Duration value) The stream idle timeout for connections managed by the connection manager.Presence of the object defines whether the connection manager emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider <envoy_v3_api_msg_config.trace.v3.Tracing>`.Configuration options for Header Validation (UHV).mergeUseRemoteAddress
(com.google.protobuf.BoolValue value) If set to true, the connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers.removeAccessLog
(int index) Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.removeEarlyHeaderMutationExtensions
(int index) The configuration for the early header mutation extensions.removeHttpFilters
(int index) A list of individual HTTP filters that make up the filter chain for requests made to the connection manager.removeOriginalIpDetectionExtensions
(int index) The configuration for the original IP detection extensions.removeUpgradeConfigs
(int index) repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
setAccessLog
(int index, AccessLog value) Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.setAccessLog
(int index, AccessLog.Builder builderForValue) Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.setAccessLogFlushInterval
(com.google.protobuf.Duration value) Deprecated.setAccessLogFlushInterval
(com.google.protobuf.Duration.Builder builderForValue) Deprecated.Additional access log options for HTTP connection manager.setAccessLogOptions
(HttpConnectionManager.HcmAccessLogOptions.Builder builderForValue) Additional access log options for HTTP connection manager.setAddProxyProtocolConnectionState
(com.google.protobuf.BoolValue value) Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state.setAddProxyProtocolConnectionState
(com.google.protobuf.BoolValue.Builder builderForValue) Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state.setAddUserAgent
(com.google.protobuf.BoolValue value) Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent` and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers.setAddUserAgent
(com.google.protobuf.BoolValue.Builder builderForValue) Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent` and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers.setAlwaysSetRequestIdInResponse
(boolean value) If set, Envoy will always set :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header in response.setAppendLocalOverload
(boolean value) Append the :ref:`config_http_conn_man_headers_x-envoy-local-overloaded` HTTP header in the scenario where the Overload Manager has been triggered.setAppendXForwardedPort
(boolean value) Append the ``x-forwarded-port`` header with the port value client used to connect to Envoy.Supplies the type of codec that the connection manager should use.setCodecTypeValue
(int value) Supplies the type of codec that the connection manager should use.Additional settings for HTTP requests handled by the connection manager.setCommonHttpProtocolOptions
(HttpProtocolOptions.Builder builderForValue) Additional settings for HTTP requests handled by the connection manager.setDelayedCloseTimeout
(com.google.protobuf.Duration value) The delayed close timeout is for downstream connections managed by the HTTP connection manager.setDelayedCloseTimeout
(com.google.protobuf.Duration.Builder builderForValue) The delayed close timeout is for downstream connections managed by the HTTP connection manager.setDrainTimeout
(com.google.protobuf.Duration value) The time that Envoy will wait between sending an HTTP/2 “shutdown notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame.setDrainTimeout
(com.google.protobuf.Duration.Builder builderForValue) The time that Envoy will wait between sending an HTTP/2 “shutdown notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame.setEarlyHeaderMutationExtensions
(int index, TypedExtensionConfig value) The configuration for the early header mutation extensions.setEarlyHeaderMutationExtensions
(int index, TypedExtensionConfig.Builder builderForValue) The configuration for the early header mutation extensions.setFlushAccessLogOnNewRequest
(boolean value) Deprecated.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.flush_access_log_on_new_request is deprecated.How to handle the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` (XFCC) HTTP header.setForwardClientCertDetailsValue
(int value) How to handle the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` (XFCC) HTTP header.setGenerateRequestId
(com.google.protobuf.BoolValue value) Whether the connection manager will generate the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if it does not exist.setGenerateRequestId
(com.google.protobuf.BoolValue.Builder builderForValue) Whether the connection manager will generate the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if it does not exist.Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.setHttp2ProtocolOptions
(Http2ProtocolOptions.Builder builderForValue) Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.Additional HTTP/3 settings that are passed directly to the HTTP/3 codec.setHttp3ProtocolOptions
(Http3ProtocolOptions.Builder builderForValue) Additional HTTP/3 settings that are passed directly to the HTTP/3 codec.setHttpFilters
(int index, HttpFilter value) A list of individual HTTP filters that make up the filter chain for requests made to the connection manager.setHttpFilters
(int index, HttpFilter.Builder builderForValue) A list of individual HTTP filters that make up the filter chain for requests made to the connection manager.Additional HTTP/1 settings that are passed to the HTTP/1 codec.setHttpProtocolOptions
(Http1ProtocolOptions.Builder builderForValue) Additional HTTP/1 settings that are passed to the HTTP/1 codec.Configures what network addresses are considered internal for stats and header sanitation purposes.Configures what network addresses are considered internal for stats and header sanitation purposes.The configuration to customize local reply returned by Envoy.setLocalReplyConfig
(LocalReplyConfig.Builder builderForValue) The configuration to customize local reply returned by Envoy.setMaxRequestHeadersKb
(com.google.protobuf.UInt32Value value) The maximum request headers size for incoming connections.setMaxRequestHeadersKb
(com.google.protobuf.UInt32Value.Builder builderForValue) The maximum request headers size for incoming connections.setMergeSlashes
(boolean value) Determines if adjacent slashes in the path are merged into one before any processing of requests by HTTP filters or routing.setNormalizePath
(com.google.protobuf.BoolValue value) Should paths be normalized according to RFC 3986 before any processing of requests by HTTP filters or routing? This affects the upstream ``:path`` header as well.setNormalizePath
(com.google.protobuf.BoolValue.Builder builderForValue) Should paths be normalized according to RFC 3986 before any processing of requests by HTTP filters or routing? This affects the upstream ``:path`` header as well.setOriginalIpDetectionExtensions
(int index, TypedExtensionConfig value) The configuration for the original IP detection extensions.setOriginalIpDetectionExtensions
(int index, TypedExtensionConfig.Builder builderForValue) The configuration for the original IP detection extensions.[#not-implemented-hide:] Path normalization configuration.[#not-implemented-hide:] Path normalization configuration.Action to take when request URL path contains escaped slash sequences (%2F, %2f, %5C and %5c).setPathWithEscapedSlashesActionValue
(int value) Action to take when request URL path contains escaped slash sequences (%2F, %2f, %5C and %5c).setPreserveExternalRequestId
(boolean value) Whether the connection manager will keep the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if passed for a request that is edge (Edge request is the request from external clients to front Envoy) and not reset it, which is the current Envoy behaviour.setProxy100Continue
(boolean value) If proxy_100_continue is true, Envoy will proxy incoming "Expect: 100-continue" headers upstream, and forward "100 Continue" responses downstream.Proxy-Status HTTP response header configuration.setProxyStatusConfig
(HttpConnectionManager.ProxyStatusConfig.Builder builderForValue) Proxy-Status HTTP response header configuration.The connection manager’s route table will be dynamically loaded via the RDS API.setRds
(Rds.Builder builderForValue) The connection manager’s route table will be dynamically loaded via the RDS API.setRepresentIpv4RemoteAddressAsIpv4MappedIpv6
(boolean value) If :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` is true and represent_ipv4_remote_address_as_ipv4_mapped_ipv6 is true and the remote address is an IPv4 address, the address will be mapped to IPv6 before it is appended to ``x-forwarded-for``.setRequestHeadersTimeout
(com.google.protobuf.Duration value) The amount of time that Envoy will wait for the request headers to be received.setRequestHeadersTimeout
(com.google.protobuf.Duration.Builder builderForValue) The amount of time that Envoy will wait for the request headers to be received.The configuration of the request ID extension.setRequestIdExtension
(RequestIDExtension.Builder builderForValue) The configuration of the request ID extension.setRequestTimeout
(com.google.protobuf.Duration value) The amount of time that Envoy will wait for the entire request to be received.setRequestTimeout
(com.google.protobuf.Duration.Builder builderForValue) The amount of time that Envoy will wait for the entire request to be received.setRouteConfig
(RouteConfiguration value) The route table for the connection manager is static and is specified in this property.setRouteConfig
(RouteConfiguration.Builder builderForValue) The route table for the connection manager is static and is specified in this property.Allows for explicit transformation of the :scheme header on the request path.setSchemeHeaderTransformation
(SchemeHeaderTransformation.Builder builderForValue) Allows for explicit transformation of the :scheme header on the request path.setScopedRoutes
(ScopedRoutes value) A route table will be dynamically assigned to each request based on request attributes (e.g., the value of a header).setScopedRoutes
(ScopedRoutes.Builder builderForValue) A route table will be dynamically assigned to each request based on request attributes (e.g., the value of a header).Defines the action to be applied to the Server header on the response path.setServerHeaderTransformationValue
(int value) Defines the action to be applied to the Server header on the response path.setServerName
(String value) An optional override that the connection manager will write to the server header in responses.setServerNameBytes
(com.google.protobuf.ByteString value) An optional override that the connection manager will write to the server header in responses.This field is valid only when :ref:`forward_client_cert_details <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>` is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS.setSetCurrentClientCertDetails
(HttpConnectionManager.SetCurrentClientCertDetails.Builder builderForValue) This field is valid only when :ref:`forward_client_cert_details <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>` is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS.setSkipXffAppend
(boolean value) If set, Envoy will not append the remote address to the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header.setStatPrefix
(String value) The human readable prefix to use when emitting statistics for the connection manager.setStatPrefixBytes
(com.google.protobuf.ByteString value) The human readable prefix to use when emitting statistics for the connection manager.setStreamErrorOnInvalidHttpMessage
(com.google.protobuf.BoolValue value) Governs Envoy's behavior when receiving invalid HTTP from downstream.setStreamErrorOnInvalidHttpMessage
(com.google.protobuf.BoolValue.Builder builderForValue) Governs Envoy's behavior when receiving invalid HTTP from downstream.setStreamIdleTimeout
(com.google.protobuf.Duration value) The stream idle timeout for connections managed by the connection manager.setStreamIdleTimeout
(com.google.protobuf.Duration.Builder builderForValue) The stream idle timeout for connections managed by the connection manager.setStripAnyHostPort
(boolean value) Determines if the port part should be removed from host/authority header before any processing of request by HTTP filters or routing.setStripMatchingHostPort
(boolean value) Determines if the port part should be removed from host/authority header before any processing of request by HTTP filters or routing.setStripTrailingHostDot
(boolean value) Determines if trailing dot of the host should be removed from host/authority header before any processing of request by HTTP filters or routing.Presence of the object defines whether the connection manager emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider <envoy_v3_api_msg_config.trace.v3.Tracing>`.setTracing
(HttpConnectionManager.Tracing.Builder builderForValue) Presence of the object defines whether the connection manager emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider <envoy_v3_api_msg_config.trace.v3.Tracing>`.Configuration options for Header Validation (UHV).setTypedHeaderValidationConfig
(TypedExtensionConfig.Builder builderForValue) Configuration options for Header Validation (UHV).setUpgradeConfigs
(int index, HttpConnectionManager.UpgradeConfig value) repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
setUpgradeConfigs
(int index, HttpConnectionManager.UpgradeConfig.Builder builderForValue) repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
setUseRemoteAddress
(com.google.protobuf.BoolValue value) If set to true, the connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers.setUseRemoteAddress
(com.google.protobuf.BoolValue.Builder builderForValue) If set to true, the connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers.Via header value to append to request and response headers.setViaBytes
(com.google.protobuf.ByteString value) Via header value to append to request and response headers.setXffNumTrustedHops
(int value) The number of additional ingress proxy hops from the right side of the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header to trust when determining the origin client's IP address.Methods inherited from class com.google.protobuf.GeneratedMessage.Builder
addRepeatedField, clearField, clearOneof, clone, getAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, getUnknownFieldSetBuilder, hasField, hasOneof, internalGetMapField, internalGetMapFieldReflection, internalGetMutableMapField, internalGetMutableMapFieldReflection, isClean, markClean, mergeUnknownFields, mergeUnknownLengthDelimitedField, mergeUnknownVarintField, newBuilderForField, onBuilt, onChanged, parseUnknownField, setField, setRepeatedField, setUnknownFields, setUnknownFieldSetBuilder, setUnknownFieldsProto3
Methods inherited from class com.google.protobuf.AbstractMessage.Builder
findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toString
Methods inherited from class com.google.protobuf.AbstractMessageLite.Builder
addAll, addAll, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, newUninitializedMessageException
Methods inherited from class java.lang.Object
equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
Methods inherited from interface com.google.protobuf.Message.Builder
mergeDelimitedFrom, mergeDelimitedFrom
Methods inherited from interface com.google.protobuf.MessageLite.Builder
mergeFrom
Methods inherited from interface com.google.protobuf.MessageOrBuilder
findInitializationErrors, getAllFields, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
-
Field Details
-
routeSpecifierCase_
private int routeSpecifierCase_ -
routeSpecifier_
-
stripPortModeCase_
private int stripPortModeCase_ -
stripPortMode_
-
bitField0_
private int bitField0_ -
bitField1_
private int bitField1_ -
codecType_
private int codecType_ -
statPrefix_
-
rdsBuilder_
-
routeConfigBuilder_
private com.google.protobuf.SingleFieldBuilder<RouteConfiguration,RouteConfiguration.Builder, routeConfigBuilder_RouteConfigurationOrBuilder> -
scopedRoutesBuilder_
private com.google.protobuf.SingleFieldBuilder<ScopedRoutes,ScopedRoutes.Builder, scopedRoutesBuilder_ScopedRoutesOrBuilder> -
httpFilters_
-
httpFiltersBuilder_
private com.google.protobuf.RepeatedFieldBuilder<HttpFilter,HttpFilter.Builder, httpFiltersBuilder_HttpFilterOrBuilder> -
addUserAgent_
private com.google.protobuf.BoolValue addUserAgent_ -
addUserAgentBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder, addUserAgentBuilder_com.google.protobuf.BoolValueOrBuilder> -
tracing_
-
tracingBuilder_
private com.google.protobuf.SingleFieldBuilder<HttpConnectionManager.Tracing,HttpConnectionManager.Tracing.Builder, tracingBuilder_HttpConnectionManager.TracingOrBuilder> -
commonHttpProtocolOptions_
-
commonHttpProtocolOptionsBuilder_
private com.google.protobuf.SingleFieldBuilder<HttpProtocolOptions,HttpProtocolOptions.Builder, commonHttpProtocolOptionsBuilder_HttpProtocolOptionsOrBuilder> -
httpProtocolOptions_
-
httpProtocolOptionsBuilder_
private com.google.protobuf.SingleFieldBuilder<Http1ProtocolOptions,Http1ProtocolOptions.Builder, httpProtocolOptionsBuilder_Http1ProtocolOptionsOrBuilder> -
http2ProtocolOptions_
-
http2ProtocolOptionsBuilder_
private com.google.protobuf.SingleFieldBuilder<Http2ProtocolOptions,Http2ProtocolOptions.Builder, http2ProtocolOptionsBuilder_Http2ProtocolOptionsOrBuilder> -
http3ProtocolOptions_
-
http3ProtocolOptionsBuilder_
private com.google.protobuf.SingleFieldBuilder<Http3ProtocolOptions,Http3ProtocolOptions.Builder, http3ProtocolOptionsBuilder_Http3ProtocolOptionsOrBuilder> -
serverName_
-
serverHeaderTransformation_
private int serverHeaderTransformation_ -
schemeHeaderTransformation_
-
schemeHeaderTransformationBuilder_
private com.google.protobuf.SingleFieldBuilder<SchemeHeaderTransformation,SchemeHeaderTransformation.Builder, schemeHeaderTransformationBuilder_SchemeHeaderTransformationOrBuilder> -
maxRequestHeadersKb_
private com.google.protobuf.UInt32Value maxRequestHeadersKb_ -
maxRequestHeadersKbBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.UInt32Value,com.google.protobuf.UInt32Value.Builder, maxRequestHeadersKbBuilder_com.google.protobuf.UInt32ValueOrBuilder> -
streamIdleTimeout_
private com.google.protobuf.Duration streamIdleTimeout_ -
streamIdleTimeoutBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder, streamIdleTimeoutBuilder_com.google.protobuf.DurationOrBuilder> -
requestTimeout_
private com.google.protobuf.Duration requestTimeout_ -
requestTimeoutBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder, requestTimeoutBuilder_com.google.protobuf.DurationOrBuilder> -
requestHeadersTimeout_
private com.google.protobuf.Duration requestHeadersTimeout_ -
requestHeadersTimeoutBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder, requestHeadersTimeoutBuilder_com.google.protobuf.DurationOrBuilder> -
drainTimeout_
private com.google.protobuf.Duration drainTimeout_ -
drainTimeoutBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder, drainTimeoutBuilder_com.google.protobuf.DurationOrBuilder> -
delayedCloseTimeout_
private com.google.protobuf.Duration delayedCloseTimeout_ -
delayedCloseTimeoutBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder, delayedCloseTimeoutBuilder_com.google.protobuf.DurationOrBuilder> -
accessLog_
-
accessLogBuilder_
private com.google.protobuf.RepeatedFieldBuilder<AccessLog,AccessLog.Builder, accessLogBuilder_AccessLogOrBuilder> -
accessLogFlushInterval_
private com.google.protobuf.Duration accessLogFlushInterval_ -
accessLogFlushIntervalBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder, accessLogFlushIntervalBuilder_com.google.protobuf.DurationOrBuilder> -
flushAccessLogOnNewRequest_
private boolean flushAccessLogOnNewRequest_ -
accessLogOptions_
-
accessLogOptionsBuilder_
private com.google.protobuf.SingleFieldBuilder<HttpConnectionManager.HcmAccessLogOptions,HttpConnectionManager.HcmAccessLogOptions.Builder, accessLogOptionsBuilder_HttpConnectionManager.HcmAccessLogOptionsOrBuilder> -
useRemoteAddress_
private com.google.protobuf.BoolValue useRemoteAddress_ -
useRemoteAddressBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder, useRemoteAddressBuilder_com.google.protobuf.BoolValueOrBuilder> -
xffNumTrustedHops_
private int xffNumTrustedHops_ -
originalIpDetectionExtensions_
-
originalIpDetectionExtensionsBuilder_
private com.google.protobuf.RepeatedFieldBuilder<TypedExtensionConfig,TypedExtensionConfig.Builder, originalIpDetectionExtensionsBuilder_TypedExtensionConfigOrBuilder> -
earlyHeaderMutationExtensions_
-
earlyHeaderMutationExtensionsBuilder_
private com.google.protobuf.RepeatedFieldBuilder<TypedExtensionConfig,TypedExtensionConfig.Builder, earlyHeaderMutationExtensionsBuilder_TypedExtensionConfigOrBuilder> -
internalAddressConfig_
-
internalAddressConfigBuilder_
private com.google.protobuf.SingleFieldBuilder<HttpConnectionManager.InternalAddressConfig,HttpConnectionManager.InternalAddressConfig.Builder, internalAddressConfigBuilder_HttpConnectionManager.InternalAddressConfigOrBuilder> -
skipXffAppend_
private boolean skipXffAppend_ -
via_
-
generateRequestId_
private com.google.protobuf.BoolValue generateRequestId_ -
generateRequestIdBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder, generateRequestIdBuilder_com.google.protobuf.BoolValueOrBuilder> -
preserveExternalRequestId_
private boolean preserveExternalRequestId_ -
alwaysSetRequestIdInResponse_
private boolean alwaysSetRequestIdInResponse_ -
forwardClientCertDetails_
private int forwardClientCertDetails_ -
setCurrentClientCertDetails_
-
setCurrentClientCertDetailsBuilder_
private com.google.protobuf.SingleFieldBuilder<HttpConnectionManager.SetCurrentClientCertDetails,HttpConnectionManager.SetCurrentClientCertDetails.Builder, setCurrentClientCertDetailsBuilder_HttpConnectionManager.SetCurrentClientCertDetailsOrBuilder> -
proxy100Continue_
private boolean proxy100Continue_ -
representIpv4RemoteAddressAsIpv4MappedIpv6_
private boolean representIpv4RemoteAddressAsIpv4MappedIpv6_ -
upgradeConfigs_
-
upgradeConfigsBuilder_
private com.google.protobuf.RepeatedFieldBuilder<HttpConnectionManager.UpgradeConfig,HttpConnectionManager.UpgradeConfig.Builder, upgradeConfigsBuilder_HttpConnectionManager.UpgradeConfigOrBuilder> -
normalizePath_
private com.google.protobuf.BoolValue normalizePath_ -
normalizePathBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder, normalizePathBuilder_com.google.protobuf.BoolValueOrBuilder> -
mergeSlashes_
private boolean mergeSlashes_ -
pathWithEscapedSlashesAction_
private int pathWithEscapedSlashesAction_ -
requestIdExtension_
-
requestIdExtensionBuilder_
private com.google.protobuf.SingleFieldBuilder<RequestIDExtension,RequestIDExtension.Builder, requestIdExtensionBuilder_RequestIDExtensionOrBuilder> -
localReplyConfig_
-
localReplyConfigBuilder_
private com.google.protobuf.SingleFieldBuilder<LocalReplyConfig,LocalReplyConfig.Builder, localReplyConfigBuilder_LocalReplyConfigOrBuilder> -
stripMatchingHostPort_
private boolean stripMatchingHostPort_ -
streamErrorOnInvalidHttpMessage_
private com.google.protobuf.BoolValue streamErrorOnInvalidHttpMessage_ -
streamErrorOnInvalidHttpMessageBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder, streamErrorOnInvalidHttpMessageBuilder_com.google.protobuf.BoolValueOrBuilder> -
pathNormalizationOptions_
-
pathNormalizationOptionsBuilder_
private com.google.protobuf.SingleFieldBuilder<HttpConnectionManager.PathNormalizationOptions,HttpConnectionManager.PathNormalizationOptions.Builder, pathNormalizationOptionsBuilder_HttpConnectionManager.PathNormalizationOptionsOrBuilder> -
stripTrailingHostDot_
private boolean stripTrailingHostDot_ -
proxyStatusConfig_
-
proxyStatusConfigBuilder_
private com.google.protobuf.SingleFieldBuilder<HttpConnectionManager.ProxyStatusConfig,HttpConnectionManager.ProxyStatusConfig.Builder, proxyStatusConfigBuilder_HttpConnectionManager.ProxyStatusConfigOrBuilder> -
typedHeaderValidationConfig_
-
typedHeaderValidationConfigBuilder_
private com.google.protobuf.SingleFieldBuilder<TypedExtensionConfig,TypedExtensionConfig.Builder, typedHeaderValidationConfigBuilder_TypedExtensionConfigOrBuilder> -
appendXForwardedPort_
private boolean appendXForwardedPort_ -
appendLocalOverload_
private boolean appendLocalOverload_ -
addProxyProtocolConnectionState_
private com.google.protobuf.BoolValue addProxyProtocolConnectionState_ -
addProxyProtocolConnectionStateBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder, addProxyProtocolConnectionStateBuilder_com.google.protobuf.BoolValueOrBuilder>
-
-
Constructor Details
-
Builder
private Builder() -
Builder
private Builder(com.google.protobuf.AbstractMessage.BuilderParent parent)
-
-
Method Details
-
getDescriptor
public static final com.google.protobuf.Descriptors.Descriptor getDescriptor() -
internalGetFieldAccessorTable
protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()- Specified by:
internalGetFieldAccessorTable
in classcom.google.protobuf.GeneratedMessage.Builder<HttpConnectionManager.Builder>
-
maybeForceBuilderInitialization
private void maybeForceBuilderInitialization() -
clear
- Specified by:
clear
in interfacecom.google.protobuf.Message.Builder
- Specified by:
clear
in interfacecom.google.protobuf.MessageLite.Builder
- Overrides:
clear
in classcom.google.protobuf.GeneratedMessage.Builder<HttpConnectionManager.Builder>
-
getDescriptorForType
public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()- Specified by:
getDescriptorForType
in interfacecom.google.protobuf.Message.Builder
- Specified by:
getDescriptorForType
in interfacecom.google.protobuf.MessageOrBuilder
- Overrides:
getDescriptorForType
in classcom.google.protobuf.GeneratedMessage.Builder<HttpConnectionManager.Builder>
-
getDefaultInstanceForType
- Specified by:
getDefaultInstanceForType
in interfacecom.google.protobuf.MessageLiteOrBuilder
- Specified by:
getDefaultInstanceForType
in interfacecom.google.protobuf.MessageOrBuilder
-
build
- Specified by:
build
in interfacecom.google.protobuf.Message.Builder
- Specified by:
build
in interfacecom.google.protobuf.MessageLite.Builder
-
buildPartial
- Specified by:
buildPartial
in interfacecom.google.protobuf.Message.Builder
- Specified by:
buildPartial
in interfacecom.google.protobuf.MessageLite.Builder
-
buildPartialRepeatedFields
-
buildPartial0
-
buildPartial1
-
buildPartialOneofs
-
mergeFrom
- Specified by:
mergeFrom
in interfacecom.google.protobuf.Message.Builder
- Overrides:
mergeFrom
in classcom.google.protobuf.AbstractMessage.Builder<HttpConnectionManager.Builder>
-
mergeFrom
-
isInitialized
public final boolean isInitialized()- Specified by:
isInitialized
in interfacecom.google.protobuf.MessageLiteOrBuilder
- Overrides:
isInitialized
in classcom.google.protobuf.GeneratedMessage.Builder<HttpConnectionManager.Builder>
-
mergeFrom
public HttpConnectionManager.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException - Specified by:
mergeFrom
in interfacecom.google.protobuf.Message.Builder
- Specified by:
mergeFrom
in interfacecom.google.protobuf.MessageLite.Builder
- Overrides:
mergeFrom
in classcom.google.protobuf.AbstractMessage.Builder<HttpConnectionManager.Builder>
- Throws:
IOException
-
getRouteSpecifierCase
- Specified by:
getRouteSpecifierCase
in interfaceHttpConnectionManagerOrBuilder
-
clearRouteSpecifier
-
getStripPortModeCase
- Specified by:
getStripPortModeCase
in interfaceHttpConnectionManagerOrBuilder
-
clearStripPortMode
-
getCodecTypeValue
public int getCodecTypeValue()Supplies the type of codec that the connection manager should use.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.CodecType codec_type = 1 [(.validate.rules) = { ... }
- Specified by:
getCodecTypeValue
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The enum numeric value on the wire for codecType.
-
setCodecTypeValue
Supplies the type of codec that the connection manager should use.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.CodecType codec_type = 1 [(.validate.rules) = { ... }
- Parameters:
value
- The enum numeric value on the wire for codecType to set.- Returns:
- This builder for chaining.
-
getCodecType
Supplies the type of codec that the connection manager should use.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.CodecType codec_type = 1 [(.validate.rules) = { ... }
- Specified by:
getCodecType
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The codecType.
-
setCodecType
Supplies the type of codec that the connection manager should use.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.CodecType codec_type = 1 [(.validate.rules) = { ... }
- Parameters:
value
- The codecType to set.- Returns:
- This builder for chaining.
-
clearCodecType
Supplies the type of codec that the connection manager should use.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.CodecType codec_type = 1 [(.validate.rules) = { ... }
- Returns:
- This builder for chaining.
-
getStatPrefix
The human readable prefix to use when emitting statistics for the connection manager. See the :ref:`statistics documentation <config_http_conn_man_stats>` for more information.
string stat_prefix = 2 [(.validate.rules) = { ... }
- Specified by:
getStatPrefix
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The statPrefix.
-
getStatPrefixBytes
public com.google.protobuf.ByteString getStatPrefixBytes()The human readable prefix to use when emitting statistics for the connection manager. See the :ref:`statistics documentation <config_http_conn_man_stats>` for more information.
string stat_prefix = 2 [(.validate.rules) = { ... }
- Specified by:
getStatPrefixBytes
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The bytes for statPrefix.
-
setStatPrefix
The human readable prefix to use when emitting statistics for the connection manager. See the :ref:`statistics documentation <config_http_conn_man_stats>` for more information.
string stat_prefix = 2 [(.validate.rules) = { ... }
- Parameters:
value
- The statPrefix to set.- Returns:
- This builder for chaining.
-
clearStatPrefix
The human readable prefix to use when emitting statistics for the connection manager. See the :ref:`statistics documentation <config_http_conn_man_stats>` for more information.
string stat_prefix = 2 [(.validate.rules) = { ... }
- Returns:
- This builder for chaining.
-
setStatPrefixBytes
The human readable prefix to use when emitting statistics for the connection manager. See the :ref:`statistics documentation <config_http_conn_man_stats>` for more information.
string stat_prefix = 2 [(.validate.rules) = { ... }
- Parameters:
value
- The bytes for statPrefix to set.- Returns:
- This builder for chaining.
-
hasRds
public boolean hasRds()The connection manager’s route table will be dynamically loaded via the RDS API.
.envoy.extensions.filters.network.http_connection_manager.v3.Rds rds = 3;
- Specified by:
hasRds
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the rds field is set.
-
getRds
The connection manager’s route table will be dynamically loaded via the RDS API.
.envoy.extensions.filters.network.http_connection_manager.v3.Rds rds = 3;
- Specified by:
getRds
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The rds.
-
setRds
The connection manager’s route table will be dynamically loaded via the RDS API.
.envoy.extensions.filters.network.http_connection_manager.v3.Rds rds = 3;
-
setRds
The connection manager’s route table will be dynamically loaded via the RDS API.
.envoy.extensions.filters.network.http_connection_manager.v3.Rds rds = 3;
-
mergeRds
The connection manager’s route table will be dynamically loaded via the RDS API.
.envoy.extensions.filters.network.http_connection_manager.v3.Rds rds = 3;
-
clearRds
The connection manager’s route table will be dynamically loaded via the RDS API.
.envoy.extensions.filters.network.http_connection_manager.v3.Rds rds = 3;
-
getRdsBuilder
The connection manager’s route table will be dynamically loaded via the RDS API.
.envoy.extensions.filters.network.http_connection_manager.v3.Rds rds = 3;
-
getRdsOrBuilder
The connection manager’s route table will be dynamically loaded via the RDS API.
.envoy.extensions.filters.network.http_connection_manager.v3.Rds rds = 3;
- Specified by:
getRdsOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetRdsFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Rds,Rds.Builder, internalGetRdsFieldBuilder()RdsOrBuilder> The connection manager’s route table will be dynamically loaded via the RDS API.
.envoy.extensions.filters.network.http_connection_manager.v3.Rds rds = 3;
-
hasRouteConfig
public boolean hasRouteConfig()The route table for the connection manager is static and is specified in this property.
.envoy.config.route.v3.RouteConfiguration route_config = 4;
- Specified by:
hasRouteConfig
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the routeConfig field is set.
-
getRouteConfig
The route table for the connection manager is static and is specified in this property.
.envoy.config.route.v3.RouteConfiguration route_config = 4;
- Specified by:
getRouteConfig
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The routeConfig.
-
setRouteConfig
The route table for the connection manager is static and is specified in this property.
.envoy.config.route.v3.RouteConfiguration route_config = 4;
-
setRouteConfig
The route table for the connection manager is static and is specified in this property.
.envoy.config.route.v3.RouteConfiguration route_config = 4;
-
mergeRouteConfig
The route table for the connection manager is static and is specified in this property.
.envoy.config.route.v3.RouteConfiguration route_config = 4;
-
clearRouteConfig
The route table for the connection manager is static and is specified in this property.
.envoy.config.route.v3.RouteConfiguration route_config = 4;
-
getRouteConfigBuilder
The route table for the connection manager is static and is specified in this property.
.envoy.config.route.v3.RouteConfiguration route_config = 4;
-
getRouteConfigOrBuilder
The route table for the connection manager is static and is specified in this property.
.envoy.config.route.v3.RouteConfiguration route_config = 4;
- Specified by:
getRouteConfigOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetRouteConfigFieldBuilder
private com.google.protobuf.SingleFieldBuilder<RouteConfiguration,RouteConfiguration.Builder, internalGetRouteConfigFieldBuilder()RouteConfigurationOrBuilder> The route table for the connection manager is static and is specified in this property.
.envoy.config.route.v3.RouteConfiguration route_config = 4;
-
hasScopedRoutes
public boolean hasScopedRoutes()A route table will be dynamically assigned to each request based on request attributes (e.g., the value of a header). The "routing scopes" (i.e., route tables) and "scope keys" are specified in this message.
.envoy.extensions.filters.network.http_connection_manager.v3.ScopedRoutes scoped_routes = 31;
- Specified by:
hasScopedRoutes
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the scopedRoutes field is set.
-
getScopedRoutes
A route table will be dynamically assigned to each request based on request attributes (e.g., the value of a header). The "routing scopes" (i.e., route tables) and "scope keys" are specified in this message.
.envoy.extensions.filters.network.http_connection_manager.v3.ScopedRoutes scoped_routes = 31;
- Specified by:
getScopedRoutes
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The scopedRoutes.
-
setScopedRoutes
A route table will be dynamically assigned to each request based on request attributes (e.g., the value of a header). The "routing scopes" (i.e., route tables) and "scope keys" are specified in this message.
.envoy.extensions.filters.network.http_connection_manager.v3.ScopedRoutes scoped_routes = 31;
-
setScopedRoutes
A route table will be dynamically assigned to each request based on request attributes (e.g., the value of a header). The "routing scopes" (i.e., route tables) and "scope keys" are specified in this message.
.envoy.extensions.filters.network.http_connection_manager.v3.ScopedRoutes scoped_routes = 31;
-
mergeScopedRoutes
A route table will be dynamically assigned to each request based on request attributes (e.g., the value of a header). The "routing scopes" (i.e., route tables) and "scope keys" are specified in this message.
.envoy.extensions.filters.network.http_connection_manager.v3.ScopedRoutes scoped_routes = 31;
-
clearScopedRoutes
A route table will be dynamically assigned to each request based on request attributes (e.g., the value of a header). The "routing scopes" (i.e., route tables) and "scope keys" are specified in this message.
.envoy.extensions.filters.network.http_connection_manager.v3.ScopedRoutes scoped_routes = 31;
-
getScopedRoutesBuilder
A route table will be dynamically assigned to each request based on request attributes (e.g., the value of a header). The "routing scopes" (i.e., route tables) and "scope keys" are specified in this message.
.envoy.extensions.filters.network.http_connection_manager.v3.ScopedRoutes scoped_routes = 31;
-
getScopedRoutesOrBuilder
A route table will be dynamically assigned to each request based on request attributes (e.g., the value of a header). The "routing scopes" (i.e., route tables) and "scope keys" are specified in this message.
.envoy.extensions.filters.network.http_connection_manager.v3.ScopedRoutes scoped_routes = 31;
- Specified by:
getScopedRoutesOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetScopedRoutesFieldBuilder
private com.google.protobuf.SingleFieldBuilder<ScopedRoutes,ScopedRoutes.Builder, internalGetScopedRoutesFieldBuilder()ScopedRoutesOrBuilder> A route table will be dynamically assigned to each request based on request attributes (e.g., the value of a header). The "routing scopes" (i.e., route tables) and "scope keys" are specified in this message.
.envoy.extensions.filters.network.http_connection_manager.v3.ScopedRoutes scoped_routes = 31;
-
ensureHttpFiltersIsMutable
private void ensureHttpFiltersIsMutable() -
getHttpFiltersList
A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>` as the filters are processed sequentially as request events happen.
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter http_filters = 5;
- Specified by:
getHttpFiltersList
in interfaceHttpConnectionManagerOrBuilder
-
getHttpFiltersCount
public int getHttpFiltersCount()A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>` as the filters are processed sequentially as request events happen.
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter http_filters = 5;
- Specified by:
getHttpFiltersCount
in interfaceHttpConnectionManagerOrBuilder
-
getHttpFilters
A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>` as the filters are processed sequentially as request events happen.
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter http_filters = 5;
- Specified by:
getHttpFilters
in interfaceHttpConnectionManagerOrBuilder
-
setHttpFilters
A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>` as the filters are processed sequentially as request events happen.
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter http_filters = 5;
-
setHttpFilters
A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>` as the filters are processed sequentially as request events happen.
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter http_filters = 5;
-
addHttpFilters
A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>` as the filters are processed sequentially as request events happen.
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter http_filters = 5;
-
addHttpFilters
A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>` as the filters are processed sequentially as request events happen.
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter http_filters = 5;
-
addHttpFilters
A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>` as the filters are processed sequentially as request events happen.
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter http_filters = 5;
-
addHttpFilters
A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>` as the filters are processed sequentially as request events happen.
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter http_filters = 5;
-
addAllHttpFilters
A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>` as the filters are processed sequentially as request events happen.
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter http_filters = 5;
-
clearHttpFilters
A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>` as the filters are processed sequentially as request events happen.
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter http_filters = 5;
-
removeHttpFilters
A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>` as the filters are processed sequentially as request events happen.
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter http_filters = 5;
-
getHttpFiltersBuilder
A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>` as the filters are processed sequentially as request events happen.
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter http_filters = 5;
-
getHttpFiltersOrBuilder
A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>` as the filters are processed sequentially as request events happen.
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter http_filters = 5;
- Specified by:
getHttpFiltersOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
getHttpFiltersOrBuilderList
A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>` as the filters are processed sequentially as request events happen.
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter http_filters = 5;
- Specified by:
getHttpFiltersOrBuilderList
in interfaceHttpConnectionManagerOrBuilder
-
addHttpFiltersBuilder
A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>` as the filters are processed sequentially as request events happen.
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter http_filters = 5;
-
addHttpFiltersBuilder
A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>` as the filters are processed sequentially as request events happen.
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter http_filters = 5;
-
getHttpFiltersBuilderList
A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>` as the filters are processed sequentially as request events happen.
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter http_filters = 5;
-
internalGetHttpFiltersFieldBuilder
private com.google.protobuf.RepeatedFieldBuilder<HttpFilter,HttpFilter.Builder, internalGetHttpFiltersFieldBuilder()HttpFilterOrBuilder> -
hasAddUserAgent
public boolean hasAddUserAgent()Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent` and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers. See the linked documentation for more information. Defaults to false.
.google.protobuf.BoolValue add_user_agent = 6;
- Specified by:
hasAddUserAgent
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the addUserAgent field is set.
-
getAddUserAgent
public com.google.protobuf.BoolValue getAddUserAgent()Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent` and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers. See the linked documentation for more information. Defaults to false.
.google.protobuf.BoolValue add_user_agent = 6;
- Specified by:
getAddUserAgent
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The addUserAgent.
-
setAddUserAgent
Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent` and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers. See the linked documentation for more information. Defaults to false.
.google.protobuf.BoolValue add_user_agent = 6;
-
setAddUserAgent
public HttpConnectionManager.Builder setAddUserAgent(com.google.protobuf.BoolValue.Builder builderForValue) Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent` and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers. See the linked documentation for more information. Defaults to false.
.google.protobuf.BoolValue add_user_agent = 6;
-
mergeAddUserAgent
Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent` and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers. See the linked documentation for more information. Defaults to false.
.google.protobuf.BoolValue add_user_agent = 6;
-
clearAddUserAgent
Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent` and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers. See the linked documentation for more information. Defaults to false.
.google.protobuf.BoolValue add_user_agent = 6;
-
getAddUserAgentBuilder
public com.google.protobuf.BoolValue.Builder getAddUserAgentBuilder()Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent` and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers. See the linked documentation for more information. Defaults to false.
.google.protobuf.BoolValue add_user_agent = 6;
-
getAddUserAgentOrBuilder
public com.google.protobuf.BoolValueOrBuilder getAddUserAgentOrBuilder()Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent` and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers. See the linked documentation for more information. Defaults to false.
.google.protobuf.BoolValue add_user_agent = 6;
- Specified by:
getAddUserAgentOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetAddUserAgentFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder, internalGetAddUserAgentFieldBuilder()com.google.protobuf.BoolValueOrBuilder> Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent` and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers. See the linked documentation for more information. Defaults to false.
.google.protobuf.BoolValue add_user_agent = 6;
-
hasTracing
public boolean hasTracing()Presence of the object defines whether the connection manager emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider <envoy_v3_api_msg_config.trace.v3.Tracing>`.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.Tracing tracing = 7;
- Specified by:
hasTracing
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the tracing field is set.
-
getTracing
Presence of the object defines whether the connection manager emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider <envoy_v3_api_msg_config.trace.v3.Tracing>`.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.Tracing tracing = 7;
- Specified by:
getTracing
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The tracing.
-
setTracing
Presence of the object defines whether the connection manager emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider <envoy_v3_api_msg_config.trace.v3.Tracing>`.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.Tracing tracing = 7;
-
setTracing
public HttpConnectionManager.Builder setTracing(HttpConnectionManager.Tracing.Builder builderForValue) Presence of the object defines whether the connection manager emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider <envoy_v3_api_msg_config.trace.v3.Tracing>`.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.Tracing tracing = 7;
-
mergeTracing
Presence of the object defines whether the connection manager emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider <envoy_v3_api_msg_config.trace.v3.Tracing>`.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.Tracing tracing = 7;
-
clearTracing
Presence of the object defines whether the connection manager emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider <envoy_v3_api_msg_config.trace.v3.Tracing>`.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.Tracing tracing = 7;
-
getTracingBuilder
Presence of the object defines whether the connection manager emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider <envoy_v3_api_msg_config.trace.v3.Tracing>`.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.Tracing tracing = 7;
-
getTracingOrBuilder
Presence of the object defines whether the connection manager emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider <envoy_v3_api_msg_config.trace.v3.Tracing>`.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.Tracing tracing = 7;
- Specified by:
getTracingOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetTracingFieldBuilder
private com.google.protobuf.SingleFieldBuilder<HttpConnectionManager.Tracing,HttpConnectionManager.Tracing.Builder, internalGetTracingFieldBuilder()HttpConnectionManager.TracingOrBuilder> Presence of the object defines whether the connection manager emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider <envoy_v3_api_msg_config.trace.v3.Tracing>`.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.Tracing tracing = 7;
-
hasCommonHttpProtocolOptions
public boolean hasCommonHttpProtocolOptions()Additional settings for HTTP requests handled by the connection manager. These will be applicable to both HTTP1 and HTTP2 requests.
.envoy.config.core.v3.HttpProtocolOptions common_http_protocol_options = 35 [(.udpa.annotations.security) = { ... }
- Specified by:
hasCommonHttpProtocolOptions
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the commonHttpProtocolOptions field is set.
-
getCommonHttpProtocolOptions
Additional settings for HTTP requests handled by the connection manager. These will be applicable to both HTTP1 and HTTP2 requests.
.envoy.config.core.v3.HttpProtocolOptions common_http_protocol_options = 35 [(.udpa.annotations.security) = { ... }
- Specified by:
getCommonHttpProtocolOptions
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The commonHttpProtocolOptions.
-
setCommonHttpProtocolOptions
Additional settings for HTTP requests handled by the connection manager. These will be applicable to both HTTP1 and HTTP2 requests.
.envoy.config.core.v3.HttpProtocolOptions common_http_protocol_options = 35 [(.udpa.annotations.security) = { ... }
-
setCommonHttpProtocolOptions
public HttpConnectionManager.Builder setCommonHttpProtocolOptions(HttpProtocolOptions.Builder builderForValue) Additional settings for HTTP requests handled by the connection manager. These will be applicable to both HTTP1 and HTTP2 requests.
.envoy.config.core.v3.HttpProtocolOptions common_http_protocol_options = 35 [(.udpa.annotations.security) = { ... }
-
mergeCommonHttpProtocolOptions
Additional settings for HTTP requests handled by the connection manager. These will be applicable to both HTTP1 and HTTP2 requests.
.envoy.config.core.v3.HttpProtocolOptions common_http_protocol_options = 35 [(.udpa.annotations.security) = { ... }
-
clearCommonHttpProtocolOptions
Additional settings for HTTP requests handled by the connection manager. These will be applicable to both HTTP1 and HTTP2 requests.
.envoy.config.core.v3.HttpProtocolOptions common_http_protocol_options = 35 [(.udpa.annotations.security) = { ... }
-
getCommonHttpProtocolOptionsBuilder
Additional settings for HTTP requests handled by the connection manager. These will be applicable to both HTTP1 and HTTP2 requests.
.envoy.config.core.v3.HttpProtocolOptions common_http_protocol_options = 35 [(.udpa.annotations.security) = { ... }
-
getCommonHttpProtocolOptionsOrBuilder
Additional settings for HTTP requests handled by the connection manager. These will be applicable to both HTTP1 and HTTP2 requests.
.envoy.config.core.v3.HttpProtocolOptions common_http_protocol_options = 35 [(.udpa.annotations.security) = { ... }
- Specified by:
getCommonHttpProtocolOptionsOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetCommonHttpProtocolOptionsFieldBuilder
private com.google.protobuf.SingleFieldBuilder<HttpProtocolOptions,HttpProtocolOptions.Builder, internalGetCommonHttpProtocolOptionsFieldBuilder()HttpProtocolOptionsOrBuilder> Additional settings for HTTP requests handled by the connection manager. These will be applicable to both HTTP1 and HTTP2 requests.
.envoy.config.core.v3.HttpProtocolOptions common_http_protocol_options = 35 [(.udpa.annotations.security) = { ... }
-
hasHttpProtocolOptions
public boolean hasHttpProtocolOptions()Additional HTTP/1 settings that are passed to the HTTP/1 codec. [#comment:TODO: The following fields are ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present: 1. :ref:`allow_chunked_length <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.allow_chunked_length>`]
.envoy.config.core.v3.Http1ProtocolOptions http_protocol_options = 8;
- Specified by:
hasHttpProtocolOptions
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the httpProtocolOptions field is set.
-
getHttpProtocolOptions
Additional HTTP/1 settings that are passed to the HTTP/1 codec. [#comment:TODO: The following fields are ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present: 1. :ref:`allow_chunked_length <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.allow_chunked_length>`]
.envoy.config.core.v3.Http1ProtocolOptions http_protocol_options = 8;
- Specified by:
getHttpProtocolOptions
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The httpProtocolOptions.
-
setHttpProtocolOptions
Additional HTTP/1 settings that are passed to the HTTP/1 codec. [#comment:TODO: The following fields are ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present: 1. :ref:`allow_chunked_length <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.allow_chunked_length>`]
.envoy.config.core.v3.Http1ProtocolOptions http_protocol_options = 8;
-
setHttpProtocolOptions
public HttpConnectionManager.Builder setHttpProtocolOptions(Http1ProtocolOptions.Builder builderForValue) Additional HTTP/1 settings that are passed to the HTTP/1 codec. [#comment:TODO: The following fields are ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present: 1. :ref:`allow_chunked_length <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.allow_chunked_length>`]
.envoy.config.core.v3.Http1ProtocolOptions http_protocol_options = 8;
-
mergeHttpProtocolOptions
Additional HTTP/1 settings that are passed to the HTTP/1 codec. [#comment:TODO: The following fields are ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present: 1. :ref:`allow_chunked_length <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.allow_chunked_length>`]
.envoy.config.core.v3.Http1ProtocolOptions http_protocol_options = 8;
-
clearHttpProtocolOptions
Additional HTTP/1 settings that are passed to the HTTP/1 codec. [#comment:TODO: The following fields are ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present: 1. :ref:`allow_chunked_length <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.allow_chunked_length>`]
.envoy.config.core.v3.Http1ProtocolOptions http_protocol_options = 8;
-
getHttpProtocolOptionsBuilder
Additional HTTP/1 settings that are passed to the HTTP/1 codec. [#comment:TODO: The following fields are ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present: 1. :ref:`allow_chunked_length <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.allow_chunked_length>`]
.envoy.config.core.v3.Http1ProtocolOptions http_protocol_options = 8;
-
getHttpProtocolOptionsOrBuilder
Additional HTTP/1 settings that are passed to the HTTP/1 codec. [#comment:TODO: The following fields are ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present: 1. :ref:`allow_chunked_length <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.allow_chunked_length>`]
.envoy.config.core.v3.Http1ProtocolOptions http_protocol_options = 8;
- Specified by:
getHttpProtocolOptionsOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetHttpProtocolOptionsFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Http1ProtocolOptions,Http1ProtocolOptions.Builder, internalGetHttpProtocolOptionsFieldBuilder()Http1ProtocolOptionsOrBuilder> Additional HTTP/1 settings that are passed to the HTTP/1 codec. [#comment:TODO: The following fields are ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present: 1. :ref:`allow_chunked_length <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.allow_chunked_length>`]
.envoy.config.core.v3.Http1ProtocolOptions http_protocol_options = 8;
-
hasHttp2ProtocolOptions
public boolean hasHttp2ProtocolOptions()Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.
.envoy.config.core.v3.Http2ProtocolOptions http2_protocol_options = 9 [(.udpa.annotations.security) = { ... }
- Specified by:
hasHttp2ProtocolOptions
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the http2ProtocolOptions field is set.
-
getHttp2ProtocolOptions
Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.
.envoy.config.core.v3.Http2ProtocolOptions http2_protocol_options = 9 [(.udpa.annotations.security) = { ... }
- Specified by:
getHttp2ProtocolOptions
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The http2ProtocolOptions.
-
setHttp2ProtocolOptions
Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.
.envoy.config.core.v3.Http2ProtocolOptions http2_protocol_options = 9 [(.udpa.annotations.security) = { ... }
-
setHttp2ProtocolOptions
public HttpConnectionManager.Builder setHttp2ProtocolOptions(Http2ProtocolOptions.Builder builderForValue) Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.
.envoy.config.core.v3.Http2ProtocolOptions http2_protocol_options = 9 [(.udpa.annotations.security) = { ... }
-
mergeHttp2ProtocolOptions
Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.
.envoy.config.core.v3.Http2ProtocolOptions http2_protocol_options = 9 [(.udpa.annotations.security) = { ... }
-
clearHttp2ProtocolOptions
Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.
.envoy.config.core.v3.Http2ProtocolOptions http2_protocol_options = 9 [(.udpa.annotations.security) = { ... }
-
getHttp2ProtocolOptionsBuilder
Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.
.envoy.config.core.v3.Http2ProtocolOptions http2_protocol_options = 9 [(.udpa.annotations.security) = { ... }
-
getHttp2ProtocolOptionsOrBuilder
Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.
.envoy.config.core.v3.Http2ProtocolOptions http2_protocol_options = 9 [(.udpa.annotations.security) = { ... }
- Specified by:
getHttp2ProtocolOptionsOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetHttp2ProtocolOptionsFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Http2ProtocolOptions,Http2ProtocolOptions.Builder, internalGetHttp2ProtocolOptionsFieldBuilder()Http2ProtocolOptionsOrBuilder> Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.
.envoy.config.core.v3.Http2ProtocolOptions http2_protocol_options = 9 [(.udpa.annotations.security) = { ... }
-
hasHttp3ProtocolOptions
public boolean hasHttp3ProtocolOptions()Additional HTTP/3 settings that are passed directly to the HTTP/3 codec. [#not-implemented-hide:]
.envoy.config.core.v3.Http3ProtocolOptions http3_protocol_options = 44;
- Specified by:
hasHttp3ProtocolOptions
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the http3ProtocolOptions field is set.
-
getHttp3ProtocolOptions
Additional HTTP/3 settings that are passed directly to the HTTP/3 codec. [#not-implemented-hide:]
.envoy.config.core.v3.Http3ProtocolOptions http3_protocol_options = 44;
- Specified by:
getHttp3ProtocolOptions
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The http3ProtocolOptions.
-
setHttp3ProtocolOptions
Additional HTTP/3 settings that are passed directly to the HTTP/3 codec. [#not-implemented-hide:]
.envoy.config.core.v3.Http3ProtocolOptions http3_protocol_options = 44;
-
setHttp3ProtocolOptions
public HttpConnectionManager.Builder setHttp3ProtocolOptions(Http3ProtocolOptions.Builder builderForValue) Additional HTTP/3 settings that are passed directly to the HTTP/3 codec. [#not-implemented-hide:]
.envoy.config.core.v3.Http3ProtocolOptions http3_protocol_options = 44;
-
mergeHttp3ProtocolOptions
Additional HTTP/3 settings that are passed directly to the HTTP/3 codec. [#not-implemented-hide:]
.envoy.config.core.v3.Http3ProtocolOptions http3_protocol_options = 44;
-
clearHttp3ProtocolOptions
Additional HTTP/3 settings that are passed directly to the HTTP/3 codec. [#not-implemented-hide:]
.envoy.config.core.v3.Http3ProtocolOptions http3_protocol_options = 44;
-
getHttp3ProtocolOptionsBuilder
Additional HTTP/3 settings that are passed directly to the HTTP/3 codec. [#not-implemented-hide:]
.envoy.config.core.v3.Http3ProtocolOptions http3_protocol_options = 44;
-
getHttp3ProtocolOptionsOrBuilder
Additional HTTP/3 settings that are passed directly to the HTTP/3 codec. [#not-implemented-hide:]
.envoy.config.core.v3.Http3ProtocolOptions http3_protocol_options = 44;
- Specified by:
getHttp3ProtocolOptionsOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetHttp3ProtocolOptionsFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Http3ProtocolOptions,Http3ProtocolOptions.Builder, internalGetHttp3ProtocolOptionsFieldBuilder()Http3ProtocolOptionsOrBuilder> Additional HTTP/3 settings that are passed directly to the HTTP/3 codec. [#not-implemented-hide:]
.envoy.config.core.v3.Http3ProtocolOptions http3_protocol_options = 44;
-
getServerName
An optional override that the connection manager will write to the server header in responses. If not set, the default is ``envoy``.
string server_name = 10 [(.validate.rules) = { ... }
- Specified by:
getServerName
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The serverName.
-
getServerNameBytes
public com.google.protobuf.ByteString getServerNameBytes()An optional override that the connection manager will write to the server header in responses. If not set, the default is ``envoy``.
string server_name = 10 [(.validate.rules) = { ... }
- Specified by:
getServerNameBytes
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The bytes for serverName.
-
setServerName
An optional override that the connection manager will write to the server header in responses. If not set, the default is ``envoy``.
string server_name = 10 [(.validate.rules) = { ... }
- Parameters:
value
- The serverName to set.- Returns:
- This builder for chaining.
-
clearServerName
An optional override that the connection manager will write to the server header in responses. If not set, the default is ``envoy``.
string server_name = 10 [(.validate.rules) = { ... }
- Returns:
- This builder for chaining.
-
setServerNameBytes
An optional override that the connection manager will write to the server header in responses. If not set, the default is ``envoy``.
string server_name = 10 [(.validate.rules) = { ... }
- Parameters:
value
- The bytes for serverName to set.- Returns:
- This builder for chaining.
-
getServerHeaderTransformationValue
public int getServerHeaderTransformationValue()Defines the action to be applied to the Server header on the response path. By default, Envoy will overwrite the header with the value specified in server_name.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ServerHeaderTransformation server_header_transformation = 34 [(.validate.rules) = { ... }
- Specified by:
getServerHeaderTransformationValue
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The enum numeric value on the wire for serverHeaderTransformation.
-
setServerHeaderTransformationValue
Defines the action to be applied to the Server header on the response path. By default, Envoy will overwrite the header with the value specified in server_name.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ServerHeaderTransformation server_header_transformation = 34 [(.validate.rules) = { ... }
- Parameters:
value
- The enum numeric value on the wire for serverHeaderTransformation to set.- Returns:
- This builder for chaining.
-
getServerHeaderTransformation
Defines the action to be applied to the Server header on the response path. By default, Envoy will overwrite the header with the value specified in server_name.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ServerHeaderTransformation server_header_transformation = 34 [(.validate.rules) = { ... }
- Specified by:
getServerHeaderTransformation
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The serverHeaderTransformation.
-
setServerHeaderTransformation
public HttpConnectionManager.Builder setServerHeaderTransformation(HttpConnectionManager.ServerHeaderTransformation value) Defines the action to be applied to the Server header on the response path. By default, Envoy will overwrite the header with the value specified in server_name.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ServerHeaderTransformation server_header_transformation = 34 [(.validate.rules) = { ... }
- Parameters:
value
- The serverHeaderTransformation to set.- Returns:
- This builder for chaining.
-
clearServerHeaderTransformation
Defines the action to be applied to the Server header on the response path. By default, Envoy will overwrite the header with the value specified in server_name.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ServerHeaderTransformation server_header_transformation = 34 [(.validate.rules) = { ... }
- Returns:
- This builder for chaining.
-
hasSchemeHeaderTransformation
public boolean hasSchemeHeaderTransformation()Allows for explicit transformation of the :scheme header on the request path. If not set, Envoy's default :ref:`scheme <config_http_conn_man_headers_scheme>` handling applies.
.envoy.config.core.v3.SchemeHeaderTransformation scheme_header_transformation = 48;
- Specified by:
hasSchemeHeaderTransformation
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the schemeHeaderTransformation field is set.
-
getSchemeHeaderTransformation
Allows for explicit transformation of the :scheme header on the request path. If not set, Envoy's default :ref:`scheme <config_http_conn_man_headers_scheme>` handling applies.
.envoy.config.core.v3.SchemeHeaderTransformation scheme_header_transformation = 48;
- Specified by:
getSchemeHeaderTransformation
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The schemeHeaderTransformation.
-
setSchemeHeaderTransformation
public HttpConnectionManager.Builder setSchemeHeaderTransformation(SchemeHeaderTransformation value) Allows for explicit transformation of the :scheme header on the request path. If not set, Envoy's default :ref:`scheme <config_http_conn_man_headers_scheme>` handling applies.
.envoy.config.core.v3.SchemeHeaderTransformation scheme_header_transformation = 48;
-
setSchemeHeaderTransformation
public HttpConnectionManager.Builder setSchemeHeaderTransformation(SchemeHeaderTransformation.Builder builderForValue) Allows for explicit transformation of the :scheme header on the request path. If not set, Envoy's default :ref:`scheme <config_http_conn_man_headers_scheme>` handling applies.
.envoy.config.core.v3.SchemeHeaderTransformation scheme_header_transformation = 48;
-
mergeSchemeHeaderTransformation
public HttpConnectionManager.Builder mergeSchemeHeaderTransformation(SchemeHeaderTransformation value) Allows for explicit transformation of the :scheme header on the request path. If not set, Envoy's default :ref:`scheme <config_http_conn_man_headers_scheme>` handling applies.
.envoy.config.core.v3.SchemeHeaderTransformation scheme_header_transformation = 48;
-
clearSchemeHeaderTransformation
Allows for explicit transformation of the :scheme header on the request path. If not set, Envoy's default :ref:`scheme <config_http_conn_man_headers_scheme>` handling applies.
.envoy.config.core.v3.SchemeHeaderTransformation scheme_header_transformation = 48;
-
getSchemeHeaderTransformationBuilder
Allows for explicit transformation of the :scheme header on the request path. If not set, Envoy's default :ref:`scheme <config_http_conn_man_headers_scheme>` handling applies.
.envoy.config.core.v3.SchemeHeaderTransformation scheme_header_transformation = 48;
-
getSchemeHeaderTransformationOrBuilder
Allows for explicit transformation of the :scheme header on the request path. If not set, Envoy's default :ref:`scheme <config_http_conn_man_headers_scheme>` handling applies.
.envoy.config.core.v3.SchemeHeaderTransformation scheme_header_transformation = 48;
- Specified by:
getSchemeHeaderTransformationOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetSchemeHeaderTransformationFieldBuilder
private com.google.protobuf.SingleFieldBuilder<SchemeHeaderTransformation,SchemeHeaderTransformation.Builder, internalGetSchemeHeaderTransformationFieldBuilder()SchemeHeaderTransformationOrBuilder> Allows for explicit transformation of the :scheme header on the request path. If not set, Envoy's default :ref:`scheme <config_http_conn_man_headers_scheme>` handling applies.
.envoy.config.core.v3.SchemeHeaderTransformation scheme_header_transformation = 48;
-
hasMaxRequestHeadersKb
public boolean hasMaxRequestHeadersKb()The maximum request headers size for incoming connections. If unconfigured, the default max request headers allowed is 60 KiB. Requests that exceed this limit will receive a 431 response.
.google.protobuf.UInt32Value max_request_headers_kb = 29 [(.validate.rules) = { ... }
- Specified by:
hasMaxRequestHeadersKb
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the maxRequestHeadersKb field is set.
-
getMaxRequestHeadersKb
public com.google.protobuf.UInt32Value getMaxRequestHeadersKb()The maximum request headers size for incoming connections. If unconfigured, the default max request headers allowed is 60 KiB. Requests that exceed this limit will receive a 431 response.
.google.protobuf.UInt32Value max_request_headers_kb = 29 [(.validate.rules) = { ... }
- Specified by:
getMaxRequestHeadersKb
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The maxRequestHeadersKb.
-
setMaxRequestHeadersKb
The maximum request headers size for incoming connections. If unconfigured, the default max request headers allowed is 60 KiB. Requests that exceed this limit will receive a 431 response.
.google.protobuf.UInt32Value max_request_headers_kb = 29 [(.validate.rules) = { ... }
-
setMaxRequestHeadersKb
public HttpConnectionManager.Builder setMaxRequestHeadersKb(com.google.protobuf.UInt32Value.Builder builderForValue) The maximum request headers size for incoming connections. If unconfigured, the default max request headers allowed is 60 KiB. Requests that exceed this limit will receive a 431 response.
.google.protobuf.UInt32Value max_request_headers_kb = 29 [(.validate.rules) = { ... }
-
mergeMaxRequestHeadersKb
public HttpConnectionManager.Builder mergeMaxRequestHeadersKb(com.google.protobuf.UInt32Value value) The maximum request headers size for incoming connections. If unconfigured, the default max request headers allowed is 60 KiB. Requests that exceed this limit will receive a 431 response.
.google.protobuf.UInt32Value max_request_headers_kb = 29 [(.validate.rules) = { ... }
-
clearMaxRequestHeadersKb
The maximum request headers size for incoming connections. If unconfigured, the default max request headers allowed is 60 KiB. Requests that exceed this limit will receive a 431 response.
.google.protobuf.UInt32Value max_request_headers_kb = 29 [(.validate.rules) = { ... }
-
getMaxRequestHeadersKbBuilder
public com.google.protobuf.UInt32Value.Builder getMaxRequestHeadersKbBuilder()The maximum request headers size for incoming connections. If unconfigured, the default max request headers allowed is 60 KiB. Requests that exceed this limit will receive a 431 response.
.google.protobuf.UInt32Value max_request_headers_kb = 29 [(.validate.rules) = { ... }
-
getMaxRequestHeadersKbOrBuilder
public com.google.protobuf.UInt32ValueOrBuilder getMaxRequestHeadersKbOrBuilder()The maximum request headers size for incoming connections. If unconfigured, the default max request headers allowed is 60 KiB. Requests that exceed this limit will receive a 431 response.
.google.protobuf.UInt32Value max_request_headers_kb = 29 [(.validate.rules) = { ... }
- Specified by:
getMaxRequestHeadersKbOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetMaxRequestHeadersKbFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.UInt32Value,com.google.protobuf.UInt32Value.Builder, internalGetMaxRequestHeadersKbFieldBuilder()com.google.protobuf.UInt32ValueOrBuilder> The maximum request headers size for incoming connections. If unconfigured, the default max request headers allowed is 60 KiB. Requests that exceed this limit will receive a 431 response.
.google.protobuf.UInt32Value max_request_headers_kb = 29 [(.validate.rules) = { ... }
-
hasStreamIdleTimeout
public boolean hasStreamIdleTimeout()The stream idle timeout for connections managed by the connection manager. If not specified, this defaults to 5 minutes. The default value was selected so as not to interfere with any smaller configured timeouts that may have existed in configurations prior to the introduction of this feature, while introducing robustness to TCP connections that terminate without a FIN. This idle timeout applies to new streams and is overridable by the :ref:`route-level idle_timeout <envoy_v3_api_field_config.route.v3.RouteAction.idle_timeout>`. Even on a stream in which the override applies, prior to receipt of the initial request headers, the :ref:`stream_idle_timeout <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_idle_timeout>` applies. Each time an encode/decode event for headers or data is processed for the stream, the timer will be reset. If the timeout fires, the stream is terminated with a 408 Request Timeout error code if no upstream response header has been received, otherwise a stream reset occurs. This timeout also specifies the amount of time that Envoy will wait for the peer to open enough window to write any remaining stream data once the entirety of stream data (local end stream is true) has been buffered pending available window. In other words, this timeout defends against a peer that does not release enough window to completely write the stream, even though all data has been proxied within available flow control windows. If the timeout is hit in this case, the :ref:`tx_flush_timeout <config_http_conn_man_stats_per_codec>` counter will be incremented. Note that :ref:`max_stream_duration <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_stream_duration>` does not apply to this corner case. If the :ref:`overload action <config_overload_manager_overload_actions>` "envoy.overload_actions.reduce_timeouts" is configured, this timeout is scaled according to the value for :ref:`HTTP_DOWNSTREAM_STREAM_IDLE <envoy_v3_api_enum_value_config.overload.v3.ScaleTimersOverloadActionConfig.TimerType.HTTP_DOWNSTREAM_STREAM_IDLE>`. Note that it is possible to idle timeout even if the wire traffic for a stream is non-idle, due to the granularity of events presented to the connection manager. For example, while receiving very large request headers, it may be the case that there is traffic regularly arriving on the wire while the connection manage is only able to observe the end-of-headers event, hence the stream may still idle timeout. A value of 0 will completely disable the connection manager stream idle timeout, although per-route idle timeout overrides will continue to apply.
.google.protobuf.Duration stream_idle_timeout = 24 [(.udpa.annotations.security) = { ... }
- Specified by:
hasStreamIdleTimeout
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the streamIdleTimeout field is set.
-
getStreamIdleTimeout
public com.google.protobuf.Duration getStreamIdleTimeout()The stream idle timeout for connections managed by the connection manager. If not specified, this defaults to 5 minutes. The default value was selected so as not to interfere with any smaller configured timeouts that may have existed in configurations prior to the introduction of this feature, while introducing robustness to TCP connections that terminate without a FIN. This idle timeout applies to new streams and is overridable by the :ref:`route-level idle_timeout <envoy_v3_api_field_config.route.v3.RouteAction.idle_timeout>`. Even on a stream in which the override applies, prior to receipt of the initial request headers, the :ref:`stream_idle_timeout <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_idle_timeout>` applies. Each time an encode/decode event for headers or data is processed for the stream, the timer will be reset. If the timeout fires, the stream is terminated with a 408 Request Timeout error code if no upstream response header has been received, otherwise a stream reset occurs. This timeout also specifies the amount of time that Envoy will wait for the peer to open enough window to write any remaining stream data once the entirety of stream data (local end stream is true) has been buffered pending available window. In other words, this timeout defends against a peer that does not release enough window to completely write the stream, even though all data has been proxied within available flow control windows. If the timeout is hit in this case, the :ref:`tx_flush_timeout <config_http_conn_man_stats_per_codec>` counter will be incremented. Note that :ref:`max_stream_duration <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_stream_duration>` does not apply to this corner case. If the :ref:`overload action <config_overload_manager_overload_actions>` "envoy.overload_actions.reduce_timeouts" is configured, this timeout is scaled according to the value for :ref:`HTTP_DOWNSTREAM_STREAM_IDLE <envoy_v3_api_enum_value_config.overload.v3.ScaleTimersOverloadActionConfig.TimerType.HTTP_DOWNSTREAM_STREAM_IDLE>`. Note that it is possible to idle timeout even if the wire traffic for a stream is non-idle, due to the granularity of events presented to the connection manager. For example, while receiving very large request headers, it may be the case that there is traffic regularly arriving on the wire while the connection manage is only able to observe the end-of-headers event, hence the stream may still idle timeout. A value of 0 will completely disable the connection manager stream idle timeout, although per-route idle timeout overrides will continue to apply.
.google.protobuf.Duration stream_idle_timeout = 24 [(.udpa.annotations.security) = { ... }
- Specified by:
getStreamIdleTimeout
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The streamIdleTimeout.
-
setStreamIdleTimeout
The stream idle timeout for connections managed by the connection manager. If not specified, this defaults to 5 minutes. The default value was selected so as not to interfere with any smaller configured timeouts that may have existed in configurations prior to the introduction of this feature, while introducing robustness to TCP connections that terminate without a FIN. This idle timeout applies to new streams and is overridable by the :ref:`route-level idle_timeout <envoy_v3_api_field_config.route.v3.RouteAction.idle_timeout>`. Even on a stream in which the override applies, prior to receipt of the initial request headers, the :ref:`stream_idle_timeout <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_idle_timeout>` applies. Each time an encode/decode event for headers or data is processed for the stream, the timer will be reset. If the timeout fires, the stream is terminated with a 408 Request Timeout error code if no upstream response header has been received, otherwise a stream reset occurs. This timeout also specifies the amount of time that Envoy will wait for the peer to open enough window to write any remaining stream data once the entirety of stream data (local end stream is true) has been buffered pending available window. In other words, this timeout defends against a peer that does not release enough window to completely write the stream, even though all data has been proxied within available flow control windows. If the timeout is hit in this case, the :ref:`tx_flush_timeout <config_http_conn_man_stats_per_codec>` counter will be incremented. Note that :ref:`max_stream_duration <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_stream_duration>` does not apply to this corner case. If the :ref:`overload action <config_overload_manager_overload_actions>` "envoy.overload_actions.reduce_timeouts" is configured, this timeout is scaled according to the value for :ref:`HTTP_DOWNSTREAM_STREAM_IDLE <envoy_v3_api_enum_value_config.overload.v3.ScaleTimersOverloadActionConfig.TimerType.HTTP_DOWNSTREAM_STREAM_IDLE>`. Note that it is possible to idle timeout even if the wire traffic for a stream is non-idle, due to the granularity of events presented to the connection manager. For example, while receiving very large request headers, it may be the case that there is traffic regularly arriving on the wire while the connection manage is only able to observe the end-of-headers event, hence the stream may still idle timeout. A value of 0 will completely disable the connection manager stream idle timeout, although per-route idle timeout overrides will continue to apply.
.google.protobuf.Duration stream_idle_timeout = 24 [(.udpa.annotations.security) = { ... }
-
setStreamIdleTimeout
public HttpConnectionManager.Builder setStreamIdleTimeout(com.google.protobuf.Duration.Builder builderForValue) The stream idle timeout for connections managed by the connection manager. If not specified, this defaults to 5 minutes. The default value was selected so as not to interfere with any smaller configured timeouts that may have existed in configurations prior to the introduction of this feature, while introducing robustness to TCP connections that terminate without a FIN. This idle timeout applies to new streams and is overridable by the :ref:`route-level idle_timeout <envoy_v3_api_field_config.route.v3.RouteAction.idle_timeout>`. Even on a stream in which the override applies, prior to receipt of the initial request headers, the :ref:`stream_idle_timeout <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_idle_timeout>` applies. Each time an encode/decode event for headers or data is processed for the stream, the timer will be reset. If the timeout fires, the stream is terminated with a 408 Request Timeout error code if no upstream response header has been received, otherwise a stream reset occurs. This timeout also specifies the amount of time that Envoy will wait for the peer to open enough window to write any remaining stream data once the entirety of stream data (local end stream is true) has been buffered pending available window. In other words, this timeout defends against a peer that does not release enough window to completely write the stream, even though all data has been proxied within available flow control windows. If the timeout is hit in this case, the :ref:`tx_flush_timeout <config_http_conn_man_stats_per_codec>` counter will be incremented. Note that :ref:`max_stream_duration <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_stream_duration>` does not apply to this corner case. If the :ref:`overload action <config_overload_manager_overload_actions>` "envoy.overload_actions.reduce_timeouts" is configured, this timeout is scaled according to the value for :ref:`HTTP_DOWNSTREAM_STREAM_IDLE <envoy_v3_api_enum_value_config.overload.v3.ScaleTimersOverloadActionConfig.TimerType.HTTP_DOWNSTREAM_STREAM_IDLE>`. Note that it is possible to idle timeout even if the wire traffic for a stream is non-idle, due to the granularity of events presented to the connection manager. For example, while receiving very large request headers, it may be the case that there is traffic regularly arriving on the wire while the connection manage is only able to observe the end-of-headers event, hence the stream may still idle timeout. A value of 0 will completely disable the connection manager stream idle timeout, although per-route idle timeout overrides will continue to apply.
.google.protobuf.Duration stream_idle_timeout = 24 [(.udpa.annotations.security) = { ... }
-
mergeStreamIdleTimeout
The stream idle timeout for connections managed by the connection manager. If not specified, this defaults to 5 minutes. The default value was selected so as not to interfere with any smaller configured timeouts that may have existed in configurations prior to the introduction of this feature, while introducing robustness to TCP connections that terminate without a FIN. This idle timeout applies to new streams and is overridable by the :ref:`route-level idle_timeout <envoy_v3_api_field_config.route.v3.RouteAction.idle_timeout>`. Even on a stream in which the override applies, prior to receipt of the initial request headers, the :ref:`stream_idle_timeout <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_idle_timeout>` applies. Each time an encode/decode event for headers or data is processed for the stream, the timer will be reset. If the timeout fires, the stream is terminated with a 408 Request Timeout error code if no upstream response header has been received, otherwise a stream reset occurs. This timeout also specifies the amount of time that Envoy will wait for the peer to open enough window to write any remaining stream data once the entirety of stream data (local end stream is true) has been buffered pending available window. In other words, this timeout defends against a peer that does not release enough window to completely write the stream, even though all data has been proxied within available flow control windows. If the timeout is hit in this case, the :ref:`tx_flush_timeout <config_http_conn_man_stats_per_codec>` counter will be incremented. Note that :ref:`max_stream_duration <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_stream_duration>` does not apply to this corner case. If the :ref:`overload action <config_overload_manager_overload_actions>` "envoy.overload_actions.reduce_timeouts" is configured, this timeout is scaled according to the value for :ref:`HTTP_DOWNSTREAM_STREAM_IDLE <envoy_v3_api_enum_value_config.overload.v3.ScaleTimersOverloadActionConfig.TimerType.HTTP_DOWNSTREAM_STREAM_IDLE>`. Note that it is possible to idle timeout even if the wire traffic for a stream is non-idle, due to the granularity of events presented to the connection manager. For example, while receiving very large request headers, it may be the case that there is traffic regularly arriving on the wire while the connection manage is only able to observe the end-of-headers event, hence the stream may still idle timeout. A value of 0 will completely disable the connection manager stream idle timeout, although per-route idle timeout overrides will continue to apply.
.google.protobuf.Duration stream_idle_timeout = 24 [(.udpa.annotations.security) = { ... }
-
clearStreamIdleTimeout
The stream idle timeout for connections managed by the connection manager. If not specified, this defaults to 5 minutes. The default value was selected so as not to interfere with any smaller configured timeouts that may have existed in configurations prior to the introduction of this feature, while introducing robustness to TCP connections that terminate without a FIN. This idle timeout applies to new streams and is overridable by the :ref:`route-level idle_timeout <envoy_v3_api_field_config.route.v3.RouteAction.idle_timeout>`. Even on a stream in which the override applies, prior to receipt of the initial request headers, the :ref:`stream_idle_timeout <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_idle_timeout>` applies. Each time an encode/decode event for headers or data is processed for the stream, the timer will be reset. If the timeout fires, the stream is terminated with a 408 Request Timeout error code if no upstream response header has been received, otherwise a stream reset occurs. This timeout also specifies the amount of time that Envoy will wait for the peer to open enough window to write any remaining stream data once the entirety of stream data (local end stream is true) has been buffered pending available window. In other words, this timeout defends against a peer that does not release enough window to completely write the stream, even though all data has been proxied within available flow control windows. If the timeout is hit in this case, the :ref:`tx_flush_timeout <config_http_conn_man_stats_per_codec>` counter will be incremented. Note that :ref:`max_stream_duration <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_stream_duration>` does not apply to this corner case. If the :ref:`overload action <config_overload_manager_overload_actions>` "envoy.overload_actions.reduce_timeouts" is configured, this timeout is scaled according to the value for :ref:`HTTP_DOWNSTREAM_STREAM_IDLE <envoy_v3_api_enum_value_config.overload.v3.ScaleTimersOverloadActionConfig.TimerType.HTTP_DOWNSTREAM_STREAM_IDLE>`. Note that it is possible to idle timeout even if the wire traffic for a stream is non-idle, due to the granularity of events presented to the connection manager. For example, while receiving very large request headers, it may be the case that there is traffic regularly arriving on the wire while the connection manage is only able to observe the end-of-headers event, hence the stream may still idle timeout. A value of 0 will completely disable the connection manager stream idle timeout, although per-route idle timeout overrides will continue to apply.
.google.protobuf.Duration stream_idle_timeout = 24 [(.udpa.annotations.security) = { ... }
-
getStreamIdleTimeoutBuilder
public com.google.protobuf.Duration.Builder getStreamIdleTimeoutBuilder()The stream idle timeout for connections managed by the connection manager. If not specified, this defaults to 5 minutes. The default value was selected so as not to interfere with any smaller configured timeouts that may have existed in configurations prior to the introduction of this feature, while introducing robustness to TCP connections that terminate without a FIN. This idle timeout applies to new streams and is overridable by the :ref:`route-level idle_timeout <envoy_v3_api_field_config.route.v3.RouteAction.idle_timeout>`. Even on a stream in which the override applies, prior to receipt of the initial request headers, the :ref:`stream_idle_timeout <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_idle_timeout>` applies. Each time an encode/decode event for headers or data is processed for the stream, the timer will be reset. If the timeout fires, the stream is terminated with a 408 Request Timeout error code if no upstream response header has been received, otherwise a stream reset occurs. This timeout also specifies the amount of time that Envoy will wait for the peer to open enough window to write any remaining stream data once the entirety of stream data (local end stream is true) has been buffered pending available window. In other words, this timeout defends against a peer that does not release enough window to completely write the stream, even though all data has been proxied within available flow control windows. If the timeout is hit in this case, the :ref:`tx_flush_timeout <config_http_conn_man_stats_per_codec>` counter will be incremented. Note that :ref:`max_stream_duration <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_stream_duration>` does not apply to this corner case. If the :ref:`overload action <config_overload_manager_overload_actions>` "envoy.overload_actions.reduce_timeouts" is configured, this timeout is scaled according to the value for :ref:`HTTP_DOWNSTREAM_STREAM_IDLE <envoy_v3_api_enum_value_config.overload.v3.ScaleTimersOverloadActionConfig.TimerType.HTTP_DOWNSTREAM_STREAM_IDLE>`. Note that it is possible to idle timeout even if the wire traffic for a stream is non-idle, due to the granularity of events presented to the connection manager. For example, while receiving very large request headers, it may be the case that there is traffic regularly arriving on the wire while the connection manage is only able to observe the end-of-headers event, hence the stream may still idle timeout. A value of 0 will completely disable the connection manager stream idle timeout, although per-route idle timeout overrides will continue to apply.
.google.protobuf.Duration stream_idle_timeout = 24 [(.udpa.annotations.security) = { ... }
-
getStreamIdleTimeoutOrBuilder
public com.google.protobuf.DurationOrBuilder getStreamIdleTimeoutOrBuilder()The stream idle timeout for connections managed by the connection manager. If not specified, this defaults to 5 minutes. The default value was selected so as not to interfere with any smaller configured timeouts that may have existed in configurations prior to the introduction of this feature, while introducing robustness to TCP connections that terminate without a FIN. This idle timeout applies to new streams and is overridable by the :ref:`route-level idle_timeout <envoy_v3_api_field_config.route.v3.RouteAction.idle_timeout>`. Even on a stream in which the override applies, prior to receipt of the initial request headers, the :ref:`stream_idle_timeout <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_idle_timeout>` applies. Each time an encode/decode event for headers or data is processed for the stream, the timer will be reset. If the timeout fires, the stream is terminated with a 408 Request Timeout error code if no upstream response header has been received, otherwise a stream reset occurs. This timeout also specifies the amount of time that Envoy will wait for the peer to open enough window to write any remaining stream data once the entirety of stream data (local end stream is true) has been buffered pending available window. In other words, this timeout defends against a peer that does not release enough window to completely write the stream, even though all data has been proxied within available flow control windows. If the timeout is hit in this case, the :ref:`tx_flush_timeout <config_http_conn_man_stats_per_codec>` counter will be incremented. Note that :ref:`max_stream_duration <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_stream_duration>` does not apply to this corner case. If the :ref:`overload action <config_overload_manager_overload_actions>` "envoy.overload_actions.reduce_timeouts" is configured, this timeout is scaled according to the value for :ref:`HTTP_DOWNSTREAM_STREAM_IDLE <envoy_v3_api_enum_value_config.overload.v3.ScaleTimersOverloadActionConfig.TimerType.HTTP_DOWNSTREAM_STREAM_IDLE>`. Note that it is possible to idle timeout even if the wire traffic for a stream is non-idle, due to the granularity of events presented to the connection manager. For example, while receiving very large request headers, it may be the case that there is traffic regularly arriving on the wire while the connection manage is only able to observe the end-of-headers event, hence the stream may still idle timeout. A value of 0 will completely disable the connection manager stream idle timeout, although per-route idle timeout overrides will continue to apply.
.google.protobuf.Duration stream_idle_timeout = 24 [(.udpa.annotations.security) = { ... }
- Specified by:
getStreamIdleTimeoutOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetStreamIdleTimeoutFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder, internalGetStreamIdleTimeoutFieldBuilder()com.google.protobuf.DurationOrBuilder> The stream idle timeout for connections managed by the connection manager. If not specified, this defaults to 5 minutes. The default value was selected so as not to interfere with any smaller configured timeouts that may have existed in configurations prior to the introduction of this feature, while introducing robustness to TCP connections that terminate without a FIN. This idle timeout applies to new streams and is overridable by the :ref:`route-level idle_timeout <envoy_v3_api_field_config.route.v3.RouteAction.idle_timeout>`. Even on a stream in which the override applies, prior to receipt of the initial request headers, the :ref:`stream_idle_timeout <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_idle_timeout>` applies. Each time an encode/decode event for headers or data is processed for the stream, the timer will be reset. If the timeout fires, the stream is terminated with a 408 Request Timeout error code if no upstream response header has been received, otherwise a stream reset occurs. This timeout also specifies the amount of time that Envoy will wait for the peer to open enough window to write any remaining stream data once the entirety of stream data (local end stream is true) has been buffered pending available window. In other words, this timeout defends against a peer that does not release enough window to completely write the stream, even though all data has been proxied within available flow control windows. If the timeout is hit in this case, the :ref:`tx_flush_timeout <config_http_conn_man_stats_per_codec>` counter will be incremented. Note that :ref:`max_stream_duration <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_stream_duration>` does not apply to this corner case. If the :ref:`overload action <config_overload_manager_overload_actions>` "envoy.overload_actions.reduce_timeouts" is configured, this timeout is scaled according to the value for :ref:`HTTP_DOWNSTREAM_STREAM_IDLE <envoy_v3_api_enum_value_config.overload.v3.ScaleTimersOverloadActionConfig.TimerType.HTTP_DOWNSTREAM_STREAM_IDLE>`. Note that it is possible to idle timeout even if the wire traffic for a stream is non-idle, due to the granularity of events presented to the connection manager. For example, while receiving very large request headers, it may be the case that there is traffic regularly arriving on the wire while the connection manage is only able to observe the end-of-headers event, hence the stream may still idle timeout. A value of 0 will completely disable the connection manager stream idle timeout, although per-route idle timeout overrides will continue to apply.
.google.protobuf.Duration stream_idle_timeout = 24 [(.udpa.annotations.security) = { ... }
-
hasRequestTimeout
public boolean hasRequestTimeout()The amount of time that Envoy will wait for the entire request to be received. The timer is activated when the request is initiated, and is disarmed when the last byte of the request is sent upstream (i.e. all decoding filters have processed the request), OR when the response is initiated. If not specified or set to 0, this timeout is disabled.
.google.protobuf.Duration request_timeout = 28 [(.udpa.annotations.security) = { ... }
- Specified by:
hasRequestTimeout
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the requestTimeout field is set.
-
getRequestTimeout
public com.google.protobuf.Duration getRequestTimeout()The amount of time that Envoy will wait for the entire request to be received. The timer is activated when the request is initiated, and is disarmed when the last byte of the request is sent upstream (i.e. all decoding filters have processed the request), OR when the response is initiated. If not specified or set to 0, this timeout is disabled.
.google.protobuf.Duration request_timeout = 28 [(.udpa.annotations.security) = { ... }
- Specified by:
getRequestTimeout
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The requestTimeout.
-
setRequestTimeout
The amount of time that Envoy will wait for the entire request to be received. The timer is activated when the request is initiated, and is disarmed when the last byte of the request is sent upstream (i.e. all decoding filters have processed the request), OR when the response is initiated. If not specified or set to 0, this timeout is disabled.
.google.protobuf.Duration request_timeout = 28 [(.udpa.annotations.security) = { ... }
-
setRequestTimeout
public HttpConnectionManager.Builder setRequestTimeout(com.google.protobuf.Duration.Builder builderForValue) The amount of time that Envoy will wait for the entire request to be received. The timer is activated when the request is initiated, and is disarmed when the last byte of the request is sent upstream (i.e. all decoding filters have processed the request), OR when the response is initiated. If not specified or set to 0, this timeout is disabled.
.google.protobuf.Duration request_timeout = 28 [(.udpa.annotations.security) = { ... }
-
mergeRequestTimeout
The amount of time that Envoy will wait for the entire request to be received. The timer is activated when the request is initiated, and is disarmed when the last byte of the request is sent upstream (i.e. all decoding filters have processed the request), OR when the response is initiated. If not specified or set to 0, this timeout is disabled.
.google.protobuf.Duration request_timeout = 28 [(.udpa.annotations.security) = { ... }
-
clearRequestTimeout
The amount of time that Envoy will wait for the entire request to be received. The timer is activated when the request is initiated, and is disarmed when the last byte of the request is sent upstream (i.e. all decoding filters have processed the request), OR when the response is initiated. If not specified or set to 0, this timeout is disabled.
.google.protobuf.Duration request_timeout = 28 [(.udpa.annotations.security) = { ... }
-
getRequestTimeoutBuilder
public com.google.protobuf.Duration.Builder getRequestTimeoutBuilder()The amount of time that Envoy will wait for the entire request to be received. The timer is activated when the request is initiated, and is disarmed when the last byte of the request is sent upstream (i.e. all decoding filters have processed the request), OR when the response is initiated. If not specified or set to 0, this timeout is disabled.
.google.protobuf.Duration request_timeout = 28 [(.udpa.annotations.security) = { ... }
-
getRequestTimeoutOrBuilder
public com.google.protobuf.DurationOrBuilder getRequestTimeoutOrBuilder()The amount of time that Envoy will wait for the entire request to be received. The timer is activated when the request is initiated, and is disarmed when the last byte of the request is sent upstream (i.e. all decoding filters have processed the request), OR when the response is initiated. If not specified or set to 0, this timeout is disabled.
.google.protobuf.Duration request_timeout = 28 [(.udpa.annotations.security) = { ... }
- Specified by:
getRequestTimeoutOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetRequestTimeoutFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder, internalGetRequestTimeoutFieldBuilder()com.google.protobuf.DurationOrBuilder> The amount of time that Envoy will wait for the entire request to be received. The timer is activated when the request is initiated, and is disarmed when the last byte of the request is sent upstream (i.e. all decoding filters have processed the request), OR when the response is initiated. If not specified or set to 0, this timeout is disabled.
.google.protobuf.Duration request_timeout = 28 [(.udpa.annotations.security) = { ... }
-
hasRequestHeadersTimeout
public boolean hasRequestHeadersTimeout()The amount of time that Envoy will wait for the request headers to be received. The timer is activated when the first byte of the headers is received, and is disarmed when the last byte of the headers has been received. If not specified or set to 0, this timeout is disabled.
.google.protobuf.Duration request_headers_timeout = 41 [(.validate.rules) = { ... }
- Specified by:
hasRequestHeadersTimeout
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the requestHeadersTimeout field is set.
-
getRequestHeadersTimeout
public com.google.protobuf.Duration getRequestHeadersTimeout()The amount of time that Envoy will wait for the request headers to be received. The timer is activated when the first byte of the headers is received, and is disarmed when the last byte of the headers has been received. If not specified or set to 0, this timeout is disabled.
.google.protobuf.Duration request_headers_timeout = 41 [(.validate.rules) = { ... }
- Specified by:
getRequestHeadersTimeout
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The requestHeadersTimeout.
-
setRequestHeadersTimeout
The amount of time that Envoy will wait for the request headers to be received. The timer is activated when the first byte of the headers is received, and is disarmed when the last byte of the headers has been received. If not specified or set to 0, this timeout is disabled.
.google.protobuf.Duration request_headers_timeout = 41 [(.validate.rules) = { ... }
-
setRequestHeadersTimeout
public HttpConnectionManager.Builder setRequestHeadersTimeout(com.google.protobuf.Duration.Builder builderForValue) The amount of time that Envoy will wait for the request headers to be received. The timer is activated when the first byte of the headers is received, and is disarmed when the last byte of the headers has been received. If not specified or set to 0, this timeout is disabled.
.google.protobuf.Duration request_headers_timeout = 41 [(.validate.rules) = { ... }
-
mergeRequestHeadersTimeout
The amount of time that Envoy will wait for the request headers to be received. The timer is activated when the first byte of the headers is received, and is disarmed when the last byte of the headers has been received. If not specified or set to 0, this timeout is disabled.
.google.protobuf.Duration request_headers_timeout = 41 [(.validate.rules) = { ... }
-
clearRequestHeadersTimeout
The amount of time that Envoy will wait for the request headers to be received. The timer is activated when the first byte of the headers is received, and is disarmed when the last byte of the headers has been received. If not specified or set to 0, this timeout is disabled.
.google.protobuf.Duration request_headers_timeout = 41 [(.validate.rules) = { ... }
-
getRequestHeadersTimeoutBuilder
public com.google.protobuf.Duration.Builder getRequestHeadersTimeoutBuilder()The amount of time that Envoy will wait for the request headers to be received. The timer is activated when the first byte of the headers is received, and is disarmed when the last byte of the headers has been received. If not specified or set to 0, this timeout is disabled.
.google.protobuf.Duration request_headers_timeout = 41 [(.validate.rules) = { ... }
-
getRequestHeadersTimeoutOrBuilder
public com.google.protobuf.DurationOrBuilder getRequestHeadersTimeoutOrBuilder()The amount of time that Envoy will wait for the request headers to be received. The timer is activated when the first byte of the headers is received, and is disarmed when the last byte of the headers has been received. If not specified or set to 0, this timeout is disabled.
.google.protobuf.Duration request_headers_timeout = 41 [(.validate.rules) = { ... }
- Specified by:
getRequestHeadersTimeoutOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetRequestHeadersTimeoutFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder, internalGetRequestHeadersTimeoutFieldBuilder()com.google.protobuf.DurationOrBuilder> The amount of time that Envoy will wait for the request headers to be received. The timer is activated when the first byte of the headers is received, and is disarmed when the last byte of the headers has been received. If not specified or set to 0, this timeout is disabled.
.google.protobuf.Duration request_headers_timeout = 41 [(.validate.rules) = { ... }
-
hasDrainTimeout
public boolean hasDrainTimeout()The time that Envoy will wait between sending an HTTP/2 “shutdown notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame. This is used so that Envoy provides a grace period for new streams that race with the final GOAWAY frame. During this grace period, Envoy will continue to accept new streams. After the grace period, a final GOAWAY frame is sent and Envoy will start refusing new streams. Draining occurs both when a connection hits the idle timeout or during general server draining. The default grace period is 5000 milliseconds (5 seconds) if this option is not specified.
.google.protobuf.Duration drain_timeout = 12;
- Specified by:
hasDrainTimeout
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the drainTimeout field is set.
-
getDrainTimeout
public com.google.protobuf.Duration getDrainTimeout()The time that Envoy will wait between sending an HTTP/2 “shutdown notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame. This is used so that Envoy provides a grace period for new streams that race with the final GOAWAY frame. During this grace period, Envoy will continue to accept new streams. After the grace period, a final GOAWAY frame is sent and Envoy will start refusing new streams. Draining occurs both when a connection hits the idle timeout or during general server draining. The default grace period is 5000 milliseconds (5 seconds) if this option is not specified.
.google.protobuf.Duration drain_timeout = 12;
- Specified by:
getDrainTimeout
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The drainTimeout.
-
setDrainTimeout
The time that Envoy will wait between sending an HTTP/2 “shutdown notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame. This is used so that Envoy provides a grace period for new streams that race with the final GOAWAY frame. During this grace period, Envoy will continue to accept new streams. After the grace period, a final GOAWAY frame is sent and Envoy will start refusing new streams. Draining occurs both when a connection hits the idle timeout or during general server draining. The default grace period is 5000 milliseconds (5 seconds) if this option is not specified.
.google.protobuf.Duration drain_timeout = 12;
-
setDrainTimeout
public HttpConnectionManager.Builder setDrainTimeout(com.google.protobuf.Duration.Builder builderForValue) The time that Envoy will wait between sending an HTTP/2 “shutdown notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame. This is used so that Envoy provides a grace period for new streams that race with the final GOAWAY frame. During this grace period, Envoy will continue to accept new streams. After the grace period, a final GOAWAY frame is sent and Envoy will start refusing new streams. Draining occurs both when a connection hits the idle timeout or during general server draining. The default grace period is 5000 milliseconds (5 seconds) if this option is not specified.
.google.protobuf.Duration drain_timeout = 12;
-
mergeDrainTimeout
The time that Envoy will wait between sending an HTTP/2 “shutdown notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame. This is used so that Envoy provides a grace period for new streams that race with the final GOAWAY frame. During this grace period, Envoy will continue to accept new streams. After the grace period, a final GOAWAY frame is sent and Envoy will start refusing new streams. Draining occurs both when a connection hits the idle timeout or during general server draining. The default grace period is 5000 milliseconds (5 seconds) if this option is not specified.
.google.protobuf.Duration drain_timeout = 12;
-
clearDrainTimeout
The time that Envoy will wait between sending an HTTP/2 “shutdown notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame. This is used so that Envoy provides a grace period for new streams that race with the final GOAWAY frame. During this grace period, Envoy will continue to accept new streams. After the grace period, a final GOAWAY frame is sent and Envoy will start refusing new streams. Draining occurs both when a connection hits the idle timeout or during general server draining. The default grace period is 5000 milliseconds (5 seconds) if this option is not specified.
.google.protobuf.Duration drain_timeout = 12;
-
getDrainTimeoutBuilder
public com.google.protobuf.Duration.Builder getDrainTimeoutBuilder()The time that Envoy will wait between sending an HTTP/2 “shutdown notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame. This is used so that Envoy provides a grace period for new streams that race with the final GOAWAY frame. During this grace period, Envoy will continue to accept new streams. After the grace period, a final GOAWAY frame is sent and Envoy will start refusing new streams. Draining occurs both when a connection hits the idle timeout or during general server draining. The default grace period is 5000 milliseconds (5 seconds) if this option is not specified.
.google.protobuf.Duration drain_timeout = 12;
-
getDrainTimeoutOrBuilder
public com.google.protobuf.DurationOrBuilder getDrainTimeoutOrBuilder()The time that Envoy will wait between sending an HTTP/2 “shutdown notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame. This is used so that Envoy provides a grace period for new streams that race with the final GOAWAY frame. During this grace period, Envoy will continue to accept new streams. After the grace period, a final GOAWAY frame is sent and Envoy will start refusing new streams. Draining occurs both when a connection hits the idle timeout or during general server draining. The default grace period is 5000 milliseconds (5 seconds) if this option is not specified.
.google.protobuf.Duration drain_timeout = 12;
- Specified by:
getDrainTimeoutOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetDrainTimeoutFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder, internalGetDrainTimeoutFieldBuilder()com.google.protobuf.DurationOrBuilder> The time that Envoy will wait between sending an HTTP/2 “shutdown notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame. This is used so that Envoy provides a grace period for new streams that race with the final GOAWAY frame. During this grace period, Envoy will continue to accept new streams. After the grace period, a final GOAWAY frame is sent and Envoy will start refusing new streams. Draining occurs both when a connection hits the idle timeout or during general server draining. The default grace period is 5000 milliseconds (5 seconds) if this option is not specified.
.google.protobuf.Duration drain_timeout = 12;
-
hasDelayedCloseTimeout
public boolean hasDelayedCloseTimeout()The delayed close timeout is for downstream connections managed by the HTTP connection manager. It is defined as a grace period after connection close processing has been locally initiated during which Envoy will wait for the peer to close (i.e., a TCP FIN/RST is received by Envoy from the downstream connection) prior to Envoy closing the socket associated with that connection. NOTE: This timeout is enforced even when the socket associated with the downstream connection is pending a flush of the write buffer. However, any progress made writing data to the socket will restart the timer associated with this timeout. This means that the total grace period for a socket in this state will be <total_time_waiting_for_write_buffer_flushes>+<delayed_close_timeout>. Delaying Envoy's connection close and giving the peer the opportunity to initiate the close sequence mitigates a race condition that exists when downstream clients do not drain/process data in a connection's receive buffer after a remote close has been detected via a socket write(). This race leads to such clients failing to process the response code sent by Envoy, which could result in erroneous downstream processing. If the timeout triggers, Envoy will close the connection's socket. The default timeout is 1000 ms if this option is not specified. .. NOTE:: To be useful in avoiding the race condition described above, this timeout must be set to *at least* <max round trip time expected between clients and Envoy>+<100ms to account for a reasonable "worst" case processing time for a full iteration of Envoy's event loop>. .. WARNING:: A value of 0 will completely disable delayed close processing. When disabled, the downstream connection's socket will be closed immediately after the write flush is completed or will never close if the write flush does not complete.
.google.protobuf.Duration delayed_close_timeout = 26;
- Specified by:
hasDelayedCloseTimeout
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the delayedCloseTimeout field is set.
-
getDelayedCloseTimeout
public com.google.protobuf.Duration getDelayedCloseTimeout()The delayed close timeout is for downstream connections managed by the HTTP connection manager. It is defined as a grace period after connection close processing has been locally initiated during which Envoy will wait for the peer to close (i.e., a TCP FIN/RST is received by Envoy from the downstream connection) prior to Envoy closing the socket associated with that connection. NOTE: This timeout is enforced even when the socket associated with the downstream connection is pending a flush of the write buffer. However, any progress made writing data to the socket will restart the timer associated with this timeout. This means that the total grace period for a socket in this state will be <total_time_waiting_for_write_buffer_flushes>+<delayed_close_timeout>. Delaying Envoy's connection close and giving the peer the opportunity to initiate the close sequence mitigates a race condition that exists when downstream clients do not drain/process data in a connection's receive buffer after a remote close has been detected via a socket write(). This race leads to such clients failing to process the response code sent by Envoy, which could result in erroneous downstream processing. If the timeout triggers, Envoy will close the connection's socket. The default timeout is 1000 ms if this option is not specified. .. NOTE:: To be useful in avoiding the race condition described above, this timeout must be set to *at least* <max round trip time expected between clients and Envoy>+<100ms to account for a reasonable "worst" case processing time for a full iteration of Envoy's event loop>. .. WARNING:: A value of 0 will completely disable delayed close processing. When disabled, the downstream connection's socket will be closed immediately after the write flush is completed or will never close if the write flush does not complete.
.google.protobuf.Duration delayed_close_timeout = 26;
- Specified by:
getDelayedCloseTimeout
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The delayedCloseTimeout.
-
setDelayedCloseTimeout
The delayed close timeout is for downstream connections managed by the HTTP connection manager. It is defined as a grace period after connection close processing has been locally initiated during which Envoy will wait for the peer to close (i.e., a TCP FIN/RST is received by Envoy from the downstream connection) prior to Envoy closing the socket associated with that connection. NOTE: This timeout is enforced even when the socket associated with the downstream connection is pending a flush of the write buffer. However, any progress made writing data to the socket will restart the timer associated with this timeout. This means that the total grace period for a socket in this state will be <total_time_waiting_for_write_buffer_flushes>+<delayed_close_timeout>. Delaying Envoy's connection close and giving the peer the opportunity to initiate the close sequence mitigates a race condition that exists when downstream clients do not drain/process data in a connection's receive buffer after a remote close has been detected via a socket write(). This race leads to such clients failing to process the response code sent by Envoy, which could result in erroneous downstream processing. If the timeout triggers, Envoy will close the connection's socket. The default timeout is 1000 ms if this option is not specified. .. NOTE:: To be useful in avoiding the race condition described above, this timeout must be set to *at least* <max round trip time expected between clients and Envoy>+<100ms to account for a reasonable "worst" case processing time for a full iteration of Envoy's event loop>. .. WARNING:: A value of 0 will completely disable delayed close processing. When disabled, the downstream connection's socket will be closed immediately after the write flush is completed or will never close if the write flush does not complete.
.google.protobuf.Duration delayed_close_timeout = 26;
-
setDelayedCloseTimeout
public HttpConnectionManager.Builder setDelayedCloseTimeout(com.google.protobuf.Duration.Builder builderForValue) The delayed close timeout is for downstream connections managed by the HTTP connection manager. It is defined as a grace period after connection close processing has been locally initiated during which Envoy will wait for the peer to close (i.e., a TCP FIN/RST is received by Envoy from the downstream connection) prior to Envoy closing the socket associated with that connection. NOTE: This timeout is enforced even when the socket associated with the downstream connection is pending a flush of the write buffer. However, any progress made writing data to the socket will restart the timer associated with this timeout. This means that the total grace period for a socket in this state will be <total_time_waiting_for_write_buffer_flushes>+<delayed_close_timeout>. Delaying Envoy's connection close and giving the peer the opportunity to initiate the close sequence mitigates a race condition that exists when downstream clients do not drain/process data in a connection's receive buffer after a remote close has been detected via a socket write(). This race leads to such clients failing to process the response code sent by Envoy, which could result in erroneous downstream processing. If the timeout triggers, Envoy will close the connection's socket. The default timeout is 1000 ms if this option is not specified. .. NOTE:: To be useful in avoiding the race condition described above, this timeout must be set to *at least* <max round trip time expected between clients and Envoy>+<100ms to account for a reasonable "worst" case processing time for a full iteration of Envoy's event loop>. .. WARNING:: A value of 0 will completely disable delayed close processing. When disabled, the downstream connection's socket will be closed immediately after the write flush is completed or will never close if the write flush does not complete.
.google.protobuf.Duration delayed_close_timeout = 26;
-
mergeDelayedCloseTimeout
The delayed close timeout is for downstream connections managed by the HTTP connection manager. It is defined as a grace period after connection close processing has been locally initiated during which Envoy will wait for the peer to close (i.e., a TCP FIN/RST is received by Envoy from the downstream connection) prior to Envoy closing the socket associated with that connection. NOTE: This timeout is enforced even when the socket associated with the downstream connection is pending a flush of the write buffer. However, any progress made writing data to the socket will restart the timer associated with this timeout. This means that the total grace period for a socket in this state will be <total_time_waiting_for_write_buffer_flushes>+<delayed_close_timeout>. Delaying Envoy's connection close and giving the peer the opportunity to initiate the close sequence mitigates a race condition that exists when downstream clients do not drain/process data in a connection's receive buffer after a remote close has been detected via a socket write(). This race leads to such clients failing to process the response code sent by Envoy, which could result in erroneous downstream processing. If the timeout triggers, Envoy will close the connection's socket. The default timeout is 1000 ms if this option is not specified. .. NOTE:: To be useful in avoiding the race condition described above, this timeout must be set to *at least* <max round trip time expected between clients and Envoy>+<100ms to account for a reasonable "worst" case processing time for a full iteration of Envoy's event loop>. .. WARNING:: A value of 0 will completely disable delayed close processing. When disabled, the downstream connection's socket will be closed immediately after the write flush is completed or will never close if the write flush does not complete.
.google.protobuf.Duration delayed_close_timeout = 26;
-
clearDelayedCloseTimeout
The delayed close timeout is for downstream connections managed by the HTTP connection manager. It is defined as a grace period after connection close processing has been locally initiated during which Envoy will wait for the peer to close (i.e., a TCP FIN/RST is received by Envoy from the downstream connection) prior to Envoy closing the socket associated with that connection. NOTE: This timeout is enforced even when the socket associated with the downstream connection is pending a flush of the write buffer. However, any progress made writing data to the socket will restart the timer associated with this timeout. This means that the total grace period for a socket in this state will be <total_time_waiting_for_write_buffer_flushes>+<delayed_close_timeout>. Delaying Envoy's connection close and giving the peer the opportunity to initiate the close sequence mitigates a race condition that exists when downstream clients do not drain/process data in a connection's receive buffer after a remote close has been detected via a socket write(). This race leads to such clients failing to process the response code sent by Envoy, which could result in erroneous downstream processing. If the timeout triggers, Envoy will close the connection's socket. The default timeout is 1000 ms if this option is not specified. .. NOTE:: To be useful in avoiding the race condition described above, this timeout must be set to *at least* <max round trip time expected between clients and Envoy>+<100ms to account for a reasonable "worst" case processing time for a full iteration of Envoy's event loop>. .. WARNING:: A value of 0 will completely disable delayed close processing. When disabled, the downstream connection's socket will be closed immediately after the write flush is completed or will never close if the write flush does not complete.
.google.protobuf.Duration delayed_close_timeout = 26;
-
getDelayedCloseTimeoutBuilder
public com.google.protobuf.Duration.Builder getDelayedCloseTimeoutBuilder()The delayed close timeout is for downstream connections managed by the HTTP connection manager. It is defined as a grace period after connection close processing has been locally initiated during which Envoy will wait for the peer to close (i.e., a TCP FIN/RST is received by Envoy from the downstream connection) prior to Envoy closing the socket associated with that connection. NOTE: This timeout is enforced even when the socket associated with the downstream connection is pending a flush of the write buffer. However, any progress made writing data to the socket will restart the timer associated with this timeout. This means that the total grace period for a socket in this state will be <total_time_waiting_for_write_buffer_flushes>+<delayed_close_timeout>. Delaying Envoy's connection close and giving the peer the opportunity to initiate the close sequence mitigates a race condition that exists when downstream clients do not drain/process data in a connection's receive buffer after a remote close has been detected via a socket write(). This race leads to such clients failing to process the response code sent by Envoy, which could result in erroneous downstream processing. If the timeout triggers, Envoy will close the connection's socket. The default timeout is 1000 ms if this option is not specified. .. NOTE:: To be useful in avoiding the race condition described above, this timeout must be set to *at least* <max round trip time expected between clients and Envoy>+<100ms to account for a reasonable "worst" case processing time for a full iteration of Envoy's event loop>. .. WARNING:: A value of 0 will completely disable delayed close processing. When disabled, the downstream connection's socket will be closed immediately after the write flush is completed or will never close if the write flush does not complete.
.google.protobuf.Duration delayed_close_timeout = 26;
-
getDelayedCloseTimeoutOrBuilder
public com.google.protobuf.DurationOrBuilder getDelayedCloseTimeoutOrBuilder()The delayed close timeout is for downstream connections managed by the HTTP connection manager. It is defined as a grace period after connection close processing has been locally initiated during which Envoy will wait for the peer to close (i.e., a TCP FIN/RST is received by Envoy from the downstream connection) prior to Envoy closing the socket associated with that connection. NOTE: This timeout is enforced even when the socket associated with the downstream connection is pending a flush of the write buffer. However, any progress made writing data to the socket will restart the timer associated with this timeout. This means that the total grace period for a socket in this state will be <total_time_waiting_for_write_buffer_flushes>+<delayed_close_timeout>. Delaying Envoy's connection close and giving the peer the opportunity to initiate the close sequence mitigates a race condition that exists when downstream clients do not drain/process data in a connection's receive buffer after a remote close has been detected via a socket write(). This race leads to such clients failing to process the response code sent by Envoy, which could result in erroneous downstream processing. If the timeout triggers, Envoy will close the connection's socket. The default timeout is 1000 ms if this option is not specified. .. NOTE:: To be useful in avoiding the race condition described above, this timeout must be set to *at least* <max round trip time expected between clients and Envoy>+<100ms to account for a reasonable "worst" case processing time for a full iteration of Envoy's event loop>. .. WARNING:: A value of 0 will completely disable delayed close processing. When disabled, the downstream connection's socket will be closed immediately after the write flush is completed or will never close if the write flush does not complete.
.google.protobuf.Duration delayed_close_timeout = 26;
- Specified by:
getDelayedCloseTimeoutOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetDelayedCloseTimeoutFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder, internalGetDelayedCloseTimeoutFieldBuilder()com.google.protobuf.DurationOrBuilder> The delayed close timeout is for downstream connections managed by the HTTP connection manager. It is defined as a grace period after connection close processing has been locally initiated during which Envoy will wait for the peer to close (i.e., a TCP FIN/RST is received by Envoy from the downstream connection) prior to Envoy closing the socket associated with that connection. NOTE: This timeout is enforced even when the socket associated with the downstream connection is pending a flush of the write buffer. However, any progress made writing data to the socket will restart the timer associated with this timeout. This means that the total grace period for a socket in this state will be <total_time_waiting_for_write_buffer_flushes>+<delayed_close_timeout>. Delaying Envoy's connection close and giving the peer the opportunity to initiate the close sequence mitigates a race condition that exists when downstream clients do not drain/process data in a connection's receive buffer after a remote close has been detected via a socket write(). This race leads to such clients failing to process the response code sent by Envoy, which could result in erroneous downstream processing. If the timeout triggers, Envoy will close the connection's socket. The default timeout is 1000 ms if this option is not specified. .. NOTE:: To be useful in avoiding the race condition described above, this timeout must be set to *at least* <max round trip time expected between clients and Envoy>+<100ms to account for a reasonable "worst" case processing time for a full iteration of Envoy's event loop>. .. WARNING:: A value of 0 will completely disable delayed close processing. When disabled, the downstream connection's socket will be closed immediately after the write flush is completed or will never close if the write flush does not complete.
.google.protobuf.Duration delayed_close_timeout = 26;
-
ensureAccessLogIsMutable
private void ensureAccessLogIsMutable() -
getAccessLogList
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.
repeated .envoy.config.accesslog.v3.AccessLog access_log = 13;
- Specified by:
getAccessLogList
in interfaceHttpConnectionManagerOrBuilder
-
getAccessLogCount
public int getAccessLogCount()Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.
repeated .envoy.config.accesslog.v3.AccessLog access_log = 13;
- Specified by:
getAccessLogCount
in interfaceHttpConnectionManagerOrBuilder
-
getAccessLog
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.
repeated .envoy.config.accesslog.v3.AccessLog access_log = 13;
- Specified by:
getAccessLog
in interfaceHttpConnectionManagerOrBuilder
-
setAccessLog
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.
repeated .envoy.config.accesslog.v3.AccessLog access_log = 13;
-
setAccessLog
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.
repeated .envoy.config.accesslog.v3.AccessLog access_log = 13;
-
addAccessLog
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.
repeated .envoy.config.accesslog.v3.AccessLog access_log = 13;
-
addAccessLog
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.
repeated .envoy.config.accesslog.v3.AccessLog access_log = 13;
-
addAccessLog
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.
repeated .envoy.config.accesslog.v3.AccessLog access_log = 13;
-
addAccessLog
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.
repeated .envoy.config.accesslog.v3.AccessLog access_log = 13;
-
addAllAccessLog
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.
repeated .envoy.config.accesslog.v3.AccessLog access_log = 13;
-
clearAccessLog
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.
repeated .envoy.config.accesslog.v3.AccessLog access_log = 13;
-
removeAccessLog
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.
repeated .envoy.config.accesslog.v3.AccessLog access_log = 13;
-
getAccessLogBuilder
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.
repeated .envoy.config.accesslog.v3.AccessLog access_log = 13;
-
getAccessLogOrBuilder
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.
repeated .envoy.config.accesslog.v3.AccessLog access_log = 13;
- Specified by:
getAccessLogOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
getAccessLogOrBuilderList
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.
repeated .envoy.config.accesslog.v3.AccessLog access_log = 13;
- Specified by:
getAccessLogOrBuilderList
in interfaceHttpConnectionManagerOrBuilder
-
addAccessLogBuilder
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.
repeated .envoy.config.accesslog.v3.AccessLog access_log = 13;
-
addAccessLogBuilder
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.
repeated .envoy.config.accesslog.v3.AccessLog access_log = 13;
-
getAccessLogBuilderList
Configuration for :ref:`HTTP access logs <arch_overview_access_logs>` emitted by the connection manager.
repeated .envoy.config.accesslog.v3.AccessLog access_log = 13;
-
internalGetAccessLogFieldBuilder
private com.google.protobuf.RepeatedFieldBuilder<AccessLog,AccessLog.Builder, internalGetAccessLogFieldBuilder()AccessLogOrBuilder> -
hasAccessLogFlushInterval
Deprecated.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.access_log_flush_interval is deprecated. See envoy/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto;l=597.. attention:: This field is deprecated in favor of :ref:`access_log_flush_interval <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>`. Note that if both this field and :ref:`access_log_flush_interval <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>` are specified, the former (deprecated field) is ignored.
.google.protobuf.Duration access_log_flush_interval = 54 [deprecated = true, (.validate.rules) = { ... }
- Specified by:
hasAccessLogFlushInterval
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the accessLogFlushInterval field is set.
-
getAccessLogFlushInterval
Deprecated.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.access_log_flush_interval is deprecated. See envoy/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto;l=597.. attention:: This field is deprecated in favor of :ref:`access_log_flush_interval <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>`. Note that if both this field and :ref:`access_log_flush_interval <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>` are specified, the former (deprecated field) is ignored.
.google.protobuf.Duration access_log_flush_interval = 54 [deprecated = true, (.validate.rules) = { ... }
- Specified by:
getAccessLogFlushInterval
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The accessLogFlushInterval.
-
setAccessLogFlushInterval
@Deprecated public HttpConnectionManager.Builder setAccessLogFlushInterval(com.google.protobuf.Duration value) Deprecated... attention:: This field is deprecated in favor of :ref:`access_log_flush_interval <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>`. Note that if both this field and :ref:`access_log_flush_interval <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>` are specified, the former (deprecated field) is ignored.
.google.protobuf.Duration access_log_flush_interval = 54 [deprecated = true, (.validate.rules) = { ... }
-
setAccessLogFlushInterval
@Deprecated public HttpConnectionManager.Builder setAccessLogFlushInterval(com.google.protobuf.Duration.Builder builderForValue) Deprecated... attention:: This field is deprecated in favor of :ref:`access_log_flush_interval <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>`. Note that if both this field and :ref:`access_log_flush_interval <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>` are specified, the former (deprecated field) is ignored.
.google.protobuf.Duration access_log_flush_interval = 54 [deprecated = true, (.validate.rules) = { ... }
-
mergeAccessLogFlushInterval
@Deprecated public HttpConnectionManager.Builder mergeAccessLogFlushInterval(com.google.protobuf.Duration value) Deprecated... attention:: This field is deprecated in favor of :ref:`access_log_flush_interval <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>`. Note that if both this field and :ref:`access_log_flush_interval <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>` are specified, the former (deprecated field) is ignored.
.google.protobuf.Duration access_log_flush_interval = 54 [deprecated = true, (.validate.rules) = { ... }
-
clearAccessLogFlushInterval
Deprecated... attention:: This field is deprecated in favor of :ref:`access_log_flush_interval <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>`. Note that if both this field and :ref:`access_log_flush_interval <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>` are specified, the former (deprecated field) is ignored.
.google.protobuf.Duration access_log_flush_interval = 54 [deprecated = true, (.validate.rules) = { ... }
-
getAccessLogFlushIntervalBuilder
Deprecated... attention:: This field is deprecated in favor of :ref:`access_log_flush_interval <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>`. Note that if both this field and :ref:`access_log_flush_interval <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>` are specified, the former (deprecated field) is ignored.
.google.protobuf.Duration access_log_flush_interval = 54 [deprecated = true, (.validate.rules) = { ... }
-
getAccessLogFlushIntervalOrBuilder
Deprecated... attention:: This field is deprecated in favor of :ref:`access_log_flush_interval <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>`. Note that if both this field and :ref:`access_log_flush_interval <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>` are specified, the former (deprecated field) is ignored.
.google.protobuf.Duration access_log_flush_interval = 54 [deprecated = true, (.validate.rules) = { ... }
- Specified by:
getAccessLogFlushIntervalOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetAccessLogFlushIntervalFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder, internalGetAccessLogFlushIntervalFieldBuilder()com.google.protobuf.DurationOrBuilder> .. attention:: This field is deprecated in favor of :ref:`access_log_flush_interval <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>`. Note that if both this field and :ref:`access_log_flush_interval <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>` are specified, the former (deprecated field) is ignored.
.google.protobuf.Duration access_log_flush_interval = 54 [deprecated = true, (.validate.rules) = { ... }
-
getFlushAccessLogOnNewRequest
Deprecated.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.flush_access_log_on_new_request is deprecated. See envoy/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto;l=610.. attention:: This field is deprecated in favor of :ref:`flush_access_log_on_new_request <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.flush_access_log_on_new_request>`. Note that if both this field and :ref:`flush_access_log_on_new_request <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.flush_access_log_on_new_request>` are specified, the former (deprecated field) is ignored.
bool flush_access_log_on_new_request = 55 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getFlushAccessLogOnNewRequest
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The flushAccessLogOnNewRequest.
-
setFlushAccessLogOnNewRequest
Deprecated.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.flush_access_log_on_new_request is deprecated. See envoy/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto;l=610.. attention:: This field is deprecated in favor of :ref:`flush_access_log_on_new_request <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.flush_access_log_on_new_request>`. Note that if both this field and :ref:`flush_access_log_on_new_request <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.flush_access_log_on_new_request>` are specified, the former (deprecated field) is ignored.
bool flush_access_log_on_new_request = 55 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Parameters:
value
- The flushAccessLogOnNewRequest to set.- Returns:
- This builder for chaining.
-
clearFlushAccessLogOnNewRequest
Deprecated.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.flush_access_log_on_new_request is deprecated. See envoy/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto;l=610.. attention:: This field is deprecated in favor of :ref:`flush_access_log_on_new_request <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.flush_access_log_on_new_request>`. Note that if both this field and :ref:`flush_access_log_on_new_request <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.flush_access_log_on_new_request>` are specified, the former (deprecated field) is ignored.
bool flush_access_log_on_new_request = 55 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Returns:
- This builder for chaining.
-
hasAccessLogOptions
public boolean hasAccessLogOptions()Additional access log options for HTTP connection manager.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions access_log_options = 56;
- Specified by:
hasAccessLogOptions
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the accessLogOptions field is set.
-
getAccessLogOptions
Additional access log options for HTTP connection manager.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions access_log_options = 56;
- Specified by:
getAccessLogOptions
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The accessLogOptions.
-
setAccessLogOptions
public HttpConnectionManager.Builder setAccessLogOptions(HttpConnectionManager.HcmAccessLogOptions value) Additional access log options for HTTP connection manager.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions access_log_options = 56;
-
setAccessLogOptions
public HttpConnectionManager.Builder setAccessLogOptions(HttpConnectionManager.HcmAccessLogOptions.Builder builderForValue) Additional access log options for HTTP connection manager.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions access_log_options = 56;
-
mergeAccessLogOptions
public HttpConnectionManager.Builder mergeAccessLogOptions(HttpConnectionManager.HcmAccessLogOptions value) Additional access log options for HTTP connection manager.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions access_log_options = 56;
-
clearAccessLogOptions
Additional access log options for HTTP connection manager.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions access_log_options = 56;
-
getAccessLogOptionsBuilder
Additional access log options for HTTP connection manager.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions access_log_options = 56;
-
getAccessLogOptionsOrBuilder
Additional access log options for HTTP connection manager.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions access_log_options = 56;
- Specified by:
getAccessLogOptionsOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetAccessLogOptionsFieldBuilder
private com.google.protobuf.SingleFieldBuilder<HttpConnectionManager.HcmAccessLogOptions,HttpConnectionManager.HcmAccessLogOptions.Builder, internalGetAccessLogOptionsFieldBuilder()HttpConnectionManager.HcmAccessLogOptionsOrBuilder> Additional access log options for HTTP connection manager.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions access_log_options = 56;
-
hasUseRemoteAddress
public boolean hasUseRemoteAddress()If set to true, the connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers. If set to false or absent, the connection manager will use the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header. See the documentation for :ref:`config_http_conn_man_headers_x-forwarded-for`, :ref:`config_http_conn_man_headers_x-envoy-internal`, and :ref:`config_http_conn_man_headers_x-envoy-external-address` for more information.
.google.protobuf.BoolValue use_remote_address = 14 [(.udpa.annotations.security) = { ... }
- Specified by:
hasUseRemoteAddress
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the useRemoteAddress field is set.
-
getUseRemoteAddress
public com.google.protobuf.BoolValue getUseRemoteAddress()If set to true, the connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers. If set to false or absent, the connection manager will use the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header. See the documentation for :ref:`config_http_conn_man_headers_x-forwarded-for`, :ref:`config_http_conn_man_headers_x-envoy-internal`, and :ref:`config_http_conn_man_headers_x-envoy-external-address` for more information.
.google.protobuf.BoolValue use_remote_address = 14 [(.udpa.annotations.security) = { ... }
- Specified by:
getUseRemoteAddress
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The useRemoteAddress.
-
setUseRemoteAddress
If set to true, the connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers. If set to false or absent, the connection manager will use the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header. See the documentation for :ref:`config_http_conn_man_headers_x-forwarded-for`, :ref:`config_http_conn_man_headers_x-envoy-internal`, and :ref:`config_http_conn_man_headers_x-envoy-external-address` for more information.
.google.protobuf.BoolValue use_remote_address = 14 [(.udpa.annotations.security) = { ... }
-
setUseRemoteAddress
public HttpConnectionManager.Builder setUseRemoteAddress(com.google.protobuf.BoolValue.Builder builderForValue) If set to true, the connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers. If set to false or absent, the connection manager will use the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header. See the documentation for :ref:`config_http_conn_man_headers_x-forwarded-for`, :ref:`config_http_conn_man_headers_x-envoy-internal`, and :ref:`config_http_conn_man_headers_x-envoy-external-address` for more information.
.google.protobuf.BoolValue use_remote_address = 14 [(.udpa.annotations.security) = { ... }
-
mergeUseRemoteAddress
If set to true, the connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers. If set to false or absent, the connection manager will use the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header. See the documentation for :ref:`config_http_conn_man_headers_x-forwarded-for`, :ref:`config_http_conn_man_headers_x-envoy-internal`, and :ref:`config_http_conn_man_headers_x-envoy-external-address` for more information.
.google.protobuf.BoolValue use_remote_address = 14 [(.udpa.annotations.security) = { ... }
-
clearUseRemoteAddress
If set to true, the connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers. If set to false or absent, the connection manager will use the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header. See the documentation for :ref:`config_http_conn_man_headers_x-forwarded-for`, :ref:`config_http_conn_man_headers_x-envoy-internal`, and :ref:`config_http_conn_man_headers_x-envoy-external-address` for more information.
.google.protobuf.BoolValue use_remote_address = 14 [(.udpa.annotations.security) = { ... }
-
getUseRemoteAddressBuilder
public com.google.protobuf.BoolValue.Builder getUseRemoteAddressBuilder()If set to true, the connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers. If set to false or absent, the connection manager will use the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header. See the documentation for :ref:`config_http_conn_man_headers_x-forwarded-for`, :ref:`config_http_conn_man_headers_x-envoy-internal`, and :ref:`config_http_conn_man_headers_x-envoy-external-address` for more information.
.google.protobuf.BoolValue use_remote_address = 14 [(.udpa.annotations.security) = { ... }
-
getUseRemoteAddressOrBuilder
public com.google.protobuf.BoolValueOrBuilder getUseRemoteAddressOrBuilder()If set to true, the connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers. If set to false or absent, the connection manager will use the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header. See the documentation for :ref:`config_http_conn_man_headers_x-forwarded-for`, :ref:`config_http_conn_man_headers_x-envoy-internal`, and :ref:`config_http_conn_man_headers_x-envoy-external-address` for more information.
.google.protobuf.BoolValue use_remote_address = 14 [(.udpa.annotations.security) = { ... }
- Specified by:
getUseRemoteAddressOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetUseRemoteAddressFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder, internalGetUseRemoteAddressFieldBuilder()com.google.protobuf.BoolValueOrBuilder> If set to true, the connection manager will use the real remote address of the client connection when determining internal versus external origin and manipulating various headers. If set to false or absent, the connection manager will use the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header. See the documentation for :ref:`config_http_conn_man_headers_x-forwarded-for`, :ref:`config_http_conn_man_headers_x-envoy-internal`, and :ref:`config_http_conn_man_headers_x-envoy-external-address` for more information.
.google.protobuf.BoolValue use_remote_address = 14 [(.udpa.annotations.security) = { ... }
-
getXffNumTrustedHops
public int getXffNumTrustedHops()The number of additional ingress proxy hops from the right side of the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header to trust when determining the origin client's IP address. The default is zero if this option is not specified. See the documentation for :ref:`config_http_conn_man_headers_x-forwarded-for` for more information.
uint32 xff_num_trusted_hops = 19;
- Specified by:
getXffNumTrustedHops
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The xffNumTrustedHops.
-
setXffNumTrustedHops
The number of additional ingress proxy hops from the right side of the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header to trust when determining the origin client's IP address. The default is zero if this option is not specified. See the documentation for :ref:`config_http_conn_man_headers_x-forwarded-for` for more information.
uint32 xff_num_trusted_hops = 19;
- Parameters:
value
- The xffNumTrustedHops to set.- Returns:
- This builder for chaining.
-
clearXffNumTrustedHops
The number of additional ingress proxy hops from the right side of the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header to trust when determining the origin client's IP address. The default is zero if this option is not specified. See the documentation for :ref:`config_http_conn_man_headers_x-forwarded-for` for more information.
uint32 xff_num_trusted_hops = 19;
- Returns:
- This builder for chaining.
-
ensureOriginalIpDetectionExtensionsIsMutable
private void ensureOriginalIpDetectionExtensionsIsMutable() -
getOriginalIpDetectionExtensionsList
The configuration for the original IP detection extensions. When configured the extensions will be called along with the request headers and information about the downstream connection, such as the directly connected address. Each extension will then use these parameters to decide the request's effective remote address. If an extension fails to detect the original IP address and isn't configured to reject the request, the HCM will try the remaining extensions until one succeeds or rejects the request. If the request isn't rejected nor any extension succeeds, the HCM will fallback to using the remote address. .. WARNING:: Extensions cannot be used in conjunction with :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` nor :ref:`xff_num_trusted_hops <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`. [#extension-category: envoy.http.original_ip_detection]
repeated .envoy.config.core.v3.TypedExtensionConfig original_ip_detection_extensions = 46;
- Specified by:
getOriginalIpDetectionExtensionsList
in interfaceHttpConnectionManagerOrBuilder
-
getOriginalIpDetectionExtensionsCount
public int getOriginalIpDetectionExtensionsCount()The configuration for the original IP detection extensions. When configured the extensions will be called along with the request headers and information about the downstream connection, such as the directly connected address. Each extension will then use these parameters to decide the request's effective remote address. If an extension fails to detect the original IP address and isn't configured to reject the request, the HCM will try the remaining extensions until one succeeds or rejects the request. If the request isn't rejected nor any extension succeeds, the HCM will fallback to using the remote address. .. WARNING:: Extensions cannot be used in conjunction with :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` nor :ref:`xff_num_trusted_hops <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`. [#extension-category: envoy.http.original_ip_detection]
repeated .envoy.config.core.v3.TypedExtensionConfig original_ip_detection_extensions = 46;
- Specified by:
getOriginalIpDetectionExtensionsCount
in interfaceHttpConnectionManagerOrBuilder
-
getOriginalIpDetectionExtensions
The configuration for the original IP detection extensions. When configured the extensions will be called along with the request headers and information about the downstream connection, such as the directly connected address. Each extension will then use these parameters to decide the request's effective remote address. If an extension fails to detect the original IP address and isn't configured to reject the request, the HCM will try the remaining extensions until one succeeds or rejects the request. If the request isn't rejected nor any extension succeeds, the HCM will fallback to using the remote address. .. WARNING:: Extensions cannot be used in conjunction with :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` nor :ref:`xff_num_trusted_hops <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`. [#extension-category: envoy.http.original_ip_detection]
repeated .envoy.config.core.v3.TypedExtensionConfig original_ip_detection_extensions = 46;
- Specified by:
getOriginalIpDetectionExtensions
in interfaceHttpConnectionManagerOrBuilder
-
setOriginalIpDetectionExtensions
public HttpConnectionManager.Builder setOriginalIpDetectionExtensions(int index, TypedExtensionConfig value) The configuration for the original IP detection extensions. When configured the extensions will be called along with the request headers and information about the downstream connection, such as the directly connected address. Each extension will then use these parameters to decide the request's effective remote address. If an extension fails to detect the original IP address and isn't configured to reject the request, the HCM will try the remaining extensions until one succeeds or rejects the request. If the request isn't rejected nor any extension succeeds, the HCM will fallback to using the remote address. .. WARNING:: Extensions cannot be used in conjunction with :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` nor :ref:`xff_num_trusted_hops <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`. [#extension-category: envoy.http.original_ip_detection]
repeated .envoy.config.core.v3.TypedExtensionConfig original_ip_detection_extensions = 46;
-
setOriginalIpDetectionExtensions
public HttpConnectionManager.Builder setOriginalIpDetectionExtensions(int index, TypedExtensionConfig.Builder builderForValue) The configuration for the original IP detection extensions. When configured the extensions will be called along with the request headers and information about the downstream connection, such as the directly connected address. Each extension will then use these parameters to decide the request's effective remote address. If an extension fails to detect the original IP address and isn't configured to reject the request, the HCM will try the remaining extensions until one succeeds or rejects the request. If the request isn't rejected nor any extension succeeds, the HCM will fallback to using the remote address. .. WARNING:: Extensions cannot be used in conjunction with :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` nor :ref:`xff_num_trusted_hops <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`. [#extension-category: envoy.http.original_ip_detection]
repeated .envoy.config.core.v3.TypedExtensionConfig original_ip_detection_extensions = 46;
-
addOriginalIpDetectionExtensions
The configuration for the original IP detection extensions. When configured the extensions will be called along with the request headers and information about the downstream connection, such as the directly connected address. Each extension will then use these parameters to decide the request's effective remote address. If an extension fails to detect the original IP address and isn't configured to reject the request, the HCM will try the remaining extensions until one succeeds or rejects the request. If the request isn't rejected nor any extension succeeds, the HCM will fallback to using the remote address. .. WARNING:: Extensions cannot be used in conjunction with :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` nor :ref:`xff_num_trusted_hops <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`. [#extension-category: envoy.http.original_ip_detection]
repeated .envoy.config.core.v3.TypedExtensionConfig original_ip_detection_extensions = 46;
-
addOriginalIpDetectionExtensions
public HttpConnectionManager.Builder addOriginalIpDetectionExtensions(int index, TypedExtensionConfig value) The configuration for the original IP detection extensions. When configured the extensions will be called along with the request headers and information about the downstream connection, such as the directly connected address. Each extension will then use these parameters to decide the request's effective remote address. If an extension fails to detect the original IP address and isn't configured to reject the request, the HCM will try the remaining extensions until one succeeds or rejects the request. If the request isn't rejected nor any extension succeeds, the HCM will fallback to using the remote address. .. WARNING:: Extensions cannot be used in conjunction with :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` nor :ref:`xff_num_trusted_hops <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`. [#extension-category: envoy.http.original_ip_detection]
repeated .envoy.config.core.v3.TypedExtensionConfig original_ip_detection_extensions = 46;
-
addOriginalIpDetectionExtensions
public HttpConnectionManager.Builder addOriginalIpDetectionExtensions(TypedExtensionConfig.Builder builderForValue) The configuration for the original IP detection extensions. When configured the extensions will be called along with the request headers and information about the downstream connection, such as the directly connected address. Each extension will then use these parameters to decide the request's effective remote address. If an extension fails to detect the original IP address and isn't configured to reject the request, the HCM will try the remaining extensions until one succeeds or rejects the request. If the request isn't rejected nor any extension succeeds, the HCM will fallback to using the remote address. .. WARNING:: Extensions cannot be used in conjunction with :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` nor :ref:`xff_num_trusted_hops <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`. [#extension-category: envoy.http.original_ip_detection]
repeated .envoy.config.core.v3.TypedExtensionConfig original_ip_detection_extensions = 46;
-
addOriginalIpDetectionExtensions
public HttpConnectionManager.Builder addOriginalIpDetectionExtensions(int index, TypedExtensionConfig.Builder builderForValue) The configuration for the original IP detection extensions. When configured the extensions will be called along with the request headers and information about the downstream connection, such as the directly connected address. Each extension will then use these parameters to decide the request's effective remote address. If an extension fails to detect the original IP address and isn't configured to reject the request, the HCM will try the remaining extensions until one succeeds or rejects the request. If the request isn't rejected nor any extension succeeds, the HCM will fallback to using the remote address. .. WARNING:: Extensions cannot be used in conjunction with :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` nor :ref:`xff_num_trusted_hops <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`. [#extension-category: envoy.http.original_ip_detection]
repeated .envoy.config.core.v3.TypedExtensionConfig original_ip_detection_extensions = 46;
-
addAllOriginalIpDetectionExtensions
public HttpConnectionManager.Builder addAllOriginalIpDetectionExtensions(Iterable<? extends TypedExtensionConfig> values) The configuration for the original IP detection extensions. When configured the extensions will be called along with the request headers and information about the downstream connection, such as the directly connected address. Each extension will then use these parameters to decide the request's effective remote address. If an extension fails to detect the original IP address and isn't configured to reject the request, the HCM will try the remaining extensions until one succeeds or rejects the request. If the request isn't rejected nor any extension succeeds, the HCM will fallback to using the remote address. .. WARNING:: Extensions cannot be used in conjunction with :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` nor :ref:`xff_num_trusted_hops <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`. [#extension-category: envoy.http.original_ip_detection]
repeated .envoy.config.core.v3.TypedExtensionConfig original_ip_detection_extensions = 46;
-
clearOriginalIpDetectionExtensions
The configuration for the original IP detection extensions. When configured the extensions will be called along with the request headers and information about the downstream connection, such as the directly connected address. Each extension will then use these parameters to decide the request's effective remote address. If an extension fails to detect the original IP address and isn't configured to reject the request, the HCM will try the remaining extensions until one succeeds or rejects the request. If the request isn't rejected nor any extension succeeds, the HCM will fallback to using the remote address. .. WARNING:: Extensions cannot be used in conjunction with :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` nor :ref:`xff_num_trusted_hops <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`. [#extension-category: envoy.http.original_ip_detection]
repeated .envoy.config.core.v3.TypedExtensionConfig original_ip_detection_extensions = 46;
-
removeOriginalIpDetectionExtensions
The configuration for the original IP detection extensions. When configured the extensions will be called along with the request headers and information about the downstream connection, such as the directly connected address. Each extension will then use these parameters to decide the request's effective remote address. If an extension fails to detect the original IP address and isn't configured to reject the request, the HCM will try the remaining extensions until one succeeds or rejects the request. If the request isn't rejected nor any extension succeeds, the HCM will fallback to using the remote address. .. WARNING:: Extensions cannot be used in conjunction with :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` nor :ref:`xff_num_trusted_hops <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`. [#extension-category: envoy.http.original_ip_detection]
repeated .envoy.config.core.v3.TypedExtensionConfig original_ip_detection_extensions = 46;
-
getOriginalIpDetectionExtensionsBuilder
The configuration for the original IP detection extensions. When configured the extensions will be called along with the request headers and information about the downstream connection, such as the directly connected address. Each extension will then use these parameters to decide the request's effective remote address. If an extension fails to detect the original IP address and isn't configured to reject the request, the HCM will try the remaining extensions until one succeeds or rejects the request. If the request isn't rejected nor any extension succeeds, the HCM will fallback to using the remote address. .. WARNING:: Extensions cannot be used in conjunction with :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` nor :ref:`xff_num_trusted_hops <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`. [#extension-category: envoy.http.original_ip_detection]
repeated .envoy.config.core.v3.TypedExtensionConfig original_ip_detection_extensions = 46;
-
getOriginalIpDetectionExtensionsOrBuilder
The configuration for the original IP detection extensions. When configured the extensions will be called along with the request headers and information about the downstream connection, such as the directly connected address. Each extension will then use these parameters to decide the request's effective remote address. If an extension fails to detect the original IP address and isn't configured to reject the request, the HCM will try the remaining extensions until one succeeds or rejects the request. If the request isn't rejected nor any extension succeeds, the HCM will fallback to using the remote address. .. WARNING:: Extensions cannot be used in conjunction with :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` nor :ref:`xff_num_trusted_hops <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`. [#extension-category: envoy.http.original_ip_detection]
repeated .envoy.config.core.v3.TypedExtensionConfig original_ip_detection_extensions = 46;
- Specified by:
getOriginalIpDetectionExtensionsOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
getOriginalIpDetectionExtensionsOrBuilderList
public List<? extends TypedExtensionConfigOrBuilder> getOriginalIpDetectionExtensionsOrBuilderList()The configuration for the original IP detection extensions. When configured the extensions will be called along with the request headers and information about the downstream connection, such as the directly connected address. Each extension will then use these parameters to decide the request's effective remote address. If an extension fails to detect the original IP address and isn't configured to reject the request, the HCM will try the remaining extensions until one succeeds or rejects the request. If the request isn't rejected nor any extension succeeds, the HCM will fallback to using the remote address. .. WARNING:: Extensions cannot be used in conjunction with :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` nor :ref:`xff_num_trusted_hops <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`. [#extension-category: envoy.http.original_ip_detection]
repeated .envoy.config.core.v3.TypedExtensionConfig original_ip_detection_extensions = 46;
- Specified by:
getOriginalIpDetectionExtensionsOrBuilderList
in interfaceHttpConnectionManagerOrBuilder
-
addOriginalIpDetectionExtensionsBuilder
The configuration for the original IP detection extensions. When configured the extensions will be called along with the request headers and information about the downstream connection, such as the directly connected address. Each extension will then use these parameters to decide the request's effective remote address. If an extension fails to detect the original IP address and isn't configured to reject the request, the HCM will try the remaining extensions until one succeeds or rejects the request. If the request isn't rejected nor any extension succeeds, the HCM will fallback to using the remote address. .. WARNING:: Extensions cannot be used in conjunction with :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` nor :ref:`xff_num_trusted_hops <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`. [#extension-category: envoy.http.original_ip_detection]
repeated .envoy.config.core.v3.TypedExtensionConfig original_ip_detection_extensions = 46;
-
addOriginalIpDetectionExtensionsBuilder
The configuration for the original IP detection extensions. When configured the extensions will be called along with the request headers and information about the downstream connection, such as the directly connected address. Each extension will then use these parameters to decide the request's effective remote address. If an extension fails to detect the original IP address and isn't configured to reject the request, the HCM will try the remaining extensions until one succeeds or rejects the request. If the request isn't rejected nor any extension succeeds, the HCM will fallback to using the remote address. .. WARNING:: Extensions cannot be used in conjunction with :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` nor :ref:`xff_num_trusted_hops <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`. [#extension-category: envoy.http.original_ip_detection]
repeated .envoy.config.core.v3.TypedExtensionConfig original_ip_detection_extensions = 46;
-
getOriginalIpDetectionExtensionsBuilderList
The configuration for the original IP detection extensions. When configured the extensions will be called along with the request headers and information about the downstream connection, such as the directly connected address. Each extension will then use these parameters to decide the request's effective remote address. If an extension fails to detect the original IP address and isn't configured to reject the request, the HCM will try the remaining extensions until one succeeds or rejects the request. If the request isn't rejected nor any extension succeeds, the HCM will fallback to using the remote address. .. WARNING:: Extensions cannot be used in conjunction with :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` nor :ref:`xff_num_trusted_hops <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`. [#extension-category: envoy.http.original_ip_detection]
repeated .envoy.config.core.v3.TypedExtensionConfig original_ip_detection_extensions = 46;
-
internalGetOriginalIpDetectionExtensionsFieldBuilder
private com.google.protobuf.RepeatedFieldBuilder<TypedExtensionConfig,TypedExtensionConfig.Builder, internalGetOriginalIpDetectionExtensionsFieldBuilder()TypedExtensionConfigOrBuilder> -
ensureEarlyHeaderMutationExtensionsIsMutable
private void ensureEarlyHeaderMutationExtensionsIsMutable() -
getEarlyHeaderMutationExtensionsList
The configuration for the early header mutation extensions. When configured the extensions will be called before any routing, tracing, or any filter processing. Each extension will be applied in the order they are configured. If the same header is mutated by multiple extensions, then the last extension will win. [#extension-category: envoy.http.early_header_mutation]
repeated .envoy.config.core.v3.TypedExtensionConfig early_header_mutation_extensions = 52;
- Specified by:
getEarlyHeaderMutationExtensionsList
in interfaceHttpConnectionManagerOrBuilder
-
getEarlyHeaderMutationExtensionsCount
public int getEarlyHeaderMutationExtensionsCount()The configuration for the early header mutation extensions. When configured the extensions will be called before any routing, tracing, or any filter processing. Each extension will be applied in the order they are configured. If the same header is mutated by multiple extensions, then the last extension will win. [#extension-category: envoy.http.early_header_mutation]
repeated .envoy.config.core.v3.TypedExtensionConfig early_header_mutation_extensions = 52;
- Specified by:
getEarlyHeaderMutationExtensionsCount
in interfaceHttpConnectionManagerOrBuilder
-
getEarlyHeaderMutationExtensions
The configuration for the early header mutation extensions. When configured the extensions will be called before any routing, tracing, or any filter processing. Each extension will be applied in the order they are configured. If the same header is mutated by multiple extensions, then the last extension will win. [#extension-category: envoy.http.early_header_mutation]
repeated .envoy.config.core.v3.TypedExtensionConfig early_header_mutation_extensions = 52;
- Specified by:
getEarlyHeaderMutationExtensions
in interfaceHttpConnectionManagerOrBuilder
-
setEarlyHeaderMutationExtensions
public HttpConnectionManager.Builder setEarlyHeaderMutationExtensions(int index, TypedExtensionConfig value) The configuration for the early header mutation extensions. When configured the extensions will be called before any routing, tracing, or any filter processing. Each extension will be applied in the order they are configured. If the same header is mutated by multiple extensions, then the last extension will win. [#extension-category: envoy.http.early_header_mutation]
repeated .envoy.config.core.v3.TypedExtensionConfig early_header_mutation_extensions = 52;
-
setEarlyHeaderMutationExtensions
public HttpConnectionManager.Builder setEarlyHeaderMutationExtensions(int index, TypedExtensionConfig.Builder builderForValue) The configuration for the early header mutation extensions. When configured the extensions will be called before any routing, tracing, or any filter processing. Each extension will be applied in the order they are configured. If the same header is mutated by multiple extensions, then the last extension will win. [#extension-category: envoy.http.early_header_mutation]
repeated .envoy.config.core.v3.TypedExtensionConfig early_header_mutation_extensions = 52;
-
addEarlyHeaderMutationExtensions
The configuration for the early header mutation extensions. When configured the extensions will be called before any routing, tracing, or any filter processing. Each extension will be applied in the order they are configured. If the same header is mutated by multiple extensions, then the last extension will win. [#extension-category: envoy.http.early_header_mutation]
repeated .envoy.config.core.v3.TypedExtensionConfig early_header_mutation_extensions = 52;
-
addEarlyHeaderMutationExtensions
public HttpConnectionManager.Builder addEarlyHeaderMutationExtensions(int index, TypedExtensionConfig value) The configuration for the early header mutation extensions. When configured the extensions will be called before any routing, tracing, or any filter processing. Each extension will be applied in the order they are configured. If the same header is mutated by multiple extensions, then the last extension will win. [#extension-category: envoy.http.early_header_mutation]
repeated .envoy.config.core.v3.TypedExtensionConfig early_header_mutation_extensions = 52;
-
addEarlyHeaderMutationExtensions
public HttpConnectionManager.Builder addEarlyHeaderMutationExtensions(TypedExtensionConfig.Builder builderForValue) The configuration for the early header mutation extensions. When configured the extensions will be called before any routing, tracing, or any filter processing. Each extension will be applied in the order they are configured. If the same header is mutated by multiple extensions, then the last extension will win. [#extension-category: envoy.http.early_header_mutation]
repeated .envoy.config.core.v3.TypedExtensionConfig early_header_mutation_extensions = 52;
-
addEarlyHeaderMutationExtensions
public HttpConnectionManager.Builder addEarlyHeaderMutationExtensions(int index, TypedExtensionConfig.Builder builderForValue) The configuration for the early header mutation extensions. When configured the extensions will be called before any routing, tracing, or any filter processing. Each extension will be applied in the order they are configured. If the same header is mutated by multiple extensions, then the last extension will win. [#extension-category: envoy.http.early_header_mutation]
repeated .envoy.config.core.v3.TypedExtensionConfig early_header_mutation_extensions = 52;
-
addAllEarlyHeaderMutationExtensions
public HttpConnectionManager.Builder addAllEarlyHeaderMutationExtensions(Iterable<? extends TypedExtensionConfig> values) The configuration for the early header mutation extensions. When configured the extensions will be called before any routing, tracing, or any filter processing. Each extension will be applied in the order they are configured. If the same header is mutated by multiple extensions, then the last extension will win. [#extension-category: envoy.http.early_header_mutation]
repeated .envoy.config.core.v3.TypedExtensionConfig early_header_mutation_extensions = 52;
-
clearEarlyHeaderMutationExtensions
The configuration for the early header mutation extensions. When configured the extensions will be called before any routing, tracing, or any filter processing. Each extension will be applied in the order they are configured. If the same header is mutated by multiple extensions, then the last extension will win. [#extension-category: envoy.http.early_header_mutation]
repeated .envoy.config.core.v3.TypedExtensionConfig early_header_mutation_extensions = 52;
-
removeEarlyHeaderMutationExtensions
The configuration for the early header mutation extensions. When configured the extensions will be called before any routing, tracing, or any filter processing. Each extension will be applied in the order they are configured. If the same header is mutated by multiple extensions, then the last extension will win. [#extension-category: envoy.http.early_header_mutation]
repeated .envoy.config.core.v3.TypedExtensionConfig early_header_mutation_extensions = 52;
-
getEarlyHeaderMutationExtensionsBuilder
The configuration for the early header mutation extensions. When configured the extensions will be called before any routing, tracing, or any filter processing. Each extension will be applied in the order they are configured. If the same header is mutated by multiple extensions, then the last extension will win. [#extension-category: envoy.http.early_header_mutation]
repeated .envoy.config.core.v3.TypedExtensionConfig early_header_mutation_extensions = 52;
-
getEarlyHeaderMutationExtensionsOrBuilder
The configuration for the early header mutation extensions. When configured the extensions will be called before any routing, tracing, or any filter processing. Each extension will be applied in the order they are configured. If the same header is mutated by multiple extensions, then the last extension will win. [#extension-category: envoy.http.early_header_mutation]
repeated .envoy.config.core.v3.TypedExtensionConfig early_header_mutation_extensions = 52;
- Specified by:
getEarlyHeaderMutationExtensionsOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
getEarlyHeaderMutationExtensionsOrBuilderList
public List<? extends TypedExtensionConfigOrBuilder> getEarlyHeaderMutationExtensionsOrBuilderList()The configuration for the early header mutation extensions. When configured the extensions will be called before any routing, tracing, or any filter processing. Each extension will be applied in the order they are configured. If the same header is mutated by multiple extensions, then the last extension will win. [#extension-category: envoy.http.early_header_mutation]
repeated .envoy.config.core.v3.TypedExtensionConfig early_header_mutation_extensions = 52;
- Specified by:
getEarlyHeaderMutationExtensionsOrBuilderList
in interfaceHttpConnectionManagerOrBuilder
-
addEarlyHeaderMutationExtensionsBuilder
The configuration for the early header mutation extensions. When configured the extensions will be called before any routing, tracing, or any filter processing. Each extension will be applied in the order they are configured. If the same header is mutated by multiple extensions, then the last extension will win. [#extension-category: envoy.http.early_header_mutation]
repeated .envoy.config.core.v3.TypedExtensionConfig early_header_mutation_extensions = 52;
-
addEarlyHeaderMutationExtensionsBuilder
The configuration for the early header mutation extensions. When configured the extensions will be called before any routing, tracing, or any filter processing. Each extension will be applied in the order they are configured. If the same header is mutated by multiple extensions, then the last extension will win. [#extension-category: envoy.http.early_header_mutation]
repeated .envoy.config.core.v3.TypedExtensionConfig early_header_mutation_extensions = 52;
-
getEarlyHeaderMutationExtensionsBuilderList
The configuration for the early header mutation extensions. When configured the extensions will be called before any routing, tracing, or any filter processing. Each extension will be applied in the order they are configured. If the same header is mutated by multiple extensions, then the last extension will win. [#extension-category: envoy.http.early_header_mutation]
repeated .envoy.config.core.v3.TypedExtensionConfig early_header_mutation_extensions = 52;
-
internalGetEarlyHeaderMutationExtensionsFieldBuilder
private com.google.protobuf.RepeatedFieldBuilder<TypedExtensionConfig,TypedExtensionConfig.Builder, internalGetEarlyHeaderMutationExtensionsFieldBuilder()TypedExtensionConfigOrBuilder> -
hasInternalAddressConfig
public boolean hasInternalAddressConfig()Configures what network addresses are considered internal for stats and header sanitation purposes. If unspecified, only RFC1918 IP addresses will be considered internal. See the documentation for :ref:`config_http_conn_man_headers_x-envoy-internal` for more information about internal/external addresses.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.InternalAddressConfig internal_address_config = 25;
- Specified by:
hasInternalAddressConfig
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the internalAddressConfig field is set.
-
getInternalAddressConfig
Configures what network addresses are considered internal for stats and header sanitation purposes. If unspecified, only RFC1918 IP addresses will be considered internal. See the documentation for :ref:`config_http_conn_man_headers_x-envoy-internal` for more information about internal/external addresses.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.InternalAddressConfig internal_address_config = 25;
- Specified by:
getInternalAddressConfig
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The internalAddressConfig.
-
setInternalAddressConfig
public HttpConnectionManager.Builder setInternalAddressConfig(HttpConnectionManager.InternalAddressConfig value) Configures what network addresses are considered internal for stats and header sanitation purposes. If unspecified, only RFC1918 IP addresses will be considered internal. See the documentation for :ref:`config_http_conn_man_headers_x-envoy-internal` for more information about internal/external addresses.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.InternalAddressConfig internal_address_config = 25;
-
setInternalAddressConfig
public HttpConnectionManager.Builder setInternalAddressConfig(HttpConnectionManager.InternalAddressConfig.Builder builderForValue) Configures what network addresses are considered internal for stats and header sanitation purposes. If unspecified, only RFC1918 IP addresses will be considered internal. See the documentation for :ref:`config_http_conn_man_headers_x-envoy-internal` for more information about internal/external addresses.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.InternalAddressConfig internal_address_config = 25;
-
mergeInternalAddressConfig
public HttpConnectionManager.Builder mergeInternalAddressConfig(HttpConnectionManager.InternalAddressConfig value) Configures what network addresses are considered internal for stats and header sanitation purposes. If unspecified, only RFC1918 IP addresses will be considered internal. See the documentation for :ref:`config_http_conn_man_headers_x-envoy-internal` for more information about internal/external addresses.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.InternalAddressConfig internal_address_config = 25;
-
clearInternalAddressConfig
Configures what network addresses are considered internal for stats and header sanitation purposes. If unspecified, only RFC1918 IP addresses will be considered internal. See the documentation for :ref:`config_http_conn_man_headers_x-envoy-internal` for more information about internal/external addresses.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.InternalAddressConfig internal_address_config = 25;
-
getInternalAddressConfigBuilder
Configures what network addresses are considered internal for stats and header sanitation purposes. If unspecified, only RFC1918 IP addresses will be considered internal. See the documentation for :ref:`config_http_conn_man_headers_x-envoy-internal` for more information about internal/external addresses.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.InternalAddressConfig internal_address_config = 25;
-
getInternalAddressConfigOrBuilder
Configures what network addresses are considered internal for stats and header sanitation purposes. If unspecified, only RFC1918 IP addresses will be considered internal. See the documentation for :ref:`config_http_conn_man_headers_x-envoy-internal` for more information about internal/external addresses.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.InternalAddressConfig internal_address_config = 25;
- Specified by:
getInternalAddressConfigOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetInternalAddressConfigFieldBuilder
private com.google.protobuf.SingleFieldBuilder<HttpConnectionManager.InternalAddressConfig,HttpConnectionManager.InternalAddressConfig.Builder, internalGetInternalAddressConfigFieldBuilder()HttpConnectionManager.InternalAddressConfigOrBuilder> Configures what network addresses are considered internal for stats and header sanitation purposes. If unspecified, only RFC1918 IP addresses will be considered internal. See the documentation for :ref:`config_http_conn_man_headers_x-envoy-internal` for more information about internal/external addresses.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.InternalAddressConfig internal_address_config = 25;
-
getSkipXffAppend
public boolean getSkipXffAppend()If set, Envoy will not append the remote address to the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header. This may be used in conjunction with HTTP filters that explicitly manipulate XFF after the HTTP connection manager has mutated the request headers. While :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` will also suppress XFF addition, it has consequences for logging and other Envoy uses of the remote address, so ``skip_xff_append`` should be used when only an elision of XFF addition is intended.
bool skip_xff_append = 21;
- Specified by:
getSkipXffAppend
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The skipXffAppend.
-
setSkipXffAppend
If set, Envoy will not append the remote address to the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header. This may be used in conjunction with HTTP filters that explicitly manipulate XFF after the HTTP connection manager has mutated the request headers. While :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` will also suppress XFF addition, it has consequences for logging and other Envoy uses of the remote address, so ``skip_xff_append`` should be used when only an elision of XFF addition is intended.
bool skip_xff_append = 21;
- Parameters:
value
- The skipXffAppend to set.- Returns:
- This builder for chaining.
-
clearSkipXffAppend
If set, Envoy will not append the remote address to the :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header. This may be used in conjunction with HTTP filters that explicitly manipulate XFF after the HTTP connection manager has mutated the request headers. While :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` will also suppress XFF addition, it has consequences for logging and other Envoy uses of the remote address, so ``skip_xff_append`` should be used when only an elision of XFF addition is intended.
bool skip_xff_append = 21;
- Returns:
- This builder for chaining.
-
getVia
Via header value to append to request and response headers. If this is empty, no via header will be appended.
string via = 22 [(.validate.rules) = { ... }
- Specified by:
getVia
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The via.
-
getViaBytes
public com.google.protobuf.ByteString getViaBytes()Via header value to append to request and response headers. If this is empty, no via header will be appended.
string via = 22 [(.validate.rules) = { ... }
- Specified by:
getViaBytes
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The bytes for via.
-
setVia
Via header value to append to request and response headers. If this is empty, no via header will be appended.
string via = 22 [(.validate.rules) = { ... }
- Parameters:
value
- The via to set.- Returns:
- This builder for chaining.
-
clearVia
Via header value to append to request and response headers. If this is empty, no via header will be appended.
string via = 22 [(.validate.rules) = { ... }
- Returns:
- This builder for chaining.
-
setViaBytes
Via header value to append to request and response headers. If this is empty, no via header will be appended.
string via = 22 [(.validate.rules) = { ... }
- Parameters:
value
- The bytes for via to set.- Returns:
- This builder for chaining.
-
hasGenerateRequestId
public boolean hasGenerateRequestId()Whether the connection manager will generate the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if it does not exist. This defaults to true. Generating a random UUID4 is expensive so in high throughput scenarios where this feature is not desired it can be disabled.
.google.protobuf.BoolValue generate_request_id = 15;
- Specified by:
hasGenerateRequestId
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the generateRequestId field is set.
-
getGenerateRequestId
public com.google.protobuf.BoolValue getGenerateRequestId()Whether the connection manager will generate the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if it does not exist. This defaults to true. Generating a random UUID4 is expensive so in high throughput scenarios where this feature is not desired it can be disabled.
.google.protobuf.BoolValue generate_request_id = 15;
- Specified by:
getGenerateRequestId
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The generateRequestId.
-
setGenerateRequestId
Whether the connection manager will generate the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if it does not exist. This defaults to true. Generating a random UUID4 is expensive so in high throughput scenarios where this feature is not desired it can be disabled.
.google.protobuf.BoolValue generate_request_id = 15;
-
setGenerateRequestId
public HttpConnectionManager.Builder setGenerateRequestId(com.google.protobuf.BoolValue.Builder builderForValue) Whether the connection manager will generate the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if it does not exist. This defaults to true. Generating a random UUID4 is expensive so in high throughput scenarios where this feature is not desired it can be disabled.
.google.protobuf.BoolValue generate_request_id = 15;
-
mergeGenerateRequestId
Whether the connection manager will generate the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if it does not exist. This defaults to true. Generating a random UUID4 is expensive so in high throughput scenarios where this feature is not desired it can be disabled.
.google.protobuf.BoolValue generate_request_id = 15;
-
clearGenerateRequestId
Whether the connection manager will generate the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if it does not exist. This defaults to true. Generating a random UUID4 is expensive so in high throughput scenarios where this feature is not desired it can be disabled.
.google.protobuf.BoolValue generate_request_id = 15;
-
getGenerateRequestIdBuilder
public com.google.protobuf.BoolValue.Builder getGenerateRequestIdBuilder()Whether the connection manager will generate the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if it does not exist. This defaults to true. Generating a random UUID4 is expensive so in high throughput scenarios where this feature is not desired it can be disabled.
.google.protobuf.BoolValue generate_request_id = 15;
-
getGenerateRequestIdOrBuilder
public com.google.protobuf.BoolValueOrBuilder getGenerateRequestIdOrBuilder()Whether the connection manager will generate the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if it does not exist. This defaults to true. Generating a random UUID4 is expensive so in high throughput scenarios where this feature is not desired it can be disabled.
.google.protobuf.BoolValue generate_request_id = 15;
- Specified by:
getGenerateRequestIdOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetGenerateRequestIdFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder, internalGetGenerateRequestIdFieldBuilder()com.google.protobuf.BoolValueOrBuilder> Whether the connection manager will generate the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if it does not exist. This defaults to true. Generating a random UUID4 is expensive so in high throughput scenarios where this feature is not desired it can be disabled.
.google.protobuf.BoolValue generate_request_id = 15;
-
getPreserveExternalRequestId
public boolean getPreserveExternalRequestId()Whether the connection manager will keep the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if passed for a request that is edge (Edge request is the request from external clients to front Envoy) and not reset it, which is the current Envoy behaviour. This defaults to false.
bool preserve_external_request_id = 32;
- Specified by:
getPreserveExternalRequestId
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The preserveExternalRequestId.
-
setPreserveExternalRequestId
Whether the connection manager will keep the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if passed for a request that is edge (Edge request is the request from external clients to front Envoy) and not reset it, which is the current Envoy behaviour. This defaults to false.
bool preserve_external_request_id = 32;
- Parameters:
value
- The preserveExternalRequestId to set.- Returns:
- This builder for chaining.
-
clearPreserveExternalRequestId
Whether the connection manager will keep the :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header if passed for a request that is edge (Edge request is the request from external clients to front Envoy) and not reset it, which is the current Envoy behaviour. This defaults to false.
bool preserve_external_request_id = 32;
- Returns:
- This builder for chaining.
-
getAlwaysSetRequestIdInResponse
public boolean getAlwaysSetRequestIdInResponse()If set, Envoy will always set :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header in response. If this is false or not set, the request ID is returned in responses only if tracing is forced using :ref:`x-envoy-force-trace <config_http_conn_man_headers_x-envoy-force-trace>` header.
bool always_set_request_id_in_response = 37;
- Specified by:
getAlwaysSetRequestIdInResponse
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The alwaysSetRequestIdInResponse.
-
setAlwaysSetRequestIdInResponse
If set, Envoy will always set :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header in response. If this is false or not set, the request ID is returned in responses only if tracing is forced using :ref:`x-envoy-force-trace <config_http_conn_man_headers_x-envoy-force-trace>` header.
bool always_set_request_id_in_response = 37;
- Parameters:
value
- The alwaysSetRequestIdInResponse to set.- Returns:
- This builder for chaining.
-
clearAlwaysSetRequestIdInResponse
If set, Envoy will always set :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header in response. If this is false or not set, the request ID is returned in responses only if tracing is forced using :ref:`x-envoy-force-trace <config_http_conn_man_headers_x-envoy-force-trace>` header.
bool always_set_request_id_in_response = 37;
- Returns:
- This builder for chaining.
-
getForwardClientCertDetailsValue
public int getForwardClientCertDetailsValue()How to handle the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` (XFCC) HTTP header.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ForwardClientCertDetails forward_client_cert_details = 16 [(.validate.rules) = { ... }
- Specified by:
getForwardClientCertDetailsValue
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The enum numeric value on the wire for forwardClientCertDetails.
-
setForwardClientCertDetailsValue
How to handle the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` (XFCC) HTTP header.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ForwardClientCertDetails forward_client_cert_details = 16 [(.validate.rules) = { ... }
- Parameters:
value
- The enum numeric value on the wire for forwardClientCertDetails to set.- Returns:
- This builder for chaining.
-
getForwardClientCertDetails
How to handle the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` (XFCC) HTTP header.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ForwardClientCertDetails forward_client_cert_details = 16 [(.validate.rules) = { ... }
- Specified by:
getForwardClientCertDetails
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The forwardClientCertDetails.
-
setForwardClientCertDetails
public HttpConnectionManager.Builder setForwardClientCertDetails(HttpConnectionManager.ForwardClientCertDetails value) How to handle the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` (XFCC) HTTP header.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ForwardClientCertDetails forward_client_cert_details = 16 [(.validate.rules) = { ... }
- Parameters:
value
- The forwardClientCertDetails to set.- Returns:
- This builder for chaining.
-
clearForwardClientCertDetails
How to handle the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` (XFCC) HTTP header.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ForwardClientCertDetails forward_client_cert_details = 16 [(.validate.rules) = { ... }
- Returns:
- This builder for chaining.
-
hasSetCurrentClientCertDetails
public boolean hasSetCurrentClientCertDetails()This field is valid only when :ref:`forward_client_cert_details <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>` is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS. It specifies the fields in the client certificate to be forwarded. Note that in the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` header, ``Hash`` is always set, and ``By`` is always set when the client certificate presents the URI type Subject Alternative Name value.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.SetCurrentClientCertDetails set_current_client_cert_details = 17;
- Specified by:
hasSetCurrentClientCertDetails
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the setCurrentClientCertDetails field is set.
-
getSetCurrentClientCertDetails
This field is valid only when :ref:`forward_client_cert_details <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>` is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS. It specifies the fields in the client certificate to be forwarded. Note that in the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` header, ``Hash`` is always set, and ``By`` is always set when the client certificate presents the URI type Subject Alternative Name value.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.SetCurrentClientCertDetails set_current_client_cert_details = 17;
- Specified by:
getSetCurrentClientCertDetails
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The setCurrentClientCertDetails.
-
setSetCurrentClientCertDetails
public HttpConnectionManager.Builder setSetCurrentClientCertDetails(HttpConnectionManager.SetCurrentClientCertDetails value) This field is valid only when :ref:`forward_client_cert_details <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>` is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS. It specifies the fields in the client certificate to be forwarded. Note that in the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` header, ``Hash`` is always set, and ``By`` is always set when the client certificate presents the URI type Subject Alternative Name value.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.SetCurrentClientCertDetails set_current_client_cert_details = 17;
-
setSetCurrentClientCertDetails
public HttpConnectionManager.Builder setSetCurrentClientCertDetails(HttpConnectionManager.SetCurrentClientCertDetails.Builder builderForValue) This field is valid only when :ref:`forward_client_cert_details <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>` is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS. It specifies the fields in the client certificate to be forwarded. Note that in the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` header, ``Hash`` is always set, and ``By`` is always set when the client certificate presents the URI type Subject Alternative Name value.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.SetCurrentClientCertDetails set_current_client_cert_details = 17;
-
mergeSetCurrentClientCertDetails
public HttpConnectionManager.Builder mergeSetCurrentClientCertDetails(HttpConnectionManager.SetCurrentClientCertDetails value) This field is valid only when :ref:`forward_client_cert_details <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>` is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS. It specifies the fields in the client certificate to be forwarded. Note that in the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` header, ``Hash`` is always set, and ``By`` is always set when the client certificate presents the URI type Subject Alternative Name value.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.SetCurrentClientCertDetails set_current_client_cert_details = 17;
-
clearSetCurrentClientCertDetails
This field is valid only when :ref:`forward_client_cert_details <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>` is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS. It specifies the fields in the client certificate to be forwarded. Note that in the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` header, ``Hash`` is always set, and ``By`` is always set when the client certificate presents the URI type Subject Alternative Name value.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.SetCurrentClientCertDetails set_current_client_cert_details = 17;
-
getSetCurrentClientCertDetailsBuilder
public HttpConnectionManager.SetCurrentClientCertDetails.Builder getSetCurrentClientCertDetailsBuilder()This field is valid only when :ref:`forward_client_cert_details <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>` is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS. It specifies the fields in the client certificate to be forwarded. Note that in the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` header, ``Hash`` is always set, and ``By`` is always set when the client certificate presents the URI type Subject Alternative Name value.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.SetCurrentClientCertDetails set_current_client_cert_details = 17;
-
getSetCurrentClientCertDetailsOrBuilder
public HttpConnectionManager.SetCurrentClientCertDetailsOrBuilder getSetCurrentClientCertDetailsOrBuilder()This field is valid only when :ref:`forward_client_cert_details <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>` is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS. It specifies the fields in the client certificate to be forwarded. Note that in the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` header, ``Hash`` is always set, and ``By`` is always set when the client certificate presents the URI type Subject Alternative Name value.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.SetCurrentClientCertDetails set_current_client_cert_details = 17;
- Specified by:
getSetCurrentClientCertDetailsOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetSetCurrentClientCertDetailsFieldBuilder
private com.google.protobuf.SingleFieldBuilder<HttpConnectionManager.SetCurrentClientCertDetails,HttpConnectionManager.SetCurrentClientCertDetails.Builder, internalGetSetCurrentClientCertDetailsFieldBuilder()HttpConnectionManager.SetCurrentClientCertDetailsOrBuilder> This field is valid only when :ref:`forward_client_cert_details <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>` is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS. It specifies the fields in the client certificate to be forwarded. Note that in the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` header, ``Hash`` is always set, and ``By`` is always set when the client certificate presents the URI type Subject Alternative Name value.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.SetCurrentClientCertDetails set_current_client_cert_details = 17;
-
getProxy100Continue
public boolean getProxy100Continue()If proxy_100_continue is true, Envoy will proxy incoming "Expect: 100-continue" headers upstream, and forward "100 Continue" responses downstream. If this is false or not set, Envoy will instead strip the "Expect: 100-continue" header, and send a "100 Continue" response itself.
bool proxy_100_continue = 18;
- Specified by:
getProxy100Continue
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The proxy100Continue.
-
setProxy100Continue
If proxy_100_continue is true, Envoy will proxy incoming "Expect: 100-continue" headers upstream, and forward "100 Continue" responses downstream. If this is false or not set, Envoy will instead strip the "Expect: 100-continue" header, and send a "100 Continue" response itself.
bool proxy_100_continue = 18;
- Parameters:
value
- The proxy100Continue to set.- Returns:
- This builder for chaining.
-
clearProxy100Continue
If proxy_100_continue is true, Envoy will proxy incoming "Expect: 100-continue" headers upstream, and forward "100 Continue" responses downstream. If this is false or not set, Envoy will instead strip the "Expect: 100-continue" header, and send a "100 Continue" response itself.
bool proxy_100_continue = 18;
- Returns:
- This builder for chaining.
-
getRepresentIpv4RemoteAddressAsIpv4MappedIpv6
public boolean getRepresentIpv4RemoteAddressAsIpv4MappedIpv6()If :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` is true and represent_ipv4_remote_address_as_ipv4_mapped_ipv6 is true and the remote address is an IPv4 address, the address will be mapped to IPv6 before it is appended to ``x-forwarded-for``. This is useful for testing compatibility of upstream services that parse the header value. For example, 50.0.0.1 is represented as ::FFFF:50.0.0.1. See `IPv4-Mapped IPv6 Addresses <https://tools.ietf.org/html/rfc4291#section-2.5.5.2>`_ for details. This will also affect the :ref:`config_http_conn_man_headers_x-envoy-external-address` header. See :ref:`http_connection_manager.represent_ipv4_remote_address_as_ipv4_mapped_ipv6 <config_http_conn_man_runtime_represent_ipv4_remote_address_as_ipv4_mapped_ipv6>` for runtime control. [#not-implemented-hide:]
bool represent_ipv4_remote_address_as_ipv4_mapped_ipv6 = 20;
- Specified by:
getRepresentIpv4RemoteAddressAsIpv4MappedIpv6
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The representIpv4RemoteAddressAsIpv4MappedIpv6.
-
setRepresentIpv4RemoteAddressAsIpv4MappedIpv6
If :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` is true and represent_ipv4_remote_address_as_ipv4_mapped_ipv6 is true and the remote address is an IPv4 address, the address will be mapped to IPv6 before it is appended to ``x-forwarded-for``. This is useful for testing compatibility of upstream services that parse the header value. For example, 50.0.0.1 is represented as ::FFFF:50.0.0.1. See `IPv4-Mapped IPv6 Addresses <https://tools.ietf.org/html/rfc4291#section-2.5.5.2>`_ for details. This will also affect the :ref:`config_http_conn_man_headers_x-envoy-external-address` header. See :ref:`http_connection_manager.represent_ipv4_remote_address_as_ipv4_mapped_ipv6 <config_http_conn_man_runtime_represent_ipv4_remote_address_as_ipv4_mapped_ipv6>` for runtime control. [#not-implemented-hide:]
bool represent_ipv4_remote_address_as_ipv4_mapped_ipv6 = 20;
- Parameters:
value
- The representIpv4RemoteAddressAsIpv4MappedIpv6 to set.- Returns:
- This builder for chaining.
-
clearRepresentIpv4RemoteAddressAsIpv4MappedIpv6
If :ref:`use_remote_address <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>` is true and represent_ipv4_remote_address_as_ipv4_mapped_ipv6 is true and the remote address is an IPv4 address, the address will be mapped to IPv6 before it is appended to ``x-forwarded-for``. This is useful for testing compatibility of upstream services that parse the header value. For example, 50.0.0.1 is represented as ::FFFF:50.0.0.1. See `IPv4-Mapped IPv6 Addresses <https://tools.ietf.org/html/rfc4291#section-2.5.5.2>`_ for details. This will also affect the :ref:`config_http_conn_man_headers_x-envoy-external-address` header. See :ref:`http_connection_manager.represent_ipv4_remote_address_as_ipv4_mapped_ipv6 <config_http_conn_man_runtime_represent_ipv4_remote_address_as_ipv4_mapped_ipv6>` for runtime control. [#not-implemented-hide:]
bool represent_ipv4_remote_address_as_ipv4_mapped_ipv6 = 20;
- Returns:
- This builder for chaining.
-
ensureUpgradeConfigsIsMutable
private void ensureUpgradeConfigsIsMutable() -
getUpgradeConfigsList
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
- Specified by:
getUpgradeConfigsList
in interfaceHttpConnectionManagerOrBuilder
-
getUpgradeConfigsCount
public int getUpgradeConfigsCount()repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
- Specified by:
getUpgradeConfigsCount
in interfaceHttpConnectionManagerOrBuilder
-
getUpgradeConfigs
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
- Specified by:
getUpgradeConfigs
in interfaceHttpConnectionManagerOrBuilder
-
setUpgradeConfigs
public HttpConnectionManager.Builder setUpgradeConfigs(int index, HttpConnectionManager.UpgradeConfig value) repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
-
setUpgradeConfigs
public HttpConnectionManager.Builder setUpgradeConfigs(int index, HttpConnectionManager.UpgradeConfig.Builder builderForValue) repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
-
addUpgradeConfigs
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
-
addUpgradeConfigs
public HttpConnectionManager.Builder addUpgradeConfigs(int index, HttpConnectionManager.UpgradeConfig value) repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
-
addUpgradeConfigs
public HttpConnectionManager.Builder addUpgradeConfigs(HttpConnectionManager.UpgradeConfig.Builder builderForValue) repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
-
addUpgradeConfigs
public HttpConnectionManager.Builder addUpgradeConfigs(int index, HttpConnectionManager.UpgradeConfig.Builder builderForValue) repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
-
addAllUpgradeConfigs
public HttpConnectionManager.Builder addAllUpgradeConfigs(Iterable<? extends HttpConnectionManager.UpgradeConfig> values) repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
-
clearUpgradeConfigs
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
-
removeUpgradeConfigs
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
-
getUpgradeConfigsBuilder
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
-
getUpgradeConfigsOrBuilder
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
- Specified by:
getUpgradeConfigsOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
getUpgradeConfigsOrBuilderList
public List<? extends HttpConnectionManager.UpgradeConfigOrBuilder> getUpgradeConfigsOrBuilderList()repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
- Specified by:
getUpgradeConfigsOrBuilderList
in interfaceHttpConnectionManagerOrBuilder
-
addUpgradeConfigsBuilder
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
-
addUpgradeConfigsBuilder
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
-
getUpgradeConfigsBuilderList
repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
-
internalGetUpgradeConfigsFieldBuilder
private com.google.protobuf.RepeatedFieldBuilder<HttpConnectionManager.UpgradeConfig,HttpConnectionManager.UpgradeConfig.Builder, internalGetUpgradeConfigsFieldBuilder()HttpConnectionManager.UpgradeConfigOrBuilder> -
hasNormalizePath
public boolean hasNormalizePath()Should paths be normalized according to RFC 3986 before any processing of requests by HTTP filters or routing? This affects the upstream ``:path`` header as well. For paths that fail this check, Envoy will respond with 400 to paths that are malformed. This defaults to false currently but will default true in the future. When not specified, this value may be overridden by the runtime variable :ref:`http_connection_manager.normalize_path<config_http_conn_man_runtime_normalize_path>`. See `Normalization and Comparison <https://tools.ietf.org/html/rfc3986#section-6>`_ for details of normalization. Note that Envoy does not perform `case normalization <https://tools.ietf.org/html/rfc3986#section-6.2.2.1>`_ [#comment:TODO: This field is ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present.]
.google.protobuf.BoolValue normalize_path = 30;
- Specified by:
hasNormalizePath
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the normalizePath field is set.
-
getNormalizePath
public com.google.protobuf.BoolValue getNormalizePath()Should paths be normalized according to RFC 3986 before any processing of requests by HTTP filters or routing? This affects the upstream ``:path`` header as well. For paths that fail this check, Envoy will respond with 400 to paths that are malformed. This defaults to false currently but will default true in the future. When not specified, this value may be overridden by the runtime variable :ref:`http_connection_manager.normalize_path<config_http_conn_man_runtime_normalize_path>`. See `Normalization and Comparison <https://tools.ietf.org/html/rfc3986#section-6>`_ for details of normalization. Note that Envoy does not perform `case normalization <https://tools.ietf.org/html/rfc3986#section-6.2.2.1>`_ [#comment:TODO: This field is ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present.]
.google.protobuf.BoolValue normalize_path = 30;
- Specified by:
getNormalizePath
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The normalizePath.
-
setNormalizePath
Should paths be normalized according to RFC 3986 before any processing of requests by HTTP filters or routing? This affects the upstream ``:path`` header as well. For paths that fail this check, Envoy will respond with 400 to paths that are malformed. This defaults to false currently but will default true in the future. When not specified, this value may be overridden by the runtime variable :ref:`http_connection_manager.normalize_path<config_http_conn_man_runtime_normalize_path>`. See `Normalization and Comparison <https://tools.ietf.org/html/rfc3986#section-6>`_ for details of normalization. Note that Envoy does not perform `case normalization <https://tools.ietf.org/html/rfc3986#section-6.2.2.1>`_ [#comment:TODO: This field is ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present.]
.google.protobuf.BoolValue normalize_path = 30;
-
setNormalizePath
public HttpConnectionManager.Builder setNormalizePath(com.google.protobuf.BoolValue.Builder builderForValue) Should paths be normalized according to RFC 3986 before any processing of requests by HTTP filters or routing? This affects the upstream ``:path`` header as well. For paths that fail this check, Envoy will respond with 400 to paths that are malformed. This defaults to false currently but will default true in the future. When not specified, this value may be overridden by the runtime variable :ref:`http_connection_manager.normalize_path<config_http_conn_man_runtime_normalize_path>`. See `Normalization and Comparison <https://tools.ietf.org/html/rfc3986#section-6>`_ for details of normalization. Note that Envoy does not perform `case normalization <https://tools.ietf.org/html/rfc3986#section-6.2.2.1>`_ [#comment:TODO: This field is ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present.]
.google.protobuf.BoolValue normalize_path = 30;
-
mergeNormalizePath
Should paths be normalized according to RFC 3986 before any processing of requests by HTTP filters or routing? This affects the upstream ``:path`` header as well. For paths that fail this check, Envoy will respond with 400 to paths that are malformed. This defaults to false currently but will default true in the future. When not specified, this value may be overridden by the runtime variable :ref:`http_connection_manager.normalize_path<config_http_conn_man_runtime_normalize_path>`. See `Normalization and Comparison <https://tools.ietf.org/html/rfc3986#section-6>`_ for details of normalization. Note that Envoy does not perform `case normalization <https://tools.ietf.org/html/rfc3986#section-6.2.2.1>`_ [#comment:TODO: This field is ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present.]
.google.protobuf.BoolValue normalize_path = 30;
-
clearNormalizePath
Should paths be normalized according to RFC 3986 before any processing of requests by HTTP filters or routing? This affects the upstream ``:path`` header as well. For paths that fail this check, Envoy will respond with 400 to paths that are malformed. This defaults to false currently but will default true in the future. When not specified, this value may be overridden by the runtime variable :ref:`http_connection_manager.normalize_path<config_http_conn_man_runtime_normalize_path>`. See `Normalization and Comparison <https://tools.ietf.org/html/rfc3986#section-6>`_ for details of normalization. Note that Envoy does not perform `case normalization <https://tools.ietf.org/html/rfc3986#section-6.2.2.1>`_ [#comment:TODO: This field is ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present.]
.google.protobuf.BoolValue normalize_path = 30;
-
getNormalizePathBuilder
public com.google.protobuf.BoolValue.Builder getNormalizePathBuilder()Should paths be normalized according to RFC 3986 before any processing of requests by HTTP filters or routing? This affects the upstream ``:path`` header as well. For paths that fail this check, Envoy will respond with 400 to paths that are malformed. This defaults to false currently but will default true in the future. When not specified, this value may be overridden by the runtime variable :ref:`http_connection_manager.normalize_path<config_http_conn_man_runtime_normalize_path>`. See `Normalization and Comparison <https://tools.ietf.org/html/rfc3986#section-6>`_ for details of normalization. Note that Envoy does not perform `case normalization <https://tools.ietf.org/html/rfc3986#section-6.2.2.1>`_ [#comment:TODO: This field is ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present.]
.google.protobuf.BoolValue normalize_path = 30;
-
getNormalizePathOrBuilder
public com.google.protobuf.BoolValueOrBuilder getNormalizePathOrBuilder()Should paths be normalized according to RFC 3986 before any processing of requests by HTTP filters or routing? This affects the upstream ``:path`` header as well. For paths that fail this check, Envoy will respond with 400 to paths that are malformed. This defaults to false currently but will default true in the future. When not specified, this value may be overridden by the runtime variable :ref:`http_connection_manager.normalize_path<config_http_conn_man_runtime_normalize_path>`. See `Normalization and Comparison <https://tools.ietf.org/html/rfc3986#section-6>`_ for details of normalization. Note that Envoy does not perform `case normalization <https://tools.ietf.org/html/rfc3986#section-6.2.2.1>`_ [#comment:TODO: This field is ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present.]
.google.protobuf.BoolValue normalize_path = 30;
- Specified by:
getNormalizePathOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetNormalizePathFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder, internalGetNormalizePathFieldBuilder()com.google.protobuf.BoolValueOrBuilder> Should paths be normalized according to RFC 3986 before any processing of requests by HTTP filters or routing? This affects the upstream ``:path`` header as well. For paths that fail this check, Envoy will respond with 400 to paths that are malformed. This defaults to false currently but will default true in the future. When not specified, this value may be overridden by the runtime variable :ref:`http_connection_manager.normalize_path<config_http_conn_man_runtime_normalize_path>`. See `Normalization and Comparison <https://tools.ietf.org/html/rfc3986#section-6>`_ for details of normalization. Note that Envoy does not perform `case normalization <https://tools.ietf.org/html/rfc3986#section-6.2.2.1>`_ [#comment:TODO: This field is ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present.]
.google.protobuf.BoolValue normalize_path = 30;
-
getMergeSlashes
public boolean getMergeSlashes()Determines if adjacent slashes in the path are merged into one before any processing of requests by HTTP filters or routing. This affects the upstream ``:path`` header as well. Without setting this option, incoming requests with path ``//dir///file`` will not match against route with ``prefix`` match set to ``/dir``. Defaults to ``false``. Note that slash merging is not part of `HTTP spec <https://tools.ietf.org/html/rfc3986>`_ and is provided for convenience. [#comment:TODO: This field is ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present.]
bool merge_slashes = 33;
- Specified by:
getMergeSlashes
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The mergeSlashes.
-
setMergeSlashes
Determines if adjacent slashes in the path are merged into one before any processing of requests by HTTP filters or routing. This affects the upstream ``:path`` header as well. Without setting this option, incoming requests with path ``//dir///file`` will not match against route with ``prefix`` match set to ``/dir``. Defaults to ``false``. Note that slash merging is not part of `HTTP spec <https://tools.ietf.org/html/rfc3986>`_ and is provided for convenience. [#comment:TODO: This field is ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present.]
bool merge_slashes = 33;
- Parameters:
value
- The mergeSlashes to set.- Returns:
- This builder for chaining.
-
clearMergeSlashes
Determines if adjacent slashes in the path are merged into one before any processing of requests by HTTP filters or routing. This affects the upstream ``:path`` header as well. Without setting this option, incoming requests with path ``//dir///file`` will not match against route with ``prefix`` match set to ``/dir``. Defaults to ``false``. Note that slash merging is not part of `HTTP spec <https://tools.ietf.org/html/rfc3986>`_ and is provided for convenience. [#comment:TODO: This field is ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present.]
bool merge_slashes = 33;
- Returns:
- This builder for chaining.
-
getPathWithEscapedSlashesActionValue
public int getPathWithEscapedSlashesActionValue()Action to take when request URL path contains escaped slash sequences (%2F, %2f, %5C and %5c). The default value can be overridden by the :ref:`http_connection_manager.path_with_escaped_slashes_action<config_http_conn_man_runtime_path_with_escaped_slashes_action>` runtime variable. The :ref:`http_connection_manager.path_with_escaped_slashes_action_sampling<config_http_conn_man_runtime_path_with_escaped_slashes_action_enabled>` runtime variable can be used to apply the action to a portion of all requests. [#comment:TODO: This field is ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present.]
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.PathWithEscapedSlashesAction path_with_escaped_slashes_action = 45;
- Specified by:
getPathWithEscapedSlashesActionValue
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The enum numeric value on the wire for pathWithEscapedSlashesAction.
-
setPathWithEscapedSlashesActionValue
Action to take when request URL path contains escaped slash sequences (%2F, %2f, %5C and %5c). The default value can be overridden by the :ref:`http_connection_manager.path_with_escaped_slashes_action<config_http_conn_man_runtime_path_with_escaped_slashes_action>` runtime variable. The :ref:`http_connection_manager.path_with_escaped_slashes_action_sampling<config_http_conn_man_runtime_path_with_escaped_slashes_action_enabled>` runtime variable can be used to apply the action to a portion of all requests. [#comment:TODO: This field is ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present.]
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.PathWithEscapedSlashesAction path_with_escaped_slashes_action = 45;
- Parameters:
value
- The enum numeric value on the wire for pathWithEscapedSlashesAction to set.- Returns:
- This builder for chaining.
-
getPathWithEscapedSlashesAction
Action to take when request URL path contains escaped slash sequences (%2F, %2f, %5C and %5c). The default value can be overridden by the :ref:`http_connection_manager.path_with_escaped_slashes_action<config_http_conn_man_runtime_path_with_escaped_slashes_action>` runtime variable. The :ref:`http_connection_manager.path_with_escaped_slashes_action_sampling<config_http_conn_man_runtime_path_with_escaped_slashes_action_enabled>` runtime variable can be used to apply the action to a portion of all requests. [#comment:TODO: This field is ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present.]
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.PathWithEscapedSlashesAction path_with_escaped_slashes_action = 45;
- Specified by:
getPathWithEscapedSlashesAction
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The pathWithEscapedSlashesAction.
-
setPathWithEscapedSlashesAction
public HttpConnectionManager.Builder setPathWithEscapedSlashesAction(HttpConnectionManager.PathWithEscapedSlashesAction value) Action to take when request URL path contains escaped slash sequences (%2F, %2f, %5C and %5c). The default value can be overridden by the :ref:`http_connection_manager.path_with_escaped_slashes_action<config_http_conn_man_runtime_path_with_escaped_slashes_action>` runtime variable. The :ref:`http_connection_manager.path_with_escaped_slashes_action_sampling<config_http_conn_man_runtime_path_with_escaped_slashes_action_enabled>` runtime variable can be used to apply the action to a portion of all requests. [#comment:TODO: This field is ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present.]
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.PathWithEscapedSlashesAction path_with_escaped_slashes_action = 45;
- Parameters:
value
- The pathWithEscapedSlashesAction to set.- Returns:
- This builder for chaining.
-
clearPathWithEscapedSlashesAction
Action to take when request URL path contains escaped slash sequences (%2F, %2f, %5C and %5c). The default value can be overridden by the :ref:`http_connection_manager.path_with_escaped_slashes_action<config_http_conn_man_runtime_path_with_escaped_slashes_action>` runtime variable. The :ref:`http_connection_manager.path_with_escaped_slashes_action_sampling<config_http_conn_man_runtime_path_with_escaped_slashes_action_enabled>` runtime variable can be used to apply the action to a portion of all requests. [#comment:TODO: This field is ignored when the :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>` is present.]
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.PathWithEscapedSlashesAction path_with_escaped_slashes_action = 45;
- Returns:
- This builder for chaining.
-
hasRequestIdExtension
public boolean hasRequestIdExtension()The configuration of the request ID extension. This includes operations such as generation, validation, and associated tracing operations. If empty, the :ref:`UuidRequestIdConfig <envoy_v3_api_msg_extensions.request_id.uuid.v3.UuidRequestIdConfig>` default extension is used with default parameters. See the documentation for that extension for details on what it does. Customizing the configuration for the default extension can be achieved by configuring it explicitly here. For example, to disable trace reason packing, the following configuration can be used: .. validated-code-block:: yaml :type-name: envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension typed_config: "@type": type.googleapis.com/envoy.extensions.request_id.uuid.v3.UuidRequestIdConfig pack_trace_reason: false [#extension-category: envoy.request_id]
.envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension request_id_extension = 36;
- Specified by:
hasRequestIdExtension
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the requestIdExtension field is set.
-
getRequestIdExtension
The configuration of the request ID extension. This includes operations such as generation, validation, and associated tracing operations. If empty, the :ref:`UuidRequestIdConfig <envoy_v3_api_msg_extensions.request_id.uuid.v3.UuidRequestIdConfig>` default extension is used with default parameters. See the documentation for that extension for details on what it does. Customizing the configuration for the default extension can be achieved by configuring it explicitly here. For example, to disable trace reason packing, the following configuration can be used: .. validated-code-block:: yaml :type-name: envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension typed_config: "@type": type.googleapis.com/envoy.extensions.request_id.uuid.v3.UuidRequestIdConfig pack_trace_reason: false [#extension-category: envoy.request_id]
.envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension request_id_extension = 36;
- Specified by:
getRequestIdExtension
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The requestIdExtension.
-
setRequestIdExtension
The configuration of the request ID extension. This includes operations such as generation, validation, and associated tracing operations. If empty, the :ref:`UuidRequestIdConfig <envoy_v3_api_msg_extensions.request_id.uuid.v3.UuidRequestIdConfig>` default extension is used with default parameters. See the documentation for that extension for details on what it does. Customizing the configuration for the default extension can be achieved by configuring it explicitly here. For example, to disable trace reason packing, the following configuration can be used: .. validated-code-block:: yaml :type-name: envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension typed_config: "@type": type.googleapis.com/envoy.extensions.request_id.uuid.v3.UuidRequestIdConfig pack_trace_reason: false [#extension-category: envoy.request_id]
.envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension request_id_extension = 36;
-
setRequestIdExtension
public HttpConnectionManager.Builder setRequestIdExtension(RequestIDExtension.Builder builderForValue) The configuration of the request ID extension. This includes operations such as generation, validation, and associated tracing operations. If empty, the :ref:`UuidRequestIdConfig <envoy_v3_api_msg_extensions.request_id.uuid.v3.UuidRequestIdConfig>` default extension is used with default parameters. See the documentation for that extension for details on what it does. Customizing the configuration for the default extension can be achieved by configuring it explicitly here. For example, to disable trace reason packing, the following configuration can be used: .. validated-code-block:: yaml :type-name: envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension typed_config: "@type": type.googleapis.com/envoy.extensions.request_id.uuid.v3.UuidRequestIdConfig pack_trace_reason: false [#extension-category: envoy.request_id]
.envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension request_id_extension = 36;
-
mergeRequestIdExtension
The configuration of the request ID extension. This includes operations such as generation, validation, and associated tracing operations. If empty, the :ref:`UuidRequestIdConfig <envoy_v3_api_msg_extensions.request_id.uuid.v3.UuidRequestIdConfig>` default extension is used with default parameters. See the documentation for that extension for details on what it does. Customizing the configuration for the default extension can be achieved by configuring it explicitly here. For example, to disable trace reason packing, the following configuration can be used: .. validated-code-block:: yaml :type-name: envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension typed_config: "@type": type.googleapis.com/envoy.extensions.request_id.uuid.v3.UuidRequestIdConfig pack_trace_reason: false [#extension-category: envoy.request_id]
.envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension request_id_extension = 36;
-
clearRequestIdExtension
The configuration of the request ID extension. This includes operations such as generation, validation, and associated tracing operations. If empty, the :ref:`UuidRequestIdConfig <envoy_v3_api_msg_extensions.request_id.uuid.v3.UuidRequestIdConfig>` default extension is used with default parameters. See the documentation for that extension for details on what it does. Customizing the configuration for the default extension can be achieved by configuring it explicitly here. For example, to disable trace reason packing, the following configuration can be used: .. validated-code-block:: yaml :type-name: envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension typed_config: "@type": type.googleapis.com/envoy.extensions.request_id.uuid.v3.UuidRequestIdConfig pack_trace_reason: false [#extension-category: envoy.request_id]
.envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension request_id_extension = 36;
-
getRequestIdExtensionBuilder
The configuration of the request ID extension. This includes operations such as generation, validation, and associated tracing operations. If empty, the :ref:`UuidRequestIdConfig <envoy_v3_api_msg_extensions.request_id.uuid.v3.UuidRequestIdConfig>` default extension is used with default parameters. See the documentation for that extension for details on what it does. Customizing the configuration for the default extension can be achieved by configuring it explicitly here. For example, to disable trace reason packing, the following configuration can be used: .. validated-code-block:: yaml :type-name: envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension typed_config: "@type": type.googleapis.com/envoy.extensions.request_id.uuid.v3.UuidRequestIdConfig pack_trace_reason: false [#extension-category: envoy.request_id]
.envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension request_id_extension = 36;
-
getRequestIdExtensionOrBuilder
The configuration of the request ID extension. This includes operations such as generation, validation, and associated tracing operations. If empty, the :ref:`UuidRequestIdConfig <envoy_v3_api_msg_extensions.request_id.uuid.v3.UuidRequestIdConfig>` default extension is used with default parameters. See the documentation for that extension for details on what it does. Customizing the configuration for the default extension can be achieved by configuring it explicitly here. For example, to disable trace reason packing, the following configuration can be used: .. validated-code-block:: yaml :type-name: envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension typed_config: "@type": type.googleapis.com/envoy.extensions.request_id.uuid.v3.UuidRequestIdConfig pack_trace_reason: false [#extension-category: envoy.request_id]
.envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension request_id_extension = 36;
- Specified by:
getRequestIdExtensionOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetRequestIdExtensionFieldBuilder
private com.google.protobuf.SingleFieldBuilder<RequestIDExtension,RequestIDExtension.Builder, internalGetRequestIdExtensionFieldBuilder()RequestIDExtensionOrBuilder> The configuration of the request ID extension. This includes operations such as generation, validation, and associated tracing operations. If empty, the :ref:`UuidRequestIdConfig <envoy_v3_api_msg_extensions.request_id.uuid.v3.UuidRequestIdConfig>` default extension is used with default parameters. See the documentation for that extension for details on what it does. Customizing the configuration for the default extension can be achieved by configuring it explicitly here. For example, to disable trace reason packing, the following configuration can be used: .. validated-code-block:: yaml :type-name: envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension typed_config: "@type": type.googleapis.com/envoy.extensions.request_id.uuid.v3.UuidRequestIdConfig pack_trace_reason: false [#extension-category: envoy.request_id]
.envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension request_id_extension = 36;
-
hasLocalReplyConfig
public boolean hasLocalReplyConfig()The configuration to customize local reply returned by Envoy. It can customize status code, body text and response content type. If not specified, status code and text body are hard coded in Envoy, the response content type is plain text.
.envoy.extensions.filters.network.http_connection_manager.v3.LocalReplyConfig local_reply_config = 38;
- Specified by:
hasLocalReplyConfig
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the localReplyConfig field is set.
-
getLocalReplyConfig
The configuration to customize local reply returned by Envoy. It can customize status code, body text and response content type. If not specified, status code and text body are hard coded in Envoy, the response content type is plain text.
.envoy.extensions.filters.network.http_connection_manager.v3.LocalReplyConfig local_reply_config = 38;
- Specified by:
getLocalReplyConfig
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The localReplyConfig.
-
setLocalReplyConfig
The configuration to customize local reply returned by Envoy. It can customize status code, body text and response content type. If not specified, status code and text body are hard coded in Envoy, the response content type is plain text.
.envoy.extensions.filters.network.http_connection_manager.v3.LocalReplyConfig local_reply_config = 38;
-
setLocalReplyConfig
The configuration to customize local reply returned by Envoy. It can customize status code, body text and response content type. If not specified, status code and text body are hard coded in Envoy, the response content type is plain text.
.envoy.extensions.filters.network.http_connection_manager.v3.LocalReplyConfig local_reply_config = 38;
-
mergeLocalReplyConfig
The configuration to customize local reply returned by Envoy. It can customize status code, body text and response content type. If not specified, status code and text body are hard coded in Envoy, the response content type is plain text.
.envoy.extensions.filters.network.http_connection_manager.v3.LocalReplyConfig local_reply_config = 38;
-
clearLocalReplyConfig
The configuration to customize local reply returned by Envoy. It can customize status code, body text and response content type. If not specified, status code and text body are hard coded in Envoy, the response content type is plain text.
.envoy.extensions.filters.network.http_connection_manager.v3.LocalReplyConfig local_reply_config = 38;
-
getLocalReplyConfigBuilder
The configuration to customize local reply returned by Envoy. It can customize status code, body text and response content type. If not specified, status code and text body are hard coded in Envoy, the response content type is plain text.
.envoy.extensions.filters.network.http_connection_manager.v3.LocalReplyConfig local_reply_config = 38;
-
getLocalReplyConfigOrBuilder
The configuration to customize local reply returned by Envoy. It can customize status code, body text and response content type. If not specified, status code and text body are hard coded in Envoy, the response content type is plain text.
.envoy.extensions.filters.network.http_connection_manager.v3.LocalReplyConfig local_reply_config = 38;
- Specified by:
getLocalReplyConfigOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetLocalReplyConfigFieldBuilder
private com.google.protobuf.SingleFieldBuilder<LocalReplyConfig,LocalReplyConfig.Builder, internalGetLocalReplyConfigFieldBuilder()LocalReplyConfigOrBuilder> The configuration to customize local reply returned by Envoy. It can customize status code, body text and response content type. If not specified, status code and text body are hard coded in Envoy, the response content type is plain text.
.envoy.extensions.filters.network.http_connection_manager.v3.LocalReplyConfig local_reply_config = 38;
-
getStripMatchingHostPort
public boolean getStripMatchingHostPort()Determines if the port part should be removed from host/authority header before any processing of request by HTTP filters or routing. The port would be removed only if it is equal to the :ref:`listener's<envoy_v3_api_field_config.listener.v3.Listener.address>` local port. This affects the upstream host header unless the method is CONNECT in which case if no filter adds a port the original port will be restored before headers are sent upstream. Without setting this option, incoming requests with host ``example:443`` will not match against route with :ref:`domains<envoy_v3_api_field_config.route.v3.VirtualHost.domains>` match set to ``example``. Defaults to ``false``. Note that port removal is not part of `HTTP spec <https://tools.ietf.org/html/rfc3986>`_ and is provided for convenience. Only one of ``strip_matching_host_port`` or ``strip_any_host_port`` can be set.
bool strip_matching_host_port = 39 [(.udpa.annotations.field_migrate) = { ... }
- Specified by:
getStripMatchingHostPort
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The stripMatchingHostPort.
-
setStripMatchingHostPort
Determines if the port part should be removed from host/authority header before any processing of request by HTTP filters or routing. The port would be removed only if it is equal to the :ref:`listener's<envoy_v3_api_field_config.listener.v3.Listener.address>` local port. This affects the upstream host header unless the method is CONNECT in which case if no filter adds a port the original port will be restored before headers are sent upstream. Without setting this option, incoming requests with host ``example:443`` will not match against route with :ref:`domains<envoy_v3_api_field_config.route.v3.VirtualHost.domains>` match set to ``example``. Defaults to ``false``. Note that port removal is not part of `HTTP spec <https://tools.ietf.org/html/rfc3986>`_ and is provided for convenience. Only one of ``strip_matching_host_port`` or ``strip_any_host_port`` can be set.
bool strip_matching_host_port = 39 [(.udpa.annotations.field_migrate) = { ... }
- Parameters:
value
- The stripMatchingHostPort to set.- Returns:
- This builder for chaining.
-
clearStripMatchingHostPort
Determines if the port part should be removed from host/authority header before any processing of request by HTTP filters or routing. The port would be removed only if it is equal to the :ref:`listener's<envoy_v3_api_field_config.listener.v3.Listener.address>` local port. This affects the upstream host header unless the method is CONNECT in which case if no filter adds a port the original port will be restored before headers are sent upstream. Without setting this option, incoming requests with host ``example:443`` will not match against route with :ref:`domains<envoy_v3_api_field_config.route.v3.VirtualHost.domains>` match set to ``example``. Defaults to ``false``. Note that port removal is not part of `HTTP spec <https://tools.ietf.org/html/rfc3986>`_ and is provided for convenience. Only one of ``strip_matching_host_port`` or ``strip_any_host_port`` can be set.
bool strip_matching_host_port = 39 [(.udpa.annotations.field_migrate) = { ... }
- Returns:
- This builder for chaining.
-
hasStripAnyHostPort
public boolean hasStripAnyHostPort()Determines if the port part should be removed from host/authority header before any processing of request by HTTP filters or routing. This affects the upstream host header unless the method is CONNECT in which case if no filter adds a port the original port will be restored before headers are sent upstream. Without setting this option, incoming requests with host ``example:443`` will not match against route with :ref:`domains<envoy_v3_api_field_config.route.v3.VirtualHost.domains>` match set to ``example``. Defaults to ``false``. Note that port removal is not part of `HTTP spec <https://tools.ietf.org/html/rfc3986>`_ and is provided for convenience. Only one of ``strip_matching_host_port`` or ``strip_any_host_port`` can be set.
bool strip_any_host_port = 42;
- Specified by:
hasStripAnyHostPort
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the stripAnyHostPort field is set.
-
getStripAnyHostPort
public boolean getStripAnyHostPort()Determines if the port part should be removed from host/authority header before any processing of request by HTTP filters or routing. This affects the upstream host header unless the method is CONNECT in which case if no filter adds a port the original port will be restored before headers are sent upstream. Without setting this option, incoming requests with host ``example:443`` will not match against route with :ref:`domains<envoy_v3_api_field_config.route.v3.VirtualHost.domains>` match set to ``example``. Defaults to ``false``. Note that port removal is not part of `HTTP spec <https://tools.ietf.org/html/rfc3986>`_ and is provided for convenience. Only one of ``strip_matching_host_port`` or ``strip_any_host_port`` can be set.
bool strip_any_host_port = 42;
- Specified by:
getStripAnyHostPort
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The stripAnyHostPort.
-
setStripAnyHostPort
Determines if the port part should be removed from host/authority header before any processing of request by HTTP filters or routing. This affects the upstream host header unless the method is CONNECT in which case if no filter adds a port the original port will be restored before headers are sent upstream. Without setting this option, incoming requests with host ``example:443`` will not match against route with :ref:`domains<envoy_v3_api_field_config.route.v3.VirtualHost.domains>` match set to ``example``. Defaults to ``false``. Note that port removal is not part of `HTTP spec <https://tools.ietf.org/html/rfc3986>`_ and is provided for convenience. Only one of ``strip_matching_host_port`` or ``strip_any_host_port`` can be set.
bool strip_any_host_port = 42;
- Parameters:
value
- The stripAnyHostPort to set.- Returns:
- This builder for chaining.
-
clearStripAnyHostPort
Determines if the port part should be removed from host/authority header before any processing of request by HTTP filters or routing. This affects the upstream host header unless the method is CONNECT in which case if no filter adds a port the original port will be restored before headers are sent upstream. Without setting this option, incoming requests with host ``example:443`` will not match against route with :ref:`domains<envoy_v3_api_field_config.route.v3.VirtualHost.domains>` match set to ``example``. Defaults to ``false``. Note that port removal is not part of `HTTP spec <https://tools.ietf.org/html/rfc3986>`_ and is provided for convenience. Only one of ``strip_matching_host_port`` or ``strip_any_host_port`` can be set.
bool strip_any_host_port = 42;
- Returns:
- This builder for chaining.
-
hasStreamErrorOnInvalidHttpMessage
public boolean hasStreamErrorOnInvalidHttpMessage()Governs Envoy's behavior when receiving invalid HTTP from downstream. If this option is false (default), Envoy will err on the conservative side handling HTTP errors, terminating both HTTP/1.1 and HTTP/2 connections when receiving an invalid request. If this option is set to true, Envoy will be more permissive, only resetting the invalid stream in the case of HTTP/2 and leaving the connection open where possible (if the entire request is read for HTTP/1.1) In general this should be true for deployments receiving trusted traffic (L2 Envoys, company-internal mesh) and false when receiving untrusted traffic (edge deployments). If different behaviors for invalid_http_message for HTTP/1 and HTTP/2 are desired, one should use the new HTTP/1 option :ref:`override_stream_error_on_invalid_http_message <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.override_stream_error_on_invalid_http_message>` or the new HTTP/2 option :ref:`override_stream_error_on_invalid_http_message <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.override_stream_error_on_invalid_http_message>` ``not`` the deprecated but similarly named :ref:`stream_error_on_invalid_http_messaging <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.stream_error_on_invalid_http_messaging>`
.google.protobuf.BoolValue stream_error_on_invalid_http_message = 40;
- Specified by:
hasStreamErrorOnInvalidHttpMessage
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the streamErrorOnInvalidHttpMessage field is set.
-
getStreamErrorOnInvalidHttpMessage
public com.google.protobuf.BoolValue getStreamErrorOnInvalidHttpMessage()Governs Envoy's behavior when receiving invalid HTTP from downstream. If this option is false (default), Envoy will err on the conservative side handling HTTP errors, terminating both HTTP/1.1 and HTTP/2 connections when receiving an invalid request. If this option is set to true, Envoy will be more permissive, only resetting the invalid stream in the case of HTTP/2 and leaving the connection open where possible (if the entire request is read for HTTP/1.1) In general this should be true for deployments receiving trusted traffic (L2 Envoys, company-internal mesh) and false when receiving untrusted traffic (edge deployments). If different behaviors for invalid_http_message for HTTP/1 and HTTP/2 are desired, one should use the new HTTP/1 option :ref:`override_stream_error_on_invalid_http_message <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.override_stream_error_on_invalid_http_message>` or the new HTTP/2 option :ref:`override_stream_error_on_invalid_http_message <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.override_stream_error_on_invalid_http_message>` ``not`` the deprecated but similarly named :ref:`stream_error_on_invalid_http_messaging <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.stream_error_on_invalid_http_messaging>`
.google.protobuf.BoolValue stream_error_on_invalid_http_message = 40;
- Specified by:
getStreamErrorOnInvalidHttpMessage
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The streamErrorOnInvalidHttpMessage.
-
setStreamErrorOnInvalidHttpMessage
public HttpConnectionManager.Builder setStreamErrorOnInvalidHttpMessage(com.google.protobuf.BoolValue value) Governs Envoy's behavior when receiving invalid HTTP from downstream. If this option is false (default), Envoy will err on the conservative side handling HTTP errors, terminating both HTTP/1.1 and HTTP/2 connections when receiving an invalid request. If this option is set to true, Envoy will be more permissive, only resetting the invalid stream in the case of HTTP/2 and leaving the connection open where possible (if the entire request is read for HTTP/1.1) In general this should be true for deployments receiving trusted traffic (L2 Envoys, company-internal mesh) and false when receiving untrusted traffic (edge deployments). If different behaviors for invalid_http_message for HTTP/1 and HTTP/2 are desired, one should use the new HTTP/1 option :ref:`override_stream_error_on_invalid_http_message <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.override_stream_error_on_invalid_http_message>` or the new HTTP/2 option :ref:`override_stream_error_on_invalid_http_message <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.override_stream_error_on_invalid_http_message>` ``not`` the deprecated but similarly named :ref:`stream_error_on_invalid_http_messaging <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.stream_error_on_invalid_http_messaging>`
.google.protobuf.BoolValue stream_error_on_invalid_http_message = 40;
-
setStreamErrorOnInvalidHttpMessage
public HttpConnectionManager.Builder setStreamErrorOnInvalidHttpMessage(com.google.protobuf.BoolValue.Builder builderForValue) Governs Envoy's behavior when receiving invalid HTTP from downstream. If this option is false (default), Envoy will err on the conservative side handling HTTP errors, terminating both HTTP/1.1 and HTTP/2 connections when receiving an invalid request. If this option is set to true, Envoy will be more permissive, only resetting the invalid stream in the case of HTTP/2 and leaving the connection open where possible (if the entire request is read for HTTP/1.1) In general this should be true for deployments receiving trusted traffic (L2 Envoys, company-internal mesh) and false when receiving untrusted traffic (edge deployments). If different behaviors for invalid_http_message for HTTP/1 and HTTP/2 are desired, one should use the new HTTP/1 option :ref:`override_stream_error_on_invalid_http_message <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.override_stream_error_on_invalid_http_message>` or the new HTTP/2 option :ref:`override_stream_error_on_invalid_http_message <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.override_stream_error_on_invalid_http_message>` ``not`` the deprecated but similarly named :ref:`stream_error_on_invalid_http_messaging <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.stream_error_on_invalid_http_messaging>`
.google.protobuf.BoolValue stream_error_on_invalid_http_message = 40;
-
mergeStreamErrorOnInvalidHttpMessage
public HttpConnectionManager.Builder mergeStreamErrorOnInvalidHttpMessage(com.google.protobuf.BoolValue value) Governs Envoy's behavior when receiving invalid HTTP from downstream. If this option is false (default), Envoy will err on the conservative side handling HTTP errors, terminating both HTTP/1.1 and HTTP/2 connections when receiving an invalid request. If this option is set to true, Envoy will be more permissive, only resetting the invalid stream in the case of HTTP/2 and leaving the connection open where possible (if the entire request is read for HTTP/1.1) In general this should be true for deployments receiving trusted traffic (L2 Envoys, company-internal mesh) and false when receiving untrusted traffic (edge deployments). If different behaviors for invalid_http_message for HTTP/1 and HTTP/2 are desired, one should use the new HTTP/1 option :ref:`override_stream_error_on_invalid_http_message <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.override_stream_error_on_invalid_http_message>` or the new HTTP/2 option :ref:`override_stream_error_on_invalid_http_message <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.override_stream_error_on_invalid_http_message>` ``not`` the deprecated but similarly named :ref:`stream_error_on_invalid_http_messaging <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.stream_error_on_invalid_http_messaging>`
.google.protobuf.BoolValue stream_error_on_invalid_http_message = 40;
-
clearStreamErrorOnInvalidHttpMessage
Governs Envoy's behavior when receiving invalid HTTP from downstream. If this option is false (default), Envoy will err on the conservative side handling HTTP errors, terminating both HTTP/1.1 and HTTP/2 connections when receiving an invalid request. If this option is set to true, Envoy will be more permissive, only resetting the invalid stream in the case of HTTP/2 and leaving the connection open where possible (if the entire request is read for HTTP/1.1) In general this should be true for deployments receiving trusted traffic (L2 Envoys, company-internal mesh) and false when receiving untrusted traffic (edge deployments). If different behaviors for invalid_http_message for HTTP/1 and HTTP/2 are desired, one should use the new HTTP/1 option :ref:`override_stream_error_on_invalid_http_message <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.override_stream_error_on_invalid_http_message>` or the new HTTP/2 option :ref:`override_stream_error_on_invalid_http_message <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.override_stream_error_on_invalid_http_message>` ``not`` the deprecated but similarly named :ref:`stream_error_on_invalid_http_messaging <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.stream_error_on_invalid_http_messaging>`
.google.protobuf.BoolValue stream_error_on_invalid_http_message = 40;
-
getStreamErrorOnInvalidHttpMessageBuilder
public com.google.protobuf.BoolValue.Builder getStreamErrorOnInvalidHttpMessageBuilder()Governs Envoy's behavior when receiving invalid HTTP from downstream. If this option is false (default), Envoy will err on the conservative side handling HTTP errors, terminating both HTTP/1.1 and HTTP/2 connections when receiving an invalid request. If this option is set to true, Envoy will be more permissive, only resetting the invalid stream in the case of HTTP/2 and leaving the connection open where possible (if the entire request is read for HTTP/1.1) In general this should be true for deployments receiving trusted traffic (L2 Envoys, company-internal mesh) and false when receiving untrusted traffic (edge deployments). If different behaviors for invalid_http_message for HTTP/1 and HTTP/2 are desired, one should use the new HTTP/1 option :ref:`override_stream_error_on_invalid_http_message <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.override_stream_error_on_invalid_http_message>` or the new HTTP/2 option :ref:`override_stream_error_on_invalid_http_message <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.override_stream_error_on_invalid_http_message>` ``not`` the deprecated but similarly named :ref:`stream_error_on_invalid_http_messaging <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.stream_error_on_invalid_http_messaging>`
.google.protobuf.BoolValue stream_error_on_invalid_http_message = 40;
-
getStreamErrorOnInvalidHttpMessageOrBuilder
public com.google.protobuf.BoolValueOrBuilder getStreamErrorOnInvalidHttpMessageOrBuilder()Governs Envoy's behavior when receiving invalid HTTP from downstream. If this option is false (default), Envoy will err on the conservative side handling HTTP errors, terminating both HTTP/1.1 and HTTP/2 connections when receiving an invalid request. If this option is set to true, Envoy will be more permissive, only resetting the invalid stream in the case of HTTP/2 and leaving the connection open where possible (if the entire request is read for HTTP/1.1) In general this should be true for deployments receiving trusted traffic (L2 Envoys, company-internal mesh) and false when receiving untrusted traffic (edge deployments). If different behaviors for invalid_http_message for HTTP/1 and HTTP/2 are desired, one should use the new HTTP/1 option :ref:`override_stream_error_on_invalid_http_message <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.override_stream_error_on_invalid_http_message>` or the new HTTP/2 option :ref:`override_stream_error_on_invalid_http_message <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.override_stream_error_on_invalid_http_message>` ``not`` the deprecated but similarly named :ref:`stream_error_on_invalid_http_messaging <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.stream_error_on_invalid_http_messaging>`
.google.protobuf.BoolValue stream_error_on_invalid_http_message = 40;
- Specified by:
getStreamErrorOnInvalidHttpMessageOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetStreamErrorOnInvalidHttpMessageFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder, internalGetStreamErrorOnInvalidHttpMessageFieldBuilder()com.google.protobuf.BoolValueOrBuilder> Governs Envoy's behavior when receiving invalid HTTP from downstream. If this option is false (default), Envoy will err on the conservative side handling HTTP errors, terminating both HTTP/1.1 and HTTP/2 connections when receiving an invalid request. If this option is set to true, Envoy will be more permissive, only resetting the invalid stream in the case of HTTP/2 and leaving the connection open where possible (if the entire request is read for HTTP/1.1) In general this should be true for deployments receiving trusted traffic (L2 Envoys, company-internal mesh) and false when receiving untrusted traffic (edge deployments). If different behaviors for invalid_http_message for HTTP/1 and HTTP/2 are desired, one should use the new HTTP/1 option :ref:`override_stream_error_on_invalid_http_message <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.override_stream_error_on_invalid_http_message>` or the new HTTP/2 option :ref:`override_stream_error_on_invalid_http_message <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.override_stream_error_on_invalid_http_message>` ``not`` the deprecated but similarly named :ref:`stream_error_on_invalid_http_messaging <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.stream_error_on_invalid_http_messaging>`
.google.protobuf.BoolValue stream_error_on_invalid_http_message = 40;
-
hasPathNormalizationOptions
public boolean hasPathNormalizationOptions()[#not-implemented-hide:] Path normalization configuration. This includes configurations for transformations (e.g. RFC 3986 normalization or merge adjacent slashes) and the policy to apply them. The policy determines whether transformations affect the forwarded ``:path`` header. RFC 3986 path normalization is enabled by default and the default policy is that the normalized header will be forwarded. See :ref:`PathNormalizationOptions <envoy_v3_api_msg_extensions.filters.network.http_connection_manager.v3.PathNormalizationOptions>` for details.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.PathNormalizationOptions path_normalization_options = 43;
- Specified by:
hasPathNormalizationOptions
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the pathNormalizationOptions field is set.
-
getPathNormalizationOptions
[#not-implemented-hide:] Path normalization configuration. This includes configurations for transformations (e.g. RFC 3986 normalization or merge adjacent slashes) and the policy to apply them. The policy determines whether transformations affect the forwarded ``:path`` header. RFC 3986 path normalization is enabled by default and the default policy is that the normalized header will be forwarded. See :ref:`PathNormalizationOptions <envoy_v3_api_msg_extensions.filters.network.http_connection_manager.v3.PathNormalizationOptions>` for details.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.PathNormalizationOptions path_normalization_options = 43;
- Specified by:
getPathNormalizationOptions
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The pathNormalizationOptions.
-
setPathNormalizationOptions
public HttpConnectionManager.Builder setPathNormalizationOptions(HttpConnectionManager.PathNormalizationOptions value) [#not-implemented-hide:] Path normalization configuration. This includes configurations for transformations (e.g. RFC 3986 normalization or merge adjacent slashes) and the policy to apply them. The policy determines whether transformations affect the forwarded ``:path`` header. RFC 3986 path normalization is enabled by default and the default policy is that the normalized header will be forwarded. See :ref:`PathNormalizationOptions <envoy_v3_api_msg_extensions.filters.network.http_connection_manager.v3.PathNormalizationOptions>` for details.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.PathNormalizationOptions path_normalization_options = 43;
-
setPathNormalizationOptions
public HttpConnectionManager.Builder setPathNormalizationOptions(HttpConnectionManager.PathNormalizationOptions.Builder builderForValue) [#not-implemented-hide:] Path normalization configuration. This includes configurations for transformations (e.g. RFC 3986 normalization or merge adjacent slashes) and the policy to apply them. The policy determines whether transformations affect the forwarded ``:path`` header. RFC 3986 path normalization is enabled by default and the default policy is that the normalized header will be forwarded. See :ref:`PathNormalizationOptions <envoy_v3_api_msg_extensions.filters.network.http_connection_manager.v3.PathNormalizationOptions>` for details.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.PathNormalizationOptions path_normalization_options = 43;
-
mergePathNormalizationOptions
public HttpConnectionManager.Builder mergePathNormalizationOptions(HttpConnectionManager.PathNormalizationOptions value) [#not-implemented-hide:] Path normalization configuration. This includes configurations for transformations (e.g. RFC 3986 normalization or merge adjacent slashes) and the policy to apply them. The policy determines whether transformations affect the forwarded ``:path`` header. RFC 3986 path normalization is enabled by default and the default policy is that the normalized header will be forwarded. See :ref:`PathNormalizationOptions <envoy_v3_api_msg_extensions.filters.network.http_connection_manager.v3.PathNormalizationOptions>` for details.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.PathNormalizationOptions path_normalization_options = 43;
-
clearPathNormalizationOptions
[#not-implemented-hide:] Path normalization configuration. This includes configurations for transformations (e.g. RFC 3986 normalization or merge adjacent slashes) and the policy to apply them. The policy determines whether transformations affect the forwarded ``:path`` header. RFC 3986 path normalization is enabled by default and the default policy is that the normalized header will be forwarded. See :ref:`PathNormalizationOptions <envoy_v3_api_msg_extensions.filters.network.http_connection_manager.v3.PathNormalizationOptions>` for details.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.PathNormalizationOptions path_normalization_options = 43;
-
getPathNormalizationOptionsBuilder
[#not-implemented-hide:] Path normalization configuration. This includes configurations for transformations (e.g. RFC 3986 normalization or merge adjacent slashes) and the policy to apply them. The policy determines whether transformations affect the forwarded ``:path`` header. RFC 3986 path normalization is enabled by default and the default policy is that the normalized header will be forwarded. See :ref:`PathNormalizationOptions <envoy_v3_api_msg_extensions.filters.network.http_connection_manager.v3.PathNormalizationOptions>` for details.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.PathNormalizationOptions path_normalization_options = 43;
-
getPathNormalizationOptionsOrBuilder
public HttpConnectionManager.PathNormalizationOptionsOrBuilder getPathNormalizationOptionsOrBuilder()[#not-implemented-hide:] Path normalization configuration. This includes configurations for transformations (e.g. RFC 3986 normalization or merge adjacent slashes) and the policy to apply them. The policy determines whether transformations affect the forwarded ``:path`` header. RFC 3986 path normalization is enabled by default and the default policy is that the normalized header will be forwarded. See :ref:`PathNormalizationOptions <envoy_v3_api_msg_extensions.filters.network.http_connection_manager.v3.PathNormalizationOptions>` for details.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.PathNormalizationOptions path_normalization_options = 43;
- Specified by:
getPathNormalizationOptionsOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetPathNormalizationOptionsFieldBuilder
private com.google.protobuf.SingleFieldBuilder<HttpConnectionManager.PathNormalizationOptions,HttpConnectionManager.PathNormalizationOptions.Builder, internalGetPathNormalizationOptionsFieldBuilder()HttpConnectionManager.PathNormalizationOptionsOrBuilder> [#not-implemented-hide:] Path normalization configuration. This includes configurations for transformations (e.g. RFC 3986 normalization or merge adjacent slashes) and the policy to apply them. The policy determines whether transformations affect the forwarded ``:path`` header. RFC 3986 path normalization is enabled by default and the default policy is that the normalized header will be forwarded. See :ref:`PathNormalizationOptions <envoy_v3_api_msg_extensions.filters.network.http_connection_manager.v3.PathNormalizationOptions>` for details.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.PathNormalizationOptions path_normalization_options = 43;
-
getStripTrailingHostDot
public boolean getStripTrailingHostDot()Determines if trailing dot of the host should be removed from host/authority header before any processing of request by HTTP filters or routing. This affects the upstream host header. Without setting this option, incoming requests with host ``example.com.`` will not match against route with :ref:`domains<envoy_v3_api_field_config.route.v3.VirtualHost.domains>` match set to ``example.com``. Defaults to ``false``. When the incoming request contains a host/authority header that includes a port number, setting this option will strip a trailing dot, if present, from the host section, leaving the port as is (e.g. host value ``example.com.:443`` will be updated to ``example.com:443``).
bool strip_trailing_host_dot = 47;
- Specified by:
getStripTrailingHostDot
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The stripTrailingHostDot.
-
setStripTrailingHostDot
Determines if trailing dot of the host should be removed from host/authority header before any processing of request by HTTP filters or routing. This affects the upstream host header. Without setting this option, incoming requests with host ``example.com.`` will not match against route with :ref:`domains<envoy_v3_api_field_config.route.v3.VirtualHost.domains>` match set to ``example.com``. Defaults to ``false``. When the incoming request contains a host/authority header that includes a port number, setting this option will strip a trailing dot, if present, from the host section, leaving the port as is (e.g. host value ``example.com.:443`` will be updated to ``example.com:443``).
bool strip_trailing_host_dot = 47;
- Parameters:
value
- The stripTrailingHostDot to set.- Returns:
- This builder for chaining.
-
clearStripTrailingHostDot
Determines if trailing dot of the host should be removed from host/authority header before any processing of request by HTTP filters or routing. This affects the upstream host header. Without setting this option, incoming requests with host ``example.com.`` will not match against route with :ref:`domains<envoy_v3_api_field_config.route.v3.VirtualHost.domains>` match set to ``example.com``. Defaults to ``false``. When the incoming request contains a host/authority header that includes a port number, setting this option will strip a trailing dot, if present, from the host section, leaving the port as is (e.g. host value ``example.com.:443`` will be updated to ``example.com:443``).
bool strip_trailing_host_dot = 47;
- Returns:
- This builder for chaining.
-
hasProxyStatusConfig
public boolean hasProxyStatusConfig()Proxy-Status HTTP response header configuration. If this config is set, the Proxy-Status HTTP response header field is populated. By default, it is not.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ProxyStatusConfig proxy_status_config = 49;
- Specified by:
hasProxyStatusConfig
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the proxyStatusConfig field is set.
-
getProxyStatusConfig
Proxy-Status HTTP response header configuration. If this config is set, the Proxy-Status HTTP response header field is populated. By default, it is not.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ProxyStatusConfig proxy_status_config = 49;
- Specified by:
getProxyStatusConfig
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The proxyStatusConfig.
-
setProxyStatusConfig
public HttpConnectionManager.Builder setProxyStatusConfig(HttpConnectionManager.ProxyStatusConfig value) Proxy-Status HTTP response header configuration. If this config is set, the Proxy-Status HTTP response header field is populated. By default, it is not.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ProxyStatusConfig proxy_status_config = 49;
-
setProxyStatusConfig
public HttpConnectionManager.Builder setProxyStatusConfig(HttpConnectionManager.ProxyStatusConfig.Builder builderForValue) Proxy-Status HTTP response header configuration. If this config is set, the Proxy-Status HTTP response header field is populated. By default, it is not.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ProxyStatusConfig proxy_status_config = 49;
-
mergeProxyStatusConfig
public HttpConnectionManager.Builder mergeProxyStatusConfig(HttpConnectionManager.ProxyStatusConfig value) Proxy-Status HTTP response header configuration. If this config is set, the Proxy-Status HTTP response header field is populated. By default, it is not.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ProxyStatusConfig proxy_status_config = 49;
-
clearProxyStatusConfig
Proxy-Status HTTP response header configuration. If this config is set, the Proxy-Status HTTP response header field is populated. By default, it is not.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ProxyStatusConfig proxy_status_config = 49;
-
getProxyStatusConfigBuilder
Proxy-Status HTTP response header configuration. If this config is set, the Proxy-Status HTTP response header field is populated. By default, it is not.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ProxyStatusConfig proxy_status_config = 49;
-
getProxyStatusConfigOrBuilder
Proxy-Status HTTP response header configuration. If this config is set, the Proxy-Status HTTP response header field is populated. By default, it is not.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ProxyStatusConfig proxy_status_config = 49;
- Specified by:
getProxyStatusConfigOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetProxyStatusConfigFieldBuilder
private com.google.protobuf.SingleFieldBuilder<HttpConnectionManager.ProxyStatusConfig,HttpConnectionManager.ProxyStatusConfig.Builder, internalGetProxyStatusConfigFieldBuilder()HttpConnectionManager.ProxyStatusConfigOrBuilder> Proxy-Status HTTP response header configuration. If this config is set, the Proxy-Status HTTP response header field is populated. By default, it is not.
.envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.ProxyStatusConfig proxy_status_config = 49;
-
hasTypedHeaderValidationConfig
public boolean hasTypedHeaderValidationConfig()Configuration options for Header Validation (UHV). UHV is an extensible mechanism for checking validity of HTTP requests as well as providing normalization for request attributes, such as URI path. If the typed_header_validation_config is present it overrides the following options: ``normalize_path``, ``merge_slashes``, ``path_with_escaped_slashes_action`` ``http_protocol_options.allow_chunked_length``, ``common_http_protocol_options.headers_with_underscores_action``. The default UHV checks the following: #. HTTP/1 header map validity according to `RFC 7230 section 3.2<https://datatracker.ietf.org/doc/html/rfc7230#section-3.2>`_ #. Syntax of HTTP/1 request target URI and response status #. HTTP/2 header map validity according to `RFC 7540 section 8.1.2<https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2`_ #. Syntax of HTTP/2 pseudo headers #. HTTP/3 header map validity according to `RFC 9114 section 4.3 <https://www.rfc-editor.org/rfc/rfc9114.html>`_ #. Syntax of HTTP/3 pseudo headers #. Syntax of ``Content-Length`` and ``Transfer-Encoding`` #. Validation of HTTP/1 requests with both ``Content-Length`` and ``Transfer-Encoding`` headers #. Normalization of the URI path according to `Normalization and Comparison <https://datatracker.ietf.org/doc/html/rfc3986#section-6>`_ without `case normalization <https://datatracker.ietf.org/doc/html/rfc3986#section-6.2.2.1>`_ [#not-implemented-hide:] [#extension-category: envoy.http.header_validators]
.envoy.config.core.v3.TypedExtensionConfig typed_header_validation_config = 50;
- Specified by:
hasTypedHeaderValidationConfig
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the typedHeaderValidationConfig field is set.
-
getTypedHeaderValidationConfig
Configuration options for Header Validation (UHV). UHV is an extensible mechanism for checking validity of HTTP requests as well as providing normalization for request attributes, such as URI path. If the typed_header_validation_config is present it overrides the following options: ``normalize_path``, ``merge_slashes``, ``path_with_escaped_slashes_action`` ``http_protocol_options.allow_chunked_length``, ``common_http_protocol_options.headers_with_underscores_action``. The default UHV checks the following: #. HTTP/1 header map validity according to `RFC 7230 section 3.2<https://datatracker.ietf.org/doc/html/rfc7230#section-3.2>`_ #. Syntax of HTTP/1 request target URI and response status #. HTTP/2 header map validity according to `RFC 7540 section 8.1.2<https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2`_ #. Syntax of HTTP/2 pseudo headers #. HTTP/3 header map validity according to `RFC 9114 section 4.3 <https://www.rfc-editor.org/rfc/rfc9114.html>`_ #. Syntax of HTTP/3 pseudo headers #. Syntax of ``Content-Length`` and ``Transfer-Encoding`` #. Validation of HTTP/1 requests with both ``Content-Length`` and ``Transfer-Encoding`` headers #. Normalization of the URI path according to `Normalization and Comparison <https://datatracker.ietf.org/doc/html/rfc3986#section-6>`_ without `case normalization <https://datatracker.ietf.org/doc/html/rfc3986#section-6.2.2.1>`_ [#not-implemented-hide:] [#extension-category: envoy.http.header_validators]
.envoy.config.core.v3.TypedExtensionConfig typed_header_validation_config = 50;
- Specified by:
getTypedHeaderValidationConfig
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The typedHeaderValidationConfig.
-
setTypedHeaderValidationConfig
Configuration options for Header Validation (UHV). UHV is an extensible mechanism for checking validity of HTTP requests as well as providing normalization for request attributes, such as URI path. If the typed_header_validation_config is present it overrides the following options: ``normalize_path``, ``merge_slashes``, ``path_with_escaped_slashes_action`` ``http_protocol_options.allow_chunked_length``, ``common_http_protocol_options.headers_with_underscores_action``. The default UHV checks the following: #. HTTP/1 header map validity according to `RFC 7230 section 3.2<https://datatracker.ietf.org/doc/html/rfc7230#section-3.2>`_ #. Syntax of HTTP/1 request target URI and response status #. HTTP/2 header map validity according to `RFC 7540 section 8.1.2<https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2`_ #. Syntax of HTTP/2 pseudo headers #. HTTP/3 header map validity according to `RFC 9114 section 4.3 <https://www.rfc-editor.org/rfc/rfc9114.html>`_ #. Syntax of HTTP/3 pseudo headers #. Syntax of ``Content-Length`` and ``Transfer-Encoding`` #. Validation of HTTP/1 requests with both ``Content-Length`` and ``Transfer-Encoding`` headers #. Normalization of the URI path according to `Normalization and Comparison <https://datatracker.ietf.org/doc/html/rfc3986#section-6>`_ without `case normalization <https://datatracker.ietf.org/doc/html/rfc3986#section-6.2.2.1>`_ [#not-implemented-hide:] [#extension-category: envoy.http.header_validators]
.envoy.config.core.v3.TypedExtensionConfig typed_header_validation_config = 50;
-
setTypedHeaderValidationConfig
public HttpConnectionManager.Builder setTypedHeaderValidationConfig(TypedExtensionConfig.Builder builderForValue) Configuration options for Header Validation (UHV). UHV is an extensible mechanism for checking validity of HTTP requests as well as providing normalization for request attributes, such as URI path. If the typed_header_validation_config is present it overrides the following options: ``normalize_path``, ``merge_slashes``, ``path_with_escaped_slashes_action`` ``http_protocol_options.allow_chunked_length``, ``common_http_protocol_options.headers_with_underscores_action``. The default UHV checks the following: #. HTTP/1 header map validity according to `RFC 7230 section 3.2<https://datatracker.ietf.org/doc/html/rfc7230#section-3.2>`_ #. Syntax of HTTP/1 request target URI and response status #. HTTP/2 header map validity according to `RFC 7540 section 8.1.2<https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2`_ #. Syntax of HTTP/2 pseudo headers #. HTTP/3 header map validity according to `RFC 9114 section 4.3 <https://www.rfc-editor.org/rfc/rfc9114.html>`_ #. Syntax of HTTP/3 pseudo headers #. Syntax of ``Content-Length`` and ``Transfer-Encoding`` #. Validation of HTTP/1 requests with both ``Content-Length`` and ``Transfer-Encoding`` headers #. Normalization of the URI path according to `Normalization and Comparison <https://datatracker.ietf.org/doc/html/rfc3986#section-6>`_ without `case normalization <https://datatracker.ietf.org/doc/html/rfc3986#section-6.2.2.1>`_ [#not-implemented-hide:] [#extension-category: envoy.http.header_validators]
.envoy.config.core.v3.TypedExtensionConfig typed_header_validation_config = 50;
-
mergeTypedHeaderValidationConfig
Configuration options for Header Validation (UHV). UHV is an extensible mechanism for checking validity of HTTP requests as well as providing normalization for request attributes, such as URI path. If the typed_header_validation_config is present it overrides the following options: ``normalize_path``, ``merge_slashes``, ``path_with_escaped_slashes_action`` ``http_protocol_options.allow_chunked_length``, ``common_http_protocol_options.headers_with_underscores_action``. The default UHV checks the following: #. HTTP/1 header map validity according to `RFC 7230 section 3.2<https://datatracker.ietf.org/doc/html/rfc7230#section-3.2>`_ #. Syntax of HTTP/1 request target URI and response status #. HTTP/2 header map validity according to `RFC 7540 section 8.1.2<https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2`_ #. Syntax of HTTP/2 pseudo headers #. HTTP/3 header map validity according to `RFC 9114 section 4.3 <https://www.rfc-editor.org/rfc/rfc9114.html>`_ #. Syntax of HTTP/3 pseudo headers #. Syntax of ``Content-Length`` and ``Transfer-Encoding`` #. Validation of HTTP/1 requests with both ``Content-Length`` and ``Transfer-Encoding`` headers #. Normalization of the URI path according to `Normalization and Comparison <https://datatracker.ietf.org/doc/html/rfc3986#section-6>`_ without `case normalization <https://datatracker.ietf.org/doc/html/rfc3986#section-6.2.2.1>`_ [#not-implemented-hide:] [#extension-category: envoy.http.header_validators]
.envoy.config.core.v3.TypedExtensionConfig typed_header_validation_config = 50;
-
clearTypedHeaderValidationConfig
Configuration options for Header Validation (UHV). UHV is an extensible mechanism for checking validity of HTTP requests as well as providing normalization for request attributes, such as URI path. If the typed_header_validation_config is present it overrides the following options: ``normalize_path``, ``merge_slashes``, ``path_with_escaped_slashes_action`` ``http_protocol_options.allow_chunked_length``, ``common_http_protocol_options.headers_with_underscores_action``. The default UHV checks the following: #. HTTP/1 header map validity according to `RFC 7230 section 3.2<https://datatracker.ietf.org/doc/html/rfc7230#section-3.2>`_ #. Syntax of HTTP/1 request target URI and response status #. HTTP/2 header map validity according to `RFC 7540 section 8.1.2<https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2`_ #. Syntax of HTTP/2 pseudo headers #. HTTP/3 header map validity according to `RFC 9114 section 4.3 <https://www.rfc-editor.org/rfc/rfc9114.html>`_ #. Syntax of HTTP/3 pseudo headers #. Syntax of ``Content-Length`` and ``Transfer-Encoding`` #. Validation of HTTP/1 requests with both ``Content-Length`` and ``Transfer-Encoding`` headers #. Normalization of the URI path according to `Normalization and Comparison <https://datatracker.ietf.org/doc/html/rfc3986#section-6>`_ without `case normalization <https://datatracker.ietf.org/doc/html/rfc3986#section-6.2.2.1>`_ [#not-implemented-hide:] [#extension-category: envoy.http.header_validators]
.envoy.config.core.v3.TypedExtensionConfig typed_header_validation_config = 50;
-
getTypedHeaderValidationConfigBuilder
Configuration options for Header Validation (UHV). UHV is an extensible mechanism for checking validity of HTTP requests as well as providing normalization for request attributes, such as URI path. If the typed_header_validation_config is present it overrides the following options: ``normalize_path``, ``merge_slashes``, ``path_with_escaped_slashes_action`` ``http_protocol_options.allow_chunked_length``, ``common_http_protocol_options.headers_with_underscores_action``. The default UHV checks the following: #. HTTP/1 header map validity according to `RFC 7230 section 3.2<https://datatracker.ietf.org/doc/html/rfc7230#section-3.2>`_ #. Syntax of HTTP/1 request target URI and response status #. HTTP/2 header map validity according to `RFC 7540 section 8.1.2<https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2`_ #. Syntax of HTTP/2 pseudo headers #. HTTP/3 header map validity according to `RFC 9114 section 4.3 <https://www.rfc-editor.org/rfc/rfc9114.html>`_ #. Syntax of HTTP/3 pseudo headers #. Syntax of ``Content-Length`` and ``Transfer-Encoding`` #. Validation of HTTP/1 requests with both ``Content-Length`` and ``Transfer-Encoding`` headers #. Normalization of the URI path according to `Normalization and Comparison <https://datatracker.ietf.org/doc/html/rfc3986#section-6>`_ without `case normalization <https://datatracker.ietf.org/doc/html/rfc3986#section-6.2.2.1>`_ [#not-implemented-hide:] [#extension-category: envoy.http.header_validators]
.envoy.config.core.v3.TypedExtensionConfig typed_header_validation_config = 50;
-
getTypedHeaderValidationConfigOrBuilder
Configuration options for Header Validation (UHV). UHV is an extensible mechanism for checking validity of HTTP requests as well as providing normalization for request attributes, such as URI path. If the typed_header_validation_config is present it overrides the following options: ``normalize_path``, ``merge_slashes``, ``path_with_escaped_slashes_action`` ``http_protocol_options.allow_chunked_length``, ``common_http_protocol_options.headers_with_underscores_action``. The default UHV checks the following: #. HTTP/1 header map validity according to `RFC 7230 section 3.2<https://datatracker.ietf.org/doc/html/rfc7230#section-3.2>`_ #. Syntax of HTTP/1 request target URI and response status #. HTTP/2 header map validity according to `RFC 7540 section 8.1.2<https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2`_ #. Syntax of HTTP/2 pseudo headers #. HTTP/3 header map validity according to `RFC 9114 section 4.3 <https://www.rfc-editor.org/rfc/rfc9114.html>`_ #. Syntax of HTTP/3 pseudo headers #. Syntax of ``Content-Length`` and ``Transfer-Encoding`` #. Validation of HTTP/1 requests with both ``Content-Length`` and ``Transfer-Encoding`` headers #. Normalization of the URI path according to `Normalization and Comparison <https://datatracker.ietf.org/doc/html/rfc3986#section-6>`_ without `case normalization <https://datatracker.ietf.org/doc/html/rfc3986#section-6.2.2.1>`_ [#not-implemented-hide:] [#extension-category: envoy.http.header_validators]
.envoy.config.core.v3.TypedExtensionConfig typed_header_validation_config = 50;
- Specified by:
getTypedHeaderValidationConfigOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetTypedHeaderValidationConfigFieldBuilder
private com.google.protobuf.SingleFieldBuilder<TypedExtensionConfig,TypedExtensionConfig.Builder, internalGetTypedHeaderValidationConfigFieldBuilder()TypedExtensionConfigOrBuilder> Configuration options for Header Validation (UHV). UHV is an extensible mechanism for checking validity of HTTP requests as well as providing normalization for request attributes, such as URI path. If the typed_header_validation_config is present it overrides the following options: ``normalize_path``, ``merge_slashes``, ``path_with_escaped_slashes_action`` ``http_protocol_options.allow_chunked_length``, ``common_http_protocol_options.headers_with_underscores_action``. The default UHV checks the following: #. HTTP/1 header map validity according to `RFC 7230 section 3.2<https://datatracker.ietf.org/doc/html/rfc7230#section-3.2>`_ #. Syntax of HTTP/1 request target URI and response status #. HTTP/2 header map validity according to `RFC 7540 section 8.1.2<https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2`_ #. Syntax of HTTP/2 pseudo headers #. HTTP/3 header map validity according to `RFC 9114 section 4.3 <https://www.rfc-editor.org/rfc/rfc9114.html>`_ #. Syntax of HTTP/3 pseudo headers #. Syntax of ``Content-Length`` and ``Transfer-Encoding`` #. Validation of HTTP/1 requests with both ``Content-Length`` and ``Transfer-Encoding`` headers #. Normalization of the URI path according to `Normalization and Comparison <https://datatracker.ietf.org/doc/html/rfc3986#section-6>`_ without `case normalization <https://datatracker.ietf.org/doc/html/rfc3986#section-6.2.2.1>`_ [#not-implemented-hide:] [#extension-category: envoy.http.header_validators]
.envoy.config.core.v3.TypedExtensionConfig typed_header_validation_config = 50;
-
getAppendXForwardedPort
public boolean getAppendXForwardedPort()Append the ``x-forwarded-port`` header with the port value client used to connect to Envoy. It will be ignored if the ``x-forwarded-port`` header has been set by any trusted proxy in front of Envoy.
bool append_x_forwarded_port = 51;
- Specified by:
getAppendXForwardedPort
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The appendXForwardedPort.
-
setAppendXForwardedPort
Append the ``x-forwarded-port`` header with the port value client used to connect to Envoy. It will be ignored if the ``x-forwarded-port`` header has been set by any trusted proxy in front of Envoy.
bool append_x_forwarded_port = 51;
- Parameters:
value
- The appendXForwardedPort to set.- Returns:
- This builder for chaining.
-
clearAppendXForwardedPort
Append the ``x-forwarded-port`` header with the port value client used to connect to Envoy. It will be ignored if the ``x-forwarded-port`` header has been set by any trusted proxy in front of Envoy.
bool append_x_forwarded_port = 51;
- Returns:
- This builder for chaining.
-
getAppendLocalOverload
public boolean getAppendLocalOverload()Append the :ref:`config_http_conn_man_headers_x-envoy-local-overloaded` HTTP header in the scenario where the Overload Manager has been triggered.
bool append_local_overload = 57;
- Specified by:
getAppendLocalOverload
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The appendLocalOverload.
-
setAppendLocalOverload
Append the :ref:`config_http_conn_man_headers_x-envoy-local-overloaded` HTTP header in the scenario where the Overload Manager has been triggered.
bool append_local_overload = 57;
- Parameters:
value
- The appendLocalOverload to set.- Returns:
- This builder for chaining.
-
clearAppendLocalOverload
Append the :ref:`config_http_conn_man_headers_x-envoy-local-overloaded` HTTP header in the scenario where the Overload Manager has been triggered.
bool append_local_overload = 57;
- Returns:
- This builder for chaining.
-
hasAddProxyProtocolConnectionState
public boolean hasAddProxyProtocolConnectionState()Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state. Defaults to ``true``. This should be set to ``false`` in cases where Envoy's view of the downstream address may not correspond to the actual client address, for example, if there's another proxy in front of the Envoy.
.google.protobuf.BoolValue add_proxy_protocol_connection_state = 53;
- Specified by:
hasAddProxyProtocolConnectionState
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- Whether the addProxyProtocolConnectionState field is set.
-
getAddProxyProtocolConnectionState
public com.google.protobuf.BoolValue getAddProxyProtocolConnectionState()Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state. Defaults to ``true``. This should be set to ``false`` in cases where Envoy's view of the downstream address may not correspond to the actual client address, for example, if there's another proxy in front of the Envoy.
.google.protobuf.BoolValue add_proxy_protocol_connection_state = 53;
- Specified by:
getAddProxyProtocolConnectionState
in interfaceHttpConnectionManagerOrBuilder
- Returns:
- The addProxyProtocolConnectionState.
-
setAddProxyProtocolConnectionState
public HttpConnectionManager.Builder setAddProxyProtocolConnectionState(com.google.protobuf.BoolValue value) Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state. Defaults to ``true``. This should be set to ``false`` in cases where Envoy's view of the downstream address may not correspond to the actual client address, for example, if there's another proxy in front of the Envoy.
.google.protobuf.BoolValue add_proxy_protocol_connection_state = 53;
-
setAddProxyProtocolConnectionState
public HttpConnectionManager.Builder setAddProxyProtocolConnectionState(com.google.protobuf.BoolValue.Builder builderForValue) Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state. Defaults to ``true``. This should be set to ``false`` in cases where Envoy's view of the downstream address may not correspond to the actual client address, for example, if there's another proxy in front of the Envoy.
.google.protobuf.BoolValue add_proxy_protocol_connection_state = 53;
-
mergeAddProxyProtocolConnectionState
public HttpConnectionManager.Builder mergeAddProxyProtocolConnectionState(com.google.protobuf.BoolValue value) Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state. Defaults to ``true``. This should be set to ``false`` in cases where Envoy's view of the downstream address may not correspond to the actual client address, for example, if there's another proxy in front of the Envoy.
.google.protobuf.BoolValue add_proxy_protocol_connection_state = 53;
-
clearAddProxyProtocolConnectionState
Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state. Defaults to ``true``. This should be set to ``false`` in cases where Envoy's view of the downstream address may not correspond to the actual client address, for example, if there's another proxy in front of the Envoy.
.google.protobuf.BoolValue add_proxy_protocol_connection_state = 53;
-
getAddProxyProtocolConnectionStateBuilder
public com.google.protobuf.BoolValue.Builder getAddProxyProtocolConnectionStateBuilder()Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state. Defaults to ``true``. This should be set to ``false`` in cases where Envoy's view of the downstream address may not correspond to the actual client address, for example, if there's another proxy in front of the Envoy.
.google.protobuf.BoolValue add_proxy_protocol_connection_state = 53;
-
getAddProxyProtocolConnectionStateOrBuilder
public com.google.protobuf.BoolValueOrBuilder getAddProxyProtocolConnectionStateOrBuilder()Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state. Defaults to ``true``. This should be set to ``false`` in cases where Envoy's view of the downstream address may not correspond to the actual client address, for example, if there's another proxy in front of the Envoy.
.google.protobuf.BoolValue add_proxy_protocol_connection_state = 53;
- Specified by:
getAddProxyProtocolConnectionStateOrBuilder
in interfaceHttpConnectionManagerOrBuilder
-
internalGetAddProxyProtocolConnectionStateFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder, internalGetAddProxyProtocolConnectionStateFieldBuilder()com.google.protobuf.BoolValueOrBuilder> Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state. Defaults to ``true``. This should be set to ``false`` in cases where Envoy's view of the downstream address may not correspond to the actual client address, for example, if there's another proxy in front of the Envoy.
.google.protobuf.BoolValue add_proxy_protocol_connection_state = 53;
-