Class HttpConnectionManager.Builder

  • All Implemented Interfaces:
    com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, HttpConnectionManagerOrBuilder, java.lang.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
    • Constructor Detail

      • Builder

        private Builder()
      • Builder

        private Builder​(com.google.protobuf.AbstractMessage.BuilderParent parent)
    • Method Detail

      • getDescriptor

        public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()
      • internalGetFieldAccessorTable

        protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()
        Specified by:
        internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessage.Builder<HttpConnectionManager.Builder>
      • maybeForceBuilderInitialization

        private void maybeForceBuilderInitialization()
      • clear

        public HttpConnectionManager.Builder clear()
        Specified by:
        clear in interface com.google.protobuf.Message.Builder
        Specified by:
        clear in interface com.google.protobuf.MessageLite.Builder
        Overrides:
        clear in class com.google.protobuf.GeneratedMessage.Builder<HttpConnectionManager.Builder>
      • getDescriptorForType

        public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
        Specified by:
        getDescriptorForType in interface com.google.protobuf.Message.Builder
        Specified by:
        getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
        Overrides:
        getDescriptorForType in class com.google.protobuf.GeneratedMessage.Builder<HttpConnectionManager.Builder>
      • getDefaultInstanceForType

        public HttpConnectionManager getDefaultInstanceForType()
        Specified by:
        getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
        Specified by:
        getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder
      • build

        public HttpConnectionManager build()
        Specified by:
        build in interface com.google.protobuf.Message.Builder
        Specified by:
        build in interface com.google.protobuf.MessageLite.Builder
      • buildPartial

        public HttpConnectionManager buildPartial()
        Specified by:
        buildPartial in interface com.google.protobuf.Message.Builder
        Specified by:
        buildPartial in interface com.google.protobuf.MessageLite.Builder
      • isInitialized

        public final boolean isInitialized()
        Specified by:
        isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
        Overrides:
        isInitialized in class com.google.protobuf.GeneratedMessage.Builder<HttpConnectionManager.Builder>
      • mergeFrom

        public HttpConnectionManager.Builder mergeFrom​(com.google.protobuf.CodedInputStream input,
                                                       com.google.protobuf.ExtensionRegistryLite extensionRegistry)
                                                throws java.io.IOException
        Specified by:
        mergeFrom in interface com.google.protobuf.Message.Builder
        Specified by:
        mergeFrom in interface com.google.protobuf.MessageLite.Builder
        Overrides:
        mergeFrom in class com.google.protobuf.AbstractMessage.Builder<HttpConnectionManager.Builder>
        Throws:
        java.io.IOException
      • 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The enum numeric value on the wire for codecType.
      • setCodecTypeValue

        public HttpConnectionManager.Builder setCodecTypeValue​(int value)
         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

        public HttpConnectionManager.CodecType 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The codecType.
      • setCodecType

        public HttpConnectionManager.Builder setCodecType​(HttpConnectionManager.CodecType value)
         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

        public HttpConnectionManager.Builder 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

        public java.lang.String 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 interface HttpConnectionManagerOrBuilder
        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 interface HttpConnectionManagerOrBuilder
        Returns:
        The bytes for statPrefix.
      • setStatPrefix

        public HttpConnectionManager.Builder setStatPrefix​(java.lang.String value)
         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

        public HttpConnectionManager.Builder 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

        public HttpConnectionManager.Builder setStatPrefixBytes​(com.google.protobuf.ByteString value)
         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 interface HttpConnectionManagerOrBuilder
        Returns:
        Whether the rds field is set.
      • getRds

        public Rds 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The rds.
      • setRds

        public HttpConnectionManager.Builder setRds​(Rds value)
         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

        public HttpConnectionManager.Builder setRds​(Rds.Builder builderForValue)
         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

        public HttpConnectionManager.Builder mergeRds​(Rds value)
         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

        public HttpConnectionManager.Builder 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

        public Rds.Builder 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

        public RdsOrBuilder 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 interface HttpConnectionManagerOrBuilder
      • getRdsFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<Rds,​Rds.Builder,​RdsOrBuilder> getRdsFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        Returns:
        Whether the routeConfig field is set.
      • getRouteConfig

        public RouteConfiguration 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The routeConfig.
      • setRouteConfig

        public HttpConnectionManager.Builder setRouteConfig​(RouteConfiguration value)
         The route table for the connection manager is static and is specified in this property.
         
        .envoy.config.route.v3.RouteConfiguration route_config = 4;
      • mergeRouteConfig

        public HttpConnectionManager.Builder mergeRouteConfig​(RouteConfiguration value)
         The route table for the connection manager is static and is specified in this property.
         
        .envoy.config.route.v3.RouteConfiguration route_config = 4;
      • clearRouteConfig

        public HttpConnectionManager.Builder 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

        public RouteConfiguration.Builder getRouteConfigBuilder()
         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 interface HttpConnectionManagerOrBuilder
        Returns:
        Whether the scopedRoutes field is set.
      • getScopedRoutes

        public ScopedRoutes 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The scopedRoutes.
      • setScopedRoutes

        public HttpConnectionManager.Builder setScopedRoutes​(ScopedRoutes value)
         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

        public HttpConnectionManager.Builder 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). 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

        public HttpConnectionManager.Builder mergeScopedRoutes​(ScopedRoutes value)
         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

        public HttpConnectionManager.Builder 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

        public ScopedRoutes.Builder 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

        public ScopedRoutesOrBuilder 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 interface HttpConnectionManagerOrBuilder
      • getScopedRoutesFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<ScopedRoutes,​ScopedRoutes.Builder,​ScopedRoutesOrBuilder> getScopedRoutesFieldBuilder()
         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

        public java.util.List<HttpFilter> 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 interface HttpConnectionManagerOrBuilder
      • 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 interface HttpConnectionManagerOrBuilder
      • getHttpFilters

        public HttpFilter getHttpFilters​(int index)
         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 interface HttpConnectionManagerOrBuilder
      • setHttpFilters

        public HttpConnectionManager.Builder setHttpFilters​(int index,
                                                            HttpFilter value)
         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

        public HttpConnectionManager.Builder 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. :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

        public HttpConnectionManager.Builder addHttpFilters​(HttpFilter value)
         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

        public HttpConnectionManager.Builder addHttpFilters​(int index,
                                                            HttpFilter value)
         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

        public HttpConnectionManager.Builder addHttpFilters​(HttpFilter.Builder builderForValue)
         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

        public HttpConnectionManager.Builder 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. :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

        public HttpConnectionManager.Builder addAllHttpFilters​(java.lang.Iterable<? extends HttpFilter> values)
         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

        public HttpConnectionManager.Builder 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

        public HttpConnectionManager.Builder removeHttpFilters​(int index)
         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

        public HttpFilter.Builder getHttpFiltersBuilder​(int index)
         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

        public HttpFilterOrBuilder getHttpFiltersOrBuilder​(int index)
         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 interface HttpConnectionManagerOrBuilder
      • getHttpFiltersOrBuilderList

        public java.util.List<? extends HttpFilterOrBuilder> 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 interface HttpConnectionManagerOrBuilder
      • addHttpFiltersBuilder

        public HttpFilter.Builder 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

        public HttpFilter.Builder addHttpFiltersBuilder​(int index)
         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

        public java.util.List<HttpFilter.Builder> 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;
      • 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 interface HttpConnectionManagerOrBuilder
        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 interface HttpConnectionManagerOrBuilder
        Returns:
        The addUserAgent.
      • setAddUserAgent

        public HttpConnectionManager.Builder 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. 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

        public HttpConnectionManager.Builder 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. See the linked
         documentation for more information. Defaults to false.
         
        .google.protobuf.BoolValue add_user_agent = 6;
      • clearAddUserAgent

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
      • getAddUserAgentFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,​com.google.protobuf.BoolValue.Builder,​com.google.protobuf.BoolValueOrBuilder> getAddUserAgentFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        Returns:
        Whether the tracing field is set.
      • getTracing

        public HttpConnectionManager.Tracing 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The tracing.
      • setTracing

        public HttpConnectionManager.Builder setTracing​(HttpConnectionManager.Tracing value)
         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

        public HttpConnectionManager.Builder mergeTracing​(HttpConnectionManager.Tracing value)
         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

        public HttpConnectionManager.Builder 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

        public HttpConnectionManager.Tracing.Builder 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

        public HttpConnectionManager.TracingOrBuilder 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 interface HttpConnectionManagerOrBuilder
      • 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 interface HttpConnectionManagerOrBuilder
        Returns:
        Whether the commonHttpProtocolOptions field is set.
      • getCommonHttpProtocolOptions

        public HttpProtocolOptions 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The commonHttpProtocolOptions.
      • setCommonHttpProtocolOptions

        public HttpConnectionManager.Builder setCommonHttpProtocolOptions​(HttpProtocolOptions value)
         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

        public HttpConnectionManager.Builder mergeCommonHttpProtocolOptions​(HttpProtocolOptions value)
         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

        public HttpConnectionManager.Builder 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

        public HttpProtocolOptions.Builder 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) = { ... }
      • getCommonHttpProtocolOptionsFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<HttpProtocolOptions,​HttpProtocolOptions.Builder,​HttpProtocolOptionsOrBuilder> getCommonHttpProtocolOptionsFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        Returns:
        Whether the httpProtocolOptions field is set.
      • getHttpProtocolOptions

        public Http1ProtocolOptions 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The httpProtocolOptions.
      • setHttpProtocolOptions

        public HttpConnectionManager.Builder setHttpProtocolOptions​(Http1ProtocolOptions value)
         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

        public HttpConnectionManager.Builder mergeHttpProtocolOptions​(Http1ProtocolOptions value)
         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

        public HttpConnectionManager.Builder 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

        public Http1ProtocolOptions.Builder 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

        public Http1ProtocolOptionsOrBuilder 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 interface HttpConnectionManagerOrBuilder
      • getHttpProtocolOptionsFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<Http1ProtocolOptions,​Http1ProtocolOptions.Builder,​Http1ProtocolOptionsOrBuilder> getHttpProtocolOptionsFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        Returns:
        Whether the http2ProtocolOptions field is set.
      • getHttp2ProtocolOptions

        public Http2ProtocolOptions 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The http2ProtocolOptions.
      • setHttp2ProtocolOptions

        public HttpConnectionManager.Builder setHttp2ProtocolOptions​(Http2ProtocolOptions value)
         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

        public HttpConnectionManager.Builder mergeHttp2ProtocolOptions​(Http2ProtocolOptions value)
         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

        public HttpConnectionManager.Builder 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

        public Http2ProtocolOptions.Builder 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) = { ... }
      • getHttp2ProtocolOptionsFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<Http2ProtocolOptions,​Http2ProtocolOptions.Builder,​Http2ProtocolOptionsOrBuilder> getHttp2ProtocolOptionsFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        Returns:
        Whether the http3ProtocolOptions field is set.
      • getHttp3ProtocolOptions

        public Http3ProtocolOptions 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The http3ProtocolOptions.
      • setHttp3ProtocolOptions

        public HttpConnectionManager.Builder setHttp3ProtocolOptions​(Http3ProtocolOptions value)
         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

        public HttpConnectionManager.Builder mergeHttp3ProtocolOptions​(Http3ProtocolOptions value)
         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

        public HttpConnectionManager.Builder 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

        public Http3ProtocolOptions.Builder 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;
      • getServerName

        public java.lang.String 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 interface HttpConnectionManagerOrBuilder
        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 interface HttpConnectionManagerOrBuilder
        Returns:
        The bytes for serverName.
      • setServerName

        public HttpConnectionManager.Builder setServerName​(java.lang.String value)
         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

        public HttpConnectionManager.Builder 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

        public HttpConnectionManager.Builder setServerNameBytes​(com.google.protobuf.ByteString value)
         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 interface HttpConnectionManagerOrBuilder
        Returns:
        The enum numeric value on the wire for serverHeaderTransformation.
      • setServerHeaderTransformationValue

        public HttpConnectionManager.Builder setServerHeaderTransformationValue​(int 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 enum numeric value on the wire for serverHeaderTransformation to set.
        Returns:
        This builder for chaining.
      • getServerHeaderTransformation

        public HttpConnectionManager.ServerHeaderTransformation 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 interface HttpConnectionManagerOrBuilder
        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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
        Returns:
        Whether the schemeHeaderTransformation field is set.
      • getSchemeHeaderTransformation

        public SchemeHeaderTransformation 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 interface HttpConnectionManagerOrBuilder
        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

        public HttpConnectionManager.Builder 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

        public SchemeHeaderTransformation.Builder 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;
      • getSchemeHeaderTransformationFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<SchemeHeaderTransformation,​SchemeHeaderTransformation.Builder,​SchemeHeaderTransformationOrBuilder> getSchemeHeaderTransformationFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        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 interface HttpConnectionManagerOrBuilder
        Returns:
        The maxRequestHeadersKb.
      • setMaxRequestHeadersKb

        public HttpConnectionManager.Builder setMaxRequestHeadersKb​(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) = { ... }
      • 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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
      • getMaxRequestHeadersKbFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.UInt32Value,​com.google.protobuf.UInt32Value.Builder,​com.google.protobuf.UInt32ValueOrBuilder> getMaxRequestHeadersKbFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        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 interface HttpConnectionManagerOrBuilder
        Returns:
        The streamIdleTimeout.
      • setStreamIdleTimeout

        public HttpConnectionManager.Builder setStreamIdleTimeout​(com.google.protobuf.Duration value)
         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

        public HttpConnectionManager.Builder mergeStreamIdleTimeout​(com.google.protobuf.Duration value)
         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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
      • getStreamIdleTimeoutFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,​com.google.protobuf.Duration.Builder,​com.google.protobuf.DurationOrBuilder> getStreamIdleTimeoutFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        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 interface HttpConnectionManagerOrBuilder
        Returns:
        The requestTimeout.
      • setRequestTimeout

        public HttpConnectionManager.Builder setRequestTimeout​(com.google.protobuf.Duration value)
         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

        public HttpConnectionManager.Builder mergeRequestTimeout​(com.google.protobuf.Duration value)
         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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
      • getRequestTimeoutFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,​com.google.protobuf.Duration.Builder,​com.google.protobuf.DurationOrBuilder> getRequestTimeoutFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        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 interface HttpConnectionManagerOrBuilder
        Returns:
        The requestHeadersTimeout.
      • setRequestHeadersTimeout

        public HttpConnectionManager.Builder setRequestHeadersTimeout​(com.google.protobuf.Duration value)
         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

        public HttpConnectionManager.Builder mergeRequestHeadersTimeout​(com.google.protobuf.Duration value)
         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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
      • getRequestHeadersTimeoutFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,​com.google.protobuf.Duration.Builder,​com.google.protobuf.DurationOrBuilder> getRequestHeadersTimeoutFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        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 interface HttpConnectionManagerOrBuilder
        Returns:
        The drainTimeout.
      • setDrainTimeout

        public HttpConnectionManager.Builder 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.
         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

        public HttpConnectionManager.Builder 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.
         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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
      • getDrainTimeoutFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,​com.google.protobuf.Duration.Builder,​com.google.protobuf.DurationOrBuilder> getDrainTimeoutFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        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 interface HttpConnectionManagerOrBuilder
        Returns:
        The delayedCloseTimeout.
      • setDelayedCloseTimeout

        public HttpConnectionManager.Builder setDelayedCloseTimeout​(com.google.protobuf.Duration value)
         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

        public HttpConnectionManager.Builder mergeDelayedCloseTimeout​(com.google.protobuf.Duration value)
         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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
      • getDelayedCloseTimeoutFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,​com.google.protobuf.Duration.Builder,​com.google.protobuf.DurationOrBuilder> getDelayedCloseTimeoutFieldBuilder()
         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

        public java.util.List<AccessLog> 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 interface HttpConnectionManagerOrBuilder
      • 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 interface HttpConnectionManagerOrBuilder
      • getAccessLog

        public AccessLog getAccessLog​(int index)
         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 interface HttpConnectionManagerOrBuilder
      • setAccessLog

        public HttpConnectionManager.Builder setAccessLog​(int index,
                                                          AccessLog value)
         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

        public HttpConnectionManager.Builder setAccessLog​(int index,
                                                          AccessLog.Builder builderForValue)
         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

        public HttpConnectionManager.Builder addAccessLog​(AccessLog value)
         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

        public HttpConnectionManager.Builder addAccessLog​(int index,
                                                          AccessLog value)
         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

        public HttpConnectionManager.Builder addAccessLog​(AccessLog.Builder builderForValue)
         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

        public HttpConnectionManager.Builder addAccessLog​(int index,
                                                          AccessLog.Builder builderForValue)
         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

        public HttpConnectionManager.Builder addAllAccessLog​(java.lang.Iterable<? extends AccessLog> values)
         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

        public HttpConnectionManager.Builder 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

        public HttpConnectionManager.Builder removeAccessLog​(int index)
         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

        public AccessLog.Builder getAccessLogBuilder​(int index)
         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

        public AccessLog.Builder 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

        public AccessLog.Builder addAccessLogBuilder​(int index)
         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

        public java.util.List<AccessLog.Builder> 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;
      • hasAccessLogFlushInterval

        @Deprecated
        public boolean 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 interface HttpConnectionManagerOrBuilder
        Returns:
        Whether the accessLogFlushInterval field is set.
      • getAccessLogFlushInterval

        @Deprecated
        public com.google.protobuf.Duration 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 interface HttpConnectionManagerOrBuilder
        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
        public HttpConnectionManager.Builder 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
        public com.google.protobuf.Duration.Builder 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
        public com.google.protobuf.DurationOrBuilder 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 interface HttpConnectionManagerOrBuilder
      • getAccessLogFlushIntervalFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,​com.google.protobuf.Duration.Builder,​com.google.protobuf.DurationOrBuilder> getAccessLogFlushIntervalFieldBuilder()
         .. 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
        public boolean 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The flushAccessLogOnNewRequest.
      • setFlushAccessLogOnNewRequest

        @Deprecated
        public HttpConnectionManager.Builder setFlushAccessLogOnNewRequest​(boolean value)
        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
        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
        Returns:
        Whether the accessLogOptions field is set.
      • clearAccessLogOptions

        public HttpConnectionManager.Builder clearAccessLogOptions()
         Additional access log options for HTTP connection manager.
         
        .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions access_log_options = 56;
      • getAccessLogOptionsBuilder

        public HttpConnectionManager.HcmAccessLogOptions.Builder getAccessLogOptionsBuilder()
         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 interface HttpConnectionManagerOrBuilder
        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 interface HttpConnectionManagerOrBuilder
        Returns:
        The useRemoteAddress.
      • setUseRemoteAddress

        public HttpConnectionManager.Builder 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. 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

        public HttpConnectionManager.Builder 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. 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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
      • getUseRemoteAddressFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,​com.google.protobuf.BoolValue.Builder,​com.google.protobuf.BoolValueOrBuilder> getUseRemoteAddressFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        Returns:
        The xffNumTrustedHops.
      • setXffNumTrustedHops

        public HttpConnectionManager.Builder 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. 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

        public HttpConnectionManager.Builder 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

        public java.util.List<TypedExtensionConfig> 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 interface HttpConnectionManagerOrBuilder
      • 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 interface HttpConnectionManagerOrBuilder
      • getOriginalIpDetectionExtensions

        public TypedExtensionConfig getOriginalIpDetectionExtensions​(int index)
         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 interface HttpConnectionManagerOrBuilder
      • 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

        public HttpConnectionManager.Builder addOriginalIpDetectionExtensions​(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​(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​(java.lang.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

        public HttpConnectionManager.Builder 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

        public HttpConnectionManager.Builder removeOriginalIpDetectionExtensions​(int index)
         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

        public TypedExtensionConfig.Builder getOriginalIpDetectionExtensionsBuilder​(int index)
         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

        public TypedExtensionConfigOrBuilder getOriginalIpDetectionExtensionsOrBuilder​(int index)
         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 interface HttpConnectionManagerOrBuilder
      • getOriginalIpDetectionExtensionsOrBuilderList

        public java.util.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 interface HttpConnectionManagerOrBuilder
      • addOriginalIpDetectionExtensionsBuilder

        public TypedExtensionConfig.Builder 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

        public TypedExtensionConfig.Builder addOriginalIpDetectionExtensionsBuilder​(int index)
         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

        public java.util.List<TypedExtensionConfig.Builder> 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;
      • ensureEarlyHeaderMutationExtensionsIsMutable

        private void ensureEarlyHeaderMutationExtensionsIsMutable()
      • getEarlyHeaderMutationExtensionsList

        public java.util.List<TypedExtensionConfig> 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 interface HttpConnectionManagerOrBuilder
      • 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 interface HttpConnectionManagerOrBuilder
      • getEarlyHeaderMutationExtensions

        public TypedExtensionConfig getEarlyHeaderMutationExtensions​(int index)
         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 interface HttpConnectionManagerOrBuilder
      • 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

        public HttpConnectionManager.Builder addEarlyHeaderMutationExtensions​(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​(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​(java.lang.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

        public HttpConnectionManager.Builder 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

        public HttpConnectionManager.Builder removeEarlyHeaderMutationExtensions​(int index)
         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

        public TypedExtensionConfig.Builder getEarlyHeaderMutationExtensionsBuilder​(int index)
         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

        public TypedExtensionConfigOrBuilder getEarlyHeaderMutationExtensionsOrBuilder​(int index)
         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 interface HttpConnectionManagerOrBuilder
      • getEarlyHeaderMutationExtensionsOrBuilderList

        public java.util.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 interface HttpConnectionManagerOrBuilder
      • addEarlyHeaderMutationExtensionsBuilder

        public TypedExtensionConfig.Builder 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

        public TypedExtensionConfig.Builder addEarlyHeaderMutationExtensionsBuilder​(int index)
         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

        public java.util.List<TypedExtensionConfig.Builder> 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;
      • 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 interface HttpConnectionManagerOrBuilder
        Returns:
        Whether the internalAddressConfig field is set.
      • getInternalAddressConfig

        public HttpConnectionManager.InternalAddressConfig 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 interface HttpConnectionManagerOrBuilder
        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

        public HttpConnectionManager.Builder 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

        public HttpConnectionManager.InternalAddressConfig.Builder 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

        public HttpConnectionManager.InternalAddressConfigOrBuilder 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 interface HttpConnectionManagerOrBuilder
      • 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The skipXffAppend.
      • setSkipXffAppend

        public HttpConnectionManager.Builder 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. 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

        public HttpConnectionManager.Builder 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

        public java.lang.String 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 interface HttpConnectionManagerOrBuilder
        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 interface HttpConnectionManagerOrBuilder
        Returns:
        The bytes for via.
      • setVia

        public HttpConnectionManager.Builder setVia​(java.lang.String value)
         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

        public HttpConnectionManager.Builder 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

        public HttpConnectionManager.Builder setViaBytes​(com.google.protobuf.ByteString value)
         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 interface HttpConnectionManagerOrBuilder
        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 interface HttpConnectionManagerOrBuilder
        Returns:
        The generateRequestId.
      • setGenerateRequestId

        public HttpConnectionManager.Builder 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. 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

        public HttpConnectionManager.Builder 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. 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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
      • getGenerateRequestIdFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,​com.google.protobuf.BoolValue.Builder,​com.google.protobuf.BoolValueOrBuilder> getGenerateRequestIdFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        Returns:
        The preserveExternalRequestId.
      • setPreserveExternalRequestId

        public HttpConnectionManager.Builder 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. This defaults to false.
         
        bool preserve_external_request_id = 32;
        Parameters:
        value - The preserveExternalRequestId to set.
        Returns:
        This builder for chaining.
      • clearPreserveExternalRequestId

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The alwaysSetRequestIdInResponse.
      • setAlwaysSetRequestIdInResponse

        public HttpConnectionManager.Builder setAlwaysSetRequestIdInResponse​(boolean value)
         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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The enum numeric value on the wire for forwardClientCertDetails.
      • setForwardClientCertDetailsValue

        public HttpConnectionManager.Builder setForwardClientCertDetailsValue​(int 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 enum numeric value on the wire for forwardClientCertDetails to set.
        Returns:
        This builder for chaining.
      • 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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
        Returns:
        Whether the setCurrentClientCertDetails field is set.
      • getSetCurrentClientCertDetails

        public HttpConnectionManager.SetCurrentClientCertDetails 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 interface HttpConnectionManagerOrBuilder
        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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
      • getSetCurrentClientCertDetailsFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<HttpConnectionManager.SetCurrentClientCertDetails,​HttpConnectionManager.SetCurrentClientCertDetails.Builder,​HttpConnectionManager.SetCurrentClientCertDetailsOrBuilder> getSetCurrentClientCertDetailsFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        Returns:
        The proxy100Continue.
      • setProxy100Continue

        public HttpConnectionManager.Builder setProxy100Continue​(boolean value)
         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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The representIpv4RemoteAddressAsIpv4MappedIpv6.
      • setRepresentIpv4RemoteAddressAsIpv4MappedIpv6

        public HttpConnectionManager.Builder 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``.
         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

        public HttpConnectionManager.Builder 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()
      • getUpgradeConfigsCount

        public int getUpgradeConfigsCount()
        repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
        Specified by:
        getUpgradeConfigsCount in interface HttpConnectionManagerOrBuilder
      • clearUpgradeConfigs

        public HttpConnectionManager.Builder clearUpgradeConfigs()
        repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
      • removeUpgradeConfigs

        public HttpConnectionManager.Builder removeUpgradeConfigs​(int index)
        repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
      • getUpgradeConfigsBuilder

        public HttpConnectionManager.UpgradeConfig.Builder getUpgradeConfigsBuilder​(int index)
        repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
      • addUpgradeConfigsBuilder

        public HttpConnectionManager.UpgradeConfig.Builder addUpgradeConfigsBuilder()
        repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
      • addUpgradeConfigsBuilder

        public HttpConnectionManager.UpgradeConfig.Builder addUpgradeConfigsBuilder​(int index)
        repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
      • getUpgradeConfigsBuilderList

        public java.util.List<HttpConnectionManager.UpgradeConfig.Builder> getUpgradeConfigsBuilderList()
        repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.UpgradeConfig upgrade_configs = 23;
      • 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 interface HttpConnectionManagerOrBuilder
        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 interface HttpConnectionManagerOrBuilder
        Returns:
        The normalizePath.
      • setNormalizePath

        public HttpConnectionManager.Builder 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. 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

        public HttpConnectionManager.Builder 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. 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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
      • getNormalizePathFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,​com.google.protobuf.BoolValue.Builder,​com.google.protobuf.BoolValueOrBuilder> getNormalizePathFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        Returns:
        The mergeSlashes.
      • setMergeSlashes

        public HttpConnectionManager.Builder setMergeSlashes​(boolean value)
         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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The enum numeric value on the wire for pathWithEscapedSlashesAction.
      • setPathWithEscapedSlashesActionValue

        public HttpConnectionManager.Builder setPathWithEscapedSlashesActionValue​(int 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 enum numeric value on the wire for pathWithEscapedSlashesAction to set.
        Returns:
        This builder for chaining.
      • getPathWithEscapedSlashesAction

        public HttpConnectionManager.PathWithEscapedSlashesAction 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 interface HttpConnectionManagerOrBuilder
        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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
        Returns:
        Whether the requestIdExtension field is set.
      • getRequestIdExtension

        public RequestIDExtension 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The requestIdExtension.
      • setRequestIdExtension

        public HttpConnectionManager.Builder setRequestIdExtension​(RequestIDExtension value)
         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

        public HttpConnectionManager.Builder mergeRequestIdExtension​(RequestIDExtension value)
         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

        public HttpConnectionManager.Builder 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

        public RequestIDExtension.Builder 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

        public RequestIDExtensionOrBuilder 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 interface HttpConnectionManagerOrBuilder
      • getRequestIdExtensionFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<RequestIDExtension,​RequestIDExtension.Builder,​RequestIDExtensionOrBuilder> getRequestIdExtensionFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        Returns:
        Whether the localReplyConfig field is set.
      • getLocalReplyConfig

        public LocalReplyConfig 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The localReplyConfig.
      • setLocalReplyConfig

        public HttpConnectionManager.Builder setLocalReplyConfig​(LocalReplyConfig value)
         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

        public HttpConnectionManager.Builder setLocalReplyConfig​(LocalReplyConfig.Builder builderForValue)
         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

        public HttpConnectionManager.Builder mergeLocalReplyConfig​(LocalReplyConfig value)
         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

        public HttpConnectionManager.Builder 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

        public LocalReplyConfig.Builder 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

        public LocalReplyConfigOrBuilder 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 interface HttpConnectionManagerOrBuilder
      • getLocalReplyConfigFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<LocalReplyConfig,​LocalReplyConfig.Builder,​LocalReplyConfigOrBuilder> getLocalReplyConfigFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        Returns:
        The stripMatchingHostPort.
      • setStripMatchingHostPort

        public HttpConnectionManager.Builder 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. 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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
        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 interface HttpConnectionManagerOrBuilder
        Returns:
        The stripAnyHostPort.
      • setStripAnyHostPort

        public HttpConnectionManager.Builder 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.
         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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
        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 interface HttpConnectionManagerOrBuilder
        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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
      • getStreamErrorOnInvalidHttpMessageFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,​com.google.protobuf.BoolValue.Builder,​com.google.protobuf.BoolValueOrBuilder> getStreamErrorOnInvalidHttpMessageFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        Returns:
        Whether the pathNormalizationOptions field is set.
      • getPathNormalizationOptions

        public HttpConnectionManager.PathNormalizationOptions 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 interface HttpConnectionManagerOrBuilder
        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

        public HttpConnectionManager.Builder 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

        public HttpConnectionManager.PathNormalizationOptions.Builder 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 interface HttpConnectionManagerOrBuilder
      • getPathNormalizationOptionsFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<HttpConnectionManager.PathNormalizationOptions,​HttpConnectionManager.PathNormalizationOptions.Builder,​HttpConnectionManager.PathNormalizationOptionsOrBuilder> getPathNormalizationOptionsFieldBuilder()
         [#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 interface HttpConnectionManagerOrBuilder
        Returns:
        The stripTrailingHostDot.
      • setStripTrailingHostDot

        public HttpConnectionManager.Builder 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.
         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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
        Returns:
        Whether the proxyStatusConfig field is set.
      • getProxyStatusConfig

        public HttpConnectionManager.ProxyStatusConfig 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 interface HttpConnectionManagerOrBuilder
        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

        public HttpConnectionManager.Builder 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

        public HttpConnectionManager.ProxyStatusConfig.Builder 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;
      • 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 interface HttpConnectionManagerOrBuilder
        Returns:
        Whether the typedHeaderValidationConfig field is set.
      • getTypedHeaderValidationConfig

        public TypedExtensionConfig 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The typedHeaderValidationConfig.
      • setTypedHeaderValidationConfig

        public HttpConnectionManager.Builder setTypedHeaderValidationConfig​(TypedExtensionConfig value)
         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

        public HttpConnectionManager.Builder mergeTypedHeaderValidationConfig​(TypedExtensionConfig value)
         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

        public HttpConnectionManager.Builder 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

        public TypedExtensionConfig.Builder 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

        public TypedExtensionConfigOrBuilder 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 interface HttpConnectionManagerOrBuilder
      • getTypedHeaderValidationConfigFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<TypedExtensionConfig,​TypedExtensionConfig.Builder,​TypedExtensionConfigOrBuilder> getTypedHeaderValidationConfigFieldBuilder()
         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 interface HttpConnectionManagerOrBuilder
        Returns:
        The appendXForwardedPort.
      • setAppendXForwardedPort

        public HttpConnectionManager.Builder setAppendXForwardedPort​(boolean value)
         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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
        Returns:
        The appendLocalOverload.
      • setAppendLocalOverload

        public HttpConnectionManager.Builder 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.
         
        bool append_local_overload = 57;
        Parameters:
        value - The appendLocalOverload to set.
        Returns:
        This builder for chaining.
      • clearAppendLocalOverload

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
        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 interface HttpConnectionManagerOrBuilder
        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

        public HttpConnectionManager.Builder 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 interface HttpConnectionManagerOrBuilder
      • getAddProxyProtocolConnectionStateFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,​com.google.protobuf.BoolValue.Builder,​com.google.protobuf.BoolValueOrBuilder> getAddProxyProtocolConnectionStateFieldBuilder()
         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;