Package io.envoyproxy.envoy.config.core.v3

Class Http2ProtocolOptions.Builder

    • Method Detail

      • getDescriptor

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

      • internalGetFieldAccessorTable

        protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
        Specified by:
        internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<Http2ProtocolOptions.Builder>

      • clear

        public Http2ProtocolOptions.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.GeneratedMessageV3.Builder<Http2ProtocolOptions.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.GeneratedMessageV3.Builder<Http2ProtocolOptions.Builder>

      • getDefaultInstanceForType

        public Http2ProtocolOptions getDefaultInstanceForType()
        Specified by:
        getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
        Specified by:
        getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

      • build

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

      • buildPartial

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

      • clone

        public Http2ProtocolOptions.Builder clone()
        Specified by:
        clone in interface com.google.protobuf.Message.Builder
        Specified by:
        clone in interface com.google.protobuf.MessageLite.Builder
        Overrides:
        clone in class com.google.protobuf.GeneratedMessageV3.Builder<Http2ProtocolOptions.Builder>

      • setField

        public Http2ProtocolOptions.Builder setField​(com.google.protobuf.Descriptors.FieldDescriptor field,
                                             Object value)
        Specified by:
        setField in interface com.google.protobuf.Message.Builder
        Overrides:
        setField in class com.google.protobuf.GeneratedMessageV3.Builder<Http2ProtocolOptions.Builder>

      • clearField

        public Http2ProtocolOptions.Builder clearField​(com.google.protobuf.Descriptors.FieldDescriptor field)
        Specified by:
        clearField in interface com.google.protobuf.Message.Builder
        Overrides:
        clearField in class com.google.protobuf.GeneratedMessageV3.Builder<Http2ProtocolOptions.Builder>

      • clearOneof

        public Http2ProtocolOptions.Builder clearOneof​(com.google.protobuf.Descriptors.OneofDescriptor oneof)
        Specified by:
        clearOneof in interface com.google.protobuf.Message.Builder
        Overrides:
        clearOneof in class com.google.protobuf.GeneratedMessageV3.Builder<Http2ProtocolOptions.Builder>

      • setRepeatedField

        public Http2ProtocolOptions.Builder setRepeatedField​(com.google.protobuf.Descriptors.FieldDescriptor field,
                                                     int index,
                                                     Object value)
        Specified by:
        setRepeatedField in interface com.google.protobuf.Message.Builder
        Overrides:
        setRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<Http2ProtocolOptions.Builder>

      • addRepeatedField

        public Http2ProtocolOptions.Builder addRepeatedField​(com.google.protobuf.Descriptors.FieldDescriptor field,
                                                     Object value)
        Specified by:
        addRepeatedField in interface com.google.protobuf.Message.Builder
        Overrides:
        addRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<Http2ProtocolOptions.Builder>

      • isInitialized

        public final boolean isInitialized()
        Specified by:
        isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
        Overrides:
        isInitialized in class com.google.protobuf.GeneratedMessageV3.Builder<Http2ProtocolOptions.Builder>

      • mergeFrom

        public Http2ProtocolOptions.Builder mergeFrom​(com.google.protobuf.CodedInputStream input,
                                              com.google.protobuf.ExtensionRegistryLite extensionRegistry)
                                       throws 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<Http2ProtocolOptions.Builder>
        Throws:
        IOException

      • hasHpackTableSize

        public boolean hasHpackTableSize()
         `Maximum table size <https://httpwg.org/specs/rfc7541.html#rfc.section.4.2>`_
 (in octets) that the encoder is permitted to use for the dynamic HPACK table. Valid values
 range from 0 to 4294967295 (2^32 - 1) and defaults to 4096. 0 effectively disables header
 compression.
        .google.protobuf.UInt32Value hpack_table_size = 1;
        Specified by:
        hasHpackTableSize in interface Http2ProtocolOptionsOrBuilder
        Returns:
        Whether the hpackTableSize field is set.

      • getHpackTableSize

        public com.google.protobuf.UInt32Value getHpackTableSize()
         `Maximum table size <https://httpwg.org/specs/rfc7541.html#rfc.section.4.2>`_
 (in octets) that the encoder is permitted to use for the dynamic HPACK table. Valid values
 range from 0 to 4294967295 (2^32 - 1) and defaults to 4096. 0 effectively disables header
 compression.
        .google.protobuf.UInt32Value hpack_table_size = 1;
        Specified by:
        getHpackTableSize in interface Http2ProtocolOptionsOrBuilder
        Returns:
        The hpackTableSize.

      • setHpackTableSize

        public Http2ProtocolOptions.Builder setHpackTableSize​(com.google.protobuf.UInt32Value value)
         `Maximum table size <https://httpwg.org/specs/rfc7541.html#rfc.section.4.2>`_
 (in octets) that the encoder is permitted to use for the dynamic HPACK table. Valid values
 range from 0 to 4294967295 (2^32 - 1) and defaults to 4096. 0 effectively disables header
 compression.
        .google.protobuf.UInt32Value hpack_table_size = 1;

      • setHpackTableSize

        public Http2ProtocolOptions.Builder setHpackTableSize​(com.google.protobuf.UInt32Value.Builder builderForValue)
         `Maximum table size <https://httpwg.org/specs/rfc7541.html#rfc.section.4.2>`_
 (in octets) that the encoder is permitted to use for the dynamic HPACK table. Valid values
 range from 0 to 4294967295 (2^32 - 1) and defaults to 4096. 0 effectively disables header
 compression.
        .google.protobuf.UInt32Value hpack_table_size = 1;

      • mergeHpackTableSize

        public Http2ProtocolOptions.Builder mergeHpackTableSize​(com.google.protobuf.UInt32Value value)
         `Maximum table size <https://httpwg.org/specs/rfc7541.html#rfc.section.4.2>`_
 (in octets) that the encoder is permitted to use for the dynamic HPACK table. Valid values
 range from 0 to 4294967295 (2^32 - 1) and defaults to 4096. 0 effectively disables header
 compression.
        .google.protobuf.UInt32Value hpack_table_size = 1;

      • clearHpackTableSize

        public Http2ProtocolOptions.Builder clearHpackTableSize()
         `Maximum table size <https://httpwg.org/specs/rfc7541.html#rfc.section.4.2>`_
 (in octets) that the encoder is permitted to use for the dynamic HPACK table. Valid values
 range from 0 to 4294967295 (2^32 - 1) and defaults to 4096. 0 effectively disables header
 compression.
        .google.protobuf.UInt32Value hpack_table_size = 1;

      • getHpackTableSizeBuilder

        public com.google.protobuf.UInt32Value.Builder getHpackTableSizeBuilder()
         `Maximum table size <https://httpwg.org/specs/rfc7541.html#rfc.section.4.2>`_
 (in octets) that the encoder is permitted to use for the dynamic HPACK table. Valid values
 range from 0 to 4294967295 (2^32 - 1) and defaults to 4096. 0 effectively disables header
 compression.
        .google.protobuf.UInt32Value hpack_table_size = 1;

      • getHpackTableSizeOrBuilder

        public com.google.protobuf.UInt32ValueOrBuilder getHpackTableSizeOrBuilder()
         `Maximum table size <https://httpwg.org/specs/rfc7541.html#rfc.section.4.2>`_
 (in octets) that the encoder is permitted to use for the dynamic HPACK table. Valid values
 range from 0 to 4294967295 (2^32 - 1) and defaults to 4096. 0 effectively disables header
 compression.
        .google.protobuf.UInt32Value hpack_table_size = 1;
        Specified by:
        getHpackTableSizeOrBuilder in interface Http2ProtocolOptionsOrBuilder

      • hasMaxConcurrentStreams

        public boolean hasMaxConcurrentStreams()
         `Maximum concurrent streams <https://httpwg.org/specs/rfc7540.html#rfc.section.5.1.2>`_
 allowed for peer on one HTTP/2 connection. Valid values range from 1 to 2147483647 (2^31 - 1)
 and defaults to 2147483647.
 For upstream connections, this also limits how many streams Envoy will initiate concurrently
 on a single connection. If the limit is reached, Envoy may queue requests or establish
 additional connections (as allowed per circuit breaker limits).
 This acts as an upper bound: Envoy will lower the max concurrent streams allowed on a given
 connection based on upstream settings. Config dumps will reflect the configured upper bound,
 not the per-connection negotiated limits.
        .google.protobuf.UInt32Value max_concurrent_streams = 2 [(.validate.rules) = { ... }
        Specified by:
        hasMaxConcurrentStreams in interface Http2ProtocolOptionsOrBuilder
        Returns:
        Whether the maxConcurrentStreams field is set.

      • getMaxConcurrentStreams

        public com.google.protobuf.UInt32Value getMaxConcurrentStreams()
         `Maximum concurrent streams <https://httpwg.org/specs/rfc7540.html#rfc.section.5.1.2>`_
 allowed for peer on one HTTP/2 connection. Valid values range from 1 to 2147483647 (2^31 - 1)
 and defaults to 2147483647.
 For upstream connections, this also limits how many streams Envoy will initiate concurrently
 on a single connection. If the limit is reached, Envoy may queue requests or establish
 additional connections (as allowed per circuit breaker limits).
 This acts as an upper bound: Envoy will lower the max concurrent streams allowed on a given
 connection based on upstream settings. Config dumps will reflect the configured upper bound,
 not the per-connection negotiated limits.
        .google.protobuf.UInt32Value max_concurrent_streams = 2 [(.validate.rules) = { ... }
        Specified by:
        getMaxConcurrentStreams in interface Http2ProtocolOptionsOrBuilder
        Returns:
        The maxConcurrentStreams.

      • setMaxConcurrentStreams

        public Http2ProtocolOptions.Builder setMaxConcurrentStreams​(com.google.protobuf.UInt32Value value)
         `Maximum concurrent streams <https://httpwg.org/specs/rfc7540.html#rfc.section.5.1.2>`_
 allowed for peer on one HTTP/2 connection. Valid values range from 1 to 2147483647 (2^31 - 1)
 and defaults to 2147483647.
 For upstream connections, this also limits how many streams Envoy will initiate concurrently
 on a single connection. If the limit is reached, Envoy may queue requests or establish
 additional connections (as allowed per circuit breaker limits).
 This acts as an upper bound: Envoy will lower the max concurrent streams allowed on a given
 connection based on upstream settings. Config dumps will reflect the configured upper bound,
 not the per-connection negotiated limits.
        .google.protobuf.UInt32Value max_concurrent_streams = 2 [(.validate.rules) = { ... }

      • setMaxConcurrentStreams

        public Http2ProtocolOptions.Builder setMaxConcurrentStreams​(com.google.protobuf.UInt32Value.Builder builderForValue)
         `Maximum concurrent streams <https://httpwg.org/specs/rfc7540.html#rfc.section.5.1.2>`_
 allowed for peer on one HTTP/2 connection. Valid values range from 1 to 2147483647 (2^31 - 1)
 and defaults to 2147483647.
 For upstream connections, this also limits how many streams Envoy will initiate concurrently
 on a single connection. If the limit is reached, Envoy may queue requests or establish
 additional connections (as allowed per circuit breaker limits).
 This acts as an upper bound: Envoy will lower the max concurrent streams allowed on a given
 connection based on upstream settings. Config dumps will reflect the configured upper bound,
 not the per-connection negotiated limits.
        .google.protobuf.UInt32Value max_concurrent_streams = 2 [(.validate.rules) = { ... }

      • mergeMaxConcurrentStreams

        public Http2ProtocolOptions.Builder mergeMaxConcurrentStreams​(com.google.protobuf.UInt32Value value)
         `Maximum concurrent streams <https://httpwg.org/specs/rfc7540.html#rfc.section.5.1.2>`_
 allowed for peer on one HTTP/2 connection. Valid values range from 1 to 2147483647 (2^31 - 1)
 and defaults to 2147483647.
 For upstream connections, this also limits how many streams Envoy will initiate concurrently
 on a single connection. If the limit is reached, Envoy may queue requests or establish
 additional connections (as allowed per circuit breaker limits).
 This acts as an upper bound: Envoy will lower the max concurrent streams allowed on a given
 connection based on upstream settings. Config dumps will reflect the configured upper bound,
 not the per-connection negotiated limits.
        .google.protobuf.UInt32Value max_concurrent_streams = 2 [(.validate.rules) = { ... }

      • clearMaxConcurrentStreams

        public Http2ProtocolOptions.Builder clearMaxConcurrentStreams()
         `Maximum concurrent streams <https://httpwg.org/specs/rfc7540.html#rfc.section.5.1.2>`_
 allowed for peer on one HTTP/2 connection. Valid values range from 1 to 2147483647 (2^31 - 1)
 and defaults to 2147483647.
 For upstream connections, this also limits how many streams Envoy will initiate concurrently
 on a single connection. If the limit is reached, Envoy may queue requests or establish
 additional connections (as allowed per circuit breaker limits).
 This acts as an upper bound: Envoy will lower the max concurrent streams allowed on a given
 connection based on upstream settings. Config dumps will reflect the configured upper bound,
 not the per-connection negotiated limits.
        .google.protobuf.UInt32Value max_concurrent_streams = 2 [(.validate.rules) = { ... }

      • getMaxConcurrentStreamsBuilder

        public com.google.protobuf.UInt32Value.Builder getMaxConcurrentStreamsBuilder()
         `Maximum concurrent streams <https://httpwg.org/specs/rfc7540.html#rfc.section.5.1.2>`_
 allowed for peer on one HTTP/2 connection. Valid values range from 1 to 2147483647 (2^31 - 1)
 and defaults to 2147483647.
 For upstream connections, this also limits how many streams Envoy will initiate concurrently
 on a single connection. If the limit is reached, Envoy may queue requests or establish
 additional connections (as allowed per circuit breaker limits).
 This acts as an upper bound: Envoy will lower the max concurrent streams allowed on a given
 connection based on upstream settings. Config dumps will reflect the configured upper bound,
 not the per-connection negotiated limits.
        .google.protobuf.UInt32Value max_concurrent_streams = 2 [(.validate.rules) = { ... }

      • getMaxConcurrentStreamsOrBuilder

        public com.google.protobuf.UInt32ValueOrBuilder getMaxConcurrentStreamsOrBuilder()
         `Maximum concurrent streams <https://httpwg.org/specs/rfc7540.html#rfc.section.5.1.2>`_
 allowed for peer on one HTTP/2 connection. Valid values range from 1 to 2147483647 (2^31 - 1)
 and defaults to 2147483647.
 For upstream connections, this also limits how many streams Envoy will initiate concurrently
 on a single connection. If the limit is reached, Envoy may queue requests or establish
 additional connections (as allowed per circuit breaker limits).
 This acts as an upper bound: Envoy will lower the max concurrent streams allowed on a given
 connection based on upstream settings. Config dumps will reflect the configured upper bound,
 not the per-connection negotiated limits.
        .google.protobuf.UInt32Value max_concurrent_streams = 2 [(.validate.rules) = { ... }
        Specified by:
        getMaxConcurrentStreamsOrBuilder in interface Http2ProtocolOptionsOrBuilder

      • hasInitialStreamWindowSize

        public boolean hasInitialStreamWindowSize()
         `Initial stream-level flow-control window
 <https://httpwg.org/specs/rfc7540.html#rfc.section.6.9.2>`_ size. Valid values range from 65535
 (2^16 - 1, HTTP/2 default) to 2147483647 (2^31 - 1, HTTP/2 maximum) and defaults to 268435456
 (256 * 1024 * 1024).
 NOTE: 65535 is the initial window size from HTTP/2 spec. We only support increasing the default
 window size now, so it's also the minimum.
 This field also acts as a soft limit on the number of bytes Envoy will buffer per-stream in the
 HTTP/2 codec buffers. Once the buffer reaches this pointer, watermark callbacks will fire to
 stop the flow of data to the codec buffers.
        .google.protobuf.UInt32Value initial_stream_window_size = 3 [(.validate.rules) = { ... }
        Specified by:
        hasInitialStreamWindowSize in interface Http2ProtocolOptionsOrBuilder
        Returns:
        Whether the initialStreamWindowSize field is set.

      • getInitialStreamWindowSize

        public com.google.protobuf.UInt32Value getInitialStreamWindowSize()
         `Initial stream-level flow-control window
 <https://httpwg.org/specs/rfc7540.html#rfc.section.6.9.2>`_ size. Valid values range from 65535
 (2^16 - 1, HTTP/2 default) to 2147483647 (2^31 - 1, HTTP/2 maximum) and defaults to 268435456
 (256 * 1024 * 1024).
 NOTE: 65535 is the initial window size from HTTP/2 spec. We only support increasing the default
 window size now, so it's also the minimum.
 This field also acts as a soft limit on the number of bytes Envoy will buffer per-stream in the
 HTTP/2 codec buffers. Once the buffer reaches this pointer, watermark callbacks will fire to
 stop the flow of data to the codec buffers.
        .google.protobuf.UInt32Value initial_stream_window_size = 3 [(.validate.rules) = { ... }
        Specified by:
        getInitialStreamWindowSize in interface Http2ProtocolOptionsOrBuilder
        Returns:
        The initialStreamWindowSize.

      • setInitialStreamWindowSize

        public Http2ProtocolOptions.Builder setInitialStreamWindowSize​(com.google.protobuf.UInt32Value value)
         `Initial stream-level flow-control window
 <https://httpwg.org/specs/rfc7540.html#rfc.section.6.9.2>`_ size. Valid values range from 65535
 (2^16 - 1, HTTP/2 default) to 2147483647 (2^31 - 1, HTTP/2 maximum) and defaults to 268435456
 (256 * 1024 * 1024).
 NOTE: 65535 is the initial window size from HTTP/2 spec. We only support increasing the default
 window size now, so it's also the minimum.
 This field also acts as a soft limit on the number of bytes Envoy will buffer per-stream in the
 HTTP/2 codec buffers. Once the buffer reaches this pointer, watermark callbacks will fire to
 stop the flow of data to the codec buffers.
        .google.protobuf.UInt32Value initial_stream_window_size = 3 [(.validate.rules) = { ... }

      • setInitialStreamWindowSize

        public Http2ProtocolOptions.Builder setInitialStreamWindowSize​(com.google.protobuf.UInt32Value.Builder builderForValue)
         `Initial stream-level flow-control window
 <https://httpwg.org/specs/rfc7540.html#rfc.section.6.9.2>`_ size. Valid values range from 65535
 (2^16 - 1, HTTP/2 default) to 2147483647 (2^31 - 1, HTTP/2 maximum) and defaults to 268435456
 (256 * 1024 * 1024).
 NOTE: 65535 is the initial window size from HTTP/2 spec. We only support increasing the default
 window size now, so it's also the minimum.
 This field also acts as a soft limit on the number of bytes Envoy will buffer per-stream in the
 HTTP/2 codec buffers. Once the buffer reaches this pointer, watermark callbacks will fire to
 stop the flow of data to the codec buffers.
        .google.protobuf.UInt32Value initial_stream_window_size = 3 [(.validate.rules) = { ... }

      • mergeInitialStreamWindowSize

        public Http2ProtocolOptions.Builder mergeInitialStreamWindowSize​(com.google.protobuf.UInt32Value value)
         `Initial stream-level flow-control window
 <https://httpwg.org/specs/rfc7540.html#rfc.section.6.9.2>`_ size. Valid values range from 65535
 (2^16 - 1, HTTP/2 default) to 2147483647 (2^31 - 1, HTTP/2 maximum) and defaults to 268435456
 (256 * 1024 * 1024).
 NOTE: 65535 is the initial window size from HTTP/2 spec. We only support increasing the default
 window size now, so it's also the minimum.
 This field also acts as a soft limit on the number of bytes Envoy will buffer per-stream in the
 HTTP/2 codec buffers. Once the buffer reaches this pointer, watermark callbacks will fire to
 stop the flow of data to the codec buffers.
        .google.protobuf.UInt32Value initial_stream_window_size = 3 [(.validate.rules) = { ... }

      • clearInitialStreamWindowSize

        public Http2ProtocolOptions.Builder clearInitialStreamWindowSize()
         `Initial stream-level flow-control window
 <https://httpwg.org/specs/rfc7540.html#rfc.section.6.9.2>`_ size. Valid values range from 65535
 (2^16 - 1, HTTP/2 default) to 2147483647 (2^31 - 1, HTTP/2 maximum) and defaults to 268435456
 (256 * 1024 * 1024).
 NOTE: 65535 is the initial window size from HTTP/2 spec. We only support increasing the default
 window size now, so it's also the minimum.
 This field also acts as a soft limit on the number of bytes Envoy will buffer per-stream in the
 HTTP/2 codec buffers. Once the buffer reaches this pointer, watermark callbacks will fire to
 stop the flow of data to the codec buffers.
        .google.protobuf.UInt32Value initial_stream_window_size = 3 [(.validate.rules) = { ... }

      • getInitialStreamWindowSizeBuilder

        public com.google.protobuf.UInt32Value.Builder getInitialStreamWindowSizeBuilder()
         `Initial stream-level flow-control window
 <https://httpwg.org/specs/rfc7540.html#rfc.section.6.9.2>`_ size. Valid values range from 65535
 (2^16 - 1, HTTP/2 default) to 2147483647 (2^31 - 1, HTTP/2 maximum) and defaults to 268435456
 (256 * 1024 * 1024).
 NOTE: 65535 is the initial window size from HTTP/2 spec. We only support increasing the default
 window size now, so it's also the minimum.
 This field also acts as a soft limit on the number of bytes Envoy will buffer per-stream in the
 HTTP/2 codec buffers. Once the buffer reaches this pointer, watermark callbacks will fire to
 stop the flow of data to the codec buffers.
        .google.protobuf.UInt32Value initial_stream_window_size = 3 [(.validate.rules) = { ... }

      • getInitialStreamWindowSizeOrBuilder

        public com.google.protobuf.UInt32ValueOrBuilder getInitialStreamWindowSizeOrBuilder()
         `Initial stream-level flow-control window
 <https://httpwg.org/specs/rfc7540.html#rfc.section.6.9.2>`_ size. Valid values range from 65535
 (2^16 - 1, HTTP/2 default) to 2147483647 (2^31 - 1, HTTP/2 maximum) and defaults to 268435456
 (256 * 1024 * 1024).
 NOTE: 65535 is the initial window size from HTTP/2 spec. We only support increasing the default
 window size now, so it's also the minimum.
 This field also acts as a soft limit on the number of bytes Envoy will buffer per-stream in the
 HTTP/2 codec buffers. Once the buffer reaches this pointer, watermark callbacks will fire to
 stop the flow of data to the codec buffers.
        .google.protobuf.UInt32Value initial_stream_window_size = 3 [(.validate.rules) = { ... }
        Specified by:
        getInitialStreamWindowSizeOrBuilder in interface Http2ProtocolOptionsOrBuilder

      • hasInitialConnectionWindowSize

        public boolean hasInitialConnectionWindowSize()
         Similar to ``initial_stream_window_size``, but for connection-level flow-control
 window. Currently, this has the same minimum/maximum/default as ``initial_stream_window_size``.
        .google.protobuf.UInt32Value initial_connection_window_size = 4 [(.validate.rules) = { ... }
        Specified by:
        hasInitialConnectionWindowSize in interface Http2ProtocolOptionsOrBuilder
        Returns:
        Whether the initialConnectionWindowSize field is set.

      • getInitialConnectionWindowSize

        public com.google.protobuf.UInt32Value getInitialConnectionWindowSize()
         Similar to ``initial_stream_window_size``, but for connection-level flow-control
 window. Currently, this has the same minimum/maximum/default as ``initial_stream_window_size``.
        .google.protobuf.UInt32Value initial_connection_window_size = 4 [(.validate.rules) = { ... }
        Specified by:
        getInitialConnectionWindowSize in interface Http2ProtocolOptionsOrBuilder
        Returns:
        The initialConnectionWindowSize.

      • setInitialConnectionWindowSize

        public Http2ProtocolOptions.Builder setInitialConnectionWindowSize​(com.google.protobuf.UInt32Value value)
         Similar to ``initial_stream_window_size``, but for connection-level flow-control
 window. Currently, this has the same minimum/maximum/default as ``initial_stream_window_size``.
        .google.protobuf.UInt32Value initial_connection_window_size = 4 [(.validate.rules) = { ... }

      • setInitialConnectionWindowSize

        public Http2ProtocolOptions.Builder setInitialConnectionWindowSize​(com.google.protobuf.UInt32Value.Builder builderForValue)
         Similar to ``initial_stream_window_size``, but for connection-level flow-control
 window. Currently, this has the same minimum/maximum/default as ``initial_stream_window_size``.
        .google.protobuf.UInt32Value initial_connection_window_size = 4 [(.validate.rules) = { ... }

      • mergeInitialConnectionWindowSize

        public Http2ProtocolOptions.Builder mergeInitialConnectionWindowSize​(com.google.protobuf.UInt32Value value)
         Similar to ``initial_stream_window_size``, but for connection-level flow-control
 window. Currently, this has the same minimum/maximum/default as ``initial_stream_window_size``.
        .google.protobuf.UInt32Value initial_connection_window_size = 4 [(.validate.rules) = { ... }

      • clearInitialConnectionWindowSize

        public Http2ProtocolOptions.Builder clearInitialConnectionWindowSize()
         Similar to ``initial_stream_window_size``, but for connection-level flow-control
 window. Currently, this has the same minimum/maximum/default as ``initial_stream_window_size``.
        .google.protobuf.UInt32Value initial_connection_window_size = 4 [(.validate.rules) = { ... }

      • getInitialConnectionWindowSizeBuilder

        public com.google.protobuf.UInt32Value.Builder getInitialConnectionWindowSizeBuilder()
         Similar to ``initial_stream_window_size``, but for connection-level flow-control
 window. Currently, this has the same minimum/maximum/default as ``initial_stream_window_size``.
        .google.protobuf.UInt32Value initial_connection_window_size = 4 [(.validate.rules) = { ... }

      • getInitialConnectionWindowSizeOrBuilder

        public com.google.protobuf.UInt32ValueOrBuilder getInitialConnectionWindowSizeOrBuilder()
         Similar to ``initial_stream_window_size``, but for connection-level flow-control
 window. Currently, this has the same minimum/maximum/default as ``initial_stream_window_size``.
        .google.protobuf.UInt32Value initial_connection_window_size = 4 [(.validate.rules) = { ... }
        Specified by:
        getInitialConnectionWindowSizeOrBuilder in interface Http2ProtocolOptionsOrBuilder

      • getAllowConnect

        public boolean getAllowConnect()
         Allows proxying Websocket and other upgrades over H2 connect.
        bool allow_connect = 5;
        Specified by:
        getAllowConnect in interface Http2ProtocolOptionsOrBuilder
        Returns:
        The allowConnect.

      • setAllowConnect

        public Http2ProtocolOptions.Builder setAllowConnect​(boolean value)
         Allows proxying Websocket and other upgrades over H2 connect.
        bool allow_connect = 5;
        Parameters:
        value - The allowConnect to set.
        Returns:
        This builder for chaining.

      • clearAllowConnect

        public Http2ProtocolOptions.Builder clearAllowConnect()
         Allows proxying Websocket and other upgrades over H2 connect.
        bool allow_connect = 5;
        Returns:
        This builder for chaining.

      • getAllowMetadata

        public boolean getAllowMetadata()
         [#not-implemented-hide:] Hiding until envoy has full metadata support.
 Still under implementation. DO NOT USE.
 Allows metadata. See [metadata
 docs](https://github.com/envoyproxy/envoy/blob/main/source/docs/h2_metadata.md) for more
 information.
        bool allow_metadata = 6;
        Specified by:
        getAllowMetadata in interface Http2ProtocolOptionsOrBuilder
        Returns:
        The allowMetadata.

      • setAllowMetadata

        public Http2ProtocolOptions.Builder setAllowMetadata​(boolean value)
         [#not-implemented-hide:] Hiding until envoy has full metadata support.
 Still under implementation. DO NOT USE.
 Allows metadata. See [metadata
 docs](https://github.com/envoyproxy/envoy/blob/main/source/docs/h2_metadata.md) for more
 information.
        bool allow_metadata = 6;
        Parameters:
        value - The allowMetadata to set.
        Returns:
        This builder for chaining.

      • clearAllowMetadata

        public Http2ProtocolOptions.Builder clearAllowMetadata()
         [#not-implemented-hide:] Hiding until envoy has full metadata support.
 Still under implementation. DO NOT USE.
 Allows metadata. See [metadata
 docs](https://github.com/envoyproxy/envoy/blob/main/source/docs/h2_metadata.md) for more
 information.
        bool allow_metadata = 6;
        Returns:
        This builder for chaining.

      • hasMaxOutboundFrames

        public boolean hasMaxOutboundFrames()
         Limit the number of pending outbound downstream frames of all types (frames that are waiting to
 be written into the socket). Exceeding this limit triggers flood mitigation and connection is
 terminated. The ``http2.outbound_flood`` stat tracks the number of terminated connections due
 to flood mitigation. The default limit is 10000.
        .google.protobuf.UInt32Value max_outbound_frames = 7 [(.validate.rules) = { ... }
        Specified by:
        hasMaxOutboundFrames in interface Http2ProtocolOptionsOrBuilder
        Returns:
        Whether the maxOutboundFrames field is set.

      • getMaxOutboundFrames

        public com.google.protobuf.UInt32Value getMaxOutboundFrames()
         Limit the number of pending outbound downstream frames of all types (frames that are waiting to
 be written into the socket). Exceeding this limit triggers flood mitigation and connection is
 terminated. The ``http2.outbound_flood`` stat tracks the number of terminated connections due
 to flood mitigation. The default limit is 10000.
        .google.protobuf.UInt32Value max_outbound_frames = 7 [(.validate.rules) = { ... }
        Specified by:
        getMaxOutboundFrames in interface Http2ProtocolOptionsOrBuilder
        Returns:
        The maxOutboundFrames.

      • setMaxOutboundFrames

        public Http2ProtocolOptions.Builder setMaxOutboundFrames​(com.google.protobuf.UInt32Value value)
         Limit the number of pending outbound downstream frames of all types (frames that are waiting to
 be written into the socket). Exceeding this limit triggers flood mitigation and connection is
 terminated. The ``http2.outbound_flood`` stat tracks the number of terminated connections due
 to flood mitigation. The default limit is 10000.
        .google.protobuf.UInt32Value max_outbound_frames = 7 [(.validate.rules) = { ... }

      • setMaxOutboundFrames

        public Http2ProtocolOptions.Builder setMaxOutboundFrames​(com.google.protobuf.UInt32Value.Builder builderForValue)
         Limit the number of pending outbound downstream frames of all types (frames that are waiting to
 be written into the socket). Exceeding this limit triggers flood mitigation and connection is
 terminated. The ``http2.outbound_flood`` stat tracks the number of terminated connections due
 to flood mitigation. The default limit is 10000.
        .google.protobuf.UInt32Value max_outbound_frames = 7 [(.validate.rules) = { ... }

      • mergeMaxOutboundFrames

        public Http2ProtocolOptions.Builder mergeMaxOutboundFrames​(com.google.protobuf.UInt32Value value)
         Limit the number of pending outbound downstream frames of all types (frames that are waiting to
 be written into the socket). Exceeding this limit triggers flood mitigation and connection is
 terminated. The ``http2.outbound_flood`` stat tracks the number of terminated connections due
 to flood mitigation. The default limit is 10000.
        .google.protobuf.UInt32Value max_outbound_frames = 7 [(.validate.rules) = { ... }

      • clearMaxOutboundFrames

        public Http2ProtocolOptions.Builder clearMaxOutboundFrames()
         Limit the number of pending outbound downstream frames of all types (frames that are waiting to
 be written into the socket). Exceeding this limit triggers flood mitigation and connection is
 terminated. The ``http2.outbound_flood`` stat tracks the number of terminated connections due
 to flood mitigation. The default limit is 10000.
        .google.protobuf.UInt32Value max_outbound_frames = 7 [(.validate.rules) = { ... }

      • getMaxOutboundFramesBuilder

        public com.google.protobuf.UInt32Value.Builder getMaxOutboundFramesBuilder()
         Limit the number of pending outbound downstream frames of all types (frames that are waiting to
 be written into the socket). Exceeding this limit triggers flood mitigation and connection is
 terminated. The ``http2.outbound_flood`` stat tracks the number of terminated connections due
 to flood mitigation. The default limit is 10000.
        .google.protobuf.UInt32Value max_outbound_frames = 7 [(.validate.rules) = { ... }

      • getMaxOutboundFramesOrBuilder

        public com.google.protobuf.UInt32ValueOrBuilder getMaxOutboundFramesOrBuilder()
         Limit the number of pending outbound downstream frames of all types (frames that are waiting to
 be written into the socket). Exceeding this limit triggers flood mitigation and connection is
 terminated. The ``http2.outbound_flood`` stat tracks the number of terminated connections due
 to flood mitigation. The default limit is 10000.
        .google.protobuf.UInt32Value max_outbound_frames = 7 [(.validate.rules) = { ... }
        Specified by:
        getMaxOutboundFramesOrBuilder in interface Http2ProtocolOptionsOrBuilder

      • hasMaxOutboundControlFrames

        public boolean hasMaxOutboundControlFrames()
         Limit the number of pending outbound downstream frames of types PING, SETTINGS and RST_STREAM,
 preventing high memory utilization when receiving continuous stream of these frames. Exceeding
 this limit triggers flood mitigation and connection is terminated. The
 ``http2.outbound_control_flood`` stat tracks the number of terminated connections due to flood
 mitigation. The default limit is 1000.
        .google.protobuf.UInt32Value max_outbound_control_frames = 8 [(.validate.rules) = { ... }
        Specified by:
        hasMaxOutboundControlFrames in interface Http2ProtocolOptionsOrBuilder
        Returns:
        Whether the maxOutboundControlFrames field is set.

      • getMaxOutboundControlFrames

        public com.google.protobuf.UInt32Value getMaxOutboundControlFrames()
         Limit the number of pending outbound downstream frames of types PING, SETTINGS and RST_STREAM,
 preventing high memory utilization when receiving continuous stream of these frames. Exceeding
 this limit triggers flood mitigation and connection is terminated. The
 ``http2.outbound_control_flood`` stat tracks the number of terminated connections due to flood
 mitigation. The default limit is 1000.
        .google.protobuf.UInt32Value max_outbound_control_frames = 8 [(.validate.rules) = { ... }
        Specified by:
        getMaxOutboundControlFrames in interface Http2ProtocolOptionsOrBuilder
        Returns:
        The maxOutboundControlFrames.

      • setMaxOutboundControlFrames

        public Http2ProtocolOptions.Builder setMaxOutboundControlFrames​(com.google.protobuf.UInt32Value value)
         Limit the number of pending outbound downstream frames of types PING, SETTINGS and RST_STREAM,
 preventing high memory utilization when receiving continuous stream of these frames. Exceeding
 this limit triggers flood mitigation and connection is terminated. The
 ``http2.outbound_control_flood`` stat tracks the number of terminated connections due to flood
 mitigation. The default limit is 1000.
        .google.protobuf.UInt32Value max_outbound_control_frames = 8 [(.validate.rules) = { ... }

      • setMaxOutboundControlFrames

        public Http2ProtocolOptions.Builder setMaxOutboundControlFrames​(com.google.protobuf.UInt32Value.Builder builderForValue)
         Limit the number of pending outbound downstream frames of types PING, SETTINGS and RST_STREAM,
 preventing high memory utilization when receiving continuous stream of these frames. Exceeding
 this limit triggers flood mitigation and connection is terminated. The
 ``http2.outbound_control_flood`` stat tracks the number of terminated connections due to flood
 mitigation. The default limit is 1000.
        .google.protobuf.UInt32Value max_outbound_control_frames = 8 [(.validate.rules) = { ... }

      • mergeMaxOutboundControlFrames

        public Http2ProtocolOptions.Builder mergeMaxOutboundControlFrames​(com.google.protobuf.UInt32Value value)
         Limit the number of pending outbound downstream frames of types PING, SETTINGS and RST_STREAM,
 preventing high memory utilization when receiving continuous stream of these frames. Exceeding
 this limit triggers flood mitigation and connection is terminated. The
 ``http2.outbound_control_flood`` stat tracks the number of terminated connections due to flood
 mitigation. The default limit is 1000.
        .google.protobuf.UInt32Value max_outbound_control_frames = 8 [(.validate.rules) = { ... }

      • clearMaxOutboundControlFrames

        public Http2ProtocolOptions.Builder clearMaxOutboundControlFrames()
         Limit the number of pending outbound downstream frames of types PING, SETTINGS and RST_STREAM,
 preventing high memory utilization when receiving continuous stream of these frames. Exceeding
 this limit triggers flood mitigation and connection is terminated. The
 ``http2.outbound_control_flood`` stat tracks the number of terminated connections due to flood
 mitigation. The default limit is 1000.
        .google.protobuf.UInt32Value max_outbound_control_frames = 8 [(.validate.rules) = { ... }

      • getMaxOutboundControlFramesBuilder

        public com.google.protobuf.UInt32Value.Builder getMaxOutboundControlFramesBuilder()
         Limit the number of pending outbound downstream frames of types PING, SETTINGS and RST_STREAM,
 preventing high memory utilization when receiving continuous stream of these frames. Exceeding
 this limit triggers flood mitigation and connection is terminated. The
 ``http2.outbound_control_flood`` stat tracks the number of terminated connections due to flood
 mitigation. The default limit is 1000.
        .google.protobuf.UInt32Value max_outbound_control_frames = 8 [(.validate.rules) = { ... }

      • getMaxOutboundControlFramesOrBuilder

        public com.google.protobuf.UInt32ValueOrBuilder getMaxOutboundControlFramesOrBuilder()
         Limit the number of pending outbound downstream frames of types PING, SETTINGS and RST_STREAM,
 preventing high memory utilization when receiving continuous stream of these frames. Exceeding
 this limit triggers flood mitigation and connection is terminated. The
 ``http2.outbound_control_flood`` stat tracks the number of terminated connections due to flood
 mitigation. The default limit is 1000.
        .google.protobuf.UInt32Value max_outbound_control_frames = 8 [(.validate.rules) = { ... }
        Specified by:
        getMaxOutboundControlFramesOrBuilder in interface Http2ProtocolOptionsOrBuilder

      • hasMaxConsecutiveInboundFramesWithEmptyPayload

        public boolean hasMaxConsecutiveInboundFramesWithEmptyPayload()
         Limit the number of consecutive inbound frames of types HEADERS, CONTINUATION and DATA with an
 empty payload and no end stream flag. Those frames have no legitimate use and are abusive, but
 might be a result of a broken HTTP/2 implementation. The `http2.inbound_empty_frames_flood``
 stat tracks the number of connections terminated due to flood mitigation.
 Setting this to 0 will terminate connection upon receiving first frame with an empty payload
 and no end stream flag. The default limit is 1.
        .google.protobuf.UInt32Value max_consecutive_inbound_frames_with_empty_payload = 9;
        Specified by:
        hasMaxConsecutiveInboundFramesWithEmptyPayload in interface Http2ProtocolOptionsOrBuilder
        Returns:
        Whether the maxConsecutiveInboundFramesWithEmptyPayload field is set.

      • getMaxConsecutiveInboundFramesWithEmptyPayload

        public com.google.protobuf.UInt32Value getMaxConsecutiveInboundFramesWithEmptyPayload()
         Limit the number of consecutive inbound frames of types HEADERS, CONTINUATION and DATA with an
 empty payload and no end stream flag. Those frames have no legitimate use and are abusive, but
 might be a result of a broken HTTP/2 implementation. The `http2.inbound_empty_frames_flood``
 stat tracks the number of connections terminated due to flood mitigation.
 Setting this to 0 will terminate connection upon receiving first frame with an empty payload
 and no end stream flag. The default limit is 1.
        .google.protobuf.UInt32Value max_consecutive_inbound_frames_with_empty_payload = 9;
        Specified by:
        getMaxConsecutiveInboundFramesWithEmptyPayload in interface Http2ProtocolOptionsOrBuilder
        Returns:
        The maxConsecutiveInboundFramesWithEmptyPayload.

      • setMaxConsecutiveInboundFramesWithEmptyPayload

        public Http2ProtocolOptions.Builder setMaxConsecutiveInboundFramesWithEmptyPayload​(com.google.protobuf.UInt32Value value)
         Limit the number of consecutive inbound frames of types HEADERS, CONTINUATION and DATA with an
 empty payload and no end stream flag. Those frames have no legitimate use and are abusive, but
 might be a result of a broken HTTP/2 implementation. The `http2.inbound_empty_frames_flood``
 stat tracks the number of connections terminated due to flood mitigation.
 Setting this to 0 will terminate connection upon receiving first frame with an empty payload
 and no end stream flag. The default limit is 1.
        .google.protobuf.UInt32Value max_consecutive_inbound_frames_with_empty_payload = 9;

      • setMaxConsecutiveInboundFramesWithEmptyPayload

        public Http2ProtocolOptions.Builder setMaxConsecutiveInboundFramesWithEmptyPayload​(com.google.protobuf.UInt32Value.Builder builderForValue)
         Limit the number of consecutive inbound frames of types HEADERS, CONTINUATION and DATA with an
 empty payload and no end stream flag. Those frames have no legitimate use and are abusive, but
 might be a result of a broken HTTP/2 implementation. The `http2.inbound_empty_frames_flood``
 stat tracks the number of connections terminated due to flood mitigation.
 Setting this to 0 will terminate connection upon receiving first frame with an empty payload
 and no end stream flag. The default limit is 1.
        .google.protobuf.UInt32Value max_consecutive_inbound_frames_with_empty_payload = 9;

      • mergeMaxConsecutiveInboundFramesWithEmptyPayload

        public Http2ProtocolOptions.Builder mergeMaxConsecutiveInboundFramesWithEmptyPayload​(com.google.protobuf.UInt32Value value)
         Limit the number of consecutive inbound frames of types HEADERS, CONTINUATION and DATA with an
 empty payload and no end stream flag. Those frames have no legitimate use and are abusive, but
 might be a result of a broken HTTP/2 implementation. The `http2.inbound_empty_frames_flood``
 stat tracks the number of connections terminated due to flood mitigation.
 Setting this to 0 will terminate connection upon receiving first frame with an empty payload
 and no end stream flag. The default limit is 1.
        .google.protobuf.UInt32Value max_consecutive_inbound_frames_with_empty_payload = 9;

      • clearMaxConsecutiveInboundFramesWithEmptyPayload

        public Http2ProtocolOptions.Builder clearMaxConsecutiveInboundFramesWithEmptyPayload()
         Limit the number of consecutive inbound frames of types HEADERS, CONTINUATION and DATA with an
 empty payload and no end stream flag. Those frames have no legitimate use and are abusive, but
 might be a result of a broken HTTP/2 implementation. The `http2.inbound_empty_frames_flood``
 stat tracks the number of connections terminated due to flood mitigation.
 Setting this to 0 will terminate connection upon receiving first frame with an empty payload
 and no end stream flag. The default limit is 1.
        .google.protobuf.UInt32Value max_consecutive_inbound_frames_with_empty_payload = 9;

      • getMaxConsecutiveInboundFramesWithEmptyPayloadBuilder

        public com.google.protobuf.UInt32Value.Builder getMaxConsecutiveInboundFramesWithEmptyPayloadBuilder()
         Limit the number of consecutive inbound frames of types HEADERS, CONTINUATION and DATA with an
 empty payload and no end stream flag. Those frames have no legitimate use and are abusive, but
 might be a result of a broken HTTP/2 implementation. The `http2.inbound_empty_frames_flood``
 stat tracks the number of connections terminated due to flood mitigation.
 Setting this to 0 will terminate connection upon receiving first frame with an empty payload
 and no end stream flag. The default limit is 1.
        .google.protobuf.UInt32Value max_consecutive_inbound_frames_with_empty_payload = 9;

      • getMaxConsecutiveInboundFramesWithEmptyPayloadOrBuilder

        public com.google.protobuf.UInt32ValueOrBuilder getMaxConsecutiveInboundFramesWithEmptyPayloadOrBuilder()
         Limit the number of consecutive inbound frames of types HEADERS, CONTINUATION and DATA with an
 empty payload and no end stream flag. Those frames have no legitimate use and are abusive, but
 might be a result of a broken HTTP/2 implementation. The `http2.inbound_empty_frames_flood``
 stat tracks the number of connections terminated due to flood mitigation.
 Setting this to 0 will terminate connection upon receiving first frame with an empty payload
 and no end stream flag. The default limit is 1.
        .google.protobuf.UInt32Value max_consecutive_inbound_frames_with_empty_payload = 9;
        Specified by:
        getMaxConsecutiveInboundFramesWithEmptyPayloadOrBuilder in interface Http2ProtocolOptionsOrBuilder

      • hasMaxInboundPriorityFramesPerStream

        public boolean hasMaxInboundPriorityFramesPerStream()
         Limit the number of inbound PRIORITY frames allowed per each opened stream. If the number
 of PRIORITY frames received over the lifetime of connection exceeds the value calculated
 using this formula::
   ``max_inbound_priority_frames_per_stream`` * (1 + ``opened_streams``)
 the connection is terminated. For downstream connections the ``opened_streams`` is incremented when
 Envoy receives complete response headers from the upstream server. For upstream connection the
 ``opened_streams`` is incremented when Envoy send the HEADERS frame for a new stream. The
 ``http2.inbound_priority_frames_flood`` stat tracks
 the number of connections terminated due to flood mitigation. The default limit is 100.
        .google.protobuf.UInt32Value max_inbound_priority_frames_per_stream = 10;
        Specified by:
        hasMaxInboundPriorityFramesPerStream in interface Http2ProtocolOptionsOrBuilder
        Returns:
        Whether the maxInboundPriorityFramesPerStream field is set.

      • getMaxInboundPriorityFramesPerStream

        public com.google.protobuf.UInt32Value getMaxInboundPriorityFramesPerStream()
         Limit the number of inbound PRIORITY frames allowed per each opened stream. If the number
 of PRIORITY frames received over the lifetime of connection exceeds the value calculated
 using this formula::
   ``max_inbound_priority_frames_per_stream`` * (1 + ``opened_streams``)
 the connection is terminated. For downstream connections the ``opened_streams`` is incremented when
 Envoy receives complete response headers from the upstream server. For upstream connection the
 ``opened_streams`` is incremented when Envoy send the HEADERS frame for a new stream. The
 ``http2.inbound_priority_frames_flood`` stat tracks
 the number of connections terminated due to flood mitigation. The default limit is 100.
        .google.protobuf.UInt32Value max_inbound_priority_frames_per_stream = 10;
        Specified by:
        getMaxInboundPriorityFramesPerStream in interface Http2ProtocolOptionsOrBuilder
        Returns:
        The maxInboundPriorityFramesPerStream.

      • setMaxInboundPriorityFramesPerStream

        public Http2ProtocolOptions.Builder setMaxInboundPriorityFramesPerStream​(com.google.protobuf.UInt32Value value)
         Limit the number of inbound PRIORITY frames allowed per each opened stream. If the number
 of PRIORITY frames received over the lifetime of connection exceeds the value calculated
 using this formula::
   ``max_inbound_priority_frames_per_stream`` * (1 + ``opened_streams``)
 the connection is terminated. For downstream connections the ``opened_streams`` is incremented when
 Envoy receives complete response headers from the upstream server. For upstream connection the
 ``opened_streams`` is incremented when Envoy send the HEADERS frame for a new stream. The
 ``http2.inbound_priority_frames_flood`` stat tracks
 the number of connections terminated due to flood mitigation. The default limit is 100.
        .google.protobuf.UInt32Value max_inbound_priority_frames_per_stream = 10;

      • setMaxInboundPriorityFramesPerStream

        public Http2ProtocolOptions.Builder setMaxInboundPriorityFramesPerStream​(com.google.protobuf.UInt32Value.Builder builderForValue)
         Limit the number of inbound PRIORITY frames allowed per each opened stream. If the number
 of PRIORITY frames received over the lifetime of connection exceeds the value calculated
 using this formula::
   ``max_inbound_priority_frames_per_stream`` * (1 + ``opened_streams``)
 the connection is terminated. For downstream connections the ``opened_streams`` is incremented when
 Envoy receives complete response headers from the upstream server. For upstream connection the
 ``opened_streams`` is incremented when Envoy send the HEADERS frame for a new stream. The
 ``http2.inbound_priority_frames_flood`` stat tracks
 the number of connections terminated due to flood mitigation. The default limit is 100.
        .google.protobuf.UInt32Value max_inbound_priority_frames_per_stream = 10;

      • mergeMaxInboundPriorityFramesPerStream

        public Http2ProtocolOptions.Builder mergeMaxInboundPriorityFramesPerStream​(com.google.protobuf.UInt32Value value)
         Limit the number of inbound PRIORITY frames allowed per each opened stream. If the number
 of PRIORITY frames received over the lifetime of connection exceeds the value calculated
 using this formula::
   ``max_inbound_priority_frames_per_stream`` * (1 + ``opened_streams``)
 the connection is terminated. For downstream connections the ``opened_streams`` is incremented when
 Envoy receives complete response headers from the upstream server. For upstream connection the
 ``opened_streams`` is incremented when Envoy send the HEADERS frame for a new stream. The
 ``http2.inbound_priority_frames_flood`` stat tracks
 the number of connections terminated due to flood mitigation. The default limit is 100.
        .google.protobuf.UInt32Value max_inbound_priority_frames_per_stream = 10;

      • clearMaxInboundPriorityFramesPerStream

        public Http2ProtocolOptions.Builder clearMaxInboundPriorityFramesPerStream()
         Limit the number of inbound PRIORITY frames allowed per each opened stream. If the number
 of PRIORITY frames received over the lifetime of connection exceeds the value calculated
 using this formula::
   ``max_inbound_priority_frames_per_stream`` * (1 + ``opened_streams``)
 the connection is terminated. For downstream connections the ``opened_streams`` is incremented when
 Envoy receives complete response headers from the upstream server. For upstream connection the
 ``opened_streams`` is incremented when Envoy send the HEADERS frame for a new stream. The
 ``http2.inbound_priority_frames_flood`` stat tracks
 the number of connections terminated due to flood mitigation. The default limit is 100.
        .google.protobuf.UInt32Value max_inbound_priority_frames_per_stream = 10;

      • getMaxInboundPriorityFramesPerStreamBuilder

        public com.google.protobuf.UInt32Value.Builder getMaxInboundPriorityFramesPerStreamBuilder()
         Limit the number of inbound PRIORITY frames allowed per each opened stream. If the number
 of PRIORITY frames received over the lifetime of connection exceeds the value calculated
 using this formula::
   ``max_inbound_priority_frames_per_stream`` * (1 + ``opened_streams``)
 the connection is terminated. For downstream connections the ``opened_streams`` is incremented when
 Envoy receives complete response headers from the upstream server. For upstream connection the
 ``opened_streams`` is incremented when Envoy send the HEADERS frame for a new stream. The
 ``http2.inbound_priority_frames_flood`` stat tracks
 the number of connections terminated due to flood mitigation. The default limit is 100.
        .google.protobuf.UInt32Value max_inbound_priority_frames_per_stream = 10;

      • getMaxInboundPriorityFramesPerStreamOrBuilder

        public com.google.protobuf.UInt32ValueOrBuilder getMaxInboundPriorityFramesPerStreamOrBuilder()
         Limit the number of inbound PRIORITY frames allowed per each opened stream. If the number
 of PRIORITY frames received over the lifetime of connection exceeds the value calculated
 using this formula::
   ``max_inbound_priority_frames_per_stream`` * (1 + ``opened_streams``)
 the connection is terminated. For downstream connections the ``opened_streams`` is incremented when
 Envoy receives complete response headers from the upstream server. For upstream connection the
 ``opened_streams`` is incremented when Envoy send the HEADERS frame for a new stream. The
 ``http2.inbound_priority_frames_flood`` stat tracks
 the number of connections terminated due to flood mitigation. The default limit is 100.
        .google.protobuf.UInt32Value max_inbound_priority_frames_per_stream = 10;
        Specified by:
        getMaxInboundPriorityFramesPerStreamOrBuilder in interface Http2ProtocolOptionsOrBuilder

      • hasMaxInboundWindowUpdateFramesPerDataFrameSent

        public boolean hasMaxInboundWindowUpdateFramesPerDataFrameSent()
         Limit the number of inbound WINDOW_UPDATE frames allowed per DATA frame sent. If the number
 of WINDOW_UPDATE frames received over the lifetime of connection exceeds the value calculated
 using this formula::
   5 + 2 * (``opened_streams`` +
            ``max_inbound_window_update_frames_per_data_frame_sent`` * ``outbound_data_frames``)
 the connection is terminated. For downstream connections the ``opened_streams`` is incremented when
 Envoy receives complete response headers from the upstream server. For upstream connections the
 ``opened_streams`` is incremented when Envoy sends the HEADERS frame for a new stream. The
 ``http2.inbound_priority_frames_flood`` stat tracks the number of connections terminated due to
 flood mitigation. The default max_inbound_window_update_frames_per_data_frame_sent value is 10.
 Setting this to 1 should be enough to support HTTP/2 implementations with basic flow control,
 but more complex implementations that try to estimate available bandwidth require at least 2.
        .google.protobuf.UInt32Value max_inbound_window_update_frames_per_data_frame_sent = 11 [(.validate.rules) = { ... }
        Specified by:
        hasMaxInboundWindowUpdateFramesPerDataFrameSent in interface Http2ProtocolOptionsOrBuilder
        Returns:
        Whether the maxInboundWindowUpdateFramesPerDataFrameSent field is set.

      • getMaxInboundWindowUpdateFramesPerDataFrameSent

        public com.google.protobuf.UInt32Value getMaxInboundWindowUpdateFramesPerDataFrameSent()
         Limit the number of inbound WINDOW_UPDATE frames allowed per DATA frame sent. If the number
 of WINDOW_UPDATE frames received over the lifetime of connection exceeds the value calculated
 using this formula::
   5 + 2 * (``opened_streams`` +
            ``max_inbound_window_update_frames_per_data_frame_sent`` * ``outbound_data_frames``)
 the connection is terminated. For downstream connections the ``opened_streams`` is incremented when
 Envoy receives complete response headers from the upstream server. For upstream connections the
 ``opened_streams`` is incremented when Envoy sends the HEADERS frame for a new stream. The
 ``http2.inbound_priority_frames_flood`` stat tracks the number of connections terminated due to
 flood mitigation. The default max_inbound_window_update_frames_per_data_frame_sent value is 10.
 Setting this to 1 should be enough to support HTTP/2 implementations with basic flow control,
 but more complex implementations that try to estimate available bandwidth require at least 2.
        .google.protobuf.UInt32Value max_inbound_window_update_frames_per_data_frame_sent = 11 [(.validate.rules) = { ... }
        Specified by:
        getMaxInboundWindowUpdateFramesPerDataFrameSent in interface Http2ProtocolOptionsOrBuilder
        Returns:
        The maxInboundWindowUpdateFramesPerDataFrameSent.

      • setMaxInboundWindowUpdateFramesPerDataFrameSent

        public Http2ProtocolOptions.Builder setMaxInboundWindowUpdateFramesPerDataFrameSent​(com.google.protobuf.UInt32Value value)
         Limit the number of inbound WINDOW_UPDATE frames allowed per DATA frame sent. If the number
 of WINDOW_UPDATE frames received over the lifetime of connection exceeds the value calculated
 using this formula::
   5 + 2 * (``opened_streams`` +
            ``max_inbound_window_update_frames_per_data_frame_sent`` * ``outbound_data_frames``)
 the connection is terminated. For downstream connections the ``opened_streams`` is incremented when
 Envoy receives complete response headers from the upstream server. For upstream connections the
 ``opened_streams`` is incremented when Envoy sends the HEADERS frame for a new stream. The
 ``http2.inbound_priority_frames_flood`` stat tracks the number of connections terminated due to
 flood mitigation. The default max_inbound_window_update_frames_per_data_frame_sent value is 10.
 Setting this to 1 should be enough to support HTTP/2 implementations with basic flow control,
 but more complex implementations that try to estimate available bandwidth require at least 2.
        .google.protobuf.UInt32Value max_inbound_window_update_frames_per_data_frame_sent = 11 [(.validate.rules) = { ... }

      • setMaxInboundWindowUpdateFramesPerDataFrameSent

        public Http2ProtocolOptions.Builder setMaxInboundWindowUpdateFramesPerDataFrameSent​(com.google.protobuf.UInt32Value.Builder builderForValue)
         Limit the number of inbound WINDOW_UPDATE frames allowed per DATA frame sent. If the number
 of WINDOW_UPDATE frames received over the lifetime of connection exceeds the value calculated
 using this formula::
   5 + 2 * (``opened_streams`` +
            ``max_inbound_window_update_frames_per_data_frame_sent`` * ``outbound_data_frames``)
 the connection is terminated. For downstream connections the ``opened_streams`` is incremented when
 Envoy receives complete response headers from the upstream server. For upstream connections the
 ``opened_streams`` is incremented when Envoy sends the HEADERS frame for a new stream. The
 ``http2.inbound_priority_frames_flood`` stat tracks the number of connections terminated due to
 flood mitigation. The default max_inbound_window_update_frames_per_data_frame_sent value is 10.
 Setting this to 1 should be enough to support HTTP/2 implementations with basic flow control,
 but more complex implementations that try to estimate available bandwidth require at least 2.
        .google.protobuf.UInt32Value max_inbound_window_update_frames_per_data_frame_sent = 11 [(.validate.rules) = { ... }

      • mergeMaxInboundWindowUpdateFramesPerDataFrameSent

        public Http2ProtocolOptions.Builder mergeMaxInboundWindowUpdateFramesPerDataFrameSent​(com.google.protobuf.UInt32Value value)
         Limit the number of inbound WINDOW_UPDATE frames allowed per DATA frame sent. If the number
 of WINDOW_UPDATE frames received over the lifetime of connection exceeds the value calculated
 using this formula::
   5 + 2 * (``opened_streams`` +
            ``max_inbound_window_update_frames_per_data_frame_sent`` * ``outbound_data_frames``)
 the connection is terminated. For downstream connections the ``opened_streams`` is incremented when
 Envoy receives complete response headers from the upstream server. For upstream connections the
 ``opened_streams`` is incremented when Envoy sends the HEADERS frame for a new stream. The
 ``http2.inbound_priority_frames_flood`` stat tracks the number of connections terminated due to
 flood mitigation. The default max_inbound_window_update_frames_per_data_frame_sent value is 10.
 Setting this to 1 should be enough to support HTTP/2 implementations with basic flow control,
 but more complex implementations that try to estimate available bandwidth require at least 2.
        .google.protobuf.UInt32Value max_inbound_window_update_frames_per_data_frame_sent = 11 [(.validate.rules) = { ... }

      • clearMaxInboundWindowUpdateFramesPerDataFrameSent

        public Http2ProtocolOptions.Builder clearMaxInboundWindowUpdateFramesPerDataFrameSent()
         Limit the number of inbound WINDOW_UPDATE frames allowed per DATA frame sent. If the number
 of WINDOW_UPDATE frames received over the lifetime of connection exceeds the value calculated
 using this formula::
   5 + 2 * (``opened_streams`` +
            ``max_inbound_window_update_frames_per_data_frame_sent`` * ``outbound_data_frames``)
 the connection is terminated. For downstream connections the ``opened_streams`` is incremented when
 Envoy receives complete response headers from the upstream server. For upstream connections the
 ``opened_streams`` is incremented when Envoy sends the HEADERS frame for a new stream. The
 ``http2.inbound_priority_frames_flood`` stat tracks the number of connections terminated due to
 flood mitigation. The default max_inbound_window_update_frames_per_data_frame_sent value is 10.
 Setting this to 1 should be enough to support HTTP/2 implementations with basic flow control,
 but more complex implementations that try to estimate available bandwidth require at least 2.
        .google.protobuf.UInt32Value max_inbound_window_update_frames_per_data_frame_sent = 11 [(.validate.rules) = { ... }

      • getMaxInboundWindowUpdateFramesPerDataFrameSentBuilder

        public com.google.protobuf.UInt32Value.Builder getMaxInboundWindowUpdateFramesPerDataFrameSentBuilder()
         Limit the number of inbound WINDOW_UPDATE frames allowed per DATA frame sent. If the number
 of WINDOW_UPDATE frames received over the lifetime of connection exceeds the value calculated
 using this formula::
   5 + 2 * (``opened_streams`` +
            ``max_inbound_window_update_frames_per_data_frame_sent`` * ``outbound_data_frames``)
 the connection is terminated. For downstream connections the ``opened_streams`` is incremented when
 Envoy receives complete response headers from the upstream server. For upstream connections the
 ``opened_streams`` is incremented when Envoy sends the HEADERS frame for a new stream. The
 ``http2.inbound_priority_frames_flood`` stat tracks the number of connections terminated due to
 flood mitigation. The default max_inbound_window_update_frames_per_data_frame_sent value is 10.
 Setting this to 1 should be enough to support HTTP/2 implementations with basic flow control,
 but more complex implementations that try to estimate available bandwidth require at least 2.
        .google.protobuf.UInt32Value max_inbound_window_update_frames_per_data_frame_sent = 11 [(.validate.rules) = { ... }

      • getMaxInboundWindowUpdateFramesPerDataFrameSentOrBuilder

        public com.google.protobuf.UInt32ValueOrBuilder getMaxInboundWindowUpdateFramesPerDataFrameSentOrBuilder()
         Limit the number of inbound WINDOW_UPDATE frames allowed per DATA frame sent. If the number
 of WINDOW_UPDATE frames received over the lifetime of connection exceeds the value calculated
 using this formula::
   5 + 2 * (``opened_streams`` +
            ``max_inbound_window_update_frames_per_data_frame_sent`` * ``outbound_data_frames``)
 the connection is terminated. For downstream connections the ``opened_streams`` is incremented when
 Envoy receives complete response headers from the upstream server. For upstream connections the
 ``opened_streams`` is incremented when Envoy sends the HEADERS frame for a new stream. The
 ``http2.inbound_priority_frames_flood`` stat tracks the number of connections terminated due to
 flood mitigation. The default max_inbound_window_update_frames_per_data_frame_sent value is 10.
 Setting this to 1 should be enough to support HTTP/2 implementations with basic flow control,
 but more complex implementations that try to estimate available bandwidth require at least 2.
        .google.protobuf.UInt32Value max_inbound_window_update_frames_per_data_frame_sent = 11 [(.validate.rules) = { ... }
        Specified by:
        getMaxInboundWindowUpdateFramesPerDataFrameSentOrBuilder in interface Http2ProtocolOptionsOrBuilder

      • getStreamErrorOnInvalidHttpMessaging

        @Deprecated
public boolean getStreamErrorOnInvalidHttpMessaging()
        Deprecated.
        envoy.config.core.v3.Http2ProtocolOptions.stream_error_on_invalid_http_messaging is deprecated. See envoy/config/core/v3/protocol.proto;l=506
         Allows invalid HTTP messaging and headers. When this option is disabled (default), then
 the whole HTTP/2 connection is terminated upon receiving invalid HEADERS frame. However,
 when this option is enabled, only the offending stream is terminated.
 This is overridden by HCM :ref:`stream_error_on_invalid_http_messaging
 <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_error_on_invalid_http_message>`
 iff present.
 This is deprecated in favor of :ref:`override_stream_error_on_invalid_http_message
 <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.override_stream_error_on_invalid_http_message>`
 See `RFC7540, sec. 8.1 <https://tools.ietf.org/html/rfc7540#section-8.1>`_ for details.
        bool stream_error_on_invalid_http_messaging = 12 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
        Specified by:
        getStreamErrorOnInvalidHttpMessaging in interface Http2ProtocolOptionsOrBuilder
        Returns:
        The streamErrorOnInvalidHttpMessaging.

      • setStreamErrorOnInvalidHttpMessaging

        @Deprecated
public Http2ProtocolOptions.Builder setStreamErrorOnInvalidHttpMessaging​(boolean value)
        Deprecated.
        envoy.config.core.v3.Http2ProtocolOptions.stream_error_on_invalid_http_messaging is deprecated. See envoy/config/core/v3/protocol.proto;l=506
         Allows invalid HTTP messaging and headers. When this option is disabled (default), then
 the whole HTTP/2 connection is terminated upon receiving invalid HEADERS frame. However,
 when this option is enabled, only the offending stream is terminated.
 This is overridden by HCM :ref:`stream_error_on_invalid_http_messaging
 <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_error_on_invalid_http_message>`
 iff present.
 This is deprecated in favor of :ref:`override_stream_error_on_invalid_http_message
 <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.override_stream_error_on_invalid_http_message>`
 See `RFC7540, sec. 8.1 <https://tools.ietf.org/html/rfc7540#section-8.1>`_ for details.
        bool stream_error_on_invalid_http_messaging = 12 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
        Parameters:
        value - The streamErrorOnInvalidHttpMessaging to set.
        Returns:
        This builder for chaining.

      • clearStreamErrorOnInvalidHttpMessaging

        @Deprecated
public Http2ProtocolOptions.Builder clearStreamErrorOnInvalidHttpMessaging()
        Deprecated.
        envoy.config.core.v3.Http2ProtocolOptions.stream_error_on_invalid_http_messaging is deprecated. See envoy/config/core/v3/protocol.proto;l=506
         Allows invalid HTTP messaging and headers. When this option is disabled (default), then
 the whole HTTP/2 connection is terminated upon receiving invalid HEADERS frame. However,
 when this option is enabled, only the offending stream is terminated.
 This is overridden by HCM :ref:`stream_error_on_invalid_http_messaging
 <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_error_on_invalid_http_message>`
 iff present.
 This is deprecated in favor of :ref:`override_stream_error_on_invalid_http_message
 <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.override_stream_error_on_invalid_http_message>`
 See `RFC7540, sec. 8.1 <https://tools.ietf.org/html/rfc7540#section-8.1>`_ for details.
        bool stream_error_on_invalid_http_messaging = 12 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
        Returns:
        This builder for chaining.

      • hasOverrideStreamErrorOnInvalidHttpMessage

        public boolean hasOverrideStreamErrorOnInvalidHttpMessage()
         Allows invalid HTTP messaging and headers. When this option is disabled (default), then
 the whole HTTP/2 connection is terminated upon receiving invalid HEADERS frame. However,
 when this option is enabled, only the offending stream is terminated.
 This overrides any HCM :ref:`stream_error_on_invalid_http_messaging
 <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_error_on_invalid_http_message>`
 See `RFC7540, sec. 8.1 <https://tools.ietf.org/html/rfc7540#section-8.1>`_ for details.
        .google.protobuf.BoolValue override_stream_error_on_invalid_http_message = 14;
        Specified by:
        hasOverrideStreamErrorOnInvalidHttpMessage in interface Http2ProtocolOptionsOrBuilder
        Returns:
        Whether the overrideStreamErrorOnInvalidHttpMessage field is set.

      • getOverrideStreamErrorOnInvalidHttpMessage

        public com.google.protobuf.BoolValue getOverrideStreamErrorOnInvalidHttpMessage()
         Allows invalid HTTP messaging and headers. When this option is disabled (default), then
 the whole HTTP/2 connection is terminated upon receiving invalid HEADERS frame. However,
 when this option is enabled, only the offending stream is terminated.
 This overrides any HCM :ref:`stream_error_on_invalid_http_messaging
 <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_error_on_invalid_http_message>`
 See `RFC7540, sec. 8.1 <https://tools.ietf.org/html/rfc7540#section-8.1>`_ for details.
        .google.protobuf.BoolValue override_stream_error_on_invalid_http_message = 14;
        Specified by:
        getOverrideStreamErrorOnInvalidHttpMessage in interface Http2ProtocolOptionsOrBuilder
        Returns:
        The overrideStreamErrorOnInvalidHttpMessage.

      • setOverrideStreamErrorOnInvalidHttpMessage

        public Http2ProtocolOptions.Builder setOverrideStreamErrorOnInvalidHttpMessage​(com.google.protobuf.BoolValue value)
         Allows invalid HTTP messaging and headers. When this option is disabled (default), then
 the whole HTTP/2 connection is terminated upon receiving invalid HEADERS frame. However,
 when this option is enabled, only the offending stream is terminated.
 This overrides any HCM :ref:`stream_error_on_invalid_http_messaging
 <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_error_on_invalid_http_message>`
 See `RFC7540, sec. 8.1 <https://tools.ietf.org/html/rfc7540#section-8.1>`_ for details.
        .google.protobuf.BoolValue override_stream_error_on_invalid_http_message = 14;

      • setOverrideStreamErrorOnInvalidHttpMessage

        public Http2ProtocolOptions.Builder setOverrideStreamErrorOnInvalidHttpMessage​(com.google.protobuf.BoolValue.Builder builderForValue)
         Allows invalid HTTP messaging and headers. When this option is disabled (default), then
 the whole HTTP/2 connection is terminated upon receiving invalid HEADERS frame. However,
 when this option is enabled, only the offending stream is terminated.
 This overrides any HCM :ref:`stream_error_on_invalid_http_messaging
 <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_error_on_invalid_http_message>`
 See `RFC7540, sec. 8.1 <https://tools.ietf.org/html/rfc7540#section-8.1>`_ for details.
        .google.protobuf.BoolValue override_stream_error_on_invalid_http_message = 14;

      • mergeOverrideStreamErrorOnInvalidHttpMessage

        public Http2ProtocolOptions.Builder mergeOverrideStreamErrorOnInvalidHttpMessage​(com.google.protobuf.BoolValue value)
         Allows invalid HTTP messaging and headers. When this option is disabled (default), then
 the whole HTTP/2 connection is terminated upon receiving invalid HEADERS frame. However,
 when this option is enabled, only the offending stream is terminated.
 This overrides any HCM :ref:`stream_error_on_invalid_http_messaging
 <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_error_on_invalid_http_message>`
 See `RFC7540, sec. 8.1 <https://tools.ietf.org/html/rfc7540#section-8.1>`_ for details.
        .google.protobuf.BoolValue override_stream_error_on_invalid_http_message = 14;

      • clearOverrideStreamErrorOnInvalidHttpMessage

        public Http2ProtocolOptions.Builder clearOverrideStreamErrorOnInvalidHttpMessage()
         Allows invalid HTTP messaging and headers. When this option is disabled (default), then
 the whole HTTP/2 connection is terminated upon receiving invalid HEADERS frame. However,
 when this option is enabled, only the offending stream is terminated.
 This overrides any HCM :ref:`stream_error_on_invalid_http_messaging
 <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_error_on_invalid_http_message>`
 See `RFC7540, sec. 8.1 <https://tools.ietf.org/html/rfc7540#section-8.1>`_ for details.
        .google.protobuf.BoolValue override_stream_error_on_invalid_http_message = 14;

      • getOverrideStreamErrorOnInvalidHttpMessageBuilder

        public com.google.protobuf.BoolValue.Builder getOverrideStreamErrorOnInvalidHttpMessageBuilder()
         Allows invalid HTTP messaging and headers. When this option is disabled (default), then
 the whole HTTP/2 connection is terminated upon receiving invalid HEADERS frame. However,
 when this option is enabled, only the offending stream is terminated.
 This overrides any HCM :ref:`stream_error_on_invalid_http_messaging
 <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_error_on_invalid_http_message>`
 See `RFC7540, sec. 8.1 <https://tools.ietf.org/html/rfc7540#section-8.1>`_ for details.
        .google.protobuf.BoolValue override_stream_error_on_invalid_http_message = 14;

      • getOverrideStreamErrorOnInvalidHttpMessageOrBuilder

        public com.google.protobuf.BoolValueOrBuilder getOverrideStreamErrorOnInvalidHttpMessageOrBuilder()
         Allows invalid HTTP messaging and headers. When this option is disabled (default), then
 the whole HTTP/2 connection is terminated upon receiving invalid HEADERS frame. However,
 when this option is enabled, only the offending stream is terminated.
 This overrides any HCM :ref:`stream_error_on_invalid_http_messaging
 <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_error_on_invalid_http_message>`
 See `RFC7540, sec. 8.1 <https://tools.ietf.org/html/rfc7540#section-8.1>`_ for details.
        .google.protobuf.BoolValue override_stream_error_on_invalid_http_message = 14;
        Specified by:
        getOverrideStreamErrorOnInvalidHttpMessageOrBuilder in interface Http2ProtocolOptionsOrBuilder

      • getCustomSettingsParametersList

        public List<Http2ProtocolOptions.SettingsParameter> getCustomSettingsParametersList()
         [#not-implemented-hide:]
 Specifies SETTINGS frame parameters to be sent to the peer, with two exceptions:
 1. SETTINGS_ENABLE_PUSH (0x2) is not configurable as HTTP/2 server push is not supported by
 Envoy.
 2. SETTINGS_ENABLE_CONNECT_PROTOCOL (0x8) is only configurable through the named field
 'allow_connect'.
 Note that custom parameters specified through this field can not also be set in the
 corresponding named parameters:
 .. code-block:: text
   ID    Field Name
   ----------------
   0x1   hpack_table_size
   0x3   max_concurrent_streams
   0x4   initial_stream_window_size
 Collisions will trigger config validation failure on load/update. Likewise, inconsistencies
 between custom parameters with the same identifier will trigger a failure.
 See `IANA HTTP/2 Settings
 <https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#settings>`_ for
 standardized identifiers.
        repeated .envoy.config.core.v3.Http2ProtocolOptions.SettingsParameter custom_settings_parameters = 13;
        Specified by:
        getCustomSettingsParametersList in interface Http2ProtocolOptionsOrBuilder

      • getCustomSettingsParametersCount

        public int getCustomSettingsParametersCount()
         [#not-implemented-hide:]
 Specifies SETTINGS frame parameters to be sent to the peer, with two exceptions:
 1. SETTINGS_ENABLE_PUSH (0x2) is not configurable as HTTP/2 server push is not supported by
 Envoy.
 2. SETTINGS_ENABLE_CONNECT_PROTOCOL (0x8) is only configurable through the named field
 'allow_connect'.
 Note that custom parameters specified through this field can not also be set in the
 corresponding named parameters:
 .. code-block:: text
   ID    Field Name
   ----------------
   0x1   hpack_table_size
   0x3   max_concurrent_streams
   0x4   initial_stream_window_size
 Collisions will trigger config validation failure on load/update. Likewise, inconsistencies
 between custom parameters with the same identifier will trigger a failure.
 See `IANA HTTP/2 Settings
 <https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#settings>`_ for
 standardized identifiers.
        repeated .envoy.config.core.v3.Http2ProtocolOptions.SettingsParameter custom_settings_parameters = 13;
        Specified by:
        getCustomSettingsParametersCount in interface Http2ProtocolOptionsOrBuilder

      • getCustomSettingsParameters

        public Http2ProtocolOptions.SettingsParameter getCustomSettingsParameters​(int index)
         [#not-implemented-hide:]
 Specifies SETTINGS frame parameters to be sent to the peer, with two exceptions:
 1. SETTINGS_ENABLE_PUSH (0x2) is not configurable as HTTP/2 server push is not supported by
 Envoy.
 2. SETTINGS_ENABLE_CONNECT_PROTOCOL (0x8) is only configurable through the named field
 'allow_connect'.
 Note that custom parameters specified through this field can not also be set in the
 corresponding named parameters:
 .. code-block:: text
   ID    Field Name
   ----------------
   0x1   hpack_table_size
   0x3   max_concurrent_streams
   0x4   initial_stream_window_size
 Collisions will trigger config validation failure on load/update. Likewise, inconsistencies
 between custom parameters with the same identifier will trigger a failure.
 See `IANA HTTP/2 Settings
 <https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#settings>`_ for
 standardized identifiers.
        repeated .envoy.config.core.v3.Http2ProtocolOptions.SettingsParameter custom_settings_parameters = 13;
        Specified by:
        getCustomSettingsParameters in interface Http2ProtocolOptionsOrBuilder

      • setCustomSettingsParameters

        public Http2ProtocolOptions.Builder setCustomSettingsParameters​(int index,
                                                                Http2ProtocolOptions.SettingsParameter value)
         [#not-implemented-hide:]
 Specifies SETTINGS frame parameters to be sent to the peer, with two exceptions:
 1. SETTINGS_ENABLE_PUSH (0x2) is not configurable as HTTP/2 server push is not supported by
 Envoy.
 2. SETTINGS_ENABLE_CONNECT_PROTOCOL (0x8) is only configurable through the named field
 'allow_connect'.
 Note that custom parameters specified through this field can not also be set in the
 corresponding named parameters:
 .. code-block:: text
   ID    Field Name
   ----------------
   0x1   hpack_table_size
   0x3   max_concurrent_streams
   0x4   initial_stream_window_size
 Collisions will trigger config validation failure on load/update. Likewise, inconsistencies
 between custom parameters with the same identifier will trigger a failure.
 See `IANA HTTP/2 Settings
 <https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#settings>`_ for
 standardized identifiers.
        repeated .envoy.config.core.v3.Http2ProtocolOptions.SettingsParameter custom_settings_parameters = 13;

      • setCustomSettingsParameters

        public Http2ProtocolOptions.Builder setCustomSettingsParameters​(int index,
                                                                Http2ProtocolOptions.SettingsParameter.Builder builderForValue)
         [#not-implemented-hide:]
 Specifies SETTINGS frame parameters to be sent to the peer, with two exceptions:
 1. SETTINGS_ENABLE_PUSH (0x2) is not configurable as HTTP/2 server push is not supported by
 Envoy.
 2. SETTINGS_ENABLE_CONNECT_PROTOCOL (0x8) is only configurable through the named field
 'allow_connect'.
 Note that custom parameters specified through this field can not also be set in the
 corresponding named parameters:
 .. code-block:: text
   ID    Field Name
   ----------------
   0x1   hpack_table_size
   0x3   max_concurrent_streams
   0x4   initial_stream_window_size
 Collisions will trigger config validation failure on load/update. Likewise, inconsistencies
 between custom parameters with the same identifier will trigger a failure.
 See `IANA HTTP/2 Settings
 <https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#settings>`_ for
 standardized identifiers.
        repeated .envoy.config.core.v3.Http2ProtocolOptions.SettingsParameter custom_settings_parameters = 13;

      • addCustomSettingsParameters

        public Http2ProtocolOptions.Builder addCustomSettingsParameters​(Http2ProtocolOptions.SettingsParameter value)
         [#not-implemented-hide:]
 Specifies SETTINGS frame parameters to be sent to the peer, with two exceptions:
 1. SETTINGS_ENABLE_PUSH (0x2) is not configurable as HTTP/2 server push is not supported by
 Envoy.
 2. SETTINGS_ENABLE_CONNECT_PROTOCOL (0x8) is only configurable through the named field
 'allow_connect'.
 Note that custom parameters specified through this field can not also be set in the
 corresponding named parameters:
 .. code-block:: text
   ID    Field Name
   ----------------
   0x1   hpack_table_size
   0x3   max_concurrent_streams
   0x4   initial_stream_window_size
 Collisions will trigger config validation failure on load/update. Likewise, inconsistencies
 between custom parameters with the same identifier will trigger a failure.
 See `IANA HTTP/2 Settings
 <https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#settings>`_ for
 standardized identifiers.
        repeated .envoy.config.core.v3.Http2ProtocolOptions.SettingsParameter custom_settings_parameters = 13;

      • addCustomSettingsParameters

        public Http2ProtocolOptions.Builder addCustomSettingsParameters​(int index,
                                                                Http2ProtocolOptions.SettingsParameter value)
         [#not-implemented-hide:]
 Specifies SETTINGS frame parameters to be sent to the peer, with two exceptions:
 1. SETTINGS_ENABLE_PUSH (0x2) is not configurable as HTTP/2 server push is not supported by
 Envoy.
 2. SETTINGS_ENABLE_CONNECT_PROTOCOL (0x8) is only configurable through the named field
 'allow_connect'.
 Note that custom parameters specified through this field can not also be set in the
 corresponding named parameters:
 .. code-block:: text
   ID    Field Name
   ----------------
   0x1   hpack_table_size
   0x3   max_concurrent_streams
   0x4   initial_stream_window_size
 Collisions will trigger config validation failure on load/update. Likewise, inconsistencies
 between custom parameters with the same identifier will trigger a failure.
 See `IANA HTTP/2 Settings
 <https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#settings>`_ for
 standardized identifiers.
        repeated .envoy.config.core.v3.Http2ProtocolOptions.SettingsParameter custom_settings_parameters = 13;

      • addCustomSettingsParameters

        public Http2ProtocolOptions.Builder addCustomSettingsParameters​(Http2ProtocolOptions.SettingsParameter.Builder builderForValue)
         [#not-implemented-hide:]
 Specifies SETTINGS frame parameters to be sent to the peer, with two exceptions:
 1. SETTINGS_ENABLE_PUSH (0x2) is not configurable as HTTP/2 server push is not supported by
 Envoy.
 2. SETTINGS_ENABLE_CONNECT_PROTOCOL (0x8) is only configurable through the named field
 'allow_connect'.
 Note that custom parameters specified through this field can not also be set in the
 corresponding named parameters:
 .. code-block:: text
   ID    Field Name
   ----------------
   0x1   hpack_table_size
   0x3   max_concurrent_streams
   0x4   initial_stream_window_size
 Collisions will trigger config validation failure on load/update. Likewise, inconsistencies
 between custom parameters with the same identifier will trigger a failure.
 See `IANA HTTP/2 Settings
 <https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#settings>`_ for
 standardized identifiers.
        repeated .envoy.config.core.v3.Http2ProtocolOptions.SettingsParameter custom_settings_parameters = 13;

      • addCustomSettingsParameters

        public Http2ProtocolOptions.Builder addCustomSettingsParameters​(int index,
                                                                Http2ProtocolOptions.SettingsParameter.Builder builderForValue)
         [#not-implemented-hide:]
 Specifies SETTINGS frame parameters to be sent to the peer, with two exceptions:
 1. SETTINGS_ENABLE_PUSH (0x2) is not configurable as HTTP/2 server push is not supported by
 Envoy.
 2. SETTINGS_ENABLE_CONNECT_PROTOCOL (0x8) is only configurable through the named field
 'allow_connect'.
 Note that custom parameters specified through this field can not also be set in the
 corresponding named parameters:
 .. code-block:: text
   ID    Field Name
   ----------------
   0x1   hpack_table_size
   0x3   max_concurrent_streams
   0x4   initial_stream_window_size
 Collisions will trigger config validation failure on load/update. Likewise, inconsistencies
 between custom parameters with the same identifier will trigger a failure.
 See `IANA HTTP/2 Settings
 <https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#settings>`_ for
 standardized identifiers.
        repeated .envoy.config.core.v3.Http2ProtocolOptions.SettingsParameter custom_settings_parameters = 13;

      • addAllCustomSettingsParameters

        public Http2ProtocolOptions.Builder addAllCustomSettingsParameters​(Iterable<? extends Http2ProtocolOptions.SettingsParameter> values)
         [#not-implemented-hide:]
 Specifies SETTINGS frame parameters to be sent to the peer, with two exceptions:
 1. SETTINGS_ENABLE_PUSH (0x2) is not configurable as HTTP/2 server push is not supported by
 Envoy.
 2. SETTINGS_ENABLE_CONNECT_PROTOCOL (0x8) is only configurable through the named field
 'allow_connect'.
 Note that custom parameters specified through this field can not also be set in the
 corresponding named parameters:
 .. code-block:: text
   ID    Field Name
   ----------------
   0x1   hpack_table_size
   0x3   max_concurrent_streams
   0x4   initial_stream_window_size
 Collisions will trigger config validation failure on load/update. Likewise, inconsistencies
 between custom parameters with the same identifier will trigger a failure.
 See `IANA HTTP/2 Settings
 <https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#settings>`_ for
 standardized identifiers.
        repeated .envoy.config.core.v3.Http2ProtocolOptions.SettingsParameter custom_settings_parameters = 13;

      • clearCustomSettingsParameters

        public Http2ProtocolOptions.Builder clearCustomSettingsParameters()
         [#not-implemented-hide:]
 Specifies SETTINGS frame parameters to be sent to the peer, with two exceptions:
 1. SETTINGS_ENABLE_PUSH (0x2) is not configurable as HTTP/2 server push is not supported by
 Envoy.
 2. SETTINGS_ENABLE_CONNECT_PROTOCOL (0x8) is only configurable through the named field
 'allow_connect'.
 Note that custom parameters specified through this field can not also be set in the
 corresponding named parameters:
 .. code-block:: text
   ID    Field Name
   ----------------
   0x1   hpack_table_size
   0x3   max_concurrent_streams
   0x4   initial_stream_window_size
 Collisions will trigger config validation failure on load/update. Likewise, inconsistencies
 between custom parameters with the same identifier will trigger a failure.
 See `IANA HTTP/2 Settings
 <https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#settings>`_ for
 standardized identifiers.
        repeated .envoy.config.core.v3.Http2ProtocolOptions.SettingsParameter custom_settings_parameters = 13;

      • removeCustomSettingsParameters

        public Http2ProtocolOptions.Builder removeCustomSettingsParameters​(int index)
         [#not-implemented-hide:]
 Specifies SETTINGS frame parameters to be sent to the peer, with two exceptions:
 1. SETTINGS_ENABLE_PUSH (0x2) is not configurable as HTTP/2 server push is not supported by
 Envoy.
 2. SETTINGS_ENABLE_CONNECT_PROTOCOL (0x8) is only configurable through the named field
 'allow_connect'.
 Note that custom parameters specified through this field can not also be set in the
 corresponding named parameters:
 .. code-block:: text
   ID    Field Name
   ----------------
   0x1   hpack_table_size
   0x3   max_concurrent_streams
   0x4   initial_stream_window_size
 Collisions will trigger config validation failure on load/update. Likewise, inconsistencies
 between custom parameters with the same identifier will trigger a failure.
 See `IANA HTTP/2 Settings
 <https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#settings>`_ for
 standardized identifiers.
        repeated .envoy.config.core.v3.Http2ProtocolOptions.SettingsParameter custom_settings_parameters = 13;

      • getCustomSettingsParametersBuilder

        public Http2ProtocolOptions.SettingsParameter.Builder getCustomSettingsParametersBuilder​(int index)
         [#not-implemented-hide:]
 Specifies SETTINGS frame parameters to be sent to the peer, with two exceptions:
 1. SETTINGS_ENABLE_PUSH (0x2) is not configurable as HTTP/2 server push is not supported by
 Envoy.
 2. SETTINGS_ENABLE_CONNECT_PROTOCOL (0x8) is only configurable through the named field
 'allow_connect'.
 Note that custom parameters specified through this field can not also be set in the
 corresponding named parameters:
 .. code-block:: text
   ID    Field Name
   ----------------
   0x1   hpack_table_size
   0x3   max_concurrent_streams
   0x4   initial_stream_window_size
 Collisions will trigger config validation failure on load/update. Likewise, inconsistencies
 between custom parameters with the same identifier will trigger a failure.
 See `IANA HTTP/2 Settings
 <https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#settings>`_ for
 standardized identifiers.
        repeated .envoy.config.core.v3.Http2ProtocolOptions.SettingsParameter custom_settings_parameters = 13;

      • getCustomSettingsParametersOrBuilder

        public Http2ProtocolOptions.SettingsParameterOrBuilder getCustomSettingsParametersOrBuilder​(int index)
         [#not-implemented-hide:]
 Specifies SETTINGS frame parameters to be sent to the peer, with two exceptions:
 1. SETTINGS_ENABLE_PUSH (0x2) is not configurable as HTTP/2 server push is not supported by
 Envoy.
 2. SETTINGS_ENABLE_CONNECT_PROTOCOL (0x8) is only configurable through the named field
 'allow_connect'.
 Note that custom parameters specified through this field can not also be set in the
 corresponding named parameters:
 .. code-block:: text
   ID    Field Name
   ----------------
   0x1   hpack_table_size
   0x3   max_concurrent_streams
   0x4   initial_stream_window_size
 Collisions will trigger config validation failure on load/update. Likewise, inconsistencies
 between custom parameters with the same identifier will trigger a failure.
 See `IANA HTTP/2 Settings
 <https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#settings>`_ for
 standardized identifiers.
        repeated .envoy.config.core.v3.Http2ProtocolOptions.SettingsParameter custom_settings_parameters = 13;
        Specified by:
        getCustomSettingsParametersOrBuilder in interface Http2ProtocolOptionsOrBuilder

      • getCustomSettingsParametersOrBuilderList

        public List<? extends Http2ProtocolOptions.SettingsParameterOrBuilder> getCustomSettingsParametersOrBuilderList()
         [#not-implemented-hide:]
 Specifies SETTINGS frame parameters to be sent to the peer, with two exceptions:
 1. SETTINGS_ENABLE_PUSH (0x2) is not configurable as HTTP/2 server push is not supported by
 Envoy.
 2. SETTINGS_ENABLE_CONNECT_PROTOCOL (0x8) is only configurable through the named field
 'allow_connect'.
 Note that custom parameters specified through this field can not also be set in the
 corresponding named parameters:
 .. code-block:: text
   ID    Field Name
   ----------------
   0x1   hpack_table_size
   0x3   max_concurrent_streams
   0x4   initial_stream_window_size
 Collisions will trigger config validation failure on load/update. Likewise, inconsistencies
 between custom parameters with the same identifier will trigger a failure.
 See `IANA HTTP/2 Settings
 <https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#settings>`_ for
 standardized identifiers.
        repeated .envoy.config.core.v3.Http2ProtocolOptions.SettingsParameter custom_settings_parameters = 13;
        Specified by:
        getCustomSettingsParametersOrBuilderList in interface Http2ProtocolOptionsOrBuilder

      • addCustomSettingsParametersBuilder

        public Http2ProtocolOptions.SettingsParameter.Builder addCustomSettingsParametersBuilder()
         [#not-implemented-hide:]
 Specifies SETTINGS frame parameters to be sent to the peer, with two exceptions:
 1. SETTINGS_ENABLE_PUSH (0x2) is not configurable as HTTP/2 server push is not supported by
 Envoy.
 2. SETTINGS_ENABLE_CONNECT_PROTOCOL (0x8) is only configurable through the named field
 'allow_connect'.
 Note that custom parameters specified through this field can not also be set in the
 corresponding named parameters:
 .. code-block:: text
   ID    Field Name
   ----------------
   0x1   hpack_table_size
   0x3   max_concurrent_streams
   0x4   initial_stream_window_size
 Collisions will trigger config validation failure on load/update. Likewise, inconsistencies
 between custom parameters with the same identifier will trigger a failure.
 See `IANA HTTP/2 Settings
 <https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#settings>`_ for
 standardized identifiers.
        repeated .envoy.config.core.v3.Http2ProtocolOptions.SettingsParameter custom_settings_parameters = 13;

      • addCustomSettingsParametersBuilder

        public Http2ProtocolOptions.SettingsParameter.Builder addCustomSettingsParametersBuilder​(int index)
         [#not-implemented-hide:]
 Specifies SETTINGS frame parameters to be sent to the peer, with two exceptions:
 1. SETTINGS_ENABLE_PUSH (0x2) is not configurable as HTTP/2 server push is not supported by
 Envoy.
 2. SETTINGS_ENABLE_CONNECT_PROTOCOL (0x8) is only configurable through the named field
 'allow_connect'.
 Note that custom parameters specified through this field can not also be set in the
 corresponding named parameters:
 .. code-block:: text
   ID    Field Name
   ----------------
   0x1   hpack_table_size
   0x3   max_concurrent_streams
   0x4   initial_stream_window_size
 Collisions will trigger config validation failure on load/update. Likewise, inconsistencies
 between custom parameters with the same identifier will trigger a failure.
 See `IANA HTTP/2 Settings
 <https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#settings>`_ for
 standardized identifiers.
        repeated .envoy.config.core.v3.Http2ProtocolOptions.SettingsParameter custom_settings_parameters = 13;

      • getCustomSettingsParametersBuilderList

        public List<Http2ProtocolOptions.SettingsParameter.Builder> getCustomSettingsParametersBuilderList()
         [#not-implemented-hide:]
 Specifies SETTINGS frame parameters to be sent to the peer, with two exceptions:
 1. SETTINGS_ENABLE_PUSH (0x2) is not configurable as HTTP/2 server push is not supported by
 Envoy.
 2. SETTINGS_ENABLE_CONNECT_PROTOCOL (0x8) is only configurable through the named field
 'allow_connect'.
 Note that custom parameters specified through this field can not also be set in the
 corresponding named parameters:
 .. code-block:: text
   ID    Field Name
   ----------------
   0x1   hpack_table_size
   0x3   max_concurrent_streams
   0x4   initial_stream_window_size
 Collisions will trigger config validation failure on load/update. Likewise, inconsistencies
 between custom parameters with the same identifier will trigger a failure.
 See `IANA HTTP/2 Settings
 <https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml#settings>`_ for
 standardized identifiers.
        repeated .envoy.config.core.v3.Http2ProtocolOptions.SettingsParameter custom_settings_parameters = 13;

      • hasConnectionKeepalive

        public boolean hasConnectionKeepalive()
         Send HTTP/2 PING frames to verify that the connection is still healthy. If the remote peer
 does not respond within the configured timeout, the connection will be aborted.
        .envoy.config.core.v3.KeepaliveSettings connection_keepalive = 15;
        Specified by:
        hasConnectionKeepalive in interface Http2ProtocolOptionsOrBuilder
        Returns:
        Whether the connectionKeepalive field is set.

      • getConnectionKeepalive

        public KeepaliveSettings getConnectionKeepalive()
         Send HTTP/2 PING frames to verify that the connection is still healthy. If the remote peer
 does not respond within the configured timeout, the connection will be aborted.
        .envoy.config.core.v3.KeepaliveSettings connection_keepalive = 15;
        Specified by:
        getConnectionKeepalive in interface Http2ProtocolOptionsOrBuilder
        Returns:
        The connectionKeepalive.

      • setConnectionKeepalive

        public Http2ProtocolOptions.Builder setConnectionKeepalive​(KeepaliveSettings value)
         Send HTTP/2 PING frames to verify that the connection is still healthy. If the remote peer
 does not respond within the configured timeout, the connection will be aborted.
        .envoy.config.core.v3.KeepaliveSettings connection_keepalive = 15;

      • setConnectionKeepalive

        public Http2ProtocolOptions.Builder setConnectionKeepalive​(KeepaliveSettings.Builder builderForValue)
         Send HTTP/2 PING frames to verify that the connection is still healthy. If the remote peer
 does not respond within the configured timeout, the connection will be aborted.
        .envoy.config.core.v3.KeepaliveSettings connection_keepalive = 15;

      • mergeConnectionKeepalive

        public Http2ProtocolOptions.Builder mergeConnectionKeepalive​(KeepaliveSettings value)
         Send HTTP/2 PING frames to verify that the connection is still healthy. If the remote peer
 does not respond within the configured timeout, the connection will be aborted.
        .envoy.config.core.v3.KeepaliveSettings connection_keepalive = 15;

      • clearConnectionKeepalive

        public Http2ProtocolOptions.Builder clearConnectionKeepalive()
         Send HTTP/2 PING frames to verify that the connection is still healthy. If the remote peer
 does not respond within the configured timeout, the connection will be aborted.
        .envoy.config.core.v3.KeepaliveSettings connection_keepalive = 15;

      • getConnectionKeepaliveBuilder

        public KeepaliveSettings.Builder getConnectionKeepaliveBuilder()
         Send HTTP/2 PING frames to verify that the connection is still healthy. If the remote peer
 does not respond within the configured timeout, the connection will be aborted.
        .envoy.config.core.v3.KeepaliveSettings connection_keepalive = 15;

      • getConnectionKeepaliveOrBuilder

        public KeepaliveSettingsOrBuilder getConnectionKeepaliveOrBuilder()
         Send HTTP/2 PING frames to verify that the connection is still healthy. If the remote peer
 does not respond within the configured timeout, the connection will be aborted.
        .envoy.config.core.v3.KeepaliveSettings connection_keepalive = 15;
        Specified by:
        getConnectionKeepaliveOrBuilder in interface Http2ProtocolOptionsOrBuilder

      • setUnknownFields

        public final Http2ProtocolOptions.Builder setUnknownFields​(com.google.protobuf.UnknownFieldSet unknownFields)
        Specified by:
        setUnknownFields in interface com.google.protobuf.Message.Builder
        Overrides:
        setUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<Http2ProtocolOptions.Builder>

      • mergeUnknownFields

        public final Http2ProtocolOptions.Builder mergeUnknownFields​(com.google.protobuf.UnknownFieldSet unknownFields)
        Specified by:
        mergeUnknownFields in interface com.google.protobuf.Message.Builder
        Overrides:
        mergeUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<Http2ProtocolOptions.Builder>