Class Listener.Builder

  • All Implemented Interfaces:
    com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, ListenerOrBuilder, java.lang.Cloneable
    Enclosing class:
    Listener

    public static final class Listener.Builder
    extends com.google.protobuf.GeneratedMessage.Builder<Listener.Builder>
    implements ListenerOrBuilder
     [#next-free-field: 36]
     
    Protobuf type envoy.config.listener.v3.Listener
    • Field Detail

      • listenerSpecifierCase_

        private int listenerSpecifierCase_
      • listenerSpecifier_

        private java.lang.Object listenerSpecifier_
      • bitField0_

        private int bitField0_
      • bitField1_

        private int bitField1_
      • name_

        private java.lang.Object name_
      • address_

        private Address address_
      • additionalAddresses_

        private java.util.List<AdditionalAddress> additionalAddresses_
      • statPrefix_

        private java.lang.Object statPrefix_
      • filterChains_

        private java.util.List<FilterChain> filterChains_
      • filterChainMatcher_

        private Matcher filterChainMatcher_
      • useOriginalDst_

        private com.google.protobuf.BoolValue useOriginalDst_
      • useOriginalDstBuilder_

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,​com.google.protobuf.BoolValue.Builder,​com.google.protobuf.BoolValueOrBuilder> useOriginalDstBuilder_
      • defaultFilterChain_

        private FilterChain defaultFilterChain_
      • perConnectionBufferLimitBytes_

        private com.google.protobuf.UInt32Value perConnectionBufferLimitBytes_
      • perConnectionBufferLimitBytesBuilder_

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.UInt32Value,​com.google.protobuf.UInt32Value.Builder,​com.google.protobuf.UInt32ValueOrBuilder> perConnectionBufferLimitBytesBuilder_
      • drainType_

        private int drainType_
      • listenerFilters_

        private java.util.List<ListenerFilter> listenerFilters_
      • listenerFiltersTimeout_

        private com.google.protobuf.Duration listenerFiltersTimeout_
      • listenerFiltersTimeoutBuilder_

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,​com.google.protobuf.Duration.Builder,​com.google.protobuf.DurationOrBuilder> listenerFiltersTimeoutBuilder_
      • continueOnListenerFiltersTimeout_

        private boolean continueOnListenerFiltersTimeout_
      • transparent_

        private com.google.protobuf.BoolValue transparent_
      • transparentBuilder_

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,​com.google.protobuf.BoolValue.Builder,​com.google.protobuf.BoolValueOrBuilder> transparentBuilder_
      • freebind_

        private com.google.protobuf.BoolValue freebind_
      • freebindBuilder_

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,​com.google.protobuf.BoolValue.Builder,​com.google.protobuf.BoolValueOrBuilder> freebindBuilder_
      • socketOptions_

        private java.util.List<SocketOption> socketOptions_
      • tcpFastOpenQueueLength_

        private com.google.protobuf.UInt32Value tcpFastOpenQueueLength_
      • tcpFastOpenQueueLengthBuilder_

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.UInt32Value,​com.google.protobuf.UInt32Value.Builder,​com.google.protobuf.UInt32ValueOrBuilder> tcpFastOpenQueueLengthBuilder_
      • trafficDirection_

        private int trafficDirection_
      • reusePort_

        private boolean reusePort_
      • enableReusePort_

        private com.google.protobuf.BoolValue enableReusePort_
      • enableReusePortBuilder_

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,​com.google.protobuf.BoolValue.Builder,​com.google.protobuf.BoolValueOrBuilder> enableReusePortBuilder_
      • accessLog_

        private java.util.List<AccessLog> accessLog_
      • tcpBacklogSize_

        private com.google.protobuf.UInt32Value tcpBacklogSize_
      • tcpBacklogSizeBuilder_

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.UInt32Value,​com.google.protobuf.UInt32Value.Builder,​com.google.protobuf.UInt32ValueOrBuilder> tcpBacklogSizeBuilder_
      • maxConnectionsToAcceptPerSocketEvent_

        private com.google.protobuf.UInt32Value maxConnectionsToAcceptPerSocketEvent_
      • maxConnectionsToAcceptPerSocketEventBuilder_

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.UInt32Value,​com.google.protobuf.UInt32Value.Builder,​com.google.protobuf.UInt32ValueOrBuilder> maxConnectionsToAcceptPerSocketEventBuilder_
      • bindToPort_

        private com.google.protobuf.BoolValue bindToPort_
      • bindToPortBuilder_

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,​com.google.protobuf.BoolValue.Builder,​com.google.protobuf.BoolValueOrBuilder> bindToPortBuilder_
      • enableMptcp_

        private boolean enableMptcp_
      • ignoreGlobalConnLimit_

        private boolean ignoreGlobalConnLimit_
      • bypassOverloadManager_

        private boolean bypassOverloadManager_
    • 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<Listener.Builder>
      • maybeForceBuilderInitialization

        private void maybeForceBuilderInitialization()
      • clear

        public Listener.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<Listener.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<Listener.Builder>
      • getDefaultInstanceForType

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

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

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

        private void buildPartialRepeatedFields​(Listener result)
      • buildPartial0

        private void buildPartial0​(Listener result)
      • buildPartial1

        private void buildPartial1​(Listener result)
      • buildPartialOneofs

        private void buildPartialOneofs​(Listener result)
      • mergeFrom

        public Listener.Builder mergeFrom​(com.google.protobuf.Message other)
        Specified by:
        mergeFrom in interface com.google.protobuf.Message.Builder
        Overrides:
        mergeFrom in class com.google.protobuf.AbstractMessage.Builder<Listener.Builder>
      • isInitialized

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

        public Listener.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<Listener.Builder>
        Throws:
        java.io.IOException
      • getName

        public java.lang.String getName()
         The unique name by which this listener is known. If no name is provided,
         Envoy will allocate an internal UUID for the listener. If the listener is to be dynamically
         updated or removed via :ref:`LDS <config_listeners_lds>` a unique name must be provided.
         
        string name = 1;
        Specified by:
        getName in interface ListenerOrBuilder
        Returns:
        The name.
      • getNameBytes

        public com.google.protobuf.ByteString getNameBytes()
         The unique name by which this listener is known. If no name is provided,
         Envoy will allocate an internal UUID for the listener. If the listener is to be dynamically
         updated or removed via :ref:`LDS <config_listeners_lds>` a unique name must be provided.
         
        string name = 1;
        Specified by:
        getNameBytes in interface ListenerOrBuilder
        Returns:
        The bytes for name.
      • setName

        public Listener.Builder setName​(java.lang.String value)
         The unique name by which this listener is known. If no name is provided,
         Envoy will allocate an internal UUID for the listener. If the listener is to be dynamically
         updated or removed via :ref:`LDS <config_listeners_lds>` a unique name must be provided.
         
        string name = 1;
        Parameters:
        value - The name to set.
        Returns:
        This builder for chaining.
      • clearName

        public Listener.Builder clearName()
         The unique name by which this listener is known. If no name is provided,
         Envoy will allocate an internal UUID for the listener. If the listener is to be dynamically
         updated or removed via :ref:`LDS <config_listeners_lds>` a unique name must be provided.
         
        string name = 1;
        Returns:
        This builder for chaining.
      • setNameBytes

        public Listener.Builder setNameBytes​(com.google.protobuf.ByteString value)
         The unique name by which this listener is known. If no name is provided,
         Envoy will allocate an internal UUID for the listener. If the listener is to be dynamically
         updated or removed via :ref:`LDS <config_listeners_lds>` a unique name must be provided.
         
        string name = 1;
        Parameters:
        value - The bytes for name to set.
        Returns:
        This builder for chaining.
      • hasAddress

        public boolean hasAddress()
         The address that the listener should listen on. In general, the address must be unique, though
         that is governed by the bind rules of the OS. E.g., multiple listeners can listen on port 0 on
         Linux as the actual port will be allocated by the OS.
         Required unless ``api_listener`` or ``listener_specifier`` is populated.
         
        .envoy.config.core.v3.Address address = 2;
        Specified by:
        hasAddress in interface ListenerOrBuilder
        Returns:
        Whether the address field is set.
      • getAddress

        public Address getAddress()
         The address that the listener should listen on. In general, the address must be unique, though
         that is governed by the bind rules of the OS. E.g., multiple listeners can listen on port 0 on
         Linux as the actual port will be allocated by the OS.
         Required unless ``api_listener`` or ``listener_specifier`` is populated.
         
        .envoy.config.core.v3.Address address = 2;
        Specified by:
        getAddress in interface ListenerOrBuilder
        Returns:
        The address.
      • setAddress

        public Listener.Builder setAddress​(Address value)
         The address that the listener should listen on. In general, the address must be unique, though
         that is governed by the bind rules of the OS. E.g., multiple listeners can listen on port 0 on
         Linux as the actual port will be allocated by the OS.
         Required unless ``api_listener`` or ``listener_specifier`` is populated.
         
        .envoy.config.core.v3.Address address = 2;
      • setAddress

        public Listener.Builder setAddress​(Address.Builder builderForValue)
         The address that the listener should listen on. In general, the address must be unique, though
         that is governed by the bind rules of the OS. E.g., multiple listeners can listen on port 0 on
         Linux as the actual port will be allocated by the OS.
         Required unless ``api_listener`` or ``listener_specifier`` is populated.
         
        .envoy.config.core.v3.Address address = 2;
      • mergeAddress

        public Listener.Builder mergeAddress​(Address value)
         The address that the listener should listen on. In general, the address must be unique, though
         that is governed by the bind rules of the OS. E.g., multiple listeners can listen on port 0 on
         Linux as the actual port will be allocated by the OS.
         Required unless ``api_listener`` or ``listener_specifier`` is populated.
         
        .envoy.config.core.v3.Address address = 2;
      • clearAddress

        public Listener.Builder clearAddress()
         The address that the listener should listen on. In general, the address must be unique, though
         that is governed by the bind rules of the OS. E.g., multiple listeners can listen on port 0 on
         Linux as the actual port will be allocated by the OS.
         Required unless ``api_listener`` or ``listener_specifier`` is populated.
         
        .envoy.config.core.v3.Address address = 2;
      • getAddressBuilder

        public Address.Builder getAddressBuilder()
         The address that the listener should listen on. In general, the address must be unique, though
         that is governed by the bind rules of the OS. E.g., multiple listeners can listen on port 0 on
         Linux as the actual port will be allocated by the OS.
         Required unless ``api_listener`` or ``listener_specifier`` is populated.
         
        .envoy.config.core.v3.Address address = 2;
      • getAddressOrBuilder

        public AddressOrBuilder getAddressOrBuilder()
         The address that the listener should listen on. In general, the address must be unique, though
         that is governed by the bind rules of the OS. E.g., multiple listeners can listen on port 0 on
         Linux as the actual port will be allocated by the OS.
         Required unless ``api_listener`` or ``listener_specifier`` is populated.
         
        .envoy.config.core.v3.Address address = 2;
        Specified by:
        getAddressOrBuilder in interface ListenerOrBuilder
      • getAddressFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<Address,​Address.Builder,​AddressOrBuilder> getAddressFieldBuilder()
         The address that the listener should listen on. In general, the address must be unique, though
         that is governed by the bind rules of the OS. E.g., multiple listeners can listen on port 0 on
         Linux as the actual port will be allocated by the OS.
         Required unless ``api_listener`` or ``listener_specifier`` is populated.
         
        .envoy.config.core.v3.Address address = 2;
      • ensureAdditionalAddressesIsMutable

        private void ensureAdditionalAddressesIsMutable()
      • getAdditionalAddressesList

        public java.util.List<AdditionalAddress> getAdditionalAddressesList()
         The additional addresses the listener should listen on. The addresses must be unique across all
         listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
         all addresses use the same protocol, and multiple internal addresses are not supported.
         
        repeated .envoy.config.listener.v3.AdditionalAddress additional_addresses = 33;
        Specified by:
        getAdditionalAddressesList in interface ListenerOrBuilder
      • getAdditionalAddressesCount

        public int getAdditionalAddressesCount()
         The additional addresses the listener should listen on. The addresses must be unique across all
         listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
         all addresses use the same protocol, and multiple internal addresses are not supported.
         
        repeated .envoy.config.listener.v3.AdditionalAddress additional_addresses = 33;
        Specified by:
        getAdditionalAddressesCount in interface ListenerOrBuilder
      • getAdditionalAddresses

        public AdditionalAddress getAdditionalAddresses​(int index)
         The additional addresses the listener should listen on. The addresses must be unique across all
         listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
         all addresses use the same protocol, and multiple internal addresses are not supported.
         
        repeated .envoy.config.listener.v3.AdditionalAddress additional_addresses = 33;
        Specified by:
        getAdditionalAddresses in interface ListenerOrBuilder
      • setAdditionalAddresses

        public Listener.Builder setAdditionalAddresses​(int index,
                                                       AdditionalAddress value)
         The additional addresses the listener should listen on. The addresses must be unique across all
         listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
         all addresses use the same protocol, and multiple internal addresses are not supported.
         
        repeated .envoy.config.listener.v3.AdditionalAddress additional_addresses = 33;
      • setAdditionalAddresses

        public Listener.Builder setAdditionalAddresses​(int index,
                                                       AdditionalAddress.Builder builderForValue)
         The additional addresses the listener should listen on. The addresses must be unique across all
         listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
         all addresses use the same protocol, and multiple internal addresses are not supported.
         
        repeated .envoy.config.listener.v3.AdditionalAddress additional_addresses = 33;
      • addAdditionalAddresses

        public Listener.Builder addAdditionalAddresses​(AdditionalAddress value)
         The additional addresses the listener should listen on. The addresses must be unique across all
         listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
         all addresses use the same protocol, and multiple internal addresses are not supported.
         
        repeated .envoy.config.listener.v3.AdditionalAddress additional_addresses = 33;
      • addAdditionalAddresses

        public Listener.Builder addAdditionalAddresses​(int index,
                                                       AdditionalAddress value)
         The additional addresses the listener should listen on. The addresses must be unique across all
         listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
         all addresses use the same protocol, and multiple internal addresses are not supported.
         
        repeated .envoy.config.listener.v3.AdditionalAddress additional_addresses = 33;
      • addAdditionalAddresses

        public Listener.Builder addAdditionalAddresses​(AdditionalAddress.Builder builderForValue)
         The additional addresses the listener should listen on. The addresses must be unique across all
         listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
         all addresses use the same protocol, and multiple internal addresses are not supported.
         
        repeated .envoy.config.listener.v3.AdditionalAddress additional_addresses = 33;
      • addAdditionalAddresses

        public Listener.Builder addAdditionalAddresses​(int index,
                                                       AdditionalAddress.Builder builderForValue)
         The additional addresses the listener should listen on. The addresses must be unique across all
         listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
         all addresses use the same protocol, and multiple internal addresses are not supported.
         
        repeated .envoy.config.listener.v3.AdditionalAddress additional_addresses = 33;
      • addAllAdditionalAddresses

        public Listener.Builder addAllAdditionalAddresses​(java.lang.Iterable<? extends AdditionalAddress> values)
         The additional addresses the listener should listen on. The addresses must be unique across all
         listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
         all addresses use the same protocol, and multiple internal addresses are not supported.
         
        repeated .envoy.config.listener.v3.AdditionalAddress additional_addresses = 33;
      • clearAdditionalAddresses

        public Listener.Builder clearAdditionalAddresses()
         The additional addresses the listener should listen on. The addresses must be unique across all
         listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
         all addresses use the same protocol, and multiple internal addresses are not supported.
         
        repeated .envoy.config.listener.v3.AdditionalAddress additional_addresses = 33;
      • removeAdditionalAddresses

        public Listener.Builder removeAdditionalAddresses​(int index)
         The additional addresses the listener should listen on. The addresses must be unique across all
         listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
         all addresses use the same protocol, and multiple internal addresses are not supported.
         
        repeated .envoy.config.listener.v3.AdditionalAddress additional_addresses = 33;
      • getAdditionalAddressesBuilder

        public AdditionalAddress.Builder getAdditionalAddressesBuilder​(int index)
         The additional addresses the listener should listen on. The addresses must be unique across all
         listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
         all addresses use the same protocol, and multiple internal addresses are not supported.
         
        repeated .envoy.config.listener.v3.AdditionalAddress additional_addresses = 33;
      • getAdditionalAddressesOrBuilder

        public AdditionalAddressOrBuilder getAdditionalAddressesOrBuilder​(int index)
         The additional addresses the listener should listen on. The addresses must be unique across all
         listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
         all addresses use the same protocol, and multiple internal addresses are not supported.
         
        repeated .envoy.config.listener.v3.AdditionalAddress additional_addresses = 33;
        Specified by:
        getAdditionalAddressesOrBuilder in interface ListenerOrBuilder
      • getAdditionalAddressesOrBuilderList

        public java.util.List<? extends AdditionalAddressOrBuilder> getAdditionalAddressesOrBuilderList()
         The additional addresses the listener should listen on. The addresses must be unique across all
         listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
         all addresses use the same protocol, and multiple internal addresses are not supported.
         
        repeated .envoy.config.listener.v3.AdditionalAddress additional_addresses = 33;
        Specified by:
        getAdditionalAddressesOrBuilderList in interface ListenerOrBuilder
      • addAdditionalAddressesBuilder

        public AdditionalAddress.Builder addAdditionalAddressesBuilder()
         The additional addresses the listener should listen on. The addresses must be unique across all
         listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
         all addresses use the same protocol, and multiple internal addresses are not supported.
         
        repeated .envoy.config.listener.v3.AdditionalAddress additional_addresses = 33;
      • addAdditionalAddressesBuilder

        public AdditionalAddress.Builder addAdditionalAddressesBuilder​(int index)
         The additional addresses the listener should listen on. The addresses must be unique across all
         listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
         all addresses use the same protocol, and multiple internal addresses are not supported.
         
        repeated .envoy.config.listener.v3.AdditionalAddress additional_addresses = 33;
      • getAdditionalAddressesBuilderList

        public java.util.List<AdditionalAddress.Builder> getAdditionalAddressesBuilderList()
         The additional addresses the listener should listen on. The addresses must be unique across all
         listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
         all addresses use the same protocol, and multiple internal addresses are not supported.
         
        repeated .envoy.config.listener.v3.AdditionalAddress additional_addresses = 33;
      • getStatPrefix

        public java.lang.String getStatPrefix()
         Optional prefix to use on listener stats. If empty, the stats will be rooted at
         ``listener.<address as string>.``. If non-empty, stats will be rooted at
         ``listener.<stat_prefix>.``.
         
        string stat_prefix = 28;
        Specified by:
        getStatPrefix in interface ListenerOrBuilder
        Returns:
        The statPrefix.
      • getStatPrefixBytes

        public com.google.protobuf.ByteString getStatPrefixBytes()
         Optional prefix to use on listener stats. If empty, the stats will be rooted at
         ``listener.<address as string>.``. If non-empty, stats will be rooted at
         ``listener.<stat_prefix>.``.
         
        string stat_prefix = 28;
        Specified by:
        getStatPrefixBytes in interface ListenerOrBuilder
        Returns:
        The bytes for statPrefix.
      • setStatPrefix

        public Listener.Builder setStatPrefix​(java.lang.String value)
         Optional prefix to use on listener stats. If empty, the stats will be rooted at
         ``listener.<address as string>.``. If non-empty, stats will be rooted at
         ``listener.<stat_prefix>.``.
         
        string stat_prefix = 28;
        Parameters:
        value - The statPrefix to set.
        Returns:
        This builder for chaining.
      • clearStatPrefix

        public Listener.Builder clearStatPrefix()
         Optional prefix to use on listener stats. If empty, the stats will be rooted at
         ``listener.<address as string>.``. If non-empty, stats will be rooted at
         ``listener.<stat_prefix>.``.
         
        string stat_prefix = 28;
        Returns:
        This builder for chaining.
      • setStatPrefixBytes

        public Listener.Builder setStatPrefixBytes​(com.google.protobuf.ByteString value)
         Optional prefix to use on listener stats. If empty, the stats will be rooted at
         ``listener.<address as string>.``. If non-empty, stats will be rooted at
         ``listener.<stat_prefix>.``.
         
        string stat_prefix = 28;
        Parameters:
        value - The bytes for statPrefix to set.
        Returns:
        This builder for chaining.
      • ensureFilterChainsIsMutable

        private void ensureFilterChainsIsMutable()
      • getFilterChainsList

        public java.util.List<FilterChain> getFilterChainsList()
         A list of filter chains to consider for this listener. The
         :ref:`FilterChain <envoy_v3_api_msg_config.listener.v3.FilterChain>` with the most specific
         :ref:`FilterChainMatch <envoy_v3_api_msg_config.listener.v3.FilterChainMatch>` criteria is used on a
         connection.
        
         Example using SNI for filter chain selection can be found in the
         :ref:`FAQ entry <faq_how_to_setup_sni>`.
         
        repeated .envoy.config.listener.v3.FilterChain filter_chains = 3;
        Specified by:
        getFilterChainsList in interface ListenerOrBuilder
      • getFilterChainsCount

        public int getFilterChainsCount()
         A list of filter chains to consider for this listener. The
         :ref:`FilterChain <envoy_v3_api_msg_config.listener.v3.FilterChain>` with the most specific
         :ref:`FilterChainMatch <envoy_v3_api_msg_config.listener.v3.FilterChainMatch>` criteria is used on a
         connection.
        
         Example using SNI for filter chain selection can be found in the
         :ref:`FAQ entry <faq_how_to_setup_sni>`.
         
        repeated .envoy.config.listener.v3.FilterChain filter_chains = 3;
        Specified by:
        getFilterChainsCount in interface ListenerOrBuilder
      • getFilterChains

        public FilterChain getFilterChains​(int index)
         A list of filter chains to consider for this listener. The
         :ref:`FilterChain <envoy_v3_api_msg_config.listener.v3.FilterChain>` with the most specific
         :ref:`FilterChainMatch <envoy_v3_api_msg_config.listener.v3.FilterChainMatch>` criteria is used on a
         connection.
        
         Example using SNI for filter chain selection can be found in the
         :ref:`FAQ entry <faq_how_to_setup_sni>`.
         
        repeated .envoy.config.listener.v3.FilterChain filter_chains = 3;
        Specified by:
        getFilterChains in interface ListenerOrBuilder
      • setFilterChains

        public Listener.Builder setFilterChains​(int index,
                                                FilterChain value)
         A list of filter chains to consider for this listener. The
         :ref:`FilterChain <envoy_v3_api_msg_config.listener.v3.FilterChain>` with the most specific
         :ref:`FilterChainMatch <envoy_v3_api_msg_config.listener.v3.FilterChainMatch>` criteria is used on a
         connection.
        
         Example using SNI for filter chain selection can be found in the
         :ref:`FAQ entry <faq_how_to_setup_sni>`.
         
        repeated .envoy.config.listener.v3.FilterChain filter_chains = 3;
      • setFilterChains

        public Listener.Builder setFilterChains​(int index,
                                                FilterChain.Builder builderForValue)
         A list of filter chains to consider for this listener. The
         :ref:`FilterChain <envoy_v3_api_msg_config.listener.v3.FilterChain>` with the most specific
         :ref:`FilterChainMatch <envoy_v3_api_msg_config.listener.v3.FilterChainMatch>` criteria is used on a
         connection.
        
         Example using SNI for filter chain selection can be found in the
         :ref:`FAQ entry <faq_how_to_setup_sni>`.
         
        repeated .envoy.config.listener.v3.FilterChain filter_chains = 3;
      • addFilterChains

        public Listener.Builder addFilterChains​(FilterChain value)
         A list of filter chains to consider for this listener. The
         :ref:`FilterChain <envoy_v3_api_msg_config.listener.v3.FilterChain>` with the most specific
         :ref:`FilterChainMatch <envoy_v3_api_msg_config.listener.v3.FilterChainMatch>` criteria is used on a
         connection.
        
         Example using SNI for filter chain selection can be found in the
         :ref:`FAQ entry <faq_how_to_setup_sni>`.
         
        repeated .envoy.config.listener.v3.FilterChain filter_chains = 3;
      • addFilterChains

        public Listener.Builder addFilterChains​(int index,
                                                FilterChain value)
         A list of filter chains to consider for this listener. The
         :ref:`FilterChain <envoy_v3_api_msg_config.listener.v3.FilterChain>` with the most specific
         :ref:`FilterChainMatch <envoy_v3_api_msg_config.listener.v3.FilterChainMatch>` criteria is used on a
         connection.
        
         Example using SNI for filter chain selection can be found in the
         :ref:`FAQ entry <faq_how_to_setup_sni>`.
         
        repeated .envoy.config.listener.v3.FilterChain filter_chains = 3;
      • addFilterChains

        public Listener.Builder addFilterChains​(FilterChain.Builder builderForValue)
         A list of filter chains to consider for this listener. The
         :ref:`FilterChain <envoy_v3_api_msg_config.listener.v3.FilterChain>` with the most specific
         :ref:`FilterChainMatch <envoy_v3_api_msg_config.listener.v3.FilterChainMatch>` criteria is used on a
         connection.
        
         Example using SNI for filter chain selection can be found in the
         :ref:`FAQ entry <faq_how_to_setup_sni>`.
         
        repeated .envoy.config.listener.v3.FilterChain filter_chains = 3;
      • addFilterChains

        public Listener.Builder addFilterChains​(int index,
                                                FilterChain.Builder builderForValue)
         A list of filter chains to consider for this listener. The
         :ref:`FilterChain <envoy_v3_api_msg_config.listener.v3.FilterChain>` with the most specific
         :ref:`FilterChainMatch <envoy_v3_api_msg_config.listener.v3.FilterChainMatch>` criteria is used on a
         connection.
        
         Example using SNI for filter chain selection can be found in the
         :ref:`FAQ entry <faq_how_to_setup_sni>`.
         
        repeated .envoy.config.listener.v3.FilterChain filter_chains = 3;
      • addAllFilterChains

        public Listener.Builder addAllFilterChains​(java.lang.Iterable<? extends FilterChain> values)
         A list of filter chains to consider for this listener. The
         :ref:`FilterChain <envoy_v3_api_msg_config.listener.v3.FilterChain>` with the most specific
         :ref:`FilterChainMatch <envoy_v3_api_msg_config.listener.v3.FilterChainMatch>` criteria is used on a
         connection.
        
         Example using SNI for filter chain selection can be found in the
         :ref:`FAQ entry <faq_how_to_setup_sni>`.
         
        repeated .envoy.config.listener.v3.FilterChain filter_chains = 3;
      • clearFilterChains

        public Listener.Builder clearFilterChains()
         A list of filter chains to consider for this listener. The
         :ref:`FilterChain <envoy_v3_api_msg_config.listener.v3.FilterChain>` with the most specific
         :ref:`FilterChainMatch <envoy_v3_api_msg_config.listener.v3.FilterChainMatch>` criteria is used on a
         connection.
        
         Example using SNI for filter chain selection can be found in the
         :ref:`FAQ entry <faq_how_to_setup_sni>`.
         
        repeated .envoy.config.listener.v3.FilterChain filter_chains = 3;
      • removeFilterChains

        public Listener.Builder removeFilterChains​(int index)
         A list of filter chains to consider for this listener. The
         :ref:`FilterChain <envoy_v3_api_msg_config.listener.v3.FilterChain>` with the most specific
         :ref:`FilterChainMatch <envoy_v3_api_msg_config.listener.v3.FilterChainMatch>` criteria is used on a
         connection.
        
         Example using SNI for filter chain selection can be found in the
         :ref:`FAQ entry <faq_how_to_setup_sni>`.
         
        repeated .envoy.config.listener.v3.FilterChain filter_chains = 3;
      • getFilterChainsBuilder

        public FilterChain.Builder getFilterChainsBuilder​(int index)
         A list of filter chains to consider for this listener. The
         :ref:`FilterChain <envoy_v3_api_msg_config.listener.v3.FilterChain>` with the most specific
         :ref:`FilterChainMatch <envoy_v3_api_msg_config.listener.v3.FilterChainMatch>` criteria is used on a
         connection.
        
         Example using SNI for filter chain selection can be found in the
         :ref:`FAQ entry <faq_how_to_setup_sni>`.
         
        repeated .envoy.config.listener.v3.FilterChain filter_chains = 3;
      • getFilterChainsOrBuilder

        public FilterChainOrBuilder getFilterChainsOrBuilder​(int index)
         A list of filter chains to consider for this listener. The
         :ref:`FilterChain <envoy_v3_api_msg_config.listener.v3.FilterChain>` with the most specific
         :ref:`FilterChainMatch <envoy_v3_api_msg_config.listener.v3.FilterChainMatch>` criteria is used on a
         connection.
        
         Example using SNI for filter chain selection can be found in the
         :ref:`FAQ entry <faq_how_to_setup_sni>`.
         
        repeated .envoy.config.listener.v3.FilterChain filter_chains = 3;
        Specified by:
        getFilterChainsOrBuilder in interface ListenerOrBuilder
      • getFilterChainsOrBuilderList

        public java.util.List<? extends FilterChainOrBuilder> getFilterChainsOrBuilderList()
         A list of filter chains to consider for this listener. The
         :ref:`FilterChain <envoy_v3_api_msg_config.listener.v3.FilterChain>` with the most specific
         :ref:`FilterChainMatch <envoy_v3_api_msg_config.listener.v3.FilterChainMatch>` criteria is used on a
         connection.
        
         Example using SNI for filter chain selection can be found in the
         :ref:`FAQ entry <faq_how_to_setup_sni>`.
         
        repeated .envoy.config.listener.v3.FilterChain filter_chains = 3;
        Specified by:
        getFilterChainsOrBuilderList in interface ListenerOrBuilder
      • addFilterChainsBuilder

        public FilterChain.Builder addFilterChainsBuilder()
         A list of filter chains to consider for this listener. The
         :ref:`FilterChain <envoy_v3_api_msg_config.listener.v3.FilterChain>` with the most specific
         :ref:`FilterChainMatch <envoy_v3_api_msg_config.listener.v3.FilterChainMatch>` criteria is used on a
         connection.
        
         Example using SNI for filter chain selection can be found in the
         :ref:`FAQ entry <faq_how_to_setup_sni>`.
         
        repeated .envoy.config.listener.v3.FilterChain filter_chains = 3;
      • addFilterChainsBuilder

        public FilterChain.Builder addFilterChainsBuilder​(int index)
         A list of filter chains to consider for this listener. The
         :ref:`FilterChain <envoy_v3_api_msg_config.listener.v3.FilterChain>` with the most specific
         :ref:`FilterChainMatch <envoy_v3_api_msg_config.listener.v3.FilterChainMatch>` criteria is used on a
         connection.
        
         Example using SNI for filter chain selection can be found in the
         :ref:`FAQ entry <faq_how_to_setup_sni>`.
         
        repeated .envoy.config.listener.v3.FilterChain filter_chains = 3;
      • getFilterChainsBuilderList

        public java.util.List<FilterChain.Builder> getFilterChainsBuilderList()
         A list of filter chains to consider for this listener. The
         :ref:`FilterChain <envoy_v3_api_msg_config.listener.v3.FilterChain>` with the most specific
         :ref:`FilterChainMatch <envoy_v3_api_msg_config.listener.v3.FilterChainMatch>` criteria is used on a
         connection.
        
         Example using SNI for filter chain selection can be found in the
         :ref:`FAQ entry <faq_how_to_setup_sni>`.
         
        repeated .envoy.config.listener.v3.FilterChain filter_chains = 3;
      • hasFilterChainMatcher

        public boolean hasFilterChainMatcher()
         :ref:`Matcher API <arch_overview_matching_listener>` resolving the filter chain name from the
         network properties. This matcher is used as a replacement for the filter chain match condition
         :ref:`filter_chain_match
         <envoy_v3_api_field_config.listener.v3.FilterChain.filter_chain_match>`. If specified, all
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>` must have a
         non-empty and unique :ref:`name <envoy_v3_api_field_config.listener.v3.FilterChain.name>` field
         and not specify :ref:`filter_chain_match
         <envoy_v3_api_field_config.listener.v3.FilterChain.filter_chain_match>` field.
        
         .. note::
        
         Once matched, each connection is permanently bound to its filter chain.
         If the matcher changes but the filter chain remains the same, the
         connections bound to the filter chain are not drained. If, however, the
         filter chain is removed or structurally modified, then the drain for its
         connections is initiated.
         
        .xds.type.matcher.v3.Matcher filter_chain_matcher = 32 [(.xds.annotations.v3.field_status) = { ... }
        Specified by:
        hasFilterChainMatcher in interface ListenerOrBuilder
        Returns:
        Whether the filterChainMatcher field is set.
      • getFilterChainMatcher

        public Matcher getFilterChainMatcher()
         :ref:`Matcher API <arch_overview_matching_listener>` resolving the filter chain name from the
         network properties. This matcher is used as a replacement for the filter chain match condition
         :ref:`filter_chain_match
         <envoy_v3_api_field_config.listener.v3.FilterChain.filter_chain_match>`. If specified, all
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>` must have a
         non-empty and unique :ref:`name <envoy_v3_api_field_config.listener.v3.FilterChain.name>` field
         and not specify :ref:`filter_chain_match
         <envoy_v3_api_field_config.listener.v3.FilterChain.filter_chain_match>` field.
        
         .. note::
        
         Once matched, each connection is permanently bound to its filter chain.
         If the matcher changes but the filter chain remains the same, the
         connections bound to the filter chain are not drained. If, however, the
         filter chain is removed or structurally modified, then the drain for its
         connections is initiated.
         
        .xds.type.matcher.v3.Matcher filter_chain_matcher = 32 [(.xds.annotations.v3.field_status) = { ... }
        Specified by:
        getFilterChainMatcher in interface ListenerOrBuilder
        Returns:
        The filterChainMatcher.
      • setFilterChainMatcher

        public Listener.Builder setFilterChainMatcher​(Matcher value)
         :ref:`Matcher API <arch_overview_matching_listener>` resolving the filter chain name from the
         network properties. This matcher is used as a replacement for the filter chain match condition
         :ref:`filter_chain_match
         <envoy_v3_api_field_config.listener.v3.FilterChain.filter_chain_match>`. If specified, all
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>` must have a
         non-empty and unique :ref:`name <envoy_v3_api_field_config.listener.v3.FilterChain.name>` field
         and not specify :ref:`filter_chain_match
         <envoy_v3_api_field_config.listener.v3.FilterChain.filter_chain_match>` field.
        
         .. note::
        
         Once matched, each connection is permanently bound to its filter chain.
         If the matcher changes but the filter chain remains the same, the
         connections bound to the filter chain are not drained. If, however, the
         filter chain is removed or structurally modified, then the drain for its
         connections is initiated.
         
        .xds.type.matcher.v3.Matcher filter_chain_matcher = 32 [(.xds.annotations.v3.field_status) = { ... }
      • setFilterChainMatcher

        public Listener.Builder setFilterChainMatcher​(Matcher.Builder builderForValue)
         :ref:`Matcher API <arch_overview_matching_listener>` resolving the filter chain name from the
         network properties. This matcher is used as a replacement for the filter chain match condition
         :ref:`filter_chain_match
         <envoy_v3_api_field_config.listener.v3.FilterChain.filter_chain_match>`. If specified, all
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>` must have a
         non-empty and unique :ref:`name <envoy_v3_api_field_config.listener.v3.FilterChain.name>` field
         and not specify :ref:`filter_chain_match
         <envoy_v3_api_field_config.listener.v3.FilterChain.filter_chain_match>` field.
        
         .. note::
        
         Once matched, each connection is permanently bound to its filter chain.
         If the matcher changes but the filter chain remains the same, the
         connections bound to the filter chain are not drained. If, however, the
         filter chain is removed or structurally modified, then the drain for its
         connections is initiated.
         
        .xds.type.matcher.v3.Matcher filter_chain_matcher = 32 [(.xds.annotations.v3.field_status) = { ... }
      • mergeFilterChainMatcher

        public Listener.Builder mergeFilterChainMatcher​(Matcher value)
         :ref:`Matcher API <arch_overview_matching_listener>` resolving the filter chain name from the
         network properties. This matcher is used as a replacement for the filter chain match condition
         :ref:`filter_chain_match
         <envoy_v3_api_field_config.listener.v3.FilterChain.filter_chain_match>`. If specified, all
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>` must have a
         non-empty and unique :ref:`name <envoy_v3_api_field_config.listener.v3.FilterChain.name>` field
         and not specify :ref:`filter_chain_match
         <envoy_v3_api_field_config.listener.v3.FilterChain.filter_chain_match>` field.
        
         .. note::
        
         Once matched, each connection is permanently bound to its filter chain.
         If the matcher changes but the filter chain remains the same, the
         connections bound to the filter chain are not drained. If, however, the
         filter chain is removed or structurally modified, then the drain for its
         connections is initiated.
         
        .xds.type.matcher.v3.Matcher filter_chain_matcher = 32 [(.xds.annotations.v3.field_status) = { ... }
      • clearFilterChainMatcher

        public Listener.Builder clearFilterChainMatcher()
         :ref:`Matcher API <arch_overview_matching_listener>` resolving the filter chain name from the
         network properties. This matcher is used as a replacement for the filter chain match condition
         :ref:`filter_chain_match
         <envoy_v3_api_field_config.listener.v3.FilterChain.filter_chain_match>`. If specified, all
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>` must have a
         non-empty and unique :ref:`name <envoy_v3_api_field_config.listener.v3.FilterChain.name>` field
         and not specify :ref:`filter_chain_match
         <envoy_v3_api_field_config.listener.v3.FilterChain.filter_chain_match>` field.
        
         .. note::
        
         Once matched, each connection is permanently bound to its filter chain.
         If the matcher changes but the filter chain remains the same, the
         connections bound to the filter chain are not drained. If, however, the
         filter chain is removed or structurally modified, then the drain for its
         connections is initiated.
         
        .xds.type.matcher.v3.Matcher filter_chain_matcher = 32 [(.xds.annotations.v3.field_status) = { ... }
      • getFilterChainMatcherBuilder

        public Matcher.Builder getFilterChainMatcherBuilder()
         :ref:`Matcher API <arch_overview_matching_listener>` resolving the filter chain name from the
         network properties. This matcher is used as a replacement for the filter chain match condition
         :ref:`filter_chain_match
         <envoy_v3_api_field_config.listener.v3.FilterChain.filter_chain_match>`. If specified, all
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>` must have a
         non-empty and unique :ref:`name <envoy_v3_api_field_config.listener.v3.FilterChain.name>` field
         and not specify :ref:`filter_chain_match
         <envoy_v3_api_field_config.listener.v3.FilterChain.filter_chain_match>` field.
        
         .. note::
        
         Once matched, each connection is permanently bound to its filter chain.
         If the matcher changes but the filter chain remains the same, the
         connections bound to the filter chain are not drained. If, however, the
         filter chain is removed or structurally modified, then the drain for its
         connections is initiated.
         
        .xds.type.matcher.v3.Matcher filter_chain_matcher = 32 [(.xds.annotations.v3.field_status) = { ... }
      • getFilterChainMatcherOrBuilder

        public MatcherOrBuilder getFilterChainMatcherOrBuilder()
         :ref:`Matcher API <arch_overview_matching_listener>` resolving the filter chain name from the
         network properties. This matcher is used as a replacement for the filter chain match condition
         :ref:`filter_chain_match
         <envoy_v3_api_field_config.listener.v3.FilterChain.filter_chain_match>`. If specified, all
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>` must have a
         non-empty and unique :ref:`name <envoy_v3_api_field_config.listener.v3.FilterChain.name>` field
         and not specify :ref:`filter_chain_match
         <envoy_v3_api_field_config.listener.v3.FilterChain.filter_chain_match>` field.
        
         .. note::
        
         Once matched, each connection is permanently bound to its filter chain.
         If the matcher changes but the filter chain remains the same, the
         connections bound to the filter chain are not drained. If, however, the
         filter chain is removed or structurally modified, then the drain for its
         connections is initiated.
         
        .xds.type.matcher.v3.Matcher filter_chain_matcher = 32 [(.xds.annotations.v3.field_status) = { ... }
        Specified by:
        getFilterChainMatcherOrBuilder in interface ListenerOrBuilder
      • getFilterChainMatcherFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<Matcher,​Matcher.Builder,​MatcherOrBuilder> getFilterChainMatcherFieldBuilder()
         :ref:`Matcher API <arch_overview_matching_listener>` resolving the filter chain name from the
         network properties. This matcher is used as a replacement for the filter chain match condition
         :ref:`filter_chain_match
         <envoy_v3_api_field_config.listener.v3.FilterChain.filter_chain_match>`. If specified, all
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>` must have a
         non-empty and unique :ref:`name <envoy_v3_api_field_config.listener.v3.FilterChain.name>` field
         and not specify :ref:`filter_chain_match
         <envoy_v3_api_field_config.listener.v3.FilterChain.filter_chain_match>` field.
        
         .. note::
        
         Once matched, each connection is permanently bound to its filter chain.
         If the matcher changes but the filter chain remains the same, the
         connections bound to the filter chain are not drained. If, however, the
         filter chain is removed or structurally modified, then the drain for its
         connections is initiated.
         
        .xds.type.matcher.v3.Matcher filter_chain_matcher = 32 [(.xds.annotations.v3.field_status) = { ... }
      • hasUseOriginalDst

        public boolean hasUseOriginalDst()
         If a connection is redirected using ``iptables``, the port on which the proxy
         receives it might be different from the original destination address. When this flag is set to
         true, the listener hands off redirected connections to the listener associated with the
         original destination address. If there is no listener associated with the original destination
         address, the connection is handled by the listener that receives it. Defaults to false.
         
        .google.protobuf.BoolValue use_original_dst = 4;
        Specified by:
        hasUseOriginalDst in interface ListenerOrBuilder
        Returns:
        Whether the useOriginalDst field is set.
      • getUseOriginalDst

        public com.google.protobuf.BoolValue getUseOriginalDst()
         If a connection is redirected using ``iptables``, the port on which the proxy
         receives it might be different from the original destination address. When this flag is set to
         true, the listener hands off redirected connections to the listener associated with the
         original destination address. If there is no listener associated with the original destination
         address, the connection is handled by the listener that receives it. Defaults to false.
         
        .google.protobuf.BoolValue use_original_dst = 4;
        Specified by:
        getUseOriginalDst in interface ListenerOrBuilder
        Returns:
        The useOriginalDst.
      • setUseOriginalDst

        public Listener.Builder setUseOriginalDst​(com.google.protobuf.BoolValue value)
         If a connection is redirected using ``iptables``, the port on which the proxy
         receives it might be different from the original destination address. When this flag is set to
         true, the listener hands off redirected connections to the listener associated with the
         original destination address. If there is no listener associated with the original destination
         address, the connection is handled by the listener that receives it. Defaults to false.
         
        .google.protobuf.BoolValue use_original_dst = 4;
      • setUseOriginalDst

        public Listener.Builder setUseOriginalDst​(com.google.protobuf.BoolValue.Builder builderForValue)
         If a connection is redirected using ``iptables``, the port on which the proxy
         receives it might be different from the original destination address. When this flag is set to
         true, the listener hands off redirected connections to the listener associated with the
         original destination address. If there is no listener associated with the original destination
         address, the connection is handled by the listener that receives it. Defaults to false.
         
        .google.protobuf.BoolValue use_original_dst = 4;
      • mergeUseOriginalDst

        public Listener.Builder mergeUseOriginalDst​(com.google.protobuf.BoolValue value)
         If a connection is redirected using ``iptables``, the port on which the proxy
         receives it might be different from the original destination address. When this flag is set to
         true, the listener hands off redirected connections to the listener associated with the
         original destination address. If there is no listener associated with the original destination
         address, the connection is handled by the listener that receives it. Defaults to false.
         
        .google.protobuf.BoolValue use_original_dst = 4;
      • clearUseOriginalDst

        public Listener.Builder clearUseOriginalDst()
         If a connection is redirected using ``iptables``, the port on which the proxy
         receives it might be different from the original destination address. When this flag is set to
         true, the listener hands off redirected connections to the listener associated with the
         original destination address. If there is no listener associated with the original destination
         address, the connection is handled by the listener that receives it. Defaults to false.
         
        .google.protobuf.BoolValue use_original_dst = 4;
      • getUseOriginalDstBuilder

        public com.google.protobuf.BoolValue.Builder getUseOriginalDstBuilder()
         If a connection is redirected using ``iptables``, the port on which the proxy
         receives it might be different from the original destination address. When this flag is set to
         true, the listener hands off redirected connections to the listener associated with the
         original destination address. If there is no listener associated with the original destination
         address, the connection is handled by the listener that receives it. Defaults to false.
         
        .google.protobuf.BoolValue use_original_dst = 4;
      • getUseOriginalDstOrBuilder

        public com.google.protobuf.BoolValueOrBuilder getUseOriginalDstOrBuilder()
         If a connection is redirected using ``iptables``, the port on which the proxy
         receives it might be different from the original destination address. When this flag is set to
         true, the listener hands off redirected connections to the listener associated with the
         original destination address. If there is no listener associated with the original destination
         address, the connection is handled by the listener that receives it. Defaults to false.
         
        .google.protobuf.BoolValue use_original_dst = 4;
        Specified by:
        getUseOriginalDstOrBuilder in interface ListenerOrBuilder
      • getUseOriginalDstFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,​com.google.protobuf.BoolValue.Builder,​com.google.protobuf.BoolValueOrBuilder> getUseOriginalDstFieldBuilder()
         If a connection is redirected using ``iptables``, the port on which the proxy
         receives it might be different from the original destination address. When this flag is set to
         true, the listener hands off redirected connections to the listener associated with the
         original destination address. If there is no listener associated with the original destination
         address, the connection is handled by the listener that receives it. Defaults to false.
         
        .google.protobuf.BoolValue use_original_dst = 4;
      • hasDefaultFilterChain

        public boolean hasDefaultFilterChain()
         The default filter chain if none of the filter chain matches. If no default filter chain is supplied,
         the connection will be closed. The filter chain match is ignored in this field.
         
        .envoy.config.listener.v3.FilterChain default_filter_chain = 25;
        Specified by:
        hasDefaultFilterChain in interface ListenerOrBuilder
        Returns:
        Whether the defaultFilterChain field is set.
      • getDefaultFilterChain

        public FilterChain getDefaultFilterChain()
         The default filter chain if none of the filter chain matches. If no default filter chain is supplied,
         the connection will be closed. The filter chain match is ignored in this field.
         
        .envoy.config.listener.v3.FilterChain default_filter_chain = 25;
        Specified by:
        getDefaultFilterChain in interface ListenerOrBuilder
        Returns:
        The defaultFilterChain.
      • setDefaultFilterChain

        public Listener.Builder setDefaultFilterChain​(FilterChain value)
         The default filter chain if none of the filter chain matches. If no default filter chain is supplied,
         the connection will be closed. The filter chain match is ignored in this field.
         
        .envoy.config.listener.v3.FilterChain default_filter_chain = 25;
      • setDefaultFilterChain

        public Listener.Builder setDefaultFilterChain​(FilterChain.Builder builderForValue)
         The default filter chain if none of the filter chain matches. If no default filter chain is supplied,
         the connection will be closed. The filter chain match is ignored in this field.
         
        .envoy.config.listener.v3.FilterChain default_filter_chain = 25;
      • mergeDefaultFilterChain

        public Listener.Builder mergeDefaultFilterChain​(FilterChain value)
         The default filter chain if none of the filter chain matches. If no default filter chain is supplied,
         the connection will be closed. The filter chain match is ignored in this field.
         
        .envoy.config.listener.v3.FilterChain default_filter_chain = 25;
      • clearDefaultFilterChain

        public Listener.Builder clearDefaultFilterChain()
         The default filter chain if none of the filter chain matches. If no default filter chain is supplied,
         the connection will be closed. The filter chain match is ignored in this field.
         
        .envoy.config.listener.v3.FilterChain default_filter_chain = 25;
      • getDefaultFilterChainBuilder

        public FilterChain.Builder getDefaultFilterChainBuilder()
         The default filter chain if none of the filter chain matches. If no default filter chain is supplied,
         the connection will be closed. The filter chain match is ignored in this field.
         
        .envoy.config.listener.v3.FilterChain default_filter_chain = 25;
      • getDefaultFilterChainOrBuilder

        public FilterChainOrBuilder getDefaultFilterChainOrBuilder()
         The default filter chain if none of the filter chain matches. If no default filter chain is supplied,
         the connection will be closed. The filter chain match is ignored in this field.
         
        .envoy.config.listener.v3.FilterChain default_filter_chain = 25;
        Specified by:
        getDefaultFilterChainOrBuilder in interface ListenerOrBuilder
      • getDefaultFilterChainFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<FilterChain,​FilterChain.Builder,​FilterChainOrBuilder> getDefaultFilterChainFieldBuilder()
         The default filter chain if none of the filter chain matches. If no default filter chain is supplied,
         the connection will be closed. The filter chain match is ignored in this field.
         
        .envoy.config.listener.v3.FilterChain default_filter_chain = 25;
      • hasPerConnectionBufferLimitBytes

        public boolean hasPerConnectionBufferLimitBytes()
         Soft limit on size of the listener’s new connection read and write buffers.
         If unspecified, an implementation defined default is applied (1MiB).
         
        .google.protobuf.UInt32Value per_connection_buffer_limit_bytes = 5 [(.udpa.annotations.security) = { ... }
        Specified by:
        hasPerConnectionBufferLimitBytes in interface ListenerOrBuilder
        Returns:
        Whether the perConnectionBufferLimitBytes field is set.
      • getPerConnectionBufferLimitBytes

        public com.google.protobuf.UInt32Value getPerConnectionBufferLimitBytes()
         Soft limit on size of the listener’s new connection read and write buffers.
         If unspecified, an implementation defined default is applied (1MiB).
         
        .google.protobuf.UInt32Value per_connection_buffer_limit_bytes = 5 [(.udpa.annotations.security) = { ... }
        Specified by:
        getPerConnectionBufferLimitBytes in interface ListenerOrBuilder
        Returns:
        The perConnectionBufferLimitBytes.
      • setPerConnectionBufferLimitBytes

        public Listener.Builder setPerConnectionBufferLimitBytes​(com.google.protobuf.UInt32Value value)
         Soft limit on size of the listener’s new connection read and write buffers.
         If unspecified, an implementation defined default is applied (1MiB).
         
        .google.protobuf.UInt32Value per_connection_buffer_limit_bytes = 5 [(.udpa.annotations.security) = { ... }
      • setPerConnectionBufferLimitBytes

        public Listener.Builder setPerConnectionBufferLimitBytes​(com.google.protobuf.UInt32Value.Builder builderForValue)
         Soft limit on size of the listener’s new connection read and write buffers.
         If unspecified, an implementation defined default is applied (1MiB).
         
        .google.protobuf.UInt32Value per_connection_buffer_limit_bytes = 5 [(.udpa.annotations.security) = { ... }
      • mergePerConnectionBufferLimitBytes

        public Listener.Builder mergePerConnectionBufferLimitBytes​(com.google.protobuf.UInt32Value value)
         Soft limit on size of the listener’s new connection read and write buffers.
         If unspecified, an implementation defined default is applied (1MiB).
         
        .google.protobuf.UInt32Value per_connection_buffer_limit_bytes = 5 [(.udpa.annotations.security) = { ... }
      • clearPerConnectionBufferLimitBytes

        public Listener.Builder clearPerConnectionBufferLimitBytes()
         Soft limit on size of the listener’s new connection read and write buffers.
         If unspecified, an implementation defined default is applied (1MiB).
         
        .google.protobuf.UInt32Value per_connection_buffer_limit_bytes = 5 [(.udpa.annotations.security) = { ... }
      • getPerConnectionBufferLimitBytesBuilder

        public com.google.protobuf.UInt32Value.Builder getPerConnectionBufferLimitBytesBuilder()
         Soft limit on size of the listener’s new connection read and write buffers.
         If unspecified, an implementation defined default is applied (1MiB).
         
        .google.protobuf.UInt32Value per_connection_buffer_limit_bytes = 5 [(.udpa.annotations.security) = { ... }
      • getPerConnectionBufferLimitBytesOrBuilder

        public com.google.protobuf.UInt32ValueOrBuilder getPerConnectionBufferLimitBytesOrBuilder()
         Soft limit on size of the listener’s new connection read and write buffers.
         If unspecified, an implementation defined default is applied (1MiB).
         
        .google.protobuf.UInt32Value per_connection_buffer_limit_bytes = 5 [(.udpa.annotations.security) = { ... }
        Specified by:
        getPerConnectionBufferLimitBytesOrBuilder in interface ListenerOrBuilder
      • getPerConnectionBufferLimitBytesFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.UInt32Value,​com.google.protobuf.UInt32Value.Builder,​com.google.protobuf.UInt32ValueOrBuilder> getPerConnectionBufferLimitBytesFieldBuilder()
         Soft limit on size of the listener’s new connection read and write buffers.
         If unspecified, an implementation defined default is applied (1MiB).
         
        .google.protobuf.UInt32Value per_connection_buffer_limit_bytes = 5 [(.udpa.annotations.security) = { ... }
      • hasMetadata

        public boolean hasMetadata()
         Listener metadata.
         
        .envoy.config.core.v3.Metadata metadata = 6;
        Specified by:
        hasMetadata in interface ListenerOrBuilder
        Returns:
        Whether the metadata field is set.
      • getMetadata

        public Metadata getMetadata()
         Listener metadata.
         
        .envoy.config.core.v3.Metadata metadata = 6;
        Specified by:
        getMetadata in interface ListenerOrBuilder
        Returns:
        The metadata.
      • setMetadata

        public Listener.Builder setMetadata​(Metadata value)
         Listener metadata.
         
        .envoy.config.core.v3.Metadata metadata = 6;
      • mergeMetadata

        public Listener.Builder mergeMetadata​(Metadata value)
         Listener metadata.
         
        .envoy.config.core.v3.Metadata metadata = 6;
      • clearMetadata

        public Listener.Builder clearMetadata()
         Listener metadata.
         
        .envoy.config.core.v3.Metadata metadata = 6;
      • getMetadataBuilder

        public Metadata.Builder getMetadataBuilder()
         Listener metadata.
         
        .envoy.config.core.v3.Metadata metadata = 6;
      • getMetadataFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<Metadata,​Metadata.Builder,​MetadataOrBuilder> getMetadataFieldBuilder()
         Listener metadata.
         
        .envoy.config.core.v3.Metadata metadata = 6;
      • hasDeprecatedV1

        @Deprecated
        public boolean hasDeprecatedV1()
        Deprecated.
        envoy.config.listener.v3.Listener.deprecated_v1 is deprecated. See envoy/config/listener/v3/listener.proto;l=188
         [#not-implemented-hide:]
         
        .envoy.config.listener.v3.Listener.DeprecatedV1 deprecated_v1 = 7 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
        Specified by:
        hasDeprecatedV1 in interface ListenerOrBuilder
        Returns:
        Whether the deprecatedV1 field is set.
      • getDeprecatedV1

        @Deprecated
        public Listener.DeprecatedV1 getDeprecatedV1()
        Deprecated.
        envoy.config.listener.v3.Listener.deprecated_v1 is deprecated. See envoy/config/listener/v3/listener.proto;l=188
         [#not-implemented-hide:]
         
        .envoy.config.listener.v3.Listener.DeprecatedV1 deprecated_v1 = 7 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
        Specified by:
        getDeprecatedV1 in interface ListenerOrBuilder
        Returns:
        The deprecatedV1.
      • setDeprecatedV1

        @Deprecated
        public Listener.Builder setDeprecatedV1​(Listener.DeprecatedV1 value)
        Deprecated.
         [#not-implemented-hide:]
         
        .envoy.config.listener.v3.Listener.DeprecatedV1 deprecated_v1 = 7 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      • setDeprecatedV1

        @Deprecated
        public Listener.Builder setDeprecatedV1​(Listener.DeprecatedV1.Builder builderForValue)
        Deprecated.
         [#not-implemented-hide:]
         
        .envoy.config.listener.v3.Listener.DeprecatedV1 deprecated_v1 = 7 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      • mergeDeprecatedV1

        @Deprecated
        public Listener.Builder mergeDeprecatedV1​(Listener.DeprecatedV1 value)
        Deprecated.
         [#not-implemented-hide:]
         
        .envoy.config.listener.v3.Listener.DeprecatedV1 deprecated_v1 = 7 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      • clearDeprecatedV1

        @Deprecated
        public Listener.Builder clearDeprecatedV1()
        Deprecated.
         [#not-implemented-hide:]
         
        .envoy.config.listener.v3.Listener.DeprecatedV1 deprecated_v1 = 7 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      • getDeprecatedV1Builder

        @Deprecated
        public Listener.DeprecatedV1.Builder getDeprecatedV1Builder()
        Deprecated.
         [#not-implemented-hide:]
         
        .envoy.config.listener.v3.Listener.DeprecatedV1 deprecated_v1 = 7 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      • getDeprecatedV1OrBuilder

        @Deprecated
        public Listener.DeprecatedV1OrBuilder getDeprecatedV1OrBuilder()
        Deprecated.
         [#not-implemented-hide:]
         
        .envoy.config.listener.v3.Listener.DeprecatedV1 deprecated_v1 = 7 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
        Specified by:
        getDeprecatedV1OrBuilder in interface ListenerOrBuilder
      • getDrainTypeValue

        public int getDrainTypeValue()
         The type of draining to perform at a listener-wide level.
         
        .envoy.config.listener.v3.Listener.DrainType drain_type = 8;
        Specified by:
        getDrainTypeValue in interface ListenerOrBuilder
        Returns:
        The enum numeric value on the wire for drainType.
      • setDrainTypeValue

        public Listener.Builder setDrainTypeValue​(int value)
         The type of draining to perform at a listener-wide level.
         
        .envoy.config.listener.v3.Listener.DrainType drain_type = 8;
        Parameters:
        value - The enum numeric value on the wire for drainType to set.
        Returns:
        This builder for chaining.
      • getDrainType

        public Listener.DrainType getDrainType()
         The type of draining to perform at a listener-wide level.
         
        .envoy.config.listener.v3.Listener.DrainType drain_type = 8;
        Specified by:
        getDrainType in interface ListenerOrBuilder
        Returns:
        The drainType.
      • setDrainType

        public Listener.Builder setDrainType​(Listener.DrainType value)
         The type of draining to perform at a listener-wide level.
         
        .envoy.config.listener.v3.Listener.DrainType drain_type = 8;
        Parameters:
        value - The drainType to set.
        Returns:
        This builder for chaining.
      • clearDrainType

        public Listener.Builder clearDrainType()
         The type of draining to perform at a listener-wide level.
         
        .envoy.config.listener.v3.Listener.DrainType drain_type = 8;
        Returns:
        This builder for chaining.
      • ensureListenerFiltersIsMutable

        private void ensureListenerFiltersIsMutable()
      • getListenerFiltersList

        public java.util.List<ListenerFilter> getListenerFiltersList()
         Listener filters have the opportunity to manipulate and augment the connection metadata that
         is used in connection filter chain matching, for example. These filters are run before any in
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>`. Order matters as the
         filters are processed sequentially right after a socket has been accepted by the listener, and
         before a connection is created.
         UDP Listener filters can be specified when the protocol in the listener socket address in
         :ref:`protocol <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>` and no
         :ref:`quic_options <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         QUIC listener filters can be specified when :ref:`quic_options
         <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is
         specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         They are processed sequentially right before connection creation. And like TCP Listener filters, they can be used to manipulate the connection metadata and socket. But the difference is that they can't be used to pause connection creation.
         
        repeated .envoy.config.listener.v3.ListenerFilter listener_filters = 9;
        Specified by:
        getListenerFiltersList in interface ListenerOrBuilder
      • getListenerFiltersCount

        public int getListenerFiltersCount()
         Listener filters have the opportunity to manipulate and augment the connection metadata that
         is used in connection filter chain matching, for example. These filters are run before any in
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>`. Order matters as the
         filters are processed sequentially right after a socket has been accepted by the listener, and
         before a connection is created.
         UDP Listener filters can be specified when the protocol in the listener socket address in
         :ref:`protocol <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>` and no
         :ref:`quic_options <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         QUIC listener filters can be specified when :ref:`quic_options
         <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is
         specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         They are processed sequentially right before connection creation. And like TCP Listener filters, they can be used to manipulate the connection metadata and socket. But the difference is that they can't be used to pause connection creation.
         
        repeated .envoy.config.listener.v3.ListenerFilter listener_filters = 9;
        Specified by:
        getListenerFiltersCount in interface ListenerOrBuilder
      • getListenerFilters

        public ListenerFilter getListenerFilters​(int index)
         Listener filters have the opportunity to manipulate and augment the connection metadata that
         is used in connection filter chain matching, for example. These filters are run before any in
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>`. Order matters as the
         filters are processed sequentially right after a socket has been accepted by the listener, and
         before a connection is created.
         UDP Listener filters can be specified when the protocol in the listener socket address in
         :ref:`protocol <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>` and no
         :ref:`quic_options <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         QUIC listener filters can be specified when :ref:`quic_options
         <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is
         specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         They are processed sequentially right before connection creation. And like TCP Listener filters, they can be used to manipulate the connection metadata and socket. But the difference is that they can't be used to pause connection creation.
         
        repeated .envoy.config.listener.v3.ListenerFilter listener_filters = 9;
        Specified by:
        getListenerFilters in interface ListenerOrBuilder
      • setListenerFilters

        public Listener.Builder setListenerFilters​(int index,
                                                   ListenerFilter value)
         Listener filters have the opportunity to manipulate and augment the connection metadata that
         is used in connection filter chain matching, for example. These filters are run before any in
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>`. Order matters as the
         filters are processed sequentially right after a socket has been accepted by the listener, and
         before a connection is created.
         UDP Listener filters can be specified when the protocol in the listener socket address in
         :ref:`protocol <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>` and no
         :ref:`quic_options <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         QUIC listener filters can be specified when :ref:`quic_options
         <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is
         specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         They are processed sequentially right before connection creation. And like TCP Listener filters, they can be used to manipulate the connection metadata and socket. But the difference is that they can't be used to pause connection creation.
         
        repeated .envoy.config.listener.v3.ListenerFilter listener_filters = 9;
      • setListenerFilters

        public Listener.Builder setListenerFilters​(int index,
                                                   ListenerFilter.Builder builderForValue)
         Listener filters have the opportunity to manipulate and augment the connection metadata that
         is used in connection filter chain matching, for example. These filters are run before any in
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>`. Order matters as the
         filters are processed sequentially right after a socket has been accepted by the listener, and
         before a connection is created.
         UDP Listener filters can be specified when the protocol in the listener socket address in
         :ref:`protocol <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>` and no
         :ref:`quic_options <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         QUIC listener filters can be specified when :ref:`quic_options
         <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is
         specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         They are processed sequentially right before connection creation. And like TCP Listener filters, they can be used to manipulate the connection metadata and socket. But the difference is that they can't be used to pause connection creation.
         
        repeated .envoy.config.listener.v3.ListenerFilter listener_filters = 9;
      • addListenerFilters

        public Listener.Builder addListenerFilters​(ListenerFilter value)
         Listener filters have the opportunity to manipulate and augment the connection metadata that
         is used in connection filter chain matching, for example. These filters are run before any in
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>`. Order matters as the
         filters are processed sequentially right after a socket has been accepted by the listener, and
         before a connection is created.
         UDP Listener filters can be specified when the protocol in the listener socket address in
         :ref:`protocol <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>` and no
         :ref:`quic_options <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         QUIC listener filters can be specified when :ref:`quic_options
         <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is
         specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         They are processed sequentially right before connection creation. And like TCP Listener filters, they can be used to manipulate the connection metadata and socket. But the difference is that they can't be used to pause connection creation.
         
        repeated .envoy.config.listener.v3.ListenerFilter listener_filters = 9;
      • addListenerFilters

        public Listener.Builder addListenerFilters​(int index,
                                                   ListenerFilter value)
         Listener filters have the opportunity to manipulate and augment the connection metadata that
         is used in connection filter chain matching, for example. These filters are run before any in
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>`. Order matters as the
         filters are processed sequentially right after a socket has been accepted by the listener, and
         before a connection is created.
         UDP Listener filters can be specified when the protocol in the listener socket address in
         :ref:`protocol <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>` and no
         :ref:`quic_options <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         QUIC listener filters can be specified when :ref:`quic_options
         <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is
         specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         They are processed sequentially right before connection creation. And like TCP Listener filters, they can be used to manipulate the connection metadata and socket. But the difference is that they can't be used to pause connection creation.
         
        repeated .envoy.config.listener.v3.ListenerFilter listener_filters = 9;
      • addListenerFilters

        public Listener.Builder addListenerFilters​(ListenerFilter.Builder builderForValue)
         Listener filters have the opportunity to manipulate and augment the connection metadata that
         is used in connection filter chain matching, for example. These filters are run before any in
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>`. Order matters as the
         filters are processed sequentially right after a socket has been accepted by the listener, and
         before a connection is created.
         UDP Listener filters can be specified when the protocol in the listener socket address in
         :ref:`protocol <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>` and no
         :ref:`quic_options <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         QUIC listener filters can be specified when :ref:`quic_options
         <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is
         specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         They are processed sequentially right before connection creation. And like TCP Listener filters, they can be used to manipulate the connection metadata and socket. But the difference is that they can't be used to pause connection creation.
         
        repeated .envoy.config.listener.v3.ListenerFilter listener_filters = 9;
      • addListenerFilters

        public Listener.Builder addListenerFilters​(int index,
                                                   ListenerFilter.Builder builderForValue)
         Listener filters have the opportunity to manipulate and augment the connection metadata that
         is used in connection filter chain matching, for example. These filters are run before any in
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>`. Order matters as the
         filters are processed sequentially right after a socket has been accepted by the listener, and
         before a connection is created.
         UDP Listener filters can be specified when the protocol in the listener socket address in
         :ref:`protocol <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>` and no
         :ref:`quic_options <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         QUIC listener filters can be specified when :ref:`quic_options
         <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is
         specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         They are processed sequentially right before connection creation. And like TCP Listener filters, they can be used to manipulate the connection metadata and socket. But the difference is that they can't be used to pause connection creation.
         
        repeated .envoy.config.listener.v3.ListenerFilter listener_filters = 9;
      • addAllListenerFilters

        public Listener.Builder addAllListenerFilters​(java.lang.Iterable<? extends ListenerFilter> values)
         Listener filters have the opportunity to manipulate and augment the connection metadata that
         is used in connection filter chain matching, for example. These filters are run before any in
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>`. Order matters as the
         filters are processed sequentially right after a socket has been accepted by the listener, and
         before a connection is created.
         UDP Listener filters can be specified when the protocol in the listener socket address in
         :ref:`protocol <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>` and no
         :ref:`quic_options <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         QUIC listener filters can be specified when :ref:`quic_options
         <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is
         specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         They are processed sequentially right before connection creation. And like TCP Listener filters, they can be used to manipulate the connection metadata and socket. But the difference is that they can't be used to pause connection creation.
         
        repeated .envoy.config.listener.v3.ListenerFilter listener_filters = 9;
      • clearListenerFilters

        public Listener.Builder clearListenerFilters()
         Listener filters have the opportunity to manipulate and augment the connection metadata that
         is used in connection filter chain matching, for example. These filters are run before any in
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>`. Order matters as the
         filters are processed sequentially right after a socket has been accepted by the listener, and
         before a connection is created.
         UDP Listener filters can be specified when the protocol in the listener socket address in
         :ref:`protocol <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>` and no
         :ref:`quic_options <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         QUIC listener filters can be specified when :ref:`quic_options
         <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is
         specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         They are processed sequentially right before connection creation. And like TCP Listener filters, they can be used to manipulate the connection metadata and socket. But the difference is that they can't be used to pause connection creation.
         
        repeated .envoy.config.listener.v3.ListenerFilter listener_filters = 9;
      • removeListenerFilters

        public Listener.Builder removeListenerFilters​(int index)
         Listener filters have the opportunity to manipulate and augment the connection metadata that
         is used in connection filter chain matching, for example. These filters are run before any in
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>`. Order matters as the
         filters are processed sequentially right after a socket has been accepted by the listener, and
         before a connection is created.
         UDP Listener filters can be specified when the protocol in the listener socket address in
         :ref:`protocol <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>` and no
         :ref:`quic_options <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         QUIC listener filters can be specified when :ref:`quic_options
         <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is
         specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         They are processed sequentially right before connection creation. And like TCP Listener filters, they can be used to manipulate the connection metadata and socket. But the difference is that they can't be used to pause connection creation.
         
        repeated .envoy.config.listener.v3.ListenerFilter listener_filters = 9;
      • getListenerFiltersBuilder

        public ListenerFilter.Builder getListenerFiltersBuilder​(int index)
         Listener filters have the opportunity to manipulate and augment the connection metadata that
         is used in connection filter chain matching, for example. These filters are run before any in
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>`. Order matters as the
         filters are processed sequentially right after a socket has been accepted by the listener, and
         before a connection is created.
         UDP Listener filters can be specified when the protocol in the listener socket address in
         :ref:`protocol <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>` and no
         :ref:`quic_options <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         QUIC listener filters can be specified when :ref:`quic_options
         <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is
         specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         They are processed sequentially right before connection creation. And like TCP Listener filters, they can be used to manipulate the connection metadata and socket. But the difference is that they can't be used to pause connection creation.
         
        repeated .envoy.config.listener.v3.ListenerFilter listener_filters = 9;
      • getListenerFiltersOrBuilder

        public ListenerFilterOrBuilder getListenerFiltersOrBuilder​(int index)
         Listener filters have the opportunity to manipulate and augment the connection metadata that
         is used in connection filter chain matching, for example. These filters are run before any in
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>`. Order matters as the
         filters are processed sequentially right after a socket has been accepted by the listener, and
         before a connection is created.
         UDP Listener filters can be specified when the protocol in the listener socket address in
         :ref:`protocol <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>` and no
         :ref:`quic_options <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         QUIC listener filters can be specified when :ref:`quic_options
         <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is
         specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         They are processed sequentially right before connection creation. And like TCP Listener filters, they can be used to manipulate the connection metadata and socket. But the difference is that they can't be used to pause connection creation.
         
        repeated .envoy.config.listener.v3.ListenerFilter listener_filters = 9;
        Specified by:
        getListenerFiltersOrBuilder in interface ListenerOrBuilder
      • getListenerFiltersOrBuilderList

        public java.util.List<? extends ListenerFilterOrBuilder> getListenerFiltersOrBuilderList()
         Listener filters have the opportunity to manipulate and augment the connection metadata that
         is used in connection filter chain matching, for example. These filters are run before any in
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>`. Order matters as the
         filters are processed sequentially right after a socket has been accepted by the listener, and
         before a connection is created.
         UDP Listener filters can be specified when the protocol in the listener socket address in
         :ref:`protocol <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>` and no
         :ref:`quic_options <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         QUIC listener filters can be specified when :ref:`quic_options
         <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is
         specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         They are processed sequentially right before connection creation. And like TCP Listener filters, they can be used to manipulate the connection metadata and socket. But the difference is that they can't be used to pause connection creation.
         
        repeated .envoy.config.listener.v3.ListenerFilter listener_filters = 9;
        Specified by:
        getListenerFiltersOrBuilderList in interface ListenerOrBuilder
      • addListenerFiltersBuilder

        public ListenerFilter.Builder addListenerFiltersBuilder()
         Listener filters have the opportunity to manipulate and augment the connection metadata that
         is used in connection filter chain matching, for example. These filters are run before any in
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>`. Order matters as the
         filters are processed sequentially right after a socket has been accepted by the listener, and
         before a connection is created.
         UDP Listener filters can be specified when the protocol in the listener socket address in
         :ref:`protocol <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>` and no
         :ref:`quic_options <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         QUIC listener filters can be specified when :ref:`quic_options
         <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is
         specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         They are processed sequentially right before connection creation. And like TCP Listener filters, they can be used to manipulate the connection metadata and socket. But the difference is that they can't be used to pause connection creation.
         
        repeated .envoy.config.listener.v3.ListenerFilter listener_filters = 9;
      • addListenerFiltersBuilder

        public ListenerFilter.Builder addListenerFiltersBuilder​(int index)
         Listener filters have the opportunity to manipulate and augment the connection metadata that
         is used in connection filter chain matching, for example. These filters are run before any in
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>`. Order matters as the
         filters are processed sequentially right after a socket has been accepted by the listener, and
         before a connection is created.
         UDP Listener filters can be specified when the protocol in the listener socket address in
         :ref:`protocol <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>` and no
         :ref:`quic_options <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         QUIC listener filters can be specified when :ref:`quic_options
         <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is
         specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         They are processed sequentially right before connection creation. And like TCP Listener filters, they can be used to manipulate the connection metadata and socket. But the difference is that they can't be used to pause connection creation.
         
        repeated .envoy.config.listener.v3.ListenerFilter listener_filters = 9;
      • getListenerFiltersBuilderList

        public java.util.List<ListenerFilter.Builder> getListenerFiltersBuilderList()
         Listener filters have the opportunity to manipulate and augment the connection metadata that
         is used in connection filter chain matching, for example. These filters are run before any in
         :ref:`filter_chains <envoy_v3_api_field_config.listener.v3.Listener.filter_chains>`. Order matters as the
         filters are processed sequentially right after a socket has been accepted by the listener, and
         before a connection is created.
         UDP Listener filters can be specified when the protocol in the listener socket address in
         :ref:`protocol <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>` and no
         :ref:`quic_options <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         QUIC listener filters can be specified when :ref:`quic_options
         <envoy_v3_api_field_config.listener.v3.UdpListenerConfig.quic_options>` is
         specified in :ref:`udp_listener_config <envoy_v3_api_field_config.listener.v3.Listener.udp_listener_config>`.
         They are processed sequentially right before connection creation. And like TCP Listener filters, they can be used to manipulate the connection metadata and socket. But the difference is that they can't be used to pause connection creation.
         
        repeated .envoy.config.listener.v3.ListenerFilter listener_filters = 9;
      • hasListenerFiltersTimeout

        public boolean hasListenerFiltersTimeout()
         The timeout to wait for all listener filters to complete operation. If the timeout is reached,
         the accepted socket is closed without a connection being created unless
         ``continue_on_listener_filters_timeout`` is set to true. Specify 0 to disable the
         timeout. If not specified, a default timeout of 15s is used.
         
        .google.protobuf.Duration listener_filters_timeout = 15;
        Specified by:
        hasListenerFiltersTimeout in interface ListenerOrBuilder
        Returns:
        Whether the listenerFiltersTimeout field is set.
      • getListenerFiltersTimeout

        public com.google.protobuf.Duration getListenerFiltersTimeout()
         The timeout to wait for all listener filters to complete operation. If the timeout is reached,
         the accepted socket is closed without a connection being created unless
         ``continue_on_listener_filters_timeout`` is set to true. Specify 0 to disable the
         timeout. If not specified, a default timeout of 15s is used.
         
        .google.protobuf.Duration listener_filters_timeout = 15;
        Specified by:
        getListenerFiltersTimeout in interface ListenerOrBuilder
        Returns:
        The listenerFiltersTimeout.
      • setListenerFiltersTimeout

        public Listener.Builder setListenerFiltersTimeout​(com.google.protobuf.Duration value)
         The timeout to wait for all listener filters to complete operation. If the timeout is reached,
         the accepted socket is closed without a connection being created unless
         ``continue_on_listener_filters_timeout`` is set to true. Specify 0 to disable the
         timeout. If not specified, a default timeout of 15s is used.
         
        .google.protobuf.Duration listener_filters_timeout = 15;
      • setListenerFiltersTimeout

        public Listener.Builder setListenerFiltersTimeout​(com.google.protobuf.Duration.Builder builderForValue)
         The timeout to wait for all listener filters to complete operation. If the timeout is reached,
         the accepted socket is closed without a connection being created unless
         ``continue_on_listener_filters_timeout`` is set to true. Specify 0 to disable the
         timeout. If not specified, a default timeout of 15s is used.
         
        .google.protobuf.Duration listener_filters_timeout = 15;
      • mergeListenerFiltersTimeout

        public Listener.Builder mergeListenerFiltersTimeout​(com.google.protobuf.Duration value)
         The timeout to wait for all listener filters to complete operation. If the timeout is reached,
         the accepted socket is closed without a connection being created unless
         ``continue_on_listener_filters_timeout`` is set to true. Specify 0 to disable the
         timeout. If not specified, a default timeout of 15s is used.
         
        .google.protobuf.Duration listener_filters_timeout = 15;
      • clearListenerFiltersTimeout

        public Listener.Builder clearListenerFiltersTimeout()
         The timeout to wait for all listener filters to complete operation. If the timeout is reached,
         the accepted socket is closed without a connection being created unless
         ``continue_on_listener_filters_timeout`` is set to true. Specify 0 to disable the
         timeout. If not specified, a default timeout of 15s is used.
         
        .google.protobuf.Duration listener_filters_timeout = 15;
      • getListenerFiltersTimeoutBuilder

        public com.google.protobuf.Duration.Builder getListenerFiltersTimeoutBuilder()
         The timeout to wait for all listener filters to complete operation. If the timeout is reached,
         the accepted socket is closed without a connection being created unless
         ``continue_on_listener_filters_timeout`` is set to true. Specify 0 to disable the
         timeout. If not specified, a default timeout of 15s is used.
         
        .google.protobuf.Duration listener_filters_timeout = 15;
      • getListenerFiltersTimeoutOrBuilder

        public com.google.protobuf.DurationOrBuilder getListenerFiltersTimeoutOrBuilder()
         The timeout to wait for all listener filters to complete operation. If the timeout is reached,
         the accepted socket is closed without a connection being created unless
         ``continue_on_listener_filters_timeout`` is set to true. Specify 0 to disable the
         timeout. If not specified, a default timeout of 15s is used.
         
        .google.protobuf.Duration listener_filters_timeout = 15;
        Specified by:
        getListenerFiltersTimeoutOrBuilder in interface ListenerOrBuilder
      • getListenerFiltersTimeoutFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,​com.google.protobuf.Duration.Builder,​com.google.protobuf.DurationOrBuilder> getListenerFiltersTimeoutFieldBuilder()
         The timeout to wait for all listener filters to complete operation. If the timeout is reached,
         the accepted socket is closed without a connection being created unless
         ``continue_on_listener_filters_timeout`` is set to true. Specify 0 to disable the
         timeout. If not specified, a default timeout of 15s is used.
         
        .google.protobuf.Duration listener_filters_timeout = 15;
      • getContinueOnListenerFiltersTimeout

        public boolean getContinueOnListenerFiltersTimeout()
         Whether a connection should be created when listener filters timeout. Default is false.
        
         .. attention::
        
         Some listener filters, such as :ref:`Proxy Protocol filter
         <config_listener_filters_proxy_protocol>`, should not be used with this option. It will cause
         unexpected behavior when a connection is created.
         
        bool continue_on_listener_filters_timeout = 17;
        Specified by:
        getContinueOnListenerFiltersTimeout in interface ListenerOrBuilder
        Returns:
        The continueOnListenerFiltersTimeout.
      • setContinueOnListenerFiltersTimeout

        public Listener.Builder setContinueOnListenerFiltersTimeout​(boolean value)
         Whether a connection should be created when listener filters timeout. Default is false.
        
         .. attention::
        
         Some listener filters, such as :ref:`Proxy Protocol filter
         <config_listener_filters_proxy_protocol>`, should not be used with this option. It will cause
         unexpected behavior when a connection is created.
         
        bool continue_on_listener_filters_timeout = 17;
        Parameters:
        value - The continueOnListenerFiltersTimeout to set.
        Returns:
        This builder for chaining.
      • clearContinueOnListenerFiltersTimeout

        public Listener.Builder clearContinueOnListenerFiltersTimeout()
         Whether a connection should be created when listener filters timeout. Default is false.
        
         .. attention::
        
         Some listener filters, such as :ref:`Proxy Protocol filter
         <config_listener_filters_proxy_protocol>`, should not be used with this option. It will cause
         unexpected behavior when a connection is created.
         
        bool continue_on_listener_filters_timeout = 17;
        Returns:
        This builder for chaining.
      • hasTransparent

        public boolean hasTransparent()
         Whether the listener should be set as a transparent socket.
         When this flag is set to true, connections can be redirected to the listener using an
         ``iptables`` ``TPROXY`` target, in which case the original source and destination addresses and
         ports are preserved on accepted connections. This flag should be used in combination with
         :ref:`an original_dst <config_listener_filters_original_dst>` :ref:`listener filter
         <envoy_v3_api_field_config.listener.v3.Listener.listener_filters>` to mark the connections' local addresses as
         "restored." This can be used to hand off each redirected connection to another listener
         associated with the connection's destination address. Direct connections to the socket without
         using ``TPROXY`` cannot be distinguished from connections redirected using ``TPROXY`` and are
         therefore treated as if they were redirected.
         When this flag is set to false, the listener's socket is explicitly reset as non-transparent.
         Setting this flag requires Envoy to run with the ``CAP_NET_ADMIN`` capability.
         When this flag is not set (default), the socket is not modified, i.e. the transparent option
         is neither set nor reset.
         
        .google.protobuf.BoolValue transparent = 10;
        Specified by:
        hasTransparent in interface ListenerOrBuilder
        Returns:
        Whether the transparent field is set.
      • getTransparent

        public com.google.protobuf.BoolValue getTransparent()
         Whether the listener should be set as a transparent socket.
         When this flag is set to true, connections can be redirected to the listener using an
         ``iptables`` ``TPROXY`` target, in which case the original source and destination addresses and
         ports are preserved on accepted connections. This flag should be used in combination with
         :ref:`an original_dst <config_listener_filters_original_dst>` :ref:`listener filter
         <envoy_v3_api_field_config.listener.v3.Listener.listener_filters>` to mark the connections' local addresses as
         "restored." This can be used to hand off each redirected connection to another listener
         associated with the connection's destination address. Direct connections to the socket without
         using ``TPROXY`` cannot be distinguished from connections redirected using ``TPROXY`` and are
         therefore treated as if they were redirected.
         When this flag is set to false, the listener's socket is explicitly reset as non-transparent.
         Setting this flag requires Envoy to run with the ``CAP_NET_ADMIN`` capability.
         When this flag is not set (default), the socket is not modified, i.e. the transparent option
         is neither set nor reset.
         
        .google.protobuf.BoolValue transparent = 10;
        Specified by:
        getTransparent in interface ListenerOrBuilder
        Returns:
        The transparent.
      • setTransparent

        public Listener.Builder setTransparent​(com.google.protobuf.BoolValue value)
         Whether the listener should be set as a transparent socket.
         When this flag is set to true, connections can be redirected to the listener using an
         ``iptables`` ``TPROXY`` target, in which case the original source and destination addresses and
         ports are preserved on accepted connections. This flag should be used in combination with
         :ref:`an original_dst <config_listener_filters_original_dst>` :ref:`listener filter
         <envoy_v3_api_field_config.listener.v3.Listener.listener_filters>` to mark the connections' local addresses as
         "restored." This can be used to hand off each redirected connection to another listener
         associated with the connection's destination address. Direct connections to the socket without
         using ``TPROXY`` cannot be distinguished from connections redirected using ``TPROXY`` and are
         therefore treated as if they were redirected.
         When this flag is set to false, the listener's socket is explicitly reset as non-transparent.
         Setting this flag requires Envoy to run with the ``CAP_NET_ADMIN`` capability.
         When this flag is not set (default), the socket is not modified, i.e. the transparent option
         is neither set nor reset.
         
        .google.protobuf.BoolValue transparent = 10;
      • setTransparent

        public Listener.Builder setTransparent​(com.google.protobuf.BoolValue.Builder builderForValue)
         Whether the listener should be set as a transparent socket.
         When this flag is set to true, connections can be redirected to the listener using an
         ``iptables`` ``TPROXY`` target, in which case the original source and destination addresses and
         ports are preserved on accepted connections. This flag should be used in combination with
         :ref:`an original_dst <config_listener_filters_original_dst>` :ref:`listener filter
         <envoy_v3_api_field_config.listener.v3.Listener.listener_filters>` to mark the connections' local addresses as
         "restored." This can be used to hand off each redirected connection to another listener
         associated with the connection's destination address. Direct connections to the socket without
         using ``TPROXY`` cannot be distinguished from connections redirected using ``TPROXY`` and are
         therefore treated as if they were redirected.
         When this flag is set to false, the listener's socket is explicitly reset as non-transparent.
         Setting this flag requires Envoy to run with the ``CAP_NET_ADMIN`` capability.
         When this flag is not set (default), the socket is not modified, i.e. the transparent option
         is neither set nor reset.
         
        .google.protobuf.BoolValue transparent = 10;
      • mergeTransparent

        public Listener.Builder mergeTransparent​(com.google.protobuf.BoolValue value)
         Whether the listener should be set as a transparent socket.
         When this flag is set to true, connections can be redirected to the listener using an
         ``iptables`` ``TPROXY`` target, in which case the original source and destination addresses and
         ports are preserved on accepted connections. This flag should be used in combination with
         :ref:`an original_dst <config_listener_filters_original_dst>` :ref:`listener filter
         <envoy_v3_api_field_config.listener.v3.Listener.listener_filters>` to mark the connections' local addresses as
         "restored." This can be used to hand off each redirected connection to another listener
         associated with the connection's destination address. Direct connections to the socket without
         using ``TPROXY`` cannot be distinguished from connections redirected using ``TPROXY`` and are
         therefore treated as if they were redirected.
         When this flag is set to false, the listener's socket is explicitly reset as non-transparent.
         Setting this flag requires Envoy to run with the ``CAP_NET_ADMIN`` capability.
         When this flag is not set (default), the socket is not modified, i.e. the transparent option
         is neither set nor reset.
         
        .google.protobuf.BoolValue transparent = 10;
      • clearTransparent

        public Listener.Builder clearTransparent()
         Whether the listener should be set as a transparent socket.
         When this flag is set to true, connections can be redirected to the listener using an
         ``iptables`` ``TPROXY`` target, in which case the original source and destination addresses and
         ports are preserved on accepted connections. This flag should be used in combination with
         :ref:`an original_dst <config_listener_filters_original_dst>` :ref:`listener filter
         <envoy_v3_api_field_config.listener.v3.Listener.listener_filters>` to mark the connections' local addresses as
         "restored." This can be used to hand off each redirected connection to another listener
         associated with the connection's destination address. Direct connections to the socket without
         using ``TPROXY`` cannot be distinguished from connections redirected using ``TPROXY`` and are
         therefore treated as if they were redirected.
         When this flag is set to false, the listener's socket is explicitly reset as non-transparent.
         Setting this flag requires Envoy to run with the ``CAP_NET_ADMIN`` capability.
         When this flag is not set (default), the socket is not modified, i.e. the transparent option
         is neither set nor reset.
         
        .google.protobuf.BoolValue transparent = 10;
      • getTransparentBuilder

        public com.google.protobuf.BoolValue.Builder getTransparentBuilder()
         Whether the listener should be set as a transparent socket.
         When this flag is set to true, connections can be redirected to the listener using an
         ``iptables`` ``TPROXY`` target, in which case the original source and destination addresses and
         ports are preserved on accepted connections. This flag should be used in combination with
         :ref:`an original_dst <config_listener_filters_original_dst>` :ref:`listener filter
         <envoy_v3_api_field_config.listener.v3.Listener.listener_filters>` to mark the connections' local addresses as
         "restored." This can be used to hand off each redirected connection to another listener
         associated with the connection's destination address. Direct connections to the socket without
         using ``TPROXY`` cannot be distinguished from connections redirected using ``TPROXY`` and are
         therefore treated as if they were redirected.
         When this flag is set to false, the listener's socket is explicitly reset as non-transparent.
         Setting this flag requires Envoy to run with the ``CAP_NET_ADMIN`` capability.
         When this flag is not set (default), the socket is not modified, i.e. the transparent option
         is neither set nor reset.
         
        .google.protobuf.BoolValue transparent = 10;
      • getTransparentOrBuilder

        public com.google.protobuf.BoolValueOrBuilder getTransparentOrBuilder()
         Whether the listener should be set as a transparent socket.
         When this flag is set to true, connections can be redirected to the listener using an
         ``iptables`` ``TPROXY`` target, in which case the original source and destination addresses and
         ports are preserved on accepted connections. This flag should be used in combination with
         :ref:`an original_dst <config_listener_filters_original_dst>` :ref:`listener filter
         <envoy_v3_api_field_config.listener.v3.Listener.listener_filters>` to mark the connections' local addresses as
         "restored." This can be used to hand off each redirected connection to another listener
         associated with the connection's destination address. Direct connections to the socket without
         using ``TPROXY`` cannot be distinguished from connections redirected using ``TPROXY`` and are
         therefore treated as if they were redirected.
         When this flag is set to false, the listener's socket is explicitly reset as non-transparent.
         Setting this flag requires Envoy to run with the ``CAP_NET_ADMIN`` capability.
         When this flag is not set (default), the socket is not modified, i.e. the transparent option
         is neither set nor reset.
         
        .google.protobuf.BoolValue transparent = 10;
        Specified by:
        getTransparentOrBuilder in interface ListenerOrBuilder
      • getTransparentFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,​com.google.protobuf.BoolValue.Builder,​com.google.protobuf.BoolValueOrBuilder> getTransparentFieldBuilder()
         Whether the listener should be set as a transparent socket.
         When this flag is set to true, connections can be redirected to the listener using an
         ``iptables`` ``TPROXY`` target, in which case the original source and destination addresses and
         ports are preserved on accepted connections. This flag should be used in combination with
         :ref:`an original_dst <config_listener_filters_original_dst>` :ref:`listener filter
         <envoy_v3_api_field_config.listener.v3.Listener.listener_filters>` to mark the connections' local addresses as
         "restored." This can be used to hand off each redirected connection to another listener
         associated with the connection's destination address. Direct connections to the socket without
         using ``TPROXY`` cannot be distinguished from connections redirected using ``TPROXY`` and are
         therefore treated as if they were redirected.
         When this flag is set to false, the listener's socket is explicitly reset as non-transparent.
         Setting this flag requires Envoy to run with the ``CAP_NET_ADMIN`` capability.
         When this flag is not set (default), the socket is not modified, i.e. the transparent option
         is neither set nor reset.
         
        .google.protobuf.BoolValue transparent = 10;
      • hasFreebind

        public boolean hasFreebind()
         Whether the listener should set the ``IP_FREEBIND`` socket option. When this
         flag is set to true, listeners can be bound to an IP address that is not
         configured on the system running Envoy. When this flag is set to false, the
         option ``IP_FREEBIND`` is disabled on the socket. When this flag is not set
         (default), the socket is not modified, i.e. the option is neither enabled
         nor disabled.
         
        .google.protobuf.BoolValue freebind = 11;
        Specified by:
        hasFreebind in interface ListenerOrBuilder
        Returns:
        Whether the freebind field is set.
      • getFreebind

        public com.google.protobuf.BoolValue getFreebind()
         Whether the listener should set the ``IP_FREEBIND`` socket option. When this
         flag is set to true, listeners can be bound to an IP address that is not
         configured on the system running Envoy. When this flag is set to false, the
         option ``IP_FREEBIND`` is disabled on the socket. When this flag is not set
         (default), the socket is not modified, i.e. the option is neither enabled
         nor disabled.
         
        .google.protobuf.BoolValue freebind = 11;
        Specified by:
        getFreebind in interface ListenerOrBuilder
        Returns:
        The freebind.
      • setFreebind

        public Listener.Builder setFreebind​(com.google.protobuf.BoolValue value)
         Whether the listener should set the ``IP_FREEBIND`` socket option. When this
         flag is set to true, listeners can be bound to an IP address that is not
         configured on the system running Envoy. When this flag is set to false, the
         option ``IP_FREEBIND`` is disabled on the socket. When this flag is not set
         (default), the socket is not modified, i.e. the option is neither enabled
         nor disabled.
         
        .google.protobuf.BoolValue freebind = 11;
      • setFreebind

        public Listener.Builder setFreebind​(com.google.protobuf.BoolValue.Builder builderForValue)
         Whether the listener should set the ``IP_FREEBIND`` socket option. When this
         flag is set to true, listeners can be bound to an IP address that is not
         configured on the system running Envoy. When this flag is set to false, the
         option ``IP_FREEBIND`` is disabled on the socket. When this flag is not set
         (default), the socket is not modified, i.e. the option is neither enabled
         nor disabled.
         
        .google.protobuf.BoolValue freebind = 11;
      • mergeFreebind

        public Listener.Builder mergeFreebind​(com.google.protobuf.BoolValue value)
         Whether the listener should set the ``IP_FREEBIND`` socket option. When this
         flag is set to true, listeners can be bound to an IP address that is not
         configured on the system running Envoy. When this flag is set to false, the
         option ``IP_FREEBIND`` is disabled on the socket. When this flag is not set
         (default), the socket is not modified, i.e. the option is neither enabled
         nor disabled.
         
        .google.protobuf.BoolValue freebind = 11;
      • clearFreebind

        public Listener.Builder clearFreebind()
         Whether the listener should set the ``IP_FREEBIND`` socket option. When this
         flag is set to true, listeners can be bound to an IP address that is not
         configured on the system running Envoy. When this flag is set to false, the
         option ``IP_FREEBIND`` is disabled on the socket. When this flag is not set
         (default), the socket is not modified, i.e. the option is neither enabled
         nor disabled.
         
        .google.protobuf.BoolValue freebind = 11;
      • getFreebindBuilder

        public com.google.protobuf.BoolValue.Builder getFreebindBuilder()
         Whether the listener should set the ``IP_FREEBIND`` socket option. When this
         flag is set to true, listeners can be bound to an IP address that is not
         configured on the system running Envoy. When this flag is set to false, the
         option ``IP_FREEBIND`` is disabled on the socket. When this flag is not set
         (default), the socket is not modified, i.e. the option is neither enabled
         nor disabled.
         
        .google.protobuf.BoolValue freebind = 11;
      • getFreebindOrBuilder

        public com.google.protobuf.BoolValueOrBuilder getFreebindOrBuilder()
         Whether the listener should set the ``IP_FREEBIND`` socket option. When this
         flag is set to true, listeners can be bound to an IP address that is not
         configured on the system running Envoy. When this flag is set to false, the
         option ``IP_FREEBIND`` is disabled on the socket. When this flag is not set
         (default), the socket is not modified, i.e. the option is neither enabled
         nor disabled.
         
        .google.protobuf.BoolValue freebind = 11;
        Specified by:
        getFreebindOrBuilder in interface ListenerOrBuilder
      • getFreebindFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,​com.google.protobuf.BoolValue.Builder,​com.google.protobuf.BoolValueOrBuilder> getFreebindFieldBuilder()
         Whether the listener should set the ``IP_FREEBIND`` socket option. When this
         flag is set to true, listeners can be bound to an IP address that is not
         configured on the system running Envoy. When this flag is set to false, the
         option ``IP_FREEBIND`` is disabled on the socket. When this flag is not set
         (default), the socket is not modified, i.e. the option is neither enabled
         nor disabled.
         
        .google.protobuf.BoolValue freebind = 11;
      • ensureSocketOptionsIsMutable

        private void ensureSocketOptionsIsMutable()
      • getSocketOptionsList

        public java.util.List<SocketOption> getSocketOptionsList()
         Additional socket options that may not be present in Envoy source code or
         precompiled binaries. The socket options can be updated for a listener when
         :ref:`enable_reuse_port <envoy_v3_api_field_config.listener.v3.Listener.enable_reuse_port>`
         is ``true``. Otherwise, if socket options change during a listener update the update will be rejected
         to make it clear that the options were not updated.
         
        repeated .envoy.config.core.v3.SocketOption socket_options = 13;
        Specified by:
        getSocketOptionsList in interface ListenerOrBuilder
      • getSocketOptionsCount

        public int getSocketOptionsCount()
         Additional socket options that may not be present in Envoy source code or
         precompiled binaries. The socket options can be updated for a listener when
         :ref:`enable_reuse_port <envoy_v3_api_field_config.listener.v3.Listener.enable_reuse_port>`
         is ``true``. Otherwise, if socket options change during a listener update the update will be rejected
         to make it clear that the options were not updated.
         
        repeated .envoy.config.core.v3.SocketOption socket_options = 13;
        Specified by:
        getSocketOptionsCount in interface ListenerOrBuilder
      • getSocketOptions

        public SocketOption getSocketOptions​(int index)
         Additional socket options that may not be present in Envoy source code or
         precompiled binaries. The socket options can be updated for a listener when
         :ref:`enable_reuse_port <envoy_v3_api_field_config.listener.v3.Listener.enable_reuse_port>`
         is ``true``. Otherwise, if socket options change during a listener update the update will be rejected
         to make it clear that the options were not updated.
         
        repeated .envoy.config.core.v3.SocketOption socket_options = 13;
        Specified by:
        getSocketOptions in interface ListenerOrBuilder
      • setSocketOptions

        public Listener.Builder setSocketOptions​(int index,
                                                 SocketOption value)
         Additional socket options that may not be present in Envoy source code or
         precompiled binaries. The socket options can be updated for a listener when
         :ref:`enable_reuse_port <envoy_v3_api_field_config.listener.v3.Listener.enable_reuse_port>`
         is ``true``. Otherwise, if socket options change during a listener update the update will be rejected
         to make it clear that the options were not updated.
         
        repeated .envoy.config.core.v3.SocketOption socket_options = 13;
      • setSocketOptions

        public Listener.Builder setSocketOptions​(int index,
                                                 SocketOption.Builder builderForValue)
         Additional socket options that may not be present in Envoy source code or
         precompiled binaries. The socket options can be updated for a listener when
         :ref:`enable_reuse_port <envoy_v3_api_field_config.listener.v3.Listener.enable_reuse_port>`
         is ``true``. Otherwise, if socket options change during a listener update the update will be rejected
         to make it clear that the options were not updated.
         
        repeated .envoy.config.core.v3.SocketOption socket_options = 13;
      • addSocketOptions

        public Listener.Builder addSocketOptions​(SocketOption value)
         Additional socket options that may not be present in Envoy source code or
         precompiled binaries. The socket options can be updated for a listener when
         :ref:`enable_reuse_port <envoy_v3_api_field_config.listener.v3.Listener.enable_reuse_port>`
         is ``true``. Otherwise, if socket options change during a listener update the update will be rejected
         to make it clear that the options were not updated.
         
        repeated .envoy.config.core.v3.SocketOption socket_options = 13;
      • addSocketOptions

        public Listener.Builder addSocketOptions​(int index,
                                                 SocketOption value)
         Additional socket options that may not be present in Envoy source code or
         precompiled binaries. The socket options can be updated for a listener when
         :ref:`enable_reuse_port <envoy_v3_api_field_config.listener.v3.Listener.enable_reuse_port>`
         is ``true``. Otherwise, if socket options change during a listener update the update will be rejected
         to make it clear that the options were not updated.
         
        repeated .envoy.config.core.v3.SocketOption socket_options = 13;
      • addSocketOptions

        public Listener.Builder addSocketOptions​(SocketOption.Builder builderForValue)
         Additional socket options that may not be present in Envoy source code or
         precompiled binaries. The socket options can be updated for a listener when
         :ref:`enable_reuse_port <envoy_v3_api_field_config.listener.v3.Listener.enable_reuse_port>`
         is ``true``. Otherwise, if socket options change during a listener update the update will be rejected
         to make it clear that the options were not updated.
         
        repeated .envoy.config.core.v3.SocketOption socket_options = 13;
      • addSocketOptions

        public Listener.Builder addSocketOptions​(int index,
                                                 SocketOption.Builder builderForValue)
         Additional socket options that may not be present in Envoy source code or
         precompiled binaries. The socket options can be updated for a listener when
         :ref:`enable_reuse_port <envoy_v3_api_field_config.listener.v3.Listener.enable_reuse_port>`
         is ``true``. Otherwise, if socket options change during a listener update the update will be rejected
         to make it clear that the options were not updated.
         
        repeated .envoy.config.core.v3.SocketOption socket_options = 13;
      • addAllSocketOptions

        public Listener.Builder addAllSocketOptions​(java.lang.Iterable<? extends SocketOption> values)
         Additional socket options that may not be present in Envoy source code or
         precompiled binaries. The socket options can be updated for a listener when
         :ref:`enable_reuse_port <envoy_v3_api_field_config.listener.v3.Listener.enable_reuse_port>`
         is ``true``. Otherwise, if socket options change during a listener update the update will be rejected
         to make it clear that the options were not updated.
         
        repeated .envoy.config.core.v3.SocketOption socket_options = 13;
      • clearSocketOptions

        public Listener.Builder clearSocketOptions()
         Additional socket options that may not be present in Envoy source code or
         precompiled binaries. The socket options can be updated for a listener when
         :ref:`enable_reuse_port <envoy_v3_api_field_config.listener.v3.Listener.enable_reuse_port>`
         is ``true``. Otherwise, if socket options change during a listener update the update will be rejected
         to make it clear that the options were not updated.
         
        repeated .envoy.config.core.v3.SocketOption socket_options = 13;
      • removeSocketOptions

        public Listener.Builder removeSocketOptions​(int index)
         Additional socket options that may not be present in Envoy source code or
         precompiled binaries. The socket options can be updated for a listener when
         :ref:`enable_reuse_port <envoy_v3_api_field_config.listener.v3.Listener.enable_reuse_port>`
         is ``true``. Otherwise, if socket options change during a listener update the update will be rejected
         to make it clear that the options were not updated.
         
        repeated .envoy.config.core.v3.SocketOption socket_options = 13;
      • getSocketOptionsBuilder

        public SocketOption.Builder getSocketOptionsBuilder​(int index)
         Additional socket options that may not be present in Envoy source code or
         precompiled binaries. The socket options can be updated for a listener when
         :ref:`enable_reuse_port <envoy_v3_api_field_config.listener.v3.Listener.enable_reuse_port>`
         is ``true``. Otherwise, if socket options change during a listener update the update will be rejected
         to make it clear that the options were not updated.
         
        repeated .envoy.config.core.v3.SocketOption socket_options = 13;
      • getSocketOptionsOrBuilder

        public SocketOptionOrBuilder getSocketOptionsOrBuilder​(int index)
         Additional socket options that may not be present in Envoy source code or
         precompiled binaries. The socket options can be updated for a listener when
         :ref:`enable_reuse_port <envoy_v3_api_field_config.listener.v3.Listener.enable_reuse_port>`
         is ``true``. Otherwise, if socket options change during a listener update the update will be rejected
         to make it clear that the options were not updated.
         
        repeated .envoy.config.core.v3.SocketOption socket_options = 13;
        Specified by:
        getSocketOptionsOrBuilder in interface ListenerOrBuilder
      • getSocketOptionsOrBuilderList

        public java.util.List<? extends SocketOptionOrBuilder> getSocketOptionsOrBuilderList()
         Additional socket options that may not be present in Envoy source code or
         precompiled binaries. The socket options can be updated for a listener when
         :ref:`enable_reuse_port <envoy_v3_api_field_config.listener.v3.Listener.enable_reuse_port>`
         is ``true``. Otherwise, if socket options change during a listener update the update will be rejected
         to make it clear that the options were not updated.
         
        repeated .envoy.config.core.v3.SocketOption socket_options = 13;
        Specified by:
        getSocketOptionsOrBuilderList in interface ListenerOrBuilder
      • addSocketOptionsBuilder

        public SocketOption.Builder addSocketOptionsBuilder()
         Additional socket options that may not be present in Envoy source code or
         precompiled binaries. The socket options can be updated for a listener when
         :ref:`enable_reuse_port <envoy_v3_api_field_config.listener.v3.Listener.enable_reuse_port>`
         is ``true``. Otherwise, if socket options change during a listener update the update will be rejected
         to make it clear that the options were not updated.
         
        repeated .envoy.config.core.v3.SocketOption socket_options = 13;
      • addSocketOptionsBuilder

        public SocketOption.Builder addSocketOptionsBuilder​(int index)
         Additional socket options that may not be present in Envoy source code or
         precompiled binaries. The socket options can be updated for a listener when
         :ref:`enable_reuse_port <envoy_v3_api_field_config.listener.v3.Listener.enable_reuse_port>`
         is ``true``. Otherwise, if socket options change during a listener update the update will be rejected
         to make it clear that the options were not updated.
         
        repeated .envoy.config.core.v3.SocketOption socket_options = 13;
      • getSocketOptionsBuilderList

        public java.util.List<SocketOption.Builder> getSocketOptionsBuilderList()
         Additional socket options that may not be present in Envoy source code or
         precompiled binaries. The socket options can be updated for a listener when
         :ref:`enable_reuse_port <envoy_v3_api_field_config.listener.v3.Listener.enable_reuse_port>`
         is ``true``. Otherwise, if socket options change during a listener update the update will be rejected
         to make it clear that the options were not updated.
         
        repeated .envoy.config.core.v3.SocketOption socket_options = 13;
      • hasTcpFastOpenQueueLength

        public boolean hasTcpFastOpenQueueLength()
         Whether the listener should accept TCP Fast Open (TFO) connections.
         When this flag is set to a value greater than 0, the option TCP_FASTOPEN is enabled on
         the socket, with a queue length of the specified size
         (see `details in RFC7413 <https://tools.ietf.org/html/rfc7413#section-5.1>`_).
         When this flag is set to 0, the option TCP_FASTOPEN is disabled on the socket.
         When this flag is not set (default), the socket is not modified,
         i.e. the option is neither enabled nor disabled.
        
         On Linux, the net.ipv4.tcp_fastopen kernel parameter must include flag 0x2 to enable
         TCP_FASTOPEN.
         See `ip-sysctl.txt <https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt>`_.
        
         On macOS, only values of 0, 1, and unset are valid; other values may result in an error.
         To set the queue length on macOS, set the net.inet.tcp.fastopen_backlog kernel parameter.
         
        .google.protobuf.UInt32Value tcp_fast_open_queue_length = 12;
        Specified by:
        hasTcpFastOpenQueueLength in interface ListenerOrBuilder
        Returns:
        Whether the tcpFastOpenQueueLength field is set.
      • getTcpFastOpenQueueLength

        public com.google.protobuf.UInt32Value getTcpFastOpenQueueLength()
         Whether the listener should accept TCP Fast Open (TFO) connections.
         When this flag is set to a value greater than 0, the option TCP_FASTOPEN is enabled on
         the socket, with a queue length of the specified size
         (see `details in RFC7413 <https://tools.ietf.org/html/rfc7413#section-5.1>`_).
         When this flag is set to 0, the option TCP_FASTOPEN is disabled on the socket.
         When this flag is not set (default), the socket is not modified,
         i.e. the option is neither enabled nor disabled.
        
         On Linux, the net.ipv4.tcp_fastopen kernel parameter must include flag 0x2 to enable
         TCP_FASTOPEN.
         See `ip-sysctl.txt <https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt>`_.
        
         On macOS, only values of 0, 1, and unset are valid; other values may result in an error.
         To set the queue length on macOS, set the net.inet.tcp.fastopen_backlog kernel parameter.
         
        .google.protobuf.UInt32Value tcp_fast_open_queue_length = 12;
        Specified by:
        getTcpFastOpenQueueLength in interface ListenerOrBuilder
        Returns:
        The tcpFastOpenQueueLength.
      • setTcpFastOpenQueueLength

        public Listener.Builder setTcpFastOpenQueueLength​(com.google.protobuf.UInt32Value value)
         Whether the listener should accept TCP Fast Open (TFO) connections.
         When this flag is set to a value greater than 0, the option TCP_FASTOPEN is enabled on
         the socket, with a queue length of the specified size
         (see `details in RFC7413 <https://tools.ietf.org/html/rfc7413#section-5.1>`_).
         When this flag is set to 0, the option TCP_FASTOPEN is disabled on the socket.
         When this flag is not set (default), the socket is not modified,
         i.e. the option is neither enabled nor disabled.
        
         On Linux, the net.ipv4.tcp_fastopen kernel parameter must include flag 0x2 to enable
         TCP_FASTOPEN.
         See `ip-sysctl.txt <https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt>`_.
        
         On macOS, only values of 0, 1, and unset are valid; other values may result in an error.
         To set the queue length on macOS, set the net.inet.tcp.fastopen_backlog kernel parameter.
         
        .google.protobuf.UInt32Value tcp_fast_open_queue_length = 12;
      • setTcpFastOpenQueueLength

        public Listener.Builder setTcpFastOpenQueueLength​(com.google.protobuf.UInt32Value.Builder builderForValue)
         Whether the listener should accept TCP Fast Open (TFO) connections.
         When this flag is set to a value greater than 0, the option TCP_FASTOPEN is enabled on
         the socket, with a queue length of the specified size
         (see `details in RFC7413 <https://tools.ietf.org/html/rfc7413#section-5.1>`_).
         When this flag is set to 0, the option TCP_FASTOPEN is disabled on the socket.
         When this flag is not set (default), the socket is not modified,
         i.e. the option is neither enabled nor disabled.
        
         On Linux, the net.ipv4.tcp_fastopen kernel parameter must include flag 0x2 to enable
         TCP_FASTOPEN.
         See `ip-sysctl.txt <https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt>`_.
        
         On macOS, only values of 0, 1, and unset are valid; other values may result in an error.
         To set the queue length on macOS, set the net.inet.tcp.fastopen_backlog kernel parameter.
         
        .google.protobuf.UInt32Value tcp_fast_open_queue_length = 12;
      • mergeTcpFastOpenQueueLength

        public Listener.Builder mergeTcpFastOpenQueueLength​(com.google.protobuf.UInt32Value value)
         Whether the listener should accept TCP Fast Open (TFO) connections.
         When this flag is set to a value greater than 0, the option TCP_FASTOPEN is enabled on
         the socket, with a queue length of the specified size
         (see `details in RFC7413 <https://tools.ietf.org/html/rfc7413#section-5.1>`_).
         When this flag is set to 0, the option TCP_FASTOPEN is disabled on the socket.
         When this flag is not set (default), the socket is not modified,
         i.e. the option is neither enabled nor disabled.
        
         On Linux, the net.ipv4.tcp_fastopen kernel parameter must include flag 0x2 to enable
         TCP_FASTOPEN.
         See `ip-sysctl.txt <https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt>`_.
        
         On macOS, only values of 0, 1, and unset are valid; other values may result in an error.
         To set the queue length on macOS, set the net.inet.tcp.fastopen_backlog kernel parameter.
         
        .google.protobuf.UInt32Value tcp_fast_open_queue_length = 12;
      • clearTcpFastOpenQueueLength

        public Listener.Builder clearTcpFastOpenQueueLength()
         Whether the listener should accept TCP Fast Open (TFO) connections.
         When this flag is set to a value greater than 0, the option TCP_FASTOPEN is enabled on
         the socket, with a queue length of the specified size
         (see `details in RFC7413 <https://tools.ietf.org/html/rfc7413#section-5.1>`_).
         When this flag is set to 0, the option TCP_FASTOPEN is disabled on the socket.
         When this flag is not set (default), the socket is not modified,
         i.e. the option is neither enabled nor disabled.
        
         On Linux, the net.ipv4.tcp_fastopen kernel parameter must include flag 0x2 to enable
         TCP_FASTOPEN.
         See `ip-sysctl.txt <https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt>`_.
        
         On macOS, only values of 0, 1, and unset are valid; other values may result in an error.
         To set the queue length on macOS, set the net.inet.tcp.fastopen_backlog kernel parameter.
         
        .google.protobuf.UInt32Value tcp_fast_open_queue_length = 12;
      • getTcpFastOpenQueueLengthBuilder

        public com.google.protobuf.UInt32Value.Builder getTcpFastOpenQueueLengthBuilder()
         Whether the listener should accept TCP Fast Open (TFO) connections.
         When this flag is set to a value greater than 0, the option TCP_FASTOPEN is enabled on
         the socket, with a queue length of the specified size
         (see `details in RFC7413 <https://tools.ietf.org/html/rfc7413#section-5.1>`_).
         When this flag is set to 0, the option TCP_FASTOPEN is disabled on the socket.
         When this flag is not set (default), the socket is not modified,
         i.e. the option is neither enabled nor disabled.
        
         On Linux, the net.ipv4.tcp_fastopen kernel parameter must include flag 0x2 to enable
         TCP_FASTOPEN.
         See `ip-sysctl.txt <https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt>`_.
        
         On macOS, only values of 0, 1, and unset are valid; other values may result in an error.
         To set the queue length on macOS, set the net.inet.tcp.fastopen_backlog kernel parameter.
         
        .google.protobuf.UInt32Value tcp_fast_open_queue_length = 12;
      • getTcpFastOpenQueueLengthOrBuilder

        public com.google.protobuf.UInt32ValueOrBuilder getTcpFastOpenQueueLengthOrBuilder()
         Whether the listener should accept TCP Fast Open (TFO) connections.
         When this flag is set to a value greater than 0, the option TCP_FASTOPEN is enabled on
         the socket, with a queue length of the specified size
         (see `details in RFC7413 <https://tools.ietf.org/html/rfc7413#section-5.1>`_).
         When this flag is set to 0, the option TCP_FASTOPEN is disabled on the socket.
         When this flag is not set (default), the socket is not modified,
         i.e. the option is neither enabled nor disabled.
        
         On Linux, the net.ipv4.tcp_fastopen kernel parameter must include flag 0x2 to enable
         TCP_FASTOPEN.
         See `ip-sysctl.txt <https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt>`_.
        
         On macOS, only values of 0, 1, and unset are valid; other values may result in an error.
         To set the queue length on macOS, set the net.inet.tcp.fastopen_backlog kernel parameter.
         
        .google.protobuf.UInt32Value tcp_fast_open_queue_length = 12;
        Specified by:
        getTcpFastOpenQueueLengthOrBuilder in interface ListenerOrBuilder
      • getTcpFastOpenQueueLengthFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.UInt32Value,​com.google.protobuf.UInt32Value.Builder,​com.google.protobuf.UInt32ValueOrBuilder> getTcpFastOpenQueueLengthFieldBuilder()
         Whether the listener should accept TCP Fast Open (TFO) connections.
         When this flag is set to a value greater than 0, the option TCP_FASTOPEN is enabled on
         the socket, with a queue length of the specified size
         (see `details in RFC7413 <https://tools.ietf.org/html/rfc7413#section-5.1>`_).
         When this flag is set to 0, the option TCP_FASTOPEN is disabled on the socket.
         When this flag is not set (default), the socket is not modified,
         i.e. the option is neither enabled nor disabled.
        
         On Linux, the net.ipv4.tcp_fastopen kernel parameter must include flag 0x2 to enable
         TCP_FASTOPEN.
         See `ip-sysctl.txt <https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt>`_.
        
         On macOS, only values of 0, 1, and unset are valid; other values may result in an error.
         To set the queue length on macOS, set the net.inet.tcp.fastopen_backlog kernel parameter.
         
        .google.protobuf.UInt32Value tcp_fast_open_queue_length = 12;
      • getTrafficDirectionValue

        public int getTrafficDirectionValue()
         Specifies the intended direction of the traffic relative to the local Envoy.
         This property is required on Windows for listeners using the original destination filter,
         see :ref:`Original Destination <config_listener_filters_original_dst>`.
         
        .envoy.config.core.v3.TrafficDirection traffic_direction = 16;
        Specified by:
        getTrafficDirectionValue in interface ListenerOrBuilder
        Returns:
        The enum numeric value on the wire for trafficDirection.
      • setTrafficDirectionValue

        public Listener.Builder setTrafficDirectionValue​(int value)
         Specifies the intended direction of the traffic relative to the local Envoy.
         This property is required on Windows for listeners using the original destination filter,
         see :ref:`Original Destination <config_listener_filters_original_dst>`.
         
        .envoy.config.core.v3.TrafficDirection traffic_direction = 16;
        Parameters:
        value - The enum numeric value on the wire for trafficDirection to set.
        Returns:
        This builder for chaining.
      • getTrafficDirection

        public TrafficDirection getTrafficDirection()
         Specifies the intended direction of the traffic relative to the local Envoy.
         This property is required on Windows for listeners using the original destination filter,
         see :ref:`Original Destination <config_listener_filters_original_dst>`.
         
        .envoy.config.core.v3.TrafficDirection traffic_direction = 16;
        Specified by:
        getTrafficDirection in interface ListenerOrBuilder
        Returns:
        The trafficDirection.
      • setTrafficDirection

        public Listener.Builder setTrafficDirection​(TrafficDirection value)
         Specifies the intended direction of the traffic relative to the local Envoy.
         This property is required on Windows for listeners using the original destination filter,
         see :ref:`Original Destination <config_listener_filters_original_dst>`.
         
        .envoy.config.core.v3.TrafficDirection traffic_direction = 16;
        Parameters:
        value - The trafficDirection to set.
        Returns:
        This builder for chaining.
      • clearTrafficDirection

        public Listener.Builder clearTrafficDirection()
         Specifies the intended direction of the traffic relative to the local Envoy.
         This property is required on Windows for listeners using the original destination filter,
         see :ref:`Original Destination <config_listener_filters_original_dst>`.
         
        .envoy.config.core.v3.TrafficDirection traffic_direction = 16;
        Returns:
        This builder for chaining.
      • hasUdpListenerConfig

        public boolean hasUdpListenerConfig()
         If the protocol in the listener socket address in :ref:`protocol
         <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>`, this field specifies UDP
         listener specific configuration.
         
        .envoy.config.listener.v3.UdpListenerConfig udp_listener_config = 18;
        Specified by:
        hasUdpListenerConfig in interface ListenerOrBuilder
        Returns:
        Whether the udpListenerConfig field is set.
      • getUdpListenerConfig

        public UdpListenerConfig getUdpListenerConfig()
         If the protocol in the listener socket address in :ref:`protocol
         <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>`, this field specifies UDP
         listener specific configuration.
         
        .envoy.config.listener.v3.UdpListenerConfig udp_listener_config = 18;
        Specified by:
        getUdpListenerConfig in interface ListenerOrBuilder
        Returns:
        The udpListenerConfig.
      • setUdpListenerConfig

        public Listener.Builder setUdpListenerConfig​(UdpListenerConfig value)
         If the protocol in the listener socket address in :ref:`protocol
         <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>`, this field specifies UDP
         listener specific configuration.
         
        .envoy.config.listener.v3.UdpListenerConfig udp_listener_config = 18;
      • setUdpListenerConfig

        public Listener.Builder setUdpListenerConfig​(UdpListenerConfig.Builder builderForValue)
         If the protocol in the listener socket address in :ref:`protocol
         <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>`, this field specifies UDP
         listener specific configuration.
         
        .envoy.config.listener.v3.UdpListenerConfig udp_listener_config = 18;
      • mergeUdpListenerConfig

        public Listener.Builder mergeUdpListenerConfig​(UdpListenerConfig value)
         If the protocol in the listener socket address in :ref:`protocol
         <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>`, this field specifies UDP
         listener specific configuration.
         
        .envoy.config.listener.v3.UdpListenerConfig udp_listener_config = 18;
      • clearUdpListenerConfig

        public Listener.Builder clearUdpListenerConfig()
         If the protocol in the listener socket address in :ref:`protocol
         <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>`, this field specifies UDP
         listener specific configuration.
         
        .envoy.config.listener.v3.UdpListenerConfig udp_listener_config = 18;
      • getUdpListenerConfigBuilder

        public UdpListenerConfig.Builder getUdpListenerConfigBuilder()
         If the protocol in the listener socket address in :ref:`protocol
         <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>`, this field specifies UDP
         listener specific configuration.
         
        .envoy.config.listener.v3.UdpListenerConfig udp_listener_config = 18;
      • getUdpListenerConfigOrBuilder

        public UdpListenerConfigOrBuilder getUdpListenerConfigOrBuilder()
         If the protocol in the listener socket address in :ref:`protocol
         <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>`, this field specifies UDP
         listener specific configuration.
         
        .envoy.config.listener.v3.UdpListenerConfig udp_listener_config = 18;
        Specified by:
        getUdpListenerConfigOrBuilder in interface ListenerOrBuilder
      • getUdpListenerConfigFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<UdpListenerConfig,​UdpListenerConfig.Builder,​UdpListenerConfigOrBuilder> getUdpListenerConfigFieldBuilder()
         If the protocol in the listener socket address in :ref:`protocol
         <envoy_v3_api_field_config.core.v3.SocketAddress.protocol>` is :ref:`UDP
         <envoy_v3_api_enum_value_config.core.v3.SocketAddress.Protocol.UDP>`, this field specifies UDP
         listener specific configuration.
         
        .envoy.config.listener.v3.UdpListenerConfig udp_listener_config = 18;
      • hasApiListener

        public boolean hasApiListener()
         Used to represent an API listener, which is used in non-proxy clients. The type of API
         exposed to the non-proxy application depends on the type of API listener.
         When this field is set, no other field except for :ref:`name<envoy_v3_api_field_config.listener.v3.Listener.name>`
         should be set.
        
         .. note::
        
         Currently only one ApiListener can be installed; and it can only be done via bootstrap config,
         not LDS.
        
         [#next-major-version: In the v3 API, instead of this messy approach where the socket
         listener fields are directly in the top-level Listener message and the API listener types
         are in the ApiListener message, the socket listener messages should be in their own message,
         and the top-level Listener should essentially be a oneof that selects between the
         socket listener and the various types of API listener. That way, a given Listener message
         can structurally only contain the fields of the relevant type.]
         
        .envoy.config.listener.v3.ApiListener api_listener = 19;
        Specified by:
        hasApiListener in interface ListenerOrBuilder
        Returns:
        Whether the apiListener field is set.
      • getApiListener

        public ApiListener getApiListener()
         Used to represent an API listener, which is used in non-proxy clients. The type of API
         exposed to the non-proxy application depends on the type of API listener.
         When this field is set, no other field except for :ref:`name<envoy_v3_api_field_config.listener.v3.Listener.name>`
         should be set.
        
         .. note::
        
         Currently only one ApiListener can be installed; and it can only be done via bootstrap config,
         not LDS.
        
         [#next-major-version: In the v3 API, instead of this messy approach where the socket
         listener fields are directly in the top-level Listener message and the API listener types
         are in the ApiListener message, the socket listener messages should be in their own message,
         and the top-level Listener should essentially be a oneof that selects between the
         socket listener and the various types of API listener. That way, a given Listener message
         can structurally only contain the fields of the relevant type.]
         
        .envoy.config.listener.v3.ApiListener api_listener = 19;
        Specified by:
        getApiListener in interface ListenerOrBuilder
        Returns:
        The apiListener.
      • setApiListener

        public Listener.Builder setApiListener​(ApiListener value)
         Used to represent an API listener, which is used in non-proxy clients. The type of API
         exposed to the non-proxy application depends on the type of API listener.
         When this field is set, no other field except for :ref:`name<envoy_v3_api_field_config.listener.v3.Listener.name>`
         should be set.
        
         .. note::
        
         Currently only one ApiListener can be installed; and it can only be done via bootstrap config,
         not LDS.
        
         [#next-major-version: In the v3 API, instead of this messy approach where the socket
         listener fields are directly in the top-level Listener message and the API listener types
         are in the ApiListener message, the socket listener messages should be in their own message,
         and the top-level Listener should essentially be a oneof that selects between the
         socket listener and the various types of API listener. That way, a given Listener message
         can structurally only contain the fields of the relevant type.]
         
        .envoy.config.listener.v3.ApiListener api_listener = 19;
      • setApiListener

        public Listener.Builder setApiListener​(ApiListener.Builder builderForValue)
         Used to represent an API listener, which is used in non-proxy clients. The type of API
         exposed to the non-proxy application depends on the type of API listener.
         When this field is set, no other field except for :ref:`name<envoy_v3_api_field_config.listener.v3.Listener.name>`
         should be set.
        
         .. note::
        
         Currently only one ApiListener can be installed; and it can only be done via bootstrap config,
         not LDS.
        
         [#next-major-version: In the v3 API, instead of this messy approach where the socket
         listener fields are directly in the top-level Listener message and the API listener types
         are in the ApiListener message, the socket listener messages should be in their own message,
         and the top-level Listener should essentially be a oneof that selects between the
         socket listener and the various types of API listener. That way, a given Listener message
         can structurally only contain the fields of the relevant type.]
         
        .envoy.config.listener.v3.ApiListener api_listener = 19;
      • mergeApiListener

        public Listener.Builder mergeApiListener​(ApiListener value)
         Used to represent an API listener, which is used in non-proxy clients. The type of API
         exposed to the non-proxy application depends on the type of API listener.
         When this field is set, no other field except for :ref:`name<envoy_v3_api_field_config.listener.v3.Listener.name>`
         should be set.
        
         .. note::
        
         Currently only one ApiListener can be installed; and it can only be done via bootstrap config,
         not LDS.
        
         [#next-major-version: In the v3 API, instead of this messy approach where the socket
         listener fields are directly in the top-level Listener message and the API listener types
         are in the ApiListener message, the socket listener messages should be in their own message,
         and the top-level Listener should essentially be a oneof that selects between the
         socket listener and the various types of API listener. That way, a given Listener message
         can structurally only contain the fields of the relevant type.]
         
        .envoy.config.listener.v3.ApiListener api_listener = 19;
      • clearApiListener

        public Listener.Builder clearApiListener()
         Used to represent an API listener, which is used in non-proxy clients. The type of API
         exposed to the non-proxy application depends on the type of API listener.
         When this field is set, no other field except for :ref:`name<envoy_v3_api_field_config.listener.v3.Listener.name>`
         should be set.
        
         .. note::
        
         Currently only one ApiListener can be installed; and it can only be done via bootstrap config,
         not LDS.
        
         [#next-major-version: In the v3 API, instead of this messy approach where the socket
         listener fields are directly in the top-level Listener message and the API listener types
         are in the ApiListener message, the socket listener messages should be in their own message,
         and the top-level Listener should essentially be a oneof that selects between the
         socket listener and the various types of API listener. That way, a given Listener message
         can structurally only contain the fields of the relevant type.]
         
        .envoy.config.listener.v3.ApiListener api_listener = 19;
      • getApiListenerBuilder

        public ApiListener.Builder getApiListenerBuilder()
         Used to represent an API listener, which is used in non-proxy clients. The type of API
         exposed to the non-proxy application depends on the type of API listener.
         When this field is set, no other field except for :ref:`name<envoy_v3_api_field_config.listener.v3.Listener.name>`
         should be set.
        
         .. note::
        
         Currently only one ApiListener can be installed; and it can only be done via bootstrap config,
         not LDS.
        
         [#next-major-version: In the v3 API, instead of this messy approach where the socket
         listener fields are directly in the top-level Listener message and the API listener types
         are in the ApiListener message, the socket listener messages should be in their own message,
         and the top-level Listener should essentially be a oneof that selects between the
         socket listener and the various types of API listener. That way, a given Listener message
         can structurally only contain the fields of the relevant type.]
         
        .envoy.config.listener.v3.ApiListener api_listener = 19;
      • getApiListenerOrBuilder

        public ApiListenerOrBuilder getApiListenerOrBuilder()
         Used to represent an API listener, which is used in non-proxy clients. The type of API
         exposed to the non-proxy application depends on the type of API listener.
         When this field is set, no other field except for :ref:`name<envoy_v3_api_field_config.listener.v3.Listener.name>`
         should be set.
        
         .. note::
        
         Currently only one ApiListener can be installed; and it can only be done via bootstrap config,
         not LDS.
        
         [#next-major-version: In the v3 API, instead of this messy approach where the socket
         listener fields are directly in the top-level Listener message and the API listener types
         are in the ApiListener message, the socket listener messages should be in their own message,
         and the top-level Listener should essentially be a oneof that selects between the
         socket listener and the various types of API listener. That way, a given Listener message
         can structurally only contain the fields of the relevant type.]
         
        .envoy.config.listener.v3.ApiListener api_listener = 19;
        Specified by:
        getApiListenerOrBuilder in interface ListenerOrBuilder
      • getApiListenerFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<ApiListener,​ApiListener.Builder,​ApiListenerOrBuilder> getApiListenerFieldBuilder()
         Used to represent an API listener, which is used in non-proxy clients. The type of API
         exposed to the non-proxy application depends on the type of API listener.
         When this field is set, no other field except for :ref:`name<envoy_v3_api_field_config.listener.v3.Listener.name>`
         should be set.
        
         .. note::
        
         Currently only one ApiListener can be installed; and it can only be done via bootstrap config,
         not LDS.
        
         [#next-major-version: In the v3 API, instead of this messy approach where the socket
         listener fields are directly in the top-level Listener message and the API listener types
         are in the ApiListener message, the socket listener messages should be in their own message,
         and the top-level Listener should essentially be a oneof that selects between the
         socket listener and the various types of API listener. That way, a given Listener message
         can structurally only contain the fields of the relevant type.]
         
        .envoy.config.listener.v3.ApiListener api_listener = 19;
      • hasConnectionBalanceConfig

        public boolean hasConnectionBalanceConfig()
         The listener's connection balancer configuration, currently only applicable to TCP listeners.
         If no configuration is specified, Envoy will not attempt to balance active connections between
         worker threads.
        
         In the scenario that the listener X redirects all the connections to the listeners Y1 and Y2
         by setting :ref:`use_original_dst <envoy_v3_api_field_config.listener.v3.Listener.use_original_dst>` in X
         and :ref:`bind_to_port <envoy_v3_api_field_config.listener.v3.Listener.bind_to_port>` to false in Y1 and Y2,
         it is recommended to disable the balance config in listener X to avoid the cost of balancing, and
         enable the balance config in Y1 and Y2 to balance the connections among the workers.
         
        .envoy.config.listener.v3.Listener.ConnectionBalanceConfig connection_balance_config = 20;
        Specified by:
        hasConnectionBalanceConfig in interface ListenerOrBuilder
        Returns:
        Whether the connectionBalanceConfig field is set.
      • getConnectionBalanceConfig

        public Listener.ConnectionBalanceConfig getConnectionBalanceConfig()
         The listener's connection balancer configuration, currently only applicable to TCP listeners.
         If no configuration is specified, Envoy will not attempt to balance active connections between
         worker threads.
        
         In the scenario that the listener X redirects all the connections to the listeners Y1 and Y2
         by setting :ref:`use_original_dst <envoy_v3_api_field_config.listener.v3.Listener.use_original_dst>` in X
         and :ref:`bind_to_port <envoy_v3_api_field_config.listener.v3.Listener.bind_to_port>` to false in Y1 and Y2,
         it is recommended to disable the balance config in listener X to avoid the cost of balancing, and
         enable the balance config in Y1 and Y2 to balance the connections among the workers.
         
        .envoy.config.listener.v3.Listener.ConnectionBalanceConfig connection_balance_config = 20;
        Specified by:
        getConnectionBalanceConfig in interface ListenerOrBuilder
        Returns:
        The connectionBalanceConfig.
      • setConnectionBalanceConfig

        public Listener.Builder setConnectionBalanceConfig​(Listener.ConnectionBalanceConfig value)
         The listener's connection balancer configuration, currently only applicable to TCP listeners.
         If no configuration is specified, Envoy will not attempt to balance active connections between
         worker threads.
        
         In the scenario that the listener X redirects all the connections to the listeners Y1 and Y2
         by setting :ref:`use_original_dst <envoy_v3_api_field_config.listener.v3.Listener.use_original_dst>` in X
         and :ref:`bind_to_port <envoy_v3_api_field_config.listener.v3.Listener.bind_to_port>` to false in Y1 and Y2,
         it is recommended to disable the balance config in listener X to avoid the cost of balancing, and
         enable the balance config in Y1 and Y2 to balance the connections among the workers.
         
        .envoy.config.listener.v3.Listener.ConnectionBalanceConfig connection_balance_config = 20;
      • setConnectionBalanceConfig

        public Listener.Builder setConnectionBalanceConfig​(Listener.ConnectionBalanceConfig.Builder builderForValue)
         The listener's connection balancer configuration, currently only applicable to TCP listeners.
         If no configuration is specified, Envoy will not attempt to balance active connections between
         worker threads.
        
         In the scenario that the listener X redirects all the connections to the listeners Y1 and Y2
         by setting :ref:`use_original_dst <envoy_v3_api_field_config.listener.v3.Listener.use_original_dst>` in X
         and :ref:`bind_to_port <envoy_v3_api_field_config.listener.v3.Listener.bind_to_port>` to false in Y1 and Y2,
         it is recommended to disable the balance config in listener X to avoid the cost of balancing, and
         enable the balance config in Y1 and Y2 to balance the connections among the workers.
         
        .envoy.config.listener.v3.Listener.ConnectionBalanceConfig connection_balance_config = 20;
      • mergeConnectionBalanceConfig

        public Listener.Builder mergeConnectionBalanceConfig​(Listener.ConnectionBalanceConfig value)
         The listener's connection balancer configuration, currently only applicable to TCP listeners.
         If no configuration is specified, Envoy will not attempt to balance active connections between
         worker threads.
        
         In the scenario that the listener X redirects all the connections to the listeners Y1 and Y2
         by setting :ref:`use_original_dst <envoy_v3_api_field_config.listener.v3.Listener.use_original_dst>` in X
         and :ref:`bind_to_port <envoy_v3_api_field_config.listener.v3.Listener.bind_to_port>` to false in Y1 and Y2,
         it is recommended to disable the balance config in listener X to avoid the cost of balancing, and
         enable the balance config in Y1 and Y2 to balance the connections among the workers.
         
        .envoy.config.listener.v3.Listener.ConnectionBalanceConfig connection_balance_config = 20;
      • clearConnectionBalanceConfig

        public Listener.Builder clearConnectionBalanceConfig()
         The listener's connection balancer configuration, currently only applicable to TCP listeners.
         If no configuration is specified, Envoy will not attempt to balance active connections between
         worker threads.
        
         In the scenario that the listener X redirects all the connections to the listeners Y1 and Y2
         by setting :ref:`use_original_dst <envoy_v3_api_field_config.listener.v3.Listener.use_original_dst>` in X
         and :ref:`bind_to_port <envoy_v3_api_field_config.listener.v3.Listener.bind_to_port>` to false in Y1 and Y2,
         it is recommended to disable the balance config in listener X to avoid the cost of balancing, and
         enable the balance config in Y1 and Y2 to balance the connections among the workers.
         
        .envoy.config.listener.v3.Listener.ConnectionBalanceConfig connection_balance_config = 20;
      • getConnectionBalanceConfigBuilder

        public Listener.ConnectionBalanceConfig.Builder getConnectionBalanceConfigBuilder()
         The listener's connection balancer configuration, currently only applicable to TCP listeners.
         If no configuration is specified, Envoy will not attempt to balance active connections between
         worker threads.
        
         In the scenario that the listener X redirects all the connections to the listeners Y1 and Y2
         by setting :ref:`use_original_dst <envoy_v3_api_field_config.listener.v3.Listener.use_original_dst>` in X
         and :ref:`bind_to_port <envoy_v3_api_field_config.listener.v3.Listener.bind_to_port>` to false in Y1 and Y2,
         it is recommended to disable the balance config in listener X to avoid the cost of balancing, and
         enable the balance config in Y1 and Y2 to balance the connections among the workers.
         
        .envoy.config.listener.v3.Listener.ConnectionBalanceConfig connection_balance_config = 20;
      • getConnectionBalanceConfigOrBuilder

        public Listener.ConnectionBalanceConfigOrBuilder getConnectionBalanceConfigOrBuilder()
         The listener's connection balancer configuration, currently only applicable to TCP listeners.
         If no configuration is specified, Envoy will not attempt to balance active connections between
         worker threads.
        
         In the scenario that the listener X redirects all the connections to the listeners Y1 and Y2
         by setting :ref:`use_original_dst <envoy_v3_api_field_config.listener.v3.Listener.use_original_dst>` in X
         and :ref:`bind_to_port <envoy_v3_api_field_config.listener.v3.Listener.bind_to_port>` to false in Y1 and Y2,
         it is recommended to disable the balance config in listener X to avoid the cost of balancing, and
         enable the balance config in Y1 and Y2 to balance the connections among the workers.
         
        .envoy.config.listener.v3.Listener.ConnectionBalanceConfig connection_balance_config = 20;
        Specified by:
        getConnectionBalanceConfigOrBuilder in interface ListenerOrBuilder
      • getConnectionBalanceConfigFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<Listener.ConnectionBalanceConfig,​Listener.ConnectionBalanceConfig.Builder,​Listener.ConnectionBalanceConfigOrBuilder> getConnectionBalanceConfigFieldBuilder()
         The listener's connection balancer configuration, currently only applicable to TCP listeners.
         If no configuration is specified, Envoy will not attempt to balance active connections between
         worker threads.
        
         In the scenario that the listener X redirects all the connections to the listeners Y1 and Y2
         by setting :ref:`use_original_dst <envoy_v3_api_field_config.listener.v3.Listener.use_original_dst>` in X
         and :ref:`bind_to_port <envoy_v3_api_field_config.listener.v3.Listener.bind_to_port>` to false in Y1 and Y2,
         it is recommended to disable the balance config in listener X to avoid the cost of balancing, and
         enable the balance config in Y1 and Y2 to balance the connections among the workers.
         
        .envoy.config.listener.v3.Listener.ConnectionBalanceConfig connection_balance_config = 20;
      • getReusePort

        @Deprecated
        public boolean getReusePort()
        Deprecated.
        envoy.config.listener.v3.Listener.reuse_port is deprecated. See envoy/config/listener/v3/listener.proto;l=312
         Deprecated. Use ``enable_reuse_port`` instead.
         
        bool reuse_port = 21 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
        Specified by:
        getReusePort in interface ListenerOrBuilder
        Returns:
        The reusePort.
      • setReusePort

        @Deprecated
        public Listener.Builder setReusePort​(boolean value)
        Deprecated.
        envoy.config.listener.v3.Listener.reuse_port is deprecated. See envoy/config/listener/v3/listener.proto;l=312
         Deprecated. Use ``enable_reuse_port`` instead.
         
        bool reuse_port = 21 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
        Parameters:
        value - The reusePort to set.
        Returns:
        This builder for chaining.
      • clearReusePort

        @Deprecated
        public Listener.Builder clearReusePort()
        Deprecated.
        envoy.config.listener.v3.Listener.reuse_port is deprecated. See envoy/config/listener/v3/listener.proto;l=312
         Deprecated. Use ``enable_reuse_port`` instead.
         
        bool reuse_port = 21 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
        Returns:
        This builder for chaining.
      • hasEnableReusePort

        public boolean hasEnableReusePort()
         When this flag is set to true, listeners set the ``SO_REUSEPORT`` socket option and
         create one socket for each worker thread. This makes inbound connections
         distribute among worker threads roughly evenly in cases where there are a high number
         of connections. When this flag is set to false, all worker threads share one socket. This field
         defaults to true. The change of field will be rejected during an listener update when the
         runtime flag ``envoy.reloadable_features.enable_update_listener_socket_options`` is enabled.
         Otherwise, the update of this field will be ignored quietly.
        
         .. attention::
        
         Although this field defaults to true, it has different behavior on different platforms. See
         the following text for more information.
        
         * On Linux, reuse_port is respected for both TCP and UDP listeners. It also works correctly
         with hot restart.
         * On macOS, reuse_port for TCP does not do what it does on Linux. Instead of load balancing,
         the last socket wins and receives all connections/packets. For TCP, reuse_port is force
         disabled and the user is warned. For UDP, it is enabled, but only one worker will receive
         packets. For QUIC/H3, SW routing will send packets to other workers. For "raw" UDP, only
         a single worker will currently receive packets.
         * On Windows, reuse_port for TCP has undefined behavior. It is force disabled and the user
         is warned similar to macOS. It is left enabled for UDP with undefined behavior currently.
         
        .google.protobuf.BoolValue enable_reuse_port = 29;
        Specified by:
        hasEnableReusePort in interface ListenerOrBuilder
        Returns:
        Whether the enableReusePort field is set.
      • getEnableReusePort

        public com.google.protobuf.BoolValue getEnableReusePort()
         When this flag is set to true, listeners set the ``SO_REUSEPORT`` socket option and
         create one socket for each worker thread. This makes inbound connections
         distribute among worker threads roughly evenly in cases where there are a high number
         of connections. When this flag is set to false, all worker threads share one socket. This field
         defaults to true. The change of field will be rejected during an listener update when the
         runtime flag ``envoy.reloadable_features.enable_update_listener_socket_options`` is enabled.
         Otherwise, the update of this field will be ignored quietly.
        
         .. attention::
        
         Although this field defaults to true, it has different behavior on different platforms. See
         the following text for more information.
        
         * On Linux, reuse_port is respected for both TCP and UDP listeners. It also works correctly
         with hot restart.
         * On macOS, reuse_port for TCP does not do what it does on Linux. Instead of load balancing,
         the last socket wins and receives all connections/packets. For TCP, reuse_port is force
         disabled and the user is warned. For UDP, it is enabled, but only one worker will receive
         packets. For QUIC/H3, SW routing will send packets to other workers. For "raw" UDP, only
         a single worker will currently receive packets.
         * On Windows, reuse_port for TCP has undefined behavior. It is force disabled and the user
         is warned similar to macOS. It is left enabled for UDP with undefined behavior currently.
         
        .google.protobuf.BoolValue enable_reuse_port = 29;
        Specified by:
        getEnableReusePort in interface ListenerOrBuilder
        Returns:
        The enableReusePort.
      • setEnableReusePort

        public Listener.Builder setEnableReusePort​(com.google.protobuf.BoolValue value)
         When this flag is set to true, listeners set the ``SO_REUSEPORT`` socket option and
         create one socket for each worker thread. This makes inbound connections
         distribute among worker threads roughly evenly in cases where there are a high number
         of connections. When this flag is set to false, all worker threads share one socket. This field
         defaults to true. The change of field will be rejected during an listener update when the
         runtime flag ``envoy.reloadable_features.enable_update_listener_socket_options`` is enabled.
         Otherwise, the update of this field will be ignored quietly.
        
         .. attention::
        
         Although this field defaults to true, it has different behavior on different platforms. See
         the following text for more information.
        
         * On Linux, reuse_port is respected for both TCP and UDP listeners. It also works correctly
         with hot restart.
         * On macOS, reuse_port for TCP does not do what it does on Linux. Instead of load balancing,
         the last socket wins and receives all connections/packets. For TCP, reuse_port is force
         disabled and the user is warned. For UDP, it is enabled, but only one worker will receive
         packets. For QUIC/H3, SW routing will send packets to other workers. For "raw" UDP, only
         a single worker will currently receive packets.
         * On Windows, reuse_port for TCP has undefined behavior. It is force disabled and the user
         is warned similar to macOS. It is left enabled for UDP with undefined behavior currently.
         
        .google.protobuf.BoolValue enable_reuse_port = 29;
      • setEnableReusePort

        public Listener.Builder setEnableReusePort​(com.google.protobuf.BoolValue.Builder builderForValue)
         When this flag is set to true, listeners set the ``SO_REUSEPORT`` socket option and
         create one socket for each worker thread. This makes inbound connections
         distribute among worker threads roughly evenly in cases where there are a high number
         of connections. When this flag is set to false, all worker threads share one socket. This field
         defaults to true. The change of field will be rejected during an listener update when the
         runtime flag ``envoy.reloadable_features.enable_update_listener_socket_options`` is enabled.
         Otherwise, the update of this field will be ignored quietly.
        
         .. attention::
        
         Although this field defaults to true, it has different behavior on different platforms. See
         the following text for more information.
        
         * On Linux, reuse_port is respected for both TCP and UDP listeners. It also works correctly
         with hot restart.
         * On macOS, reuse_port for TCP does not do what it does on Linux. Instead of load balancing,
         the last socket wins and receives all connections/packets. For TCP, reuse_port is force
         disabled and the user is warned. For UDP, it is enabled, but only one worker will receive
         packets. For QUIC/H3, SW routing will send packets to other workers. For "raw" UDP, only
         a single worker will currently receive packets.
         * On Windows, reuse_port for TCP has undefined behavior. It is force disabled and the user
         is warned similar to macOS. It is left enabled for UDP with undefined behavior currently.
         
        .google.protobuf.BoolValue enable_reuse_port = 29;
      • mergeEnableReusePort

        public Listener.Builder mergeEnableReusePort​(com.google.protobuf.BoolValue value)
         When this flag is set to true, listeners set the ``SO_REUSEPORT`` socket option and
         create one socket for each worker thread. This makes inbound connections
         distribute among worker threads roughly evenly in cases where there are a high number
         of connections. When this flag is set to false, all worker threads share one socket. This field
         defaults to true. The change of field will be rejected during an listener update when the
         runtime flag ``envoy.reloadable_features.enable_update_listener_socket_options`` is enabled.
         Otherwise, the update of this field will be ignored quietly.
        
         .. attention::
        
         Although this field defaults to true, it has different behavior on different platforms. See
         the following text for more information.
        
         * On Linux, reuse_port is respected for both TCP and UDP listeners. It also works correctly
         with hot restart.
         * On macOS, reuse_port for TCP does not do what it does on Linux. Instead of load balancing,
         the last socket wins and receives all connections/packets. For TCP, reuse_port is force
         disabled and the user is warned. For UDP, it is enabled, but only one worker will receive
         packets. For QUIC/H3, SW routing will send packets to other workers. For "raw" UDP, only
         a single worker will currently receive packets.
         * On Windows, reuse_port for TCP has undefined behavior. It is force disabled and the user
         is warned similar to macOS. It is left enabled for UDP with undefined behavior currently.
         
        .google.protobuf.BoolValue enable_reuse_port = 29;
      • clearEnableReusePort

        public Listener.Builder clearEnableReusePort()
         When this flag is set to true, listeners set the ``SO_REUSEPORT`` socket option and
         create one socket for each worker thread. This makes inbound connections
         distribute among worker threads roughly evenly in cases where there are a high number
         of connections. When this flag is set to false, all worker threads share one socket. This field
         defaults to true. The change of field will be rejected during an listener update when the
         runtime flag ``envoy.reloadable_features.enable_update_listener_socket_options`` is enabled.
         Otherwise, the update of this field will be ignored quietly.
        
         .. attention::
        
         Although this field defaults to true, it has different behavior on different platforms. See
         the following text for more information.
        
         * On Linux, reuse_port is respected for both TCP and UDP listeners. It also works correctly
         with hot restart.
         * On macOS, reuse_port for TCP does not do what it does on Linux. Instead of load balancing,
         the last socket wins and receives all connections/packets. For TCP, reuse_port is force
         disabled and the user is warned. For UDP, it is enabled, but only one worker will receive
         packets. For QUIC/H3, SW routing will send packets to other workers. For "raw" UDP, only
         a single worker will currently receive packets.
         * On Windows, reuse_port for TCP has undefined behavior. It is force disabled and the user
         is warned similar to macOS. It is left enabled for UDP with undefined behavior currently.
         
        .google.protobuf.BoolValue enable_reuse_port = 29;
      • getEnableReusePortBuilder

        public com.google.protobuf.BoolValue.Builder getEnableReusePortBuilder()
         When this flag is set to true, listeners set the ``SO_REUSEPORT`` socket option and
         create one socket for each worker thread. This makes inbound connections
         distribute among worker threads roughly evenly in cases where there are a high number
         of connections. When this flag is set to false, all worker threads share one socket. This field
         defaults to true. The change of field will be rejected during an listener update when the
         runtime flag ``envoy.reloadable_features.enable_update_listener_socket_options`` is enabled.
         Otherwise, the update of this field will be ignored quietly.
        
         .. attention::
        
         Although this field defaults to true, it has different behavior on different platforms. See
         the following text for more information.
        
         * On Linux, reuse_port is respected for both TCP and UDP listeners. It also works correctly
         with hot restart.
         * On macOS, reuse_port for TCP does not do what it does on Linux. Instead of load balancing,
         the last socket wins and receives all connections/packets. For TCP, reuse_port is force
         disabled and the user is warned. For UDP, it is enabled, but only one worker will receive
         packets. For QUIC/H3, SW routing will send packets to other workers. For "raw" UDP, only
         a single worker will currently receive packets.
         * On Windows, reuse_port for TCP has undefined behavior. It is force disabled and the user
         is warned similar to macOS. It is left enabled for UDP with undefined behavior currently.
         
        .google.protobuf.BoolValue enable_reuse_port = 29;
      • getEnableReusePortOrBuilder

        public com.google.protobuf.BoolValueOrBuilder getEnableReusePortOrBuilder()
         When this flag is set to true, listeners set the ``SO_REUSEPORT`` socket option and
         create one socket for each worker thread. This makes inbound connections
         distribute among worker threads roughly evenly in cases where there are a high number
         of connections. When this flag is set to false, all worker threads share one socket. This field
         defaults to true. The change of field will be rejected during an listener update when the
         runtime flag ``envoy.reloadable_features.enable_update_listener_socket_options`` is enabled.
         Otherwise, the update of this field will be ignored quietly.
        
         .. attention::
        
         Although this field defaults to true, it has different behavior on different platforms. See
         the following text for more information.
        
         * On Linux, reuse_port is respected for both TCP and UDP listeners. It also works correctly
         with hot restart.
         * On macOS, reuse_port for TCP does not do what it does on Linux. Instead of load balancing,
         the last socket wins and receives all connections/packets. For TCP, reuse_port is force
         disabled and the user is warned. For UDP, it is enabled, but only one worker will receive
         packets. For QUIC/H3, SW routing will send packets to other workers. For "raw" UDP, only
         a single worker will currently receive packets.
         * On Windows, reuse_port for TCP has undefined behavior. It is force disabled and the user
         is warned similar to macOS. It is left enabled for UDP with undefined behavior currently.
         
        .google.protobuf.BoolValue enable_reuse_port = 29;
        Specified by:
        getEnableReusePortOrBuilder in interface ListenerOrBuilder
      • getEnableReusePortFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,​com.google.protobuf.BoolValue.Builder,​com.google.protobuf.BoolValueOrBuilder> getEnableReusePortFieldBuilder()
         When this flag is set to true, listeners set the ``SO_REUSEPORT`` socket option and
         create one socket for each worker thread. This makes inbound connections
         distribute among worker threads roughly evenly in cases where there are a high number
         of connections. When this flag is set to false, all worker threads share one socket. This field
         defaults to true. The change of field will be rejected during an listener update when the
         runtime flag ``envoy.reloadable_features.enable_update_listener_socket_options`` is enabled.
         Otherwise, the update of this field will be ignored quietly.
        
         .. attention::
        
         Although this field defaults to true, it has different behavior on different platforms. See
         the following text for more information.
        
         * On Linux, reuse_port is respected for both TCP and UDP listeners. It also works correctly
         with hot restart.
         * On macOS, reuse_port for TCP does not do what it does on Linux. Instead of load balancing,
         the last socket wins and receives all connections/packets. For TCP, reuse_port is force
         disabled and the user is warned. For UDP, it is enabled, but only one worker will receive
         packets. For QUIC/H3, SW routing will send packets to other workers. For "raw" UDP, only
         a single worker will currently receive packets.
         * On Windows, reuse_port for TCP has undefined behavior. It is force disabled and the user
         is warned similar to macOS. It is left enabled for UDP with undefined behavior currently.
         
        .google.protobuf.BoolValue enable_reuse_port = 29;
      • ensureAccessLogIsMutable

        private void ensureAccessLogIsMutable()
      • getAccessLogList

        public java.util.List<AccessLog> getAccessLogList()
         Configuration for :ref:`access logs <arch_overview_access_logs>`
         emitted by this listener.
         
        repeated .envoy.config.accesslog.v3.AccessLog access_log = 22;
        Specified by:
        getAccessLogList in interface ListenerOrBuilder
      • getAccessLogCount

        public int getAccessLogCount()
         Configuration for :ref:`access logs <arch_overview_access_logs>`
         emitted by this listener.
         
        repeated .envoy.config.accesslog.v3.AccessLog access_log = 22;
        Specified by:
        getAccessLogCount in interface ListenerOrBuilder
      • getAccessLog

        public AccessLog getAccessLog​(int index)
         Configuration for :ref:`access logs <arch_overview_access_logs>`
         emitted by this listener.
         
        repeated .envoy.config.accesslog.v3.AccessLog access_log = 22;
        Specified by:
        getAccessLog in interface ListenerOrBuilder
      • setAccessLog

        public Listener.Builder setAccessLog​(int index,
                                             AccessLog value)
         Configuration for :ref:`access logs <arch_overview_access_logs>`
         emitted by this listener.
         
        repeated .envoy.config.accesslog.v3.AccessLog access_log = 22;
      • setAccessLog

        public Listener.Builder setAccessLog​(int index,
                                             AccessLog.Builder builderForValue)
         Configuration for :ref:`access logs <arch_overview_access_logs>`
         emitted by this listener.
         
        repeated .envoy.config.accesslog.v3.AccessLog access_log = 22;
      • addAccessLog

        public Listener.Builder addAccessLog​(AccessLog value)
         Configuration for :ref:`access logs <arch_overview_access_logs>`
         emitted by this listener.
         
        repeated .envoy.config.accesslog.v3.AccessLog access_log = 22;
      • addAccessLog

        public Listener.Builder addAccessLog​(int index,
                                             AccessLog value)
         Configuration for :ref:`access logs <arch_overview_access_logs>`
         emitted by this listener.
         
        repeated .envoy.config.accesslog.v3.AccessLog access_log = 22;
      • addAccessLog

        public Listener.Builder addAccessLog​(AccessLog.Builder builderForValue)
         Configuration for :ref:`access logs <arch_overview_access_logs>`
         emitted by this listener.
         
        repeated .envoy.config.accesslog.v3.AccessLog access_log = 22;
      • addAccessLog

        public Listener.Builder addAccessLog​(int index,
                                             AccessLog.Builder builderForValue)
         Configuration for :ref:`access logs <arch_overview_access_logs>`
         emitted by this listener.
         
        repeated .envoy.config.accesslog.v3.AccessLog access_log = 22;
      • addAllAccessLog

        public Listener.Builder addAllAccessLog​(java.lang.Iterable<? extends AccessLog> values)
         Configuration for :ref:`access logs <arch_overview_access_logs>`
         emitted by this listener.
         
        repeated .envoy.config.accesslog.v3.AccessLog access_log = 22;
      • clearAccessLog

        public Listener.Builder clearAccessLog()
         Configuration for :ref:`access logs <arch_overview_access_logs>`
         emitted by this listener.
         
        repeated .envoy.config.accesslog.v3.AccessLog access_log = 22;
      • removeAccessLog

        public Listener.Builder removeAccessLog​(int index)
         Configuration for :ref:`access logs <arch_overview_access_logs>`
         emitted by this listener.
         
        repeated .envoy.config.accesslog.v3.AccessLog access_log = 22;
      • getAccessLogBuilder

        public AccessLog.Builder getAccessLogBuilder​(int index)
         Configuration for :ref:`access logs <arch_overview_access_logs>`
         emitted by this listener.
         
        repeated .envoy.config.accesslog.v3.AccessLog access_log = 22;
      • getAccessLogOrBuilder

        public AccessLogOrBuilder getAccessLogOrBuilder​(int index)
         Configuration for :ref:`access logs <arch_overview_access_logs>`
         emitted by this listener.
         
        repeated .envoy.config.accesslog.v3.AccessLog access_log = 22;
        Specified by:
        getAccessLogOrBuilder in interface ListenerOrBuilder
      • getAccessLogOrBuilderList

        public java.util.List<? extends AccessLogOrBuilder> getAccessLogOrBuilderList()
         Configuration for :ref:`access logs <arch_overview_access_logs>`
         emitted by this listener.
         
        repeated .envoy.config.accesslog.v3.AccessLog access_log = 22;
        Specified by:
        getAccessLogOrBuilderList in interface ListenerOrBuilder
      • addAccessLogBuilder

        public AccessLog.Builder addAccessLogBuilder()
         Configuration for :ref:`access logs <arch_overview_access_logs>`
         emitted by this listener.
         
        repeated .envoy.config.accesslog.v3.AccessLog access_log = 22;
      • addAccessLogBuilder

        public AccessLog.Builder addAccessLogBuilder​(int index)
         Configuration for :ref:`access logs <arch_overview_access_logs>`
         emitted by this listener.
         
        repeated .envoy.config.accesslog.v3.AccessLog access_log = 22;
      • getAccessLogBuilderList

        public java.util.List<AccessLog.Builder> getAccessLogBuilderList()
         Configuration for :ref:`access logs <arch_overview_access_logs>`
         emitted by this listener.
         
        repeated .envoy.config.accesslog.v3.AccessLog access_log = 22;
      • hasTcpBacklogSize

        public boolean hasTcpBacklogSize()
         The maximum length a tcp listener's pending connections queue can grow to. If no value is
         provided net.core.somaxconn will be used on Linux and 128 otherwise.
         
        .google.protobuf.UInt32Value tcp_backlog_size = 24;
        Specified by:
        hasTcpBacklogSize in interface ListenerOrBuilder
        Returns:
        Whether the tcpBacklogSize field is set.
      • getTcpBacklogSize

        public com.google.protobuf.UInt32Value getTcpBacklogSize()
         The maximum length a tcp listener's pending connections queue can grow to. If no value is
         provided net.core.somaxconn will be used on Linux and 128 otherwise.
         
        .google.protobuf.UInt32Value tcp_backlog_size = 24;
        Specified by:
        getTcpBacklogSize in interface ListenerOrBuilder
        Returns:
        The tcpBacklogSize.
      • setTcpBacklogSize

        public Listener.Builder setTcpBacklogSize​(com.google.protobuf.UInt32Value value)
         The maximum length a tcp listener's pending connections queue can grow to. If no value is
         provided net.core.somaxconn will be used on Linux and 128 otherwise.
         
        .google.protobuf.UInt32Value tcp_backlog_size = 24;
      • setTcpBacklogSize

        public Listener.Builder setTcpBacklogSize​(com.google.protobuf.UInt32Value.Builder builderForValue)
         The maximum length a tcp listener's pending connections queue can grow to. If no value is
         provided net.core.somaxconn will be used on Linux and 128 otherwise.
         
        .google.protobuf.UInt32Value tcp_backlog_size = 24;
      • mergeTcpBacklogSize

        public Listener.Builder mergeTcpBacklogSize​(com.google.protobuf.UInt32Value value)
         The maximum length a tcp listener's pending connections queue can grow to. If no value is
         provided net.core.somaxconn will be used on Linux and 128 otherwise.
         
        .google.protobuf.UInt32Value tcp_backlog_size = 24;
      • clearTcpBacklogSize

        public Listener.Builder clearTcpBacklogSize()
         The maximum length a tcp listener's pending connections queue can grow to. If no value is
         provided net.core.somaxconn will be used on Linux and 128 otherwise.
         
        .google.protobuf.UInt32Value tcp_backlog_size = 24;
      • getTcpBacklogSizeBuilder

        public com.google.protobuf.UInt32Value.Builder getTcpBacklogSizeBuilder()
         The maximum length a tcp listener's pending connections queue can grow to. If no value is
         provided net.core.somaxconn will be used on Linux and 128 otherwise.
         
        .google.protobuf.UInt32Value tcp_backlog_size = 24;
      • getTcpBacklogSizeOrBuilder

        public com.google.protobuf.UInt32ValueOrBuilder getTcpBacklogSizeOrBuilder()
         The maximum length a tcp listener's pending connections queue can grow to. If no value is
         provided net.core.somaxconn will be used on Linux and 128 otherwise.
         
        .google.protobuf.UInt32Value tcp_backlog_size = 24;
        Specified by:
        getTcpBacklogSizeOrBuilder in interface ListenerOrBuilder
      • getTcpBacklogSizeFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.UInt32Value,​com.google.protobuf.UInt32Value.Builder,​com.google.protobuf.UInt32ValueOrBuilder> getTcpBacklogSizeFieldBuilder()
         The maximum length a tcp listener's pending connections queue can grow to. If no value is
         provided net.core.somaxconn will be used on Linux and 128 otherwise.
         
        .google.protobuf.UInt32Value tcp_backlog_size = 24;
      • hasMaxConnectionsToAcceptPerSocketEvent

        public boolean hasMaxConnectionsToAcceptPerSocketEvent()
         The maximum number of connections to accept from the kernel per socket
         event. Envoy may decide to close these connections after accepting them
         from the kernel e.g. due to load shedding, or other policies.
         If there are more than max_connections_to_accept_per_socket_event
         connections pending accept, connections over this threshold will be
         accepted in later event loop iterations.
         If no value is provided Envoy will accept all connections pending accept
         from the kernel.
         
        .google.protobuf.UInt32Value max_connections_to_accept_per_socket_event = 34 [(.validate.rules) = { ... }
        Specified by:
        hasMaxConnectionsToAcceptPerSocketEvent in interface ListenerOrBuilder
        Returns:
        Whether the maxConnectionsToAcceptPerSocketEvent field is set.
      • getMaxConnectionsToAcceptPerSocketEvent

        public com.google.protobuf.UInt32Value getMaxConnectionsToAcceptPerSocketEvent()
         The maximum number of connections to accept from the kernel per socket
         event. Envoy may decide to close these connections after accepting them
         from the kernel e.g. due to load shedding, or other policies.
         If there are more than max_connections_to_accept_per_socket_event
         connections pending accept, connections over this threshold will be
         accepted in later event loop iterations.
         If no value is provided Envoy will accept all connections pending accept
         from the kernel.
         
        .google.protobuf.UInt32Value max_connections_to_accept_per_socket_event = 34 [(.validate.rules) = { ... }
        Specified by:
        getMaxConnectionsToAcceptPerSocketEvent in interface ListenerOrBuilder
        Returns:
        The maxConnectionsToAcceptPerSocketEvent.
      • setMaxConnectionsToAcceptPerSocketEvent

        public Listener.Builder setMaxConnectionsToAcceptPerSocketEvent​(com.google.protobuf.UInt32Value value)
         The maximum number of connections to accept from the kernel per socket
         event. Envoy may decide to close these connections after accepting them
         from the kernel e.g. due to load shedding, or other policies.
         If there are more than max_connections_to_accept_per_socket_event
         connections pending accept, connections over this threshold will be
         accepted in later event loop iterations.
         If no value is provided Envoy will accept all connections pending accept
         from the kernel.
         
        .google.protobuf.UInt32Value max_connections_to_accept_per_socket_event = 34 [(.validate.rules) = { ... }
      • setMaxConnectionsToAcceptPerSocketEvent

        public Listener.Builder setMaxConnectionsToAcceptPerSocketEvent​(com.google.protobuf.UInt32Value.Builder builderForValue)
         The maximum number of connections to accept from the kernel per socket
         event. Envoy may decide to close these connections after accepting them
         from the kernel e.g. due to load shedding, or other policies.
         If there are more than max_connections_to_accept_per_socket_event
         connections pending accept, connections over this threshold will be
         accepted in later event loop iterations.
         If no value is provided Envoy will accept all connections pending accept
         from the kernel.
         
        .google.protobuf.UInt32Value max_connections_to_accept_per_socket_event = 34 [(.validate.rules) = { ... }
      • mergeMaxConnectionsToAcceptPerSocketEvent

        public Listener.Builder mergeMaxConnectionsToAcceptPerSocketEvent​(com.google.protobuf.UInt32Value value)
         The maximum number of connections to accept from the kernel per socket
         event. Envoy may decide to close these connections after accepting them
         from the kernel e.g. due to load shedding, or other policies.
         If there are more than max_connections_to_accept_per_socket_event
         connections pending accept, connections over this threshold will be
         accepted in later event loop iterations.
         If no value is provided Envoy will accept all connections pending accept
         from the kernel.
         
        .google.protobuf.UInt32Value max_connections_to_accept_per_socket_event = 34 [(.validate.rules) = { ... }
      • clearMaxConnectionsToAcceptPerSocketEvent

        public Listener.Builder clearMaxConnectionsToAcceptPerSocketEvent()
         The maximum number of connections to accept from the kernel per socket
         event. Envoy may decide to close these connections after accepting them
         from the kernel e.g. due to load shedding, or other policies.
         If there are more than max_connections_to_accept_per_socket_event
         connections pending accept, connections over this threshold will be
         accepted in later event loop iterations.
         If no value is provided Envoy will accept all connections pending accept
         from the kernel.
         
        .google.protobuf.UInt32Value max_connections_to_accept_per_socket_event = 34 [(.validate.rules) = { ... }
      • getMaxConnectionsToAcceptPerSocketEventBuilder

        public com.google.protobuf.UInt32Value.Builder getMaxConnectionsToAcceptPerSocketEventBuilder()
         The maximum number of connections to accept from the kernel per socket
         event. Envoy may decide to close these connections after accepting them
         from the kernel e.g. due to load shedding, or other policies.
         If there are more than max_connections_to_accept_per_socket_event
         connections pending accept, connections over this threshold will be
         accepted in later event loop iterations.
         If no value is provided Envoy will accept all connections pending accept
         from the kernel.
         
        .google.protobuf.UInt32Value max_connections_to_accept_per_socket_event = 34 [(.validate.rules) = { ... }
      • getMaxConnectionsToAcceptPerSocketEventOrBuilder

        public com.google.protobuf.UInt32ValueOrBuilder getMaxConnectionsToAcceptPerSocketEventOrBuilder()
         The maximum number of connections to accept from the kernel per socket
         event. Envoy may decide to close these connections after accepting them
         from the kernel e.g. due to load shedding, or other policies.
         If there are more than max_connections_to_accept_per_socket_event
         connections pending accept, connections over this threshold will be
         accepted in later event loop iterations.
         If no value is provided Envoy will accept all connections pending accept
         from the kernel.
         
        .google.protobuf.UInt32Value max_connections_to_accept_per_socket_event = 34 [(.validate.rules) = { ... }
        Specified by:
        getMaxConnectionsToAcceptPerSocketEventOrBuilder in interface ListenerOrBuilder
      • getMaxConnectionsToAcceptPerSocketEventFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.UInt32Value,​com.google.protobuf.UInt32Value.Builder,​com.google.protobuf.UInt32ValueOrBuilder> getMaxConnectionsToAcceptPerSocketEventFieldBuilder()
         The maximum number of connections to accept from the kernel per socket
         event. Envoy may decide to close these connections after accepting them
         from the kernel e.g. due to load shedding, or other policies.
         If there are more than max_connections_to_accept_per_socket_event
         connections pending accept, connections over this threshold will be
         accepted in later event loop iterations.
         If no value is provided Envoy will accept all connections pending accept
         from the kernel.
         
        .google.protobuf.UInt32Value max_connections_to_accept_per_socket_event = 34 [(.validate.rules) = { ... }
      • hasBindToPort

        public boolean hasBindToPort()
         Whether the listener should bind to the port. A listener that doesn't
         bind can only receive connections redirected from other listeners that set
         :ref:`use_original_dst <envoy_v3_api_field_config.listener.v3.Listener.use_original_dst>`
         to true. Default is true.
         
        .google.protobuf.BoolValue bind_to_port = 26;
        Specified by:
        hasBindToPort in interface ListenerOrBuilder
        Returns:
        Whether the bindToPort field is set.
      • getBindToPort

        public com.google.protobuf.BoolValue getBindToPort()
         Whether the listener should bind to the port. A listener that doesn't
         bind can only receive connections redirected from other listeners that set
         :ref:`use_original_dst <envoy_v3_api_field_config.listener.v3.Listener.use_original_dst>`
         to true. Default is true.
         
        .google.protobuf.BoolValue bind_to_port = 26;
        Specified by:
        getBindToPort in interface ListenerOrBuilder
        Returns:
        The bindToPort.
      • setBindToPort

        public Listener.Builder setBindToPort​(com.google.protobuf.BoolValue value)
         Whether the listener should bind to the port. A listener that doesn't
         bind can only receive connections redirected from other listeners that set
         :ref:`use_original_dst <envoy_v3_api_field_config.listener.v3.Listener.use_original_dst>`
         to true. Default is true.
         
        .google.protobuf.BoolValue bind_to_port = 26;
      • setBindToPort

        public Listener.Builder setBindToPort​(com.google.protobuf.BoolValue.Builder builderForValue)
         Whether the listener should bind to the port. A listener that doesn't
         bind can only receive connections redirected from other listeners that set
         :ref:`use_original_dst <envoy_v3_api_field_config.listener.v3.Listener.use_original_dst>`
         to true. Default is true.
         
        .google.protobuf.BoolValue bind_to_port = 26;
      • mergeBindToPort

        public Listener.Builder mergeBindToPort​(com.google.protobuf.BoolValue value)
         Whether the listener should bind to the port. A listener that doesn't
         bind can only receive connections redirected from other listeners that set
         :ref:`use_original_dst <envoy_v3_api_field_config.listener.v3.Listener.use_original_dst>`
         to true. Default is true.
         
        .google.protobuf.BoolValue bind_to_port = 26;
      • clearBindToPort

        public Listener.Builder clearBindToPort()
         Whether the listener should bind to the port. A listener that doesn't
         bind can only receive connections redirected from other listeners that set
         :ref:`use_original_dst <envoy_v3_api_field_config.listener.v3.Listener.use_original_dst>`
         to true. Default is true.
         
        .google.protobuf.BoolValue bind_to_port = 26;
      • getBindToPortBuilder

        public com.google.protobuf.BoolValue.Builder getBindToPortBuilder()
         Whether the listener should bind to the port. A listener that doesn't
         bind can only receive connections redirected from other listeners that set
         :ref:`use_original_dst <envoy_v3_api_field_config.listener.v3.Listener.use_original_dst>`
         to true. Default is true.
         
        .google.protobuf.BoolValue bind_to_port = 26;
      • getBindToPortOrBuilder

        public com.google.protobuf.BoolValueOrBuilder getBindToPortOrBuilder()
         Whether the listener should bind to the port. A listener that doesn't
         bind can only receive connections redirected from other listeners that set
         :ref:`use_original_dst <envoy_v3_api_field_config.listener.v3.Listener.use_original_dst>`
         to true. Default is true.
         
        .google.protobuf.BoolValue bind_to_port = 26;
        Specified by:
        getBindToPortOrBuilder in interface ListenerOrBuilder
      • getBindToPortFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,​com.google.protobuf.BoolValue.Builder,​com.google.protobuf.BoolValueOrBuilder> getBindToPortFieldBuilder()
         Whether the listener should bind to the port. A listener that doesn't
         bind can only receive connections redirected from other listeners that set
         :ref:`use_original_dst <envoy_v3_api_field_config.listener.v3.Listener.use_original_dst>`
         to true. Default is true.
         
        .google.protobuf.BoolValue bind_to_port = 26;
      • hasInternalListener

        public boolean hasInternalListener()
         Used to represent an internal listener which does not listen on OSI L4 address but can be used by the
         :ref:`envoy cluster <envoy_v3_api_msg_config.cluster.v3.Cluster>` to create a user space connection to.
         The internal listener acts as a TCP listener. It supports listener filters and network filter chains.
         Upstream clusters refer to the internal listeners by their :ref:`name
         <envoy_v3_api_field_config.listener.v3.Listener.name>`. :ref:`Address
         <envoy_v3_api_field_config.listener.v3.Listener.address>` must not be set on the internal listeners.
        
         There are some limitations that are derived from the implementation. The known limitations include:
        
         * :ref:`ConnectionBalanceConfig <envoy_v3_api_msg_config.listener.v3.Listener.ConnectionBalanceConfig>` is not
         allowed because both the cluster connection and the listener connection must be owned by the same dispatcher.
         * :ref:`tcp_backlog_size <envoy_v3_api_field_config.listener.v3.Listener.tcp_backlog_size>`
         * :ref:`freebind <envoy_v3_api_field_config.listener.v3.Listener.freebind>`
         * :ref:`transparent <envoy_v3_api_field_config.listener.v3.Listener.transparent>`
         
        .envoy.config.listener.v3.Listener.InternalListenerConfig internal_listener = 27;
        Specified by:
        hasInternalListener in interface ListenerOrBuilder
        Returns:
        Whether the internalListener field is set.
      • getInternalListener

        public Listener.InternalListenerConfig getInternalListener()
         Used to represent an internal listener which does not listen on OSI L4 address but can be used by the
         :ref:`envoy cluster <envoy_v3_api_msg_config.cluster.v3.Cluster>` to create a user space connection to.
         The internal listener acts as a TCP listener. It supports listener filters and network filter chains.
         Upstream clusters refer to the internal listeners by their :ref:`name
         <envoy_v3_api_field_config.listener.v3.Listener.name>`. :ref:`Address
         <envoy_v3_api_field_config.listener.v3.Listener.address>` must not be set on the internal listeners.
        
         There are some limitations that are derived from the implementation. The known limitations include:
        
         * :ref:`ConnectionBalanceConfig <envoy_v3_api_msg_config.listener.v3.Listener.ConnectionBalanceConfig>` is not
         allowed because both the cluster connection and the listener connection must be owned by the same dispatcher.
         * :ref:`tcp_backlog_size <envoy_v3_api_field_config.listener.v3.Listener.tcp_backlog_size>`
         * :ref:`freebind <envoy_v3_api_field_config.listener.v3.Listener.freebind>`
         * :ref:`transparent <envoy_v3_api_field_config.listener.v3.Listener.transparent>`
         
        .envoy.config.listener.v3.Listener.InternalListenerConfig internal_listener = 27;
        Specified by:
        getInternalListener in interface ListenerOrBuilder
        Returns:
        The internalListener.
      • setInternalListener

        public Listener.Builder setInternalListener​(Listener.InternalListenerConfig value)
         Used to represent an internal listener which does not listen on OSI L4 address but can be used by the
         :ref:`envoy cluster <envoy_v3_api_msg_config.cluster.v3.Cluster>` to create a user space connection to.
         The internal listener acts as a TCP listener. It supports listener filters and network filter chains.
         Upstream clusters refer to the internal listeners by their :ref:`name
         <envoy_v3_api_field_config.listener.v3.Listener.name>`. :ref:`Address
         <envoy_v3_api_field_config.listener.v3.Listener.address>` must not be set on the internal listeners.
        
         There are some limitations that are derived from the implementation. The known limitations include:
        
         * :ref:`ConnectionBalanceConfig <envoy_v3_api_msg_config.listener.v3.Listener.ConnectionBalanceConfig>` is not
         allowed because both the cluster connection and the listener connection must be owned by the same dispatcher.
         * :ref:`tcp_backlog_size <envoy_v3_api_field_config.listener.v3.Listener.tcp_backlog_size>`
         * :ref:`freebind <envoy_v3_api_field_config.listener.v3.Listener.freebind>`
         * :ref:`transparent <envoy_v3_api_field_config.listener.v3.Listener.transparent>`
         
        .envoy.config.listener.v3.Listener.InternalListenerConfig internal_listener = 27;
      • setInternalListener

        public Listener.Builder setInternalListener​(Listener.InternalListenerConfig.Builder builderForValue)
         Used to represent an internal listener which does not listen on OSI L4 address but can be used by the
         :ref:`envoy cluster <envoy_v3_api_msg_config.cluster.v3.Cluster>` to create a user space connection to.
         The internal listener acts as a TCP listener. It supports listener filters and network filter chains.
         Upstream clusters refer to the internal listeners by their :ref:`name
         <envoy_v3_api_field_config.listener.v3.Listener.name>`. :ref:`Address
         <envoy_v3_api_field_config.listener.v3.Listener.address>` must not be set on the internal listeners.
        
         There are some limitations that are derived from the implementation. The known limitations include:
        
         * :ref:`ConnectionBalanceConfig <envoy_v3_api_msg_config.listener.v3.Listener.ConnectionBalanceConfig>` is not
         allowed because both the cluster connection and the listener connection must be owned by the same dispatcher.
         * :ref:`tcp_backlog_size <envoy_v3_api_field_config.listener.v3.Listener.tcp_backlog_size>`
         * :ref:`freebind <envoy_v3_api_field_config.listener.v3.Listener.freebind>`
         * :ref:`transparent <envoy_v3_api_field_config.listener.v3.Listener.transparent>`
         
        .envoy.config.listener.v3.Listener.InternalListenerConfig internal_listener = 27;
      • mergeInternalListener

        public Listener.Builder mergeInternalListener​(Listener.InternalListenerConfig value)
         Used to represent an internal listener which does not listen on OSI L4 address but can be used by the
         :ref:`envoy cluster <envoy_v3_api_msg_config.cluster.v3.Cluster>` to create a user space connection to.
         The internal listener acts as a TCP listener. It supports listener filters and network filter chains.
         Upstream clusters refer to the internal listeners by their :ref:`name
         <envoy_v3_api_field_config.listener.v3.Listener.name>`. :ref:`Address
         <envoy_v3_api_field_config.listener.v3.Listener.address>` must not be set on the internal listeners.
        
         There are some limitations that are derived from the implementation. The known limitations include:
        
         * :ref:`ConnectionBalanceConfig <envoy_v3_api_msg_config.listener.v3.Listener.ConnectionBalanceConfig>` is not
         allowed because both the cluster connection and the listener connection must be owned by the same dispatcher.
         * :ref:`tcp_backlog_size <envoy_v3_api_field_config.listener.v3.Listener.tcp_backlog_size>`
         * :ref:`freebind <envoy_v3_api_field_config.listener.v3.Listener.freebind>`
         * :ref:`transparent <envoy_v3_api_field_config.listener.v3.Listener.transparent>`
         
        .envoy.config.listener.v3.Listener.InternalListenerConfig internal_listener = 27;
      • clearInternalListener

        public Listener.Builder clearInternalListener()
         Used to represent an internal listener which does not listen on OSI L4 address but can be used by the
         :ref:`envoy cluster <envoy_v3_api_msg_config.cluster.v3.Cluster>` to create a user space connection to.
         The internal listener acts as a TCP listener. It supports listener filters and network filter chains.
         Upstream clusters refer to the internal listeners by their :ref:`name
         <envoy_v3_api_field_config.listener.v3.Listener.name>`. :ref:`Address
         <envoy_v3_api_field_config.listener.v3.Listener.address>` must not be set on the internal listeners.
        
         There are some limitations that are derived from the implementation. The known limitations include:
        
         * :ref:`ConnectionBalanceConfig <envoy_v3_api_msg_config.listener.v3.Listener.ConnectionBalanceConfig>` is not
         allowed because both the cluster connection and the listener connection must be owned by the same dispatcher.
         * :ref:`tcp_backlog_size <envoy_v3_api_field_config.listener.v3.Listener.tcp_backlog_size>`
         * :ref:`freebind <envoy_v3_api_field_config.listener.v3.Listener.freebind>`
         * :ref:`transparent <envoy_v3_api_field_config.listener.v3.Listener.transparent>`
         
        .envoy.config.listener.v3.Listener.InternalListenerConfig internal_listener = 27;
      • getInternalListenerBuilder

        public Listener.InternalListenerConfig.Builder getInternalListenerBuilder()
         Used to represent an internal listener which does not listen on OSI L4 address but can be used by the
         :ref:`envoy cluster <envoy_v3_api_msg_config.cluster.v3.Cluster>` to create a user space connection to.
         The internal listener acts as a TCP listener. It supports listener filters and network filter chains.
         Upstream clusters refer to the internal listeners by their :ref:`name
         <envoy_v3_api_field_config.listener.v3.Listener.name>`. :ref:`Address
         <envoy_v3_api_field_config.listener.v3.Listener.address>` must not be set on the internal listeners.
        
         There are some limitations that are derived from the implementation. The known limitations include:
        
         * :ref:`ConnectionBalanceConfig <envoy_v3_api_msg_config.listener.v3.Listener.ConnectionBalanceConfig>` is not
         allowed because both the cluster connection and the listener connection must be owned by the same dispatcher.
         * :ref:`tcp_backlog_size <envoy_v3_api_field_config.listener.v3.Listener.tcp_backlog_size>`
         * :ref:`freebind <envoy_v3_api_field_config.listener.v3.Listener.freebind>`
         * :ref:`transparent <envoy_v3_api_field_config.listener.v3.Listener.transparent>`
         
        .envoy.config.listener.v3.Listener.InternalListenerConfig internal_listener = 27;
      • getInternalListenerOrBuilder

        public Listener.InternalListenerConfigOrBuilder getInternalListenerOrBuilder()
         Used to represent an internal listener which does not listen on OSI L4 address but can be used by the
         :ref:`envoy cluster <envoy_v3_api_msg_config.cluster.v3.Cluster>` to create a user space connection to.
         The internal listener acts as a TCP listener. It supports listener filters and network filter chains.
         Upstream clusters refer to the internal listeners by their :ref:`name
         <envoy_v3_api_field_config.listener.v3.Listener.name>`. :ref:`Address
         <envoy_v3_api_field_config.listener.v3.Listener.address>` must not be set on the internal listeners.
        
         There are some limitations that are derived from the implementation. The known limitations include:
        
         * :ref:`ConnectionBalanceConfig <envoy_v3_api_msg_config.listener.v3.Listener.ConnectionBalanceConfig>` is not
         allowed because both the cluster connection and the listener connection must be owned by the same dispatcher.
         * :ref:`tcp_backlog_size <envoy_v3_api_field_config.listener.v3.Listener.tcp_backlog_size>`
         * :ref:`freebind <envoy_v3_api_field_config.listener.v3.Listener.freebind>`
         * :ref:`transparent <envoy_v3_api_field_config.listener.v3.Listener.transparent>`
         
        .envoy.config.listener.v3.Listener.InternalListenerConfig internal_listener = 27;
        Specified by:
        getInternalListenerOrBuilder in interface ListenerOrBuilder
      • getInternalListenerFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<Listener.InternalListenerConfig,​Listener.InternalListenerConfig.Builder,​Listener.InternalListenerConfigOrBuilder> getInternalListenerFieldBuilder()
         Used to represent an internal listener which does not listen on OSI L4 address but can be used by the
         :ref:`envoy cluster <envoy_v3_api_msg_config.cluster.v3.Cluster>` to create a user space connection to.
         The internal listener acts as a TCP listener. It supports listener filters and network filter chains.
         Upstream clusters refer to the internal listeners by their :ref:`name
         <envoy_v3_api_field_config.listener.v3.Listener.name>`. :ref:`Address
         <envoy_v3_api_field_config.listener.v3.Listener.address>` must not be set on the internal listeners.
        
         There are some limitations that are derived from the implementation. The known limitations include:
        
         * :ref:`ConnectionBalanceConfig <envoy_v3_api_msg_config.listener.v3.Listener.ConnectionBalanceConfig>` is not
         allowed because both the cluster connection and the listener connection must be owned by the same dispatcher.
         * :ref:`tcp_backlog_size <envoy_v3_api_field_config.listener.v3.Listener.tcp_backlog_size>`
         * :ref:`freebind <envoy_v3_api_field_config.listener.v3.Listener.freebind>`
         * :ref:`transparent <envoy_v3_api_field_config.listener.v3.Listener.transparent>`
         
        .envoy.config.listener.v3.Listener.InternalListenerConfig internal_listener = 27;
      • getEnableMptcp

        public boolean getEnableMptcp()
         Enable MPTCP (multi-path TCP) on this listener. Clients will be allowed to establish
         MPTCP connections. Non-MPTCP clients will fall back to regular TCP.
         
        bool enable_mptcp = 30;
        Specified by:
        getEnableMptcp in interface ListenerOrBuilder
        Returns:
        The enableMptcp.
      • setEnableMptcp

        public Listener.Builder setEnableMptcp​(boolean value)
         Enable MPTCP (multi-path TCP) on this listener. Clients will be allowed to establish
         MPTCP connections. Non-MPTCP clients will fall back to regular TCP.
         
        bool enable_mptcp = 30;
        Parameters:
        value - The enableMptcp to set.
        Returns:
        This builder for chaining.
      • clearEnableMptcp

        public Listener.Builder clearEnableMptcp()
         Enable MPTCP (multi-path TCP) on this listener. Clients will be allowed to establish
         MPTCP connections. Non-MPTCP clients will fall back to regular TCP.
         
        bool enable_mptcp = 30;
        Returns:
        This builder for chaining.
      • getIgnoreGlobalConnLimit

        public boolean getIgnoreGlobalConnLimit()
         Whether the listener should limit connections based upon the value of
         :ref:`global_downstream_max_connections <config_overload_manager_limiting_connections>`.
         
        bool ignore_global_conn_limit = 31;
        Specified by:
        getIgnoreGlobalConnLimit in interface ListenerOrBuilder
        Returns:
        The ignoreGlobalConnLimit.
      • setIgnoreGlobalConnLimit

        public Listener.Builder setIgnoreGlobalConnLimit​(boolean value)
         Whether the listener should limit connections based upon the value of
         :ref:`global_downstream_max_connections <config_overload_manager_limiting_connections>`.
         
        bool ignore_global_conn_limit = 31;
        Parameters:
        value - The ignoreGlobalConnLimit to set.
        Returns:
        This builder for chaining.
      • clearIgnoreGlobalConnLimit

        public Listener.Builder clearIgnoreGlobalConnLimit()
         Whether the listener should limit connections based upon the value of
         :ref:`global_downstream_max_connections <config_overload_manager_limiting_connections>`.
         
        bool ignore_global_conn_limit = 31;
        Returns:
        This builder for chaining.
      • getBypassOverloadManager

        public boolean getBypassOverloadManager()
         Whether the listener bypasses configured overload manager actions.
         
        bool bypass_overload_manager = 35;
        Specified by:
        getBypassOverloadManager in interface ListenerOrBuilder
        Returns:
        The bypassOverloadManager.
      • setBypassOverloadManager

        public Listener.Builder setBypassOverloadManager​(boolean value)
         Whether the listener bypasses configured overload manager actions.
         
        bool bypass_overload_manager = 35;
        Parameters:
        value - The bypassOverloadManager to set.
        Returns:
        This builder for chaining.
      • clearBypassOverloadManager

        public Listener.Builder clearBypassOverloadManager()
         Whether the listener bypasses configured overload manager actions.
         
        bool bypass_overload_manager = 35;
        Returns:
        This builder for chaining.