java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<Router.Builder>
com.google.protobuf.GeneratedMessage.Builder<Router.Builder>
io.envoyproxy.envoy.extensions.filters.http.router.v3.Router.Builder
All Implemented Interfaces:
com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, RouterOrBuilder, Cloneable
Enclosing class:
Router

public static final class Router.Builder extends com.google.protobuf.GeneratedMessage.Builder<Router.Builder> implements RouterOrBuilder
 [#next-free-field: 10]
 
Protobuf type envoy.extensions.filters.http.router.v3.Router
  • Field Details

    • bitField0_

      private int bitField0_
    • dynamicStats_

      private com.google.protobuf.BoolValue dynamicStats_
    • dynamicStatsBuilder_

      private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder,com.google.protobuf.BoolValueOrBuilder> dynamicStatsBuilder_
    • startChildSpan_

      private boolean startChildSpan_
    • upstreamLog_

      private List<AccessLog> upstreamLog_
    • upstreamLogBuilder_

      private com.google.protobuf.RepeatedFieldBuilder<AccessLog,AccessLog.Builder,AccessLogOrBuilder> upstreamLogBuilder_
    • upstreamLogOptions_

      private Router.UpstreamAccessLogOptions upstreamLogOptions_
    • upstreamLogOptionsBuilder_

      private com.google.protobuf.SingleFieldBuilder<Router.UpstreamAccessLogOptions,Router.UpstreamAccessLogOptions.Builder,Router.UpstreamAccessLogOptionsOrBuilder> upstreamLogOptionsBuilder_
    • suppressEnvoyHeaders_

      private boolean suppressEnvoyHeaders_
    • strictCheckHeaders_

      private com.google.protobuf.LazyStringArrayList strictCheckHeaders_
    • respectExpectedRqTimeout_

      private boolean respectExpectedRqTimeout_
    • suppressGrpcRequestFailureCodeStats_

      private boolean suppressGrpcRequestFailureCodeStats_
    • upstreamHttpFilters_

      private List<HttpFilter> upstreamHttpFilters_
    • upstreamHttpFiltersBuilder_

      private com.google.protobuf.RepeatedFieldBuilder<HttpFilter,HttpFilter.Builder,HttpFilterOrBuilder> upstreamHttpFiltersBuilder_
  • Constructor Details

    • Builder

      private Builder()
    • Builder

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

    • getDescriptor

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

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

      private void maybeForceBuilderInitialization()
    • clear

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

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

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

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

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

      private void buildPartialRepeatedFields(Router result)
    • buildPartial0

      private void buildPartial0(Router result)
    • mergeFrom

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

      public Router.Builder mergeFrom(Router other)
    • isInitialized

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

      public Router.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<Router.Builder>
      Throws:
      IOException
    • hasDynamicStats

      public boolean hasDynamicStats()
       Whether the router generates dynamic cluster statistics. Defaults to
       true. Can be disabled in high performance scenarios.
       
      .google.protobuf.BoolValue dynamic_stats = 1;
      Specified by:
      hasDynamicStats in interface RouterOrBuilder
      Returns:
      Whether the dynamicStats field is set.
    • getDynamicStats

      public com.google.protobuf.BoolValue getDynamicStats()
       Whether the router generates dynamic cluster statistics. Defaults to
       true. Can be disabled in high performance scenarios.
       
      .google.protobuf.BoolValue dynamic_stats = 1;
      Specified by:
      getDynamicStats in interface RouterOrBuilder
      Returns:
      The dynamicStats.
    • setDynamicStats

      public Router.Builder setDynamicStats(com.google.protobuf.BoolValue value)
       Whether the router generates dynamic cluster statistics. Defaults to
       true. Can be disabled in high performance scenarios.
       
      .google.protobuf.BoolValue dynamic_stats = 1;
    • setDynamicStats

      public Router.Builder setDynamicStats(com.google.protobuf.BoolValue.Builder builderForValue)
       Whether the router generates dynamic cluster statistics. Defaults to
       true. Can be disabled in high performance scenarios.
       
      .google.protobuf.BoolValue dynamic_stats = 1;
    • mergeDynamicStats

      public Router.Builder mergeDynamicStats(com.google.protobuf.BoolValue value)
       Whether the router generates dynamic cluster statistics. Defaults to
       true. Can be disabled in high performance scenarios.
       
      .google.protobuf.BoolValue dynamic_stats = 1;
    • clearDynamicStats

      public Router.Builder clearDynamicStats()
       Whether the router generates dynamic cluster statistics. Defaults to
       true. Can be disabled in high performance scenarios.
       
      .google.protobuf.BoolValue dynamic_stats = 1;
    • getDynamicStatsBuilder

      public com.google.protobuf.BoolValue.Builder getDynamicStatsBuilder()
       Whether the router generates dynamic cluster statistics. Defaults to
       true. Can be disabled in high performance scenarios.
       
      .google.protobuf.BoolValue dynamic_stats = 1;
    • getDynamicStatsOrBuilder

      public com.google.protobuf.BoolValueOrBuilder getDynamicStatsOrBuilder()
       Whether the router generates dynamic cluster statistics. Defaults to
       true. Can be disabled in high performance scenarios.
       
      .google.protobuf.BoolValue dynamic_stats = 1;
      Specified by:
      getDynamicStatsOrBuilder in interface RouterOrBuilder
    • internalGetDynamicStatsFieldBuilder

      private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder,com.google.protobuf.BoolValueOrBuilder> internalGetDynamicStatsFieldBuilder()
       Whether the router generates dynamic cluster statistics. Defaults to
       true. Can be disabled in high performance scenarios.
       
      .google.protobuf.BoolValue dynamic_stats = 1;
    • getStartChildSpan

      @Deprecated public boolean getStartChildSpan()
      Deprecated.
      envoy.extensions.filters.http.router.v3.Router.start_child_span is deprecated. See envoy/extensions/filters/http/router/v3/router.proto;l=60
       Whether to start a child span for egress routed calls. This can be
       useful in scenarios where other filters (auth, ratelimit, etc.) make
       outbound calls and have child spans rooted at the same ingress
       parent. Defaults to false.
      
       .. attention::
       This field is deprecated by the
       :ref:`spawn_upstream_span <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.Tracing.spawn_upstream_span>`.
       Please use that ``spawn_upstream_span`` field to control the span creation.
       
      bool start_child_span = 2 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      Specified by:
      getStartChildSpan in interface RouterOrBuilder
      Returns:
      The startChildSpan.
    • setStartChildSpan

      @Deprecated public Router.Builder setStartChildSpan(boolean value)
      Deprecated.
      envoy.extensions.filters.http.router.v3.Router.start_child_span is deprecated. See envoy/extensions/filters/http/router/v3/router.proto;l=60
       Whether to start a child span for egress routed calls. This can be
       useful in scenarios where other filters (auth, ratelimit, etc.) make
       outbound calls and have child spans rooted at the same ingress
       parent. Defaults to false.
      
       .. attention::
       This field is deprecated by the
       :ref:`spawn_upstream_span <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.Tracing.spawn_upstream_span>`.
       Please use that ``spawn_upstream_span`` field to control the span creation.
       
      bool start_child_span = 2 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      Parameters:
      value - The startChildSpan to set.
      Returns:
      This builder for chaining.
    • clearStartChildSpan

      @Deprecated public Router.Builder clearStartChildSpan()
      Deprecated.
      envoy.extensions.filters.http.router.v3.Router.start_child_span is deprecated. See envoy/extensions/filters/http/router/v3/router.proto;l=60
       Whether to start a child span for egress routed calls. This can be
       useful in scenarios where other filters (auth, ratelimit, etc.) make
       outbound calls and have child spans rooted at the same ingress
       parent. Defaults to false.
      
       .. attention::
       This field is deprecated by the
       :ref:`spawn_upstream_span <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.Tracing.spawn_upstream_span>`.
       Please use that ``spawn_upstream_span`` field to control the span creation.
       
      bool start_child_span = 2 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      Returns:
      This builder for chaining.
    • ensureUpstreamLogIsMutable

      private void ensureUpstreamLogIsMutable()
    • getUpstreamLogList

      public List<AccessLog> getUpstreamLogList()
       Configuration for HTTP upstream logs emitted by the router. Upstream logs
       are configured in the same way as access logs, but each log entry represents
       an upstream request. Presuming retries are configured, multiple upstream
       requests may be made for each downstream (inbound) request.
       
      repeated .envoy.config.accesslog.v3.AccessLog upstream_log = 3;
      Specified by:
      getUpstreamLogList in interface RouterOrBuilder
    • getUpstreamLogCount

      public int getUpstreamLogCount()
       Configuration for HTTP upstream logs emitted by the router. Upstream logs
       are configured in the same way as access logs, but each log entry represents
       an upstream request. Presuming retries are configured, multiple upstream
       requests may be made for each downstream (inbound) request.
       
      repeated .envoy.config.accesslog.v3.AccessLog upstream_log = 3;
      Specified by:
      getUpstreamLogCount in interface RouterOrBuilder
    • getUpstreamLog

      public AccessLog getUpstreamLog(int index)
       Configuration for HTTP upstream logs emitted by the router. Upstream logs
       are configured in the same way as access logs, but each log entry represents
       an upstream request. Presuming retries are configured, multiple upstream
       requests may be made for each downstream (inbound) request.
       
      repeated .envoy.config.accesslog.v3.AccessLog upstream_log = 3;
      Specified by:
      getUpstreamLog in interface RouterOrBuilder
    • setUpstreamLog

      public Router.Builder setUpstreamLog(int index, AccessLog value)
       Configuration for HTTP upstream logs emitted by the router. Upstream logs
       are configured in the same way as access logs, but each log entry represents
       an upstream request. Presuming retries are configured, multiple upstream
       requests may be made for each downstream (inbound) request.
       
      repeated .envoy.config.accesslog.v3.AccessLog upstream_log = 3;
    • setUpstreamLog

      public Router.Builder setUpstreamLog(int index, AccessLog.Builder builderForValue)
       Configuration for HTTP upstream logs emitted by the router. Upstream logs
       are configured in the same way as access logs, but each log entry represents
       an upstream request. Presuming retries are configured, multiple upstream
       requests may be made for each downstream (inbound) request.
       
      repeated .envoy.config.accesslog.v3.AccessLog upstream_log = 3;
    • addUpstreamLog

      public Router.Builder addUpstreamLog(AccessLog value)
       Configuration for HTTP upstream logs emitted by the router. Upstream logs
       are configured in the same way as access logs, but each log entry represents
       an upstream request. Presuming retries are configured, multiple upstream
       requests may be made for each downstream (inbound) request.
       
      repeated .envoy.config.accesslog.v3.AccessLog upstream_log = 3;
    • addUpstreamLog

      public Router.Builder addUpstreamLog(int index, AccessLog value)
       Configuration for HTTP upstream logs emitted by the router. Upstream logs
       are configured in the same way as access logs, but each log entry represents
       an upstream request. Presuming retries are configured, multiple upstream
       requests may be made for each downstream (inbound) request.
       
      repeated .envoy.config.accesslog.v3.AccessLog upstream_log = 3;
    • addUpstreamLog

      public Router.Builder addUpstreamLog(AccessLog.Builder builderForValue)
       Configuration for HTTP upstream logs emitted by the router. Upstream logs
       are configured in the same way as access logs, but each log entry represents
       an upstream request. Presuming retries are configured, multiple upstream
       requests may be made for each downstream (inbound) request.
       
      repeated .envoy.config.accesslog.v3.AccessLog upstream_log = 3;
    • addUpstreamLog

      public Router.Builder addUpstreamLog(int index, AccessLog.Builder builderForValue)
       Configuration for HTTP upstream logs emitted by the router. Upstream logs
       are configured in the same way as access logs, but each log entry represents
       an upstream request. Presuming retries are configured, multiple upstream
       requests may be made for each downstream (inbound) request.
       
      repeated .envoy.config.accesslog.v3.AccessLog upstream_log = 3;
    • addAllUpstreamLog

      public Router.Builder addAllUpstreamLog(Iterable<? extends AccessLog> values)
       Configuration for HTTP upstream logs emitted by the router. Upstream logs
       are configured in the same way as access logs, but each log entry represents
       an upstream request. Presuming retries are configured, multiple upstream
       requests may be made for each downstream (inbound) request.
       
      repeated .envoy.config.accesslog.v3.AccessLog upstream_log = 3;
    • clearUpstreamLog

      public Router.Builder clearUpstreamLog()
       Configuration for HTTP upstream logs emitted by the router. Upstream logs
       are configured in the same way as access logs, but each log entry represents
       an upstream request. Presuming retries are configured, multiple upstream
       requests may be made for each downstream (inbound) request.
       
      repeated .envoy.config.accesslog.v3.AccessLog upstream_log = 3;
    • removeUpstreamLog

      public Router.Builder removeUpstreamLog(int index)
       Configuration for HTTP upstream logs emitted by the router. Upstream logs
       are configured in the same way as access logs, but each log entry represents
       an upstream request. Presuming retries are configured, multiple upstream
       requests may be made for each downstream (inbound) request.
       
      repeated .envoy.config.accesslog.v3.AccessLog upstream_log = 3;
    • getUpstreamLogBuilder

      public AccessLog.Builder getUpstreamLogBuilder(int index)
       Configuration for HTTP upstream logs emitted by the router. Upstream logs
       are configured in the same way as access logs, but each log entry represents
       an upstream request. Presuming retries are configured, multiple upstream
       requests may be made for each downstream (inbound) request.
       
      repeated .envoy.config.accesslog.v3.AccessLog upstream_log = 3;
    • getUpstreamLogOrBuilder

      public AccessLogOrBuilder getUpstreamLogOrBuilder(int index)
       Configuration for HTTP upstream logs emitted by the router. Upstream logs
       are configured in the same way as access logs, but each log entry represents
       an upstream request. Presuming retries are configured, multiple upstream
       requests may be made for each downstream (inbound) request.
       
      repeated .envoy.config.accesslog.v3.AccessLog upstream_log = 3;
      Specified by:
      getUpstreamLogOrBuilder in interface RouterOrBuilder
    • getUpstreamLogOrBuilderList

      public List<? extends AccessLogOrBuilder> getUpstreamLogOrBuilderList()
       Configuration for HTTP upstream logs emitted by the router. Upstream logs
       are configured in the same way as access logs, but each log entry represents
       an upstream request. Presuming retries are configured, multiple upstream
       requests may be made for each downstream (inbound) request.
       
      repeated .envoy.config.accesslog.v3.AccessLog upstream_log = 3;
      Specified by:
      getUpstreamLogOrBuilderList in interface RouterOrBuilder
    • addUpstreamLogBuilder

      public AccessLog.Builder addUpstreamLogBuilder()
       Configuration for HTTP upstream logs emitted by the router. Upstream logs
       are configured in the same way as access logs, but each log entry represents
       an upstream request. Presuming retries are configured, multiple upstream
       requests may be made for each downstream (inbound) request.
       
      repeated .envoy.config.accesslog.v3.AccessLog upstream_log = 3;
    • addUpstreamLogBuilder

      public AccessLog.Builder addUpstreamLogBuilder(int index)
       Configuration for HTTP upstream logs emitted by the router. Upstream logs
       are configured in the same way as access logs, but each log entry represents
       an upstream request. Presuming retries are configured, multiple upstream
       requests may be made for each downstream (inbound) request.
       
      repeated .envoy.config.accesslog.v3.AccessLog upstream_log = 3;
    • getUpstreamLogBuilderList

      public List<AccessLog.Builder> getUpstreamLogBuilderList()
       Configuration for HTTP upstream logs emitted by the router. Upstream logs
       are configured in the same way as access logs, but each log entry represents
       an upstream request. Presuming retries are configured, multiple upstream
       requests may be made for each downstream (inbound) request.
       
      repeated .envoy.config.accesslog.v3.AccessLog upstream_log = 3;
    • internalGetUpstreamLogFieldBuilder

      private com.google.protobuf.RepeatedFieldBuilder<AccessLog,AccessLog.Builder,AccessLogOrBuilder> internalGetUpstreamLogFieldBuilder()
    • hasUpstreamLogOptions

      public boolean hasUpstreamLogOptions()
       Additional upstream access log options.
       
      .envoy.extensions.filters.http.router.v3.Router.UpstreamAccessLogOptions upstream_log_options = 9;
      Specified by:
      hasUpstreamLogOptions in interface RouterOrBuilder
      Returns:
      Whether the upstreamLogOptions field is set.
    • getUpstreamLogOptions

      public Router.UpstreamAccessLogOptions getUpstreamLogOptions()
       Additional upstream access log options.
       
      .envoy.extensions.filters.http.router.v3.Router.UpstreamAccessLogOptions upstream_log_options = 9;
      Specified by:
      getUpstreamLogOptions in interface RouterOrBuilder
      Returns:
      The upstreamLogOptions.
    • setUpstreamLogOptions

      public Router.Builder setUpstreamLogOptions(Router.UpstreamAccessLogOptions value)
       Additional upstream access log options.
       
      .envoy.extensions.filters.http.router.v3.Router.UpstreamAccessLogOptions upstream_log_options = 9;
    • setUpstreamLogOptions

      public Router.Builder setUpstreamLogOptions(Router.UpstreamAccessLogOptions.Builder builderForValue)
       Additional upstream access log options.
       
      .envoy.extensions.filters.http.router.v3.Router.UpstreamAccessLogOptions upstream_log_options = 9;
    • mergeUpstreamLogOptions

      public Router.Builder mergeUpstreamLogOptions(Router.UpstreamAccessLogOptions value)
       Additional upstream access log options.
       
      .envoy.extensions.filters.http.router.v3.Router.UpstreamAccessLogOptions upstream_log_options = 9;
    • clearUpstreamLogOptions

      public Router.Builder clearUpstreamLogOptions()
       Additional upstream access log options.
       
      .envoy.extensions.filters.http.router.v3.Router.UpstreamAccessLogOptions upstream_log_options = 9;
    • getUpstreamLogOptionsBuilder

      public Router.UpstreamAccessLogOptions.Builder getUpstreamLogOptionsBuilder()
       Additional upstream access log options.
       
      .envoy.extensions.filters.http.router.v3.Router.UpstreamAccessLogOptions upstream_log_options = 9;
    • getUpstreamLogOptionsOrBuilder

      public Router.UpstreamAccessLogOptionsOrBuilder getUpstreamLogOptionsOrBuilder()
       Additional upstream access log options.
       
      .envoy.extensions.filters.http.router.v3.Router.UpstreamAccessLogOptions upstream_log_options = 9;
      Specified by:
      getUpstreamLogOptionsOrBuilder in interface RouterOrBuilder
    • internalGetUpstreamLogOptionsFieldBuilder

      private com.google.protobuf.SingleFieldBuilder<Router.UpstreamAccessLogOptions,Router.UpstreamAccessLogOptions.Builder,Router.UpstreamAccessLogOptionsOrBuilder> internalGetUpstreamLogOptionsFieldBuilder()
       Additional upstream access log options.
       
      .envoy.extensions.filters.http.router.v3.Router.UpstreamAccessLogOptions upstream_log_options = 9;
    • getSuppressEnvoyHeaders

      public boolean getSuppressEnvoyHeaders()
       Do not add any additional ``x-envoy-`` headers to requests or responses. This
       only affects the :ref:`router filter generated x-envoy- headers
       <config_http_filters_router_headers_set>`, other Envoy filters and the HTTP
       connection manager may continue to set ``x-envoy-`` headers.
       
      bool suppress_envoy_headers = 4;
      Specified by:
      getSuppressEnvoyHeaders in interface RouterOrBuilder
      Returns:
      The suppressEnvoyHeaders.
    • setSuppressEnvoyHeaders

      public Router.Builder setSuppressEnvoyHeaders(boolean value)
       Do not add any additional ``x-envoy-`` headers to requests or responses. This
       only affects the :ref:`router filter generated x-envoy- headers
       <config_http_filters_router_headers_set>`, other Envoy filters and the HTTP
       connection manager may continue to set ``x-envoy-`` headers.
       
      bool suppress_envoy_headers = 4;
      Parameters:
      value - The suppressEnvoyHeaders to set.
      Returns:
      This builder for chaining.
    • clearSuppressEnvoyHeaders

      public Router.Builder clearSuppressEnvoyHeaders()
       Do not add any additional ``x-envoy-`` headers to requests or responses. This
       only affects the :ref:`router filter generated x-envoy- headers
       <config_http_filters_router_headers_set>`, other Envoy filters and the HTTP
       connection manager may continue to set ``x-envoy-`` headers.
       
      bool suppress_envoy_headers = 4;
      Returns:
      This builder for chaining.
    • ensureStrictCheckHeadersIsMutable

      private void ensureStrictCheckHeadersIsMutable()
    • getStrictCheckHeadersList

      public com.google.protobuf.ProtocolStringList getStrictCheckHeadersList()
       Specifies a list of HTTP headers to strictly validate. Envoy will reject a
       request and respond with HTTP status 400 if the request contains an invalid
       value for any of the headers listed in this field. Strict header checking
       is only supported for the following headers:
      
       Value must be a ','-delimited list (i.e. no spaces) of supported retry
       policy values:
      
       * :ref:`config_http_filters_router_x-envoy-retry-grpc-on`
       * :ref:`config_http_filters_router_x-envoy-retry-on`
      
       Value must be an integer:
      
       * :ref:`config_http_filters_router_x-envoy-max-retries`
       * :ref:`config_http_filters_router_x-envoy-upstream-rq-timeout-ms`
       * :ref:`config_http_filters_router_x-envoy-upstream-rq-per-try-timeout-ms`
       
      repeated string strict_check_headers = 5 [(.validate.rules) = { ... }
      Specified by:
      getStrictCheckHeadersList in interface RouterOrBuilder
      Returns:
      A list containing the strictCheckHeaders.
    • getStrictCheckHeadersCount

      public int getStrictCheckHeadersCount()
       Specifies a list of HTTP headers to strictly validate. Envoy will reject a
       request and respond with HTTP status 400 if the request contains an invalid
       value for any of the headers listed in this field. Strict header checking
       is only supported for the following headers:
      
       Value must be a ','-delimited list (i.e. no spaces) of supported retry
       policy values:
      
       * :ref:`config_http_filters_router_x-envoy-retry-grpc-on`
       * :ref:`config_http_filters_router_x-envoy-retry-on`
      
       Value must be an integer:
      
       * :ref:`config_http_filters_router_x-envoy-max-retries`
       * :ref:`config_http_filters_router_x-envoy-upstream-rq-timeout-ms`
       * :ref:`config_http_filters_router_x-envoy-upstream-rq-per-try-timeout-ms`
       
      repeated string strict_check_headers = 5 [(.validate.rules) = { ... }
      Specified by:
      getStrictCheckHeadersCount in interface RouterOrBuilder
      Returns:
      The count of strictCheckHeaders.
    • getStrictCheckHeaders

      public String getStrictCheckHeaders(int index)
       Specifies a list of HTTP headers to strictly validate. Envoy will reject a
       request and respond with HTTP status 400 if the request contains an invalid
       value for any of the headers listed in this field. Strict header checking
       is only supported for the following headers:
      
       Value must be a ','-delimited list (i.e. no spaces) of supported retry
       policy values:
      
       * :ref:`config_http_filters_router_x-envoy-retry-grpc-on`
       * :ref:`config_http_filters_router_x-envoy-retry-on`
      
       Value must be an integer:
      
       * :ref:`config_http_filters_router_x-envoy-max-retries`
       * :ref:`config_http_filters_router_x-envoy-upstream-rq-timeout-ms`
       * :ref:`config_http_filters_router_x-envoy-upstream-rq-per-try-timeout-ms`
       
      repeated string strict_check_headers = 5 [(.validate.rules) = { ... }
      Specified by:
      getStrictCheckHeaders in interface RouterOrBuilder
      Parameters:
      index - The index of the element to return.
      Returns:
      The strictCheckHeaders at the given index.
    • getStrictCheckHeadersBytes

      public com.google.protobuf.ByteString getStrictCheckHeadersBytes(int index)
       Specifies a list of HTTP headers to strictly validate. Envoy will reject a
       request and respond with HTTP status 400 if the request contains an invalid
       value for any of the headers listed in this field. Strict header checking
       is only supported for the following headers:
      
       Value must be a ','-delimited list (i.e. no spaces) of supported retry
       policy values:
      
       * :ref:`config_http_filters_router_x-envoy-retry-grpc-on`
       * :ref:`config_http_filters_router_x-envoy-retry-on`
      
       Value must be an integer:
      
       * :ref:`config_http_filters_router_x-envoy-max-retries`
       * :ref:`config_http_filters_router_x-envoy-upstream-rq-timeout-ms`
       * :ref:`config_http_filters_router_x-envoy-upstream-rq-per-try-timeout-ms`
       
      repeated string strict_check_headers = 5 [(.validate.rules) = { ... }
      Specified by:
      getStrictCheckHeadersBytes in interface RouterOrBuilder
      Parameters:
      index - The index of the value to return.
      Returns:
      The bytes of the strictCheckHeaders at the given index.
    • setStrictCheckHeaders

      public Router.Builder setStrictCheckHeaders(int index, String value)
       Specifies a list of HTTP headers to strictly validate. Envoy will reject a
       request and respond with HTTP status 400 if the request contains an invalid
       value for any of the headers listed in this field. Strict header checking
       is only supported for the following headers:
      
       Value must be a ','-delimited list (i.e. no spaces) of supported retry
       policy values:
      
       * :ref:`config_http_filters_router_x-envoy-retry-grpc-on`
       * :ref:`config_http_filters_router_x-envoy-retry-on`
      
       Value must be an integer:
      
       * :ref:`config_http_filters_router_x-envoy-max-retries`
       * :ref:`config_http_filters_router_x-envoy-upstream-rq-timeout-ms`
       * :ref:`config_http_filters_router_x-envoy-upstream-rq-per-try-timeout-ms`
       
      repeated string strict_check_headers = 5 [(.validate.rules) = { ... }
      Parameters:
      index - The index to set the value at.
      value - The strictCheckHeaders to set.
      Returns:
      This builder for chaining.
    • addStrictCheckHeaders

      public Router.Builder addStrictCheckHeaders(String value)
       Specifies a list of HTTP headers to strictly validate. Envoy will reject a
       request and respond with HTTP status 400 if the request contains an invalid
       value for any of the headers listed in this field. Strict header checking
       is only supported for the following headers:
      
       Value must be a ','-delimited list (i.e. no spaces) of supported retry
       policy values:
      
       * :ref:`config_http_filters_router_x-envoy-retry-grpc-on`
       * :ref:`config_http_filters_router_x-envoy-retry-on`
      
       Value must be an integer:
      
       * :ref:`config_http_filters_router_x-envoy-max-retries`
       * :ref:`config_http_filters_router_x-envoy-upstream-rq-timeout-ms`
       * :ref:`config_http_filters_router_x-envoy-upstream-rq-per-try-timeout-ms`
       
      repeated string strict_check_headers = 5 [(.validate.rules) = { ... }
      Parameters:
      value - The strictCheckHeaders to add.
      Returns:
      This builder for chaining.
    • addAllStrictCheckHeaders

      public Router.Builder addAllStrictCheckHeaders(Iterable<String> values)
       Specifies a list of HTTP headers to strictly validate. Envoy will reject a
       request and respond with HTTP status 400 if the request contains an invalid
       value for any of the headers listed in this field. Strict header checking
       is only supported for the following headers:
      
       Value must be a ','-delimited list (i.e. no spaces) of supported retry
       policy values:
      
       * :ref:`config_http_filters_router_x-envoy-retry-grpc-on`
       * :ref:`config_http_filters_router_x-envoy-retry-on`
      
       Value must be an integer:
      
       * :ref:`config_http_filters_router_x-envoy-max-retries`
       * :ref:`config_http_filters_router_x-envoy-upstream-rq-timeout-ms`
       * :ref:`config_http_filters_router_x-envoy-upstream-rq-per-try-timeout-ms`
       
      repeated string strict_check_headers = 5 [(.validate.rules) = { ... }
      Parameters:
      values - The strictCheckHeaders to add.
      Returns:
      This builder for chaining.
    • clearStrictCheckHeaders

      public Router.Builder clearStrictCheckHeaders()
       Specifies a list of HTTP headers to strictly validate. Envoy will reject a
       request and respond with HTTP status 400 if the request contains an invalid
       value for any of the headers listed in this field. Strict header checking
       is only supported for the following headers:
      
       Value must be a ','-delimited list (i.e. no spaces) of supported retry
       policy values:
      
       * :ref:`config_http_filters_router_x-envoy-retry-grpc-on`
       * :ref:`config_http_filters_router_x-envoy-retry-on`
      
       Value must be an integer:
      
       * :ref:`config_http_filters_router_x-envoy-max-retries`
       * :ref:`config_http_filters_router_x-envoy-upstream-rq-timeout-ms`
       * :ref:`config_http_filters_router_x-envoy-upstream-rq-per-try-timeout-ms`
       
      repeated string strict_check_headers = 5 [(.validate.rules) = { ... }
      Returns:
      This builder for chaining.
    • addStrictCheckHeadersBytes

      public Router.Builder addStrictCheckHeadersBytes(com.google.protobuf.ByteString value)
       Specifies a list of HTTP headers to strictly validate. Envoy will reject a
       request and respond with HTTP status 400 if the request contains an invalid
       value for any of the headers listed in this field. Strict header checking
       is only supported for the following headers:
      
       Value must be a ','-delimited list (i.e. no spaces) of supported retry
       policy values:
      
       * :ref:`config_http_filters_router_x-envoy-retry-grpc-on`
       * :ref:`config_http_filters_router_x-envoy-retry-on`
      
       Value must be an integer:
      
       * :ref:`config_http_filters_router_x-envoy-max-retries`
       * :ref:`config_http_filters_router_x-envoy-upstream-rq-timeout-ms`
       * :ref:`config_http_filters_router_x-envoy-upstream-rq-per-try-timeout-ms`
       
      repeated string strict_check_headers = 5 [(.validate.rules) = { ... }
      Parameters:
      value - The bytes of the strictCheckHeaders to add.
      Returns:
      This builder for chaining.
    • getRespectExpectedRqTimeout

      public boolean getRespectExpectedRqTimeout()
       If not set, ingress Envoy will ignore
       :ref:`config_http_filters_router_x-envoy-expected-rq-timeout-ms` header, populated by egress
       Envoy, when deriving timeout for upstream cluster.
       
      bool respect_expected_rq_timeout = 6;
      Specified by:
      getRespectExpectedRqTimeout in interface RouterOrBuilder
      Returns:
      The respectExpectedRqTimeout.
    • setRespectExpectedRqTimeout

      public Router.Builder setRespectExpectedRqTimeout(boolean value)
       If not set, ingress Envoy will ignore
       :ref:`config_http_filters_router_x-envoy-expected-rq-timeout-ms` header, populated by egress
       Envoy, when deriving timeout for upstream cluster.
       
      bool respect_expected_rq_timeout = 6;
      Parameters:
      value - The respectExpectedRqTimeout to set.
      Returns:
      This builder for chaining.
    • clearRespectExpectedRqTimeout

      public Router.Builder clearRespectExpectedRqTimeout()
       If not set, ingress Envoy will ignore
       :ref:`config_http_filters_router_x-envoy-expected-rq-timeout-ms` header, populated by egress
       Envoy, when deriving timeout for upstream cluster.
       
      bool respect_expected_rq_timeout = 6;
      Returns:
      This builder for chaining.
    • getSuppressGrpcRequestFailureCodeStats

      public boolean getSuppressGrpcRequestFailureCodeStats()
       If set, Envoy will avoid incrementing HTTP failure code stats
       on gRPC requests. This includes the individual status code value
       (e.g. upstream_rq_504) and group stats (e.g. upstream_rq_5xx).
       This field is useful if interested in relying only on the gRPC
       stats filter to define success and failure metrics for gRPC requests
       as not all failed gRPC requests charge HTTP status code metrics. See
       :ref:`gRPC stats filter<config_http_filters_grpc_stats>` documentation
       for more details.
       
      bool suppress_grpc_request_failure_code_stats = 7;
      Specified by:
      getSuppressGrpcRequestFailureCodeStats in interface RouterOrBuilder
      Returns:
      The suppressGrpcRequestFailureCodeStats.
    • setSuppressGrpcRequestFailureCodeStats

      public Router.Builder setSuppressGrpcRequestFailureCodeStats(boolean value)
       If set, Envoy will avoid incrementing HTTP failure code stats
       on gRPC requests. This includes the individual status code value
       (e.g. upstream_rq_504) and group stats (e.g. upstream_rq_5xx).
       This field is useful if interested in relying only on the gRPC
       stats filter to define success and failure metrics for gRPC requests
       as not all failed gRPC requests charge HTTP status code metrics. See
       :ref:`gRPC stats filter<config_http_filters_grpc_stats>` documentation
       for more details.
       
      bool suppress_grpc_request_failure_code_stats = 7;
      Parameters:
      value - The suppressGrpcRequestFailureCodeStats to set.
      Returns:
      This builder for chaining.
    • clearSuppressGrpcRequestFailureCodeStats

      public Router.Builder clearSuppressGrpcRequestFailureCodeStats()
       If set, Envoy will avoid incrementing HTTP failure code stats
       on gRPC requests. This includes the individual status code value
       (e.g. upstream_rq_504) and group stats (e.g. upstream_rq_5xx).
       This field is useful if interested in relying only on the gRPC
       stats filter to define success and failure metrics for gRPC requests
       as not all failed gRPC requests charge HTTP status code metrics. See
       :ref:`gRPC stats filter<config_http_filters_grpc_stats>` documentation
       for more details.
       
      bool suppress_grpc_request_failure_code_stats = 7;
      Returns:
      This builder for chaining.
    • ensureUpstreamHttpFiltersIsMutable

      private void ensureUpstreamHttpFiltersIsMutable()
    • getUpstreamHttpFiltersList

      public List<HttpFilter> getUpstreamHttpFiltersList()
       .. note::
       Upstream HTTP filters are currently in alpha.
      
       Optional HTTP filters for the upstream HTTP filter chain.
      
       These filters will be applied for all requests that pass through the router.
       They will also be applied to shadowed requests.
       Upstream HTTP filters cannot change route or cluster.
       Upstream HTTP filters specified on the cluster will override these filters.
      
       If using upstream HTTP filters, please be aware that local errors sent by
       upstream HTTP filters will not trigger retries, and local errors sent by
       upstream HTTP filters will count as a final response if hedging is configured.
       [#extension-category: envoy.filters.http.upstream]
       
      repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter upstream_http_filters = 8;
      Specified by:
      getUpstreamHttpFiltersList in interface RouterOrBuilder
    • getUpstreamHttpFiltersCount

      public int getUpstreamHttpFiltersCount()
       .. note::
       Upstream HTTP filters are currently in alpha.
      
       Optional HTTP filters for the upstream HTTP filter chain.
      
       These filters will be applied for all requests that pass through the router.
       They will also be applied to shadowed requests.
       Upstream HTTP filters cannot change route or cluster.
       Upstream HTTP filters specified on the cluster will override these filters.
      
       If using upstream HTTP filters, please be aware that local errors sent by
       upstream HTTP filters will not trigger retries, and local errors sent by
       upstream HTTP filters will count as a final response if hedging is configured.
       [#extension-category: envoy.filters.http.upstream]
       
      repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter upstream_http_filters = 8;
      Specified by:
      getUpstreamHttpFiltersCount in interface RouterOrBuilder
    • getUpstreamHttpFilters

      public HttpFilter getUpstreamHttpFilters(int index)
       .. note::
       Upstream HTTP filters are currently in alpha.
      
       Optional HTTP filters for the upstream HTTP filter chain.
      
       These filters will be applied for all requests that pass through the router.
       They will also be applied to shadowed requests.
       Upstream HTTP filters cannot change route or cluster.
       Upstream HTTP filters specified on the cluster will override these filters.
      
       If using upstream HTTP filters, please be aware that local errors sent by
       upstream HTTP filters will not trigger retries, and local errors sent by
       upstream HTTP filters will count as a final response if hedging is configured.
       [#extension-category: envoy.filters.http.upstream]
       
      repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter upstream_http_filters = 8;
      Specified by:
      getUpstreamHttpFilters in interface RouterOrBuilder
    • setUpstreamHttpFilters

      public Router.Builder setUpstreamHttpFilters(int index, HttpFilter value)
       .. note::
       Upstream HTTP filters are currently in alpha.
      
       Optional HTTP filters for the upstream HTTP filter chain.
      
       These filters will be applied for all requests that pass through the router.
       They will also be applied to shadowed requests.
       Upstream HTTP filters cannot change route or cluster.
       Upstream HTTP filters specified on the cluster will override these filters.
      
       If using upstream HTTP filters, please be aware that local errors sent by
       upstream HTTP filters will not trigger retries, and local errors sent by
       upstream HTTP filters will count as a final response if hedging is configured.
       [#extension-category: envoy.filters.http.upstream]
       
      repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter upstream_http_filters = 8;
    • setUpstreamHttpFilters

      public Router.Builder setUpstreamHttpFilters(int index, HttpFilter.Builder builderForValue)
       .. note::
       Upstream HTTP filters are currently in alpha.
      
       Optional HTTP filters for the upstream HTTP filter chain.
      
       These filters will be applied for all requests that pass through the router.
       They will also be applied to shadowed requests.
       Upstream HTTP filters cannot change route or cluster.
       Upstream HTTP filters specified on the cluster will override these filters.
      
       If using upstream HTTP filters, please be aware that local errors sent by
       upstream HTTP filters will not trigger retries, and local errors sent by
       upstream HTTP filters will count as a final response if hedging is configured.
       [#extension-category: envoy.filters.http.upstream]
       
      repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter upstream_http_filters = 8;
    • addUpstreamHttpFilters

      public Router.Builder addUpstreamHttpFilters(HttpFilter value)
       .. note::
       Upstream HTTP filters are currently in alpha.
      
       Optional HTTP filters for the upstream HTTP filter chain.
      
       These filters will be applied for all requests that pass through the router.
       They will also be applied to shadowed requests.
       Upstream HTTP filters cannot change route or cluster.
       Upstream HTTP filters specified on the cluster will override these filters.
      
       If using upstream HTTP filters, please be aware that local errors sent by
       upstream HTTP filters will not trigger retries, and local errors sent by
       upstream HTTP filters will count as a final response if hedging is configured.
       [#extension-category: envoy.filters.http.upstream]
       
      repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter upstream_http_filters = 8;
    • addUpstreamHttpFilters

      public Router.Builder addUpstreamHttpFilters(int index, HttpFilter value)
       .. note::
       Upstream HTTP filters are currently in alpha.
      
       Optional HTTP filters for the upstream HTTP filter chain.
      
       These filters will be applied for all requests that pass through the router.
       They will also be applied to shadowed requests.
       Upstream HTTP filters cannot change route or cluster.
       Upstream HTTP filters specified on the cluster will override these filters.
      
       If using upstream HTTP filters, please be aware that local errors sent by
       upstream HTTP filters will not trigger retries, and local errors sent by
       upstream HTTP filters will count as a final response if hedging is configured.
       [#extension-category: envoy.filters.http.upstream]
       
      repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter upstream_http_filters = 8;
    • addUpstreamHttpFilters

      public Router.Builder addUpstreamHttpFilters(HttpFilter.Builder builderForValue)
       .. note::
       Upstream HTTP filters are currently in alpha.
      
       Optional HTTP filters for the upstream HTTP filter chain.
      
       These filters will be applied for all requests that pass through the router.
       They will also be applied to shadowed requests.
       Upstream HTTP filters cannot change route or cluster.
       Upstream HTTP filters specified on the cluster will override these filters.
      
       If using upstream HTTP filters, please be aware that local errors sent by
       upstream HTTP filters will not trigger retries, and local errors sent by
       upstream HTTP filters will count as a final response if hedging is configured.
       [#extension-category: envoy.filters.http.upstream]
       
      repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter upstream_http_filters = 8;
    • addUpstreamHttpFilters

      public Router.Builder addUpstreamHttpFilters(int index, HttpFilter.Builder builderForValue)
       .. note::
       Upstream HTTP filters are currently in alpha.
      
       Optional HTTP filters for the upstream HTTP filter chain.
      
       These filters will be applied for all requests that pass through the router.
       They will also be applied to shadowed requests.
       Upstream HTTP filters cannot change route or cluster.
       Upstream HTTP filters specified on the cluster will override these filters.
      
       If using upstream HTTP filters, please be aware that local errors sent by
       upstream HTTP filters will not trigger retries, and local errors sent by
       upstream HTTP filters will count as a final response if hedging is configured.
       [#extension-category: envoy.filters.http.upstream]
       
      repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter upstream_http_filters = 8;
    • addAllUpstreamHttpFilters

      public Router.Builder addAllUpstreamHttpFilters(Iterable<? extends HttpFilter> values)
       .. note::
       Upstream HTTP filters are currently in alpha.
      
       Optional HTTP filters for the upstream HTTP filter chain.
      
       These filters will be applied for all requests that pass through the router.
       They will also be applied to shadowed requests.
       Upstream HTTP filters cannot change route or cluster.
       Upstream HTTP filters specified on the cluster will override these filters.
      
       If using upstream HTTP filters, please be aware that local errors sent by
       upstream HTTP filters will not trigger retries, and local errors sent by
       upstream HTTP filters will count as a final response if hedging is configured.
       [#extension-category: envoy.filters.http.upstream]
       
      repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter upstream_http_filters = 8;
    • clearUpstreamHttpFilters

      public Router.Builder clearUpstreamHttpFilters()
       .. note::
       Upstream HTTP filters are currently in alpha.
      
       Optional HTTP filters for the upstream HTTP filter chain.
      
       These filters will be applied for all requests that pass through the router.
       They will also be applied to shadowed requests.
       Upstream HTTP filters cannot change route or cluster.
       Upstream HTTP filters specified on the cluster will override these filters.
      
       If using upstream HTTP filters, please be aware that local errors sent by
       upstream HTTP filters will not trigger retries, and local errors sent by
       upstream HTTP filters will count as a final response if hedging is configured.
       [#extension-category: envoy.filters.http.upstream]
       
      repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter upstream_http_filters = 8;
    • removeUpstreamHttpFilters

      public Router.Builder removeUpstreamHttpFilters(int index)
       .. note::
       Upstream HTTP filters are currently in alpha.
      
       Optional HTTP filters for the upstream HTTP filter chain.
      
       These filters will be applied for all requests that pass through the router.
       They will also be applied to shadowed requests.
       Upstream HTTP filters cannot change route or cluster.
       Upstream HTTP filters specified on the cluster will override these filters.
      
       If using upstream HTTP filters, please be aware that local errors sent by
       upstream HTTP filters will not trigger retries, and local errors sent by
       upstream HTTP filters will count as a final response if hedging is configured.
       [#extension-category: envoy.filters.http.upstream]
       
      repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter upstream_http_filters = 8;
    • getUpstreamHttpFiltersBuilder

      public HttpFilter.Builder getUpstreamHttpFiltersBuilder(int index)
       .. note::
       Upstream HTTP filters are currently in alpha.
      
       Optional HTTP filters for the upstream HTTP filter chain.
      
       These filters will be applied for all requests that pass through the router.
       They will also be applied to shadowed requests.
       Upstream HTTP filters cannot change route or cluster.
       Upstream HTTP filters specified on the cluster will override these filters.
      
       If using upstream HTTP filters, please be aware that local errors sent by
       upstream HTTP filters will not trigger retries, and local errors sent by
       upstream HTTP filters will count as a final response if hedging is configured.
       [#extension-category: envoy.filters.http.upstream]
       
      repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter upstream_http_filters = 8;
    • getUpstreamHttpFiltersOrBuilder

      public HttpFilterOrBuilder getUpstreamHttpFiltersOrBuilder(int index)
       .. note::
       Upstream HTTP filters are currently in alpha.
      
       Optional HTTP filters for the upstream HTTP filter chain.
      
       These filters will be applied for all requests that pass through the router.
       They will also be applied to shadowed requests.
       Upstream HTTP filters cannot change route or cluster.
       Upstream HTTP filters specified on the cluster will override these filters.
      
       If using upstream HTTP filters, please be aware that local errors sent by
       upstream HTTP filters will not trigger retries, and local errors sent by
       upstream HTTP filters will count as a final response if hedging is configured.
       [#extension-category: envoy.filters.http.upstream]
       
      repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter upstream_http_filters = 8;
      Specified by:
      getUpstreamHttpFiltersOrBuilder in interface RouterOrBuilder
    • getUpstreamHttpFiltersOrBuilderList

      public List<? extends HttpFilterOrBuilder> getUpstreamHttpFiltersOrBuilderList()
       .. note::
       Upstream HTTP filters are currently in alpha.
      
       Optional HTTP filters for the upstream HTTP filter chain.
      
       These filters will be applied for all requests that pass through the router.
       They will also be applied to shadowed requests.
       Upstream HTTP filters cannot change route or cluster.
       Upstream HTTP filters specified on the cluster will override these filters.
      
       If using upstream HTTP filters, please be aware that local errors sent by
       upstream HTTP filters will not trigger retries, and local errors sent by
       upstream HTTP filters will count as a final response if hedging is configured.
       [#extension-category: envoy.filters.http.upstream]
       
      repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter upstream_http_filters = 8;
      Specified by:
      getUpstreamHttpFiltersOrBuilderList in interface RouterOrBuilder
    • addUpstreamHttpFiltersBuilder

      public HttpFilter.Builder addUpstreamHttpFiltersBuilder()
       .. note::
       Upstream HTTP filters are currently in alpha.
      
       Optional HTTP filters for the upstream HTTP filter chain.
      
       These filters will be applied for all requests that pass through the router.
       They will also be applied to shadowed requests.
       Upstream HTTP filters cannot change route or cluster.
       Upstream HTTP filters specified on the cluster will override these filters.
      
       If using upstream HTTP filters, please be aware that local errors sent by
       upstream HTTP filters will not trigger retries, and local errors sent by
       upstream HTTP filters will count as a final response if hedging is configured.
       [#extension-category: envoy.filters.http.upstream]
       
      repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter upstream_http_filters = 8;
    • addUpstreamHttpFiltersBuilder

      public HttpFilter.Builder addUpstreamHttpFiltersBuilder(int index)
       .. note::
       Upstream HTTP filters are currently in alpha.
      
       Optional HTTP filters for the upstream HTTP filter chain.
      
       These filters will be applied for all requests that pass through the router.
       They will also be applied to shadowed requests.
       Upstream HTTP filters cannot change route or cluster.
       Upstream HTTP filters specified on the cluster will override these filters.
      
       If using upstream HTTP filters, please be aware that local errors sent by
       upstream HTTP filters will not trigger retries, and local errors sent by
       upstream HTTP filters will count as a final response if hedging is configured.
       [#extension-category: envoy.filters.http.upstream]
       
      repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter upstream_http_filters = 8;
    • getUpstreamHttpFiltersBuilderList

      public List<HttpFilter.Builder> getUpstreamHttpFiltersBuilderList()
       .. note::
       Upstream HTTP filters are currently in alpha.
      
       Optional HTTP filters for the upstream HTTP filter chain.
      
       These filters will be applied for all requests that pass through the router.
       They will also be applied to shadowed requests.
       Upstream HTTP filters cannot change route or cluster.
       Upstream HTTP filters specified on the cluster will override these filters.
      
       If using upstream HTTP filters, please be aware that local errors sent by
       upstream HTTP filters will not trigger retries, and local errors sent by
       upstream HTTP filters will count as a final response if hedging is configured.
       [#extension-category: envoy.filters.http.upstream]
       
      repeated .envoy.extensions.filters.network.http_connection_manager.v3.HttpFilter upstream_http_filters = 8;
    • internalGetUpstreamHttpFiltersFieldBuilder

      private com.google.protobuf.RepeatedFieldBuilder<HttpFilter,HttpFilter.Builder,HttpFilterOrBuilder> internalGetUpstreamHttpFiltersFieldBuilder()