Class Router.Builder
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 Summary
FieldsModifier and TypeFieldDescriptionprivate int
private com.google.protobuf.BoolValue
private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.BoolValue, com.google.protobuf.BoolValue.Builder, com.google.protobuf.BoolValueOrBuilder> private boolean
private boolean
private com.google.protobuf.LazyStringArrayList
private boolean
private boolean
private List
<HttpFilter> private com.google.protobuf.RepeatedFieldBuilder
<HttpFilter, HttpFilter.Builder, HttpFilterOrBuilder> private com.google.protobuf.RepeatedFieldBuilder
<AccessLog, AccessLog.Builder, AccessLogOrBuilder> private Router.UpstreamAccessLogOptions
private com.google.protobuf.SingleFieldBuilder
<Router.UpstreamAccessLogOptions, Router.UpstreamAccessLogOptions.Builder, Router.UpstreamAccessLogOptionsOrBuilder> -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionaddAllStrictCheckHeaders
(Iterable<String> values) Specifies a list of HTTP headers to strictly validate.addAllUpstreamHttpFilters
(Iterable<? extends HttpFilter> values) ..addAllUpstreamLog
(Iterable<? extends AccessLog> values) Configuration for HTTP upstream logs emitted by the router.addStrictCheckHeaders
(String value) Specifies a list of HTTP headers to strictly validate.addStrictCheckHeadersBytes
(com.google.protobuf.ByteString value) Specifies a list of HTTP headers to strictly validate.addUpstreamHttpFilters
(int index, HttpFilter value) ..addUpstreamHttpFilters
(int index, HttpFilter.Builder builderForValue) ..addUpstreamHttpFilters
(HttpFilter value) ..addUpstreamHttpFilters
(HttpFilter.Builder builderForValue) ....addUpstreamHttpFiltersBuilder
(int index) ..addUpstreamLog
(int index, AccessLog value) Configuration for HTTP upstream logs emitted by the router.addUpstreamLog
(int index, AccessLog.Builder builderForValue) Configuration for HTTP upstream logs emitted by the router.addUpstreamLog
(AccessLog value) Configuration for HTTP upstream logs emitted by the router.addUpstreamLog
(AccessLog.Builder builderForValue) Configuration for HTTP upstream logs emitted by the router.Configuration for HTTP upstream logs emitted by the router.addUpstreamLogBuilder
(int index) Configuration for HTTP upstream logs emitted by the router.build()
private void
buildPartial0
(Router result) private void
buildPartialRepeatedFields
(Router result) clear()
Whether the router generates dynamic cluster statistics.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.Deprecated.envoy.extensions.filters.http.router.v3.Router.start_child_span is deprecated.Specifies a list of HTTP headers to strictly validate.Do not add any additional ``x-envoy-`` headers to requests or responses.If set, Envoy will avoid incrementing HTTP failure code stats on gRPC requests...Configuration for HTTP upstream logs emitted by the router.Additional upstream access log options.private void
private void
private void
static final com.google.protobuf.Descriptors.Descriptor
com.google.protobuf.Descriptors.Descriptor
com.google.protobuf.BoolValue
Whether the router generates dynamic cluster statistics.com.google.protobuf.BoolValue.Builder
Whether the router generates dynamic cluster statistics.com.google.protobuf.BoolValueOrBuilder
Whether the router generates dynamic cluster statistics.boolean
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.boolean
Deprecated.envoy.extensions.filters.http.router.v3.Router.start_child_span is deprecated.getStrictCheckHeaders
(int index) Specifies a list of HTTP headers to strictly validate.com.google.protobuf.ByteString
getStrictCheckHeadersBytes
(int index) Specifies a list of HTTP headers to strictly validate.int
Specifies a list of HTTP headers to strictly validate.com.google.protobuf.ProtocolStringList
Specifies a list of HTTP headers to strictly validate.boolean
Do not add any additional ``x-envoy-`` headers to requests or responses.boolean
If set, Envoy will avoid incrementing HTTP failure code stats on gRPC requests.getUpstreamHttpFilters
(int index) ..getUpstreamHttpFiltersBuilder
(int index) ....int
....getUpstreamHttpFiltersOrBuilder
(int index) ..List
<? extends HttpFilterOrBuilder> ..getUpstreamLog
(int index) Configuration for HTTP upstream logs emitted by the router.getUpstreamLogBuilder
(int index) Configuration for HTTP upstream logs emitted by the router.Configuration for HTTP upstream logs emitted by the router.int
Configuration for HTTP upstream logs emitted by the router.Configuration for HTTP upstream logs emitted by the router.Additional upstream access log options.Additional upstream access log options.Additional upstream access log options.getUpstreamLogOrBuilder
(int index) Configuration for HTTP upstream logs emitted by the router.List
<? extends AccessLogOrBuilder> Configuration for HTTP upstream logs emitted by the router.boolean
Whether the router generates dynamic cluster statistics.boolean
Additional upstream access log options.private com.google.protobuf.SingleFieldBuilder
<com.google.protobuf.BoolValue, com.google.protobuf.BoolValue.Builder, com.google.protobuf.BoolValueOrBuilder> Whether the router generates dynamic cluster statistics.protected com.google.protobuf.GeneratedMessage.FieldAccessorTable
private com.google.protobuf.RepeatedFieldBuilder
<HttpFilter, HttpFilter.Builder, HttpFilterOrBuilder> private com.google.protobuf.RepeatedFieldBuilder
<AccessLog, AccessLog.Builder, AccessLogOrBuilder> private com.google.protobuf.SingleFieldBuilder
<Router.UpstreamAccessLogOptions, Router.UpstreamAccessLogOptions.Builder, Router.UpstreamAccessLogOptionsOrBuilder> Additional upstream access log options.final boolean
private void
mergeDynamicStats
(com.google.protobuf.BoolValue value) Whether the router generates dynamic cluster statistics.mergeFrom
(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) mergeFrom
(com.google.protobuf.Message other) Additional upstream access log options.removeUpstreamHttpFilters
(int index) ..removeUpstreamLog
(int index) Configuration for HTTP upstream logs emitted by the router.setDynamicStats
(com.google.protobuf.BoolValue value) Whether the router generates dynamic cluster statistics.setDynamicStats
(com.google.protobuf.BoolValue.Builder builderForValue) Whether the router generates dynamic cluster statistics.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.setStartChildSpan
(boolean value) Deprecated.envoy.extensions.filters.http.router.v3.Router.start_child_span is deprecated.setStrictCheckHeaders
(int index, String value) Specifies a list of HTTP headers to strictly validate.setSuppressEnvoyHeaders
(boolean value) Do not add any additional ``x-envoy-`` headers to requests or responses.setSuppressGrpcRequestFailureCodeStats
(boolean value) If set, Envoy will avoid incrementing HTTP failure code stats on gRPC requests.setUpstreamHttpFilters
(int index, HttpFilter value) ..setUpstreamHttpFilters
(int index, HttpFilter.Builder builderForValue) ..setUpstreamLog
(int index, AccessLog value) Configuration for HTTP upstream logs emitted by the router.setUpstreamLog
(int index, AccessLog.Builder builderForValue) Configuration for HTTP upstream logs emitted by the router.Additional upstream access log options.setUpstreamLogOptions
(Router.UpstreamAccessLogOptions.Builder builderForValue) Additional upstream access log options.Methods inherited from class com.google.protobuf.GeneratedMessage.Builder
addRepeatedField, clearField, clearOneof, clone, getAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, getUnknownFieldSetBuilder, hasField, hasOneof, internalGetMapField, internalGetMapFieldReflection, internalGetMutableMapField, internalGetMutableMapFieldReflection, isClean, markClean, mergeUnknownFields, mergeUnknownLengthDelimitedField, mergeUnknownVarintField, newBuilderForField, onBuilt, onChanged, parseUnknownField, setField, setRepeatedField, setUnknownFields, setUnknownFieldSetBuilder, setUnknownFieldsProto3
Methods inherited from class com.google.protobuf.AbstractMessage.Builder
findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toString
Methods inherited from class com.google.protobuf.AbstractMessageLite.Builder
addAll, addAll, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, newUninitializedMessageException
Methods inherited from class java.lang.Object
equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
Methods inherited from interface com.google.protobuf.Message.Builder
mergeDelimitedFrom, mergeDelimitedFrom
Methods inherited from interface com.google.protobuf.MessageLite.Builder
mergeFrom
Methods inherited from interface com.google.protobuf.MessageOrBuilder
findInitializationErrors, getAllFields, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
-
Field Details
-
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, dynamicStatsBuilder_com.google.protobuf.BoolValueOrBuilder> -
startChildSpan_
private boolean startChildSpan_ -
upstreamLog_
-
upstreamLogBuilder_
private com.google.protobuf.RepeatedFieldBuilder<AccessLog,AccessLog.Builder, upstreamLogBuilder_AccessLogOrBuilder> -
upstreamLogOptions_
-
upstreamLogOptionsBuilder_
private com.google.protobuf.SingleFieldBuilder<Router.UpstreamAccessLogOptions,Router.UpstreamAccessLogOptions.Builder, upstreamLogOptionsBuilder_Router.UpstreamAccessLogOptionsOrBuilder> -
suppressEnvoyHeaders_
private boolean suppressEnvoyHeaders_ -
strictCheckHeaders_
private com.google.protobuf.LazyStringArrayList strictCheckHeaders_ -
respectExpectedRqTimeout_
private boolean respectExpectedRqTimeout_ -
suppressGrpcRequestFailureCodeStats_
private boolean suppressGrpcRequestFailureCodeStats_ -
upstreamHttpFilters_
-
upstreamHttpFiltersBuilder_
private com.google.protobuf.RepeatedFieldBuilder<HttpFilter,HttpFilter.Builder, upstreamHttpFiltersBuilder_HttpFilterOrBuilder>
-
-
Constructor Details
-
Builder
private Builder() -
Builder
private Builder(com.google.protobuf.AbstractMessage.BuilderParent parent)
-
-
Method Details
-
getDescriptor
public static final com.google.protobuf.Descriptors.Descriptor getDescriptor() -
internalGetFieldAccessorTable
protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()- Specified by:
internalGetFieldAccessorTable
in classcom.google.protobuf.GeneratedMessage.Builder<Router.Builder>
-
maybeForceBuilderInitialization
private void maybeForceBuilderInitialization() -
clear
- Specified by:
clear
in interfacecom.google.protobuf.Message.Builder
- Specified by:
clear
in interfacecom.google.protobuf.MessageLite.Builder
- Overrides:
clear
in classcom.google.protobuf.GeneratedMessage.Builder<Router.Builder>
-
getDescriptorForType
public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()- Specified by:
getDescriptorForType
in interfacecom.google.protobuf.Message.Builder
- Specified by:
getDescriptorForType
in interfacecom.google.protobuf.MessageOrBuilder
- Overrides:
getDescriptorForType
in classcom.google.protobuf.GeneratedMessage.Builder<Router.Builder>
-
getDefaultInstanceForType
- Specified by:
getDefaultInstanceForType
in interfacecom.google.protobuf.MessageLiteOrBuilder
- Specified by:
getDefaultInstanceForType
in interfacecom.google.protobuf.MessageOrBuilder
-
build
- Specified by:
build
in interfacecom.google.protobuf.Message.Builder
- Specified by:
build
in interfacecom.google.protobuf.MessageLite.Builder
-
buildPartial
- Specified by:
buildPartial
in interfacecom.google.protobuf.Message.Builder
- Specified by:
buildPartial
in interfacecom.google.protobuf.MessageLite.Builder
-
buildPartialRepeatedFields
-
buildPartial0
-
mergeFrom
- Specified by:
mergeFrom
in interfacecom.google.protobuf.Message.Builder
- Overrides:
mergeFrom
in classcom.google.protobuf.AbstractMessage.Builder<Router.Builder>
-
mergeFrom
-
isInitialized
public final boolean isInitialized()- Specified by:
isInitialized
in interfacecom.google.protobuf.MessageLiteOrBuilder
- Overrides:
isInitialized
in classcom.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 interfacecom.google.protobuf.Message.Builder
- Specified by:
mergeFrom
in interfacecom.google.protobuf.MessageLite.Builder
- Overrides:
mergeFrom
in classcom.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 interfaceRouterOrBuilder
- 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 interfaceRouterOrBuilder
- Returns:
- The dynamicStats.
-
setDynamicStats
Whether the router generates dynamic cluster statistics. Defaults to true. Can be disabled in high performance scenarios.
.google.protobuf.BoolValue dynamic_stats = 1;
-
setDynamicStats
Whether the router generates dynamic cluster statistics. Defaults to true. Can be disabled in high performance scenarios.
.google.protobuf.BoolValue dynamic_stats = 1;
-
mergeDynamicStats
Whether the router generates dynamic cluster statistics. Defaults to true. Can be disabled in high performance scenarios.
.google.protobuf.BoolValue dynamic_stats = 1;
-
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 interfaceRouterOrBuilder
-
internalGetDynamicStatsFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder, internalGetDynamicStatsFieldBuilder()com.google.protobuf.BoolValueOrBuilder> 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.envoy.extensions.filters.http.router.v3.Router.start_child_span is deprecated. See envoy/extensions/filters/http/router/v3/router.proto;l=60Whether 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 interfaceRouterOrBuilder
- Returns:
- The startChildSpan.
-
setStartChildSpan
Deprecated.envoy.extensions.filters.http.router.v3.Router.start_child_span is deprecated. See envoy/extensions/filters/http/router/v3/router.proto;l=60Whether 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.envoy.extensions.filters.http.router.v3.Router.start_child_span is deprecated. See envoy/extensions/filters/http/router/v3/router.proto;l=60Whether 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
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 interfaceRouterOrBuilder
-
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 interfaceRouterOrBuilder
-
getUpstreamLog
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 interfaceRouterOrBuilder
-
setUpstreamLog
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
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
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
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
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
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
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
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
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
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
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 interfaceRouterOrBuilder
-
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 interfaceRouterOrBuilder
-
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
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
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, internalGetUpstreamLogFieldBuilder()AccessLogOrBuilder> -
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 interfaceRouterOrBuilder
- Returns:
- Whether the upstreamLogOptions field is set.
-
getUpstreamLogOptions
Additional upstream access log options.
.envoy.extensions.filters.http.router.v3.Router.UpstreamAccessLogOptions upstream_log_options = 9;
- Specified by:
getUpstreamLogOptions
in interfaceRouterOrBuilder
- Returns:
- The upstreamLogOptions.
-
setUpstreamLogOptions
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
Additional upstream access log options.
.envoy.extensions.filters.http.router.v3.Router.UpstreamAccessLogOptions upstream_log_options = 9;
-
clearUpstreamLogOptions
Additional upstream access log options.
.envoy.extensions.filters.http.router.v3.Router.UpstreamAccessLogOptions upstream_log_options = 9;
-
getUpstreamLogOptionsBuilder
Additional upstream access log options.
.envoy.extensions.filters.http.router.v3.Router.UpstreamAccessLogOptions upstream_log_options = 9;
-
getUpstreamLogOptionsOrBuilder
Additional upstream access log options.
.envoy.extensions.filters.http.router.v3.Router.UpstreamAccessLogOptions upstream_log_options = 9;
- Specified by:
getUpstreamLogOptionsOrBuilder
in interfaceRouterOrBuilder
-
internalGetUpstreamLogOptionsFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Router.UpstreamAccessLogOptions,Router.UpstreamAccessLogOptions.Builder, internalGetUpstreamLogOptionsFieldBuilder()Router.UpstreamAccessLogOptionsOrBuilder> 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 interfaceRouterOrBuilder
- Returns:
- The suppressEnvoyHeaders.
-
setSuppressEnvoyHeaders
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
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 interfaceRouterOrBuilder
- 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 interfaceRouterOrBuilder
- Returns:
- The count of strictCheckHeaders.
-
getStrictCheckHeaders
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 interfaceRouterOrBuilder
- 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 interfaceRouterOrBuilder
- Parameters:
index
- The index of the value to return.- Returns:
- The bytes of the strictCheckHeaders at the given index.
-
setStrictCheckHeaders
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
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
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
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
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 interfaceRouterOrBuilder
- Returns:
- The respectExpectedRqTimeout.
-
setRespectExpectedRqTimeout
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
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 interfaceRouterOrBuilder
- Returns:
- The suppressGrpcRequestFailureCodeStats.
-
setSuppressGrpcRequestFailureCodeStats
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
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
.. 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 interfaceRouterOrBuilder
-
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 interfaceRouterOrBuilder
-
getUpstreamHttpFilters
.. 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 interfaceRouterOrBuilder
-
setUpstreamHttpFilters
.. 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
.. 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
.. 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
.. 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
.. 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
.. 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
.. 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
.. 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
.. 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
.. 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
.. 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 interfaceRouterOrBuilder
-
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 interfaceRouterOrBuilder
-
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
.. 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
.. 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, internalGetUpstreamHttpFiltersFieldBuilder()HttpFilterOrBuilder>
-