http_connection_managerv3

type EnvoyMobileHttpConnectionManager struct {

	// The configuration for the underlying HttpConnectionManager which will be
	// instantiated for Envoy mobile.
	Config *HttpConnectionManager `protobuf:"bytes,1,opt,name=config,proto3" json:"config,omitempty"`
	// contains filtered or unexported fields
}

type EnvoyMobileHttpConnectionManagerMultiError []error

type EnvoyMobileHttpConnectionManagerValidationError struct {
	// contains filtered or unexported fields
}

type HttpConnectionManager struct {

	// Supplies the type of codec that the connection manager should use.
	CodecType HttpConnectionManager_CodecType `` /* 186-byte string literal not displayed */
	// The human readable prefix to use when emitting statistics for the
	// connection manager. See the :ref:`statistics documentation <config_http_conn_man_stats>` for
	// more information.
	StatPrefix string `protobuf:"bytes,2,opt,name=stat_prefix,json=statPrefix,proto3" json:"stat_prefix,omitempty"`
	// Types that are assignable to RouteSpecifier:
	//
	//	*HttpConnectionManager_Rds
	//	*HttpConnectionManager_RouteConfig
	//	*HttpConnectionManager_ScopedRoutes
	RouteSpecifier isHttpConnectionManager_RouteSpecifier `protobuf_oneof:"route_specifier"`
	// A list of individual HTTP filters that make up the filter chain for
	// requests made to the connection manager. :ref:`Order matters <arch_overview_http_filters_ordering>`
	// as the filters are processed sequentially as request events happen.
	HttpFilters []*HttpFilter `protobuf:"bytes,5,rep,name=http_filters,json=httpFilters,proto3" json:"http_filters,omitempty"`
	// Whether the connection manager manipulates the :ref:`config_http_conn_man_headers_user-agent`
	// and :ref:`config_http_conn_man_headers_downstream-service-cluster` headers. See the linked
	// documentation for more information. Defaults to false.
	AddUserAgent *wrappers.BoolValue `protobuf:"bytes,6,opt,name=add_user_agent,json=addUserAgent,proto3" json:"add_user_agent,omitempty"`
	// Presence of the object defines whether the connection manager
	// emits :ref:`tracing <arch_overview_tracing>` data to the :ref:`configured tracing provider
	// <envoy_v3_api_msg_config.trace.v3.Tracing>`.
	Tracing *HttpConnectionManager_Tracing `protobuf:"bytes,7,opt,name=tracing,proto3" json:"tracing,omitempty"`
	// Additional settings for HTTP requests handled by the connection manager. These will be
	// applicable to both HTTP1 and HTTP2 requests.
	CommonHttpProtocolOptions *v3.HttpProtocolOptions `` /* 141-byte string literal not displayed */
	// Additional HTTP/1 settings that are passed to the HTTP/1 codec.
	// [#comment:TODO: The following fields are ignored when the
	// :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>`
	// is present:
	// 1. :ref:`allow_chunked_length <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.allow_chunked_length>`]
	HttpProtocolOptions *v3.Http1ProtocolOptions `protobuf:"bytes,8,opt,name=http_protocol_options,json=httpProtocolOptions,proto3" json:"http_protocol_options,omitempty"`
	// Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.
	Http2ProtocolOptions *v3.Http2ProtocolOptions `protobuf:"bytes,9,opt,name=http2_protocol_options,json=http2ProtocolOptions,proto3" json:"http2_protocol_options,omitempty"`
	// Additional HTTP/3 settings that are passed directly to the HTTP/3 codec.
	// [#not-implemented-hide:]
	Http3ProtocolOptions *v3.Http3ProtocolOptions `protobuf:"bytes,44,opt,name=http3_protocol_options,json=http3ProtocolOptions,proto3" json:"http3_protocol_options,omitempty"`
	// An optional override that the connection manager will write to the server
	// header in responses. If not set, the default is “envoy“.
	ServerName string `protobuf:"bytes,10,opt,name=server_name,json=serverName,proto3" json:"server_name,omitempty"`
	// Defines the action to be applied to the Server header on the response path.
	// By default, Envoy will overwrite the header with the value specified in
	// server_name.
	ServerHeaderTransformation HttpConnectionManager_ServerHeaderTransformation `` /* 257-byte string literal not displayed */
	// Allows for explicit transformation of the :scheme header on the request path.
	// If not set, Envoy's default :ref:`scheme  <config_http_conn_man_headers_scheme>`
	// handling applies.
	SchemeHeaderTransformation *v3.SchemeHeaderTransformation `` /* 142-byte string literal not displayed */
	// The maximum request headers size for incoming connections.
	// If unconfigured, the default max request headers allowed is 60 KiB.
	// Requests that exceed this limit will receive a 431 response.
	MaxRequestHeadersKb *wrappers.UInt32Value `protobuf:"bytes,29,opt,name=max_request_headers_kb,json=maxRequestHeadersKb,proto3" json:"max_request_headers_kb,omitempty"`
	// The stream idle timeout for connections managed by the connection manager.
	// If not specified, this defaults to 5 minutes. The default value was selected
	// so as not to interfere with any smaller configured timeouts that may have
	// existed in configurations prior to the introduction of this feature, while
	// introducing robustness to TCP connections that terminate without a FIN.
	//
	// This idle timeout applies to new streams and is overridable by the
	// :ref:`route-level idle_timeout
	// <envoy_v3_api_field_config.route.v3.RouteAction.idle_timeout>`. Even on a stream in
	// which the override applies, prior to receipt of the initial request
	// headers, the :ref:`stream_idle_timeout
	// <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_idle_timeout>`
	// applies. Each time an encode/decode event for headers or data is processed
	// for the stream, the timer will be reset. If the timeout fires, the stream
	// is terminated with a 408 Request Timeout error code if no upstream response
	// header has been received, otherwise a stream reset occurs.
	//
	// This timeout also specifies the amount of time that Envoy will wait for the peer to open enough
	// window to write any remaining stream data once the entirety of stream data (local end stream is
	// true) has been buffered pending available window. In other words, this timeout defends against
	// a peer that does not release enough window to completely write the stream, even though all
	// data has been proxied within available flow control windows. If the timeout is hit in this
	// case, the :ref:`tx_flush_timeout <config_http_conn_man_stats_per_codec>` counter will be
	// incremented. Note that :ref:`max_stream_duration
	// <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_stream_duration>` does not apply to
	// this corner case.
	//
	// If the :ref:`overload action <config_overload_manager_overload_actions>` "envoy.overload_actions.reduce_timeouts"
	// is configured, this timeout is scaled according to the value for
	// :ref:`HTTP_DOWNSTREAM_STREAM_IDLE <envoy_v3_api_enum_value_config.overload.v3.ScaleTimersOverloadActionConfig.TimerType.HTTP_DOWNSTREAM_STREAM_IDLE>`.
	//
	// Note that it is possible to idle timeout even if the wire traffic for a stream is non-idle, due
	// to the granularity of events presented to the connection manager. For example, while receiving
	// very large request headers, it may be the case that there is traffic regularly arriving on the
	// wire while the connection manage is only able to observe the end-of-headers event, hence the
	// stream may still idle timeout.
	//
	// A value of 0 will completely disable the connection manager stream idle
	// timeout, although per-route idle timeout overrides will continue to apply.
	StreamIdleTimeout *duration.Duration `protobuf:"bytes,24,opt,name=stream_idle_timeout,json=streamIdleTimeout,proto3" json:"stream_idle_timeout,omitempty"`
	// The amount of time that Envoy will wait for the entire request to be received.
	// The timer is activated when the request is initiated, and is disarmed when the last byte of the
	// request is sent upstream (i.e. all decoding filters have processed the request), OR when the
	// response is initiated. If not specified or set to 0, this timeout is disabled.
	RequestTimeout *duration.Duration `protobuf:"bytes,28,opt,name=request_timeout,json=requestTimeout,proto3" json:"request_timeout,omitempty"`
	// The amount of time that Envoy will wait for the request headers to be received. The timer is
	// activated when the first byte of the headers is received, and is disarmed when the last byte of
	// the headers has been received. If not specified or set to 0, this timeout is disabled.
	RequestHeadersTimeout *duration.Duration `` /* 127-byte string literal not displayed */
	// The time that Envoy will wait between sending an HTTP/2 “shutdown
	// notification” (GOAWAY frame with max stream ID) and a final GOAWAY frame.
	// This is used so that Envoy provides a grace period for new streams that
	// race with the final GOAWAY frame. During this grace period, Envoy will
	// continue to accept new streams. After the grace period, a final GOAWAY
	// frame is sent and Envoy will start refusing new streams. Draining occurs
	// both when a connection hits the idle timeout or during general server
	// draining. The default grace period is 5000 milliseconds (5 seconds) if this
	// option is not specified.
	DrainTimeout *duration.Duration `protobuf:"bytes,12,opt,name=drain_timeout,json=drainTimeout,proto3" json:"drain_timeout,omitempty"`
	// The delayed close timeout is for downstream connections managed by the HTTP connection manager.
	// It is defined as a grace period after connection close processing has been locally initiated
	// during which Envoy will wait for the peer to close (i.e., a TCP FIN/RST is received by Envoy
	// from the downstream connection) prior to Envoy closing the socket associated with that
	// connection.
	// NOTE: This timeout is enforced even when the socket associated with the downstream connection
	// is pending a flush of the write buffer. However, any progress made writing data to the socket
	// will restart the timer associated with this timeout. This means that the total grace period for
	// a socket in this state will be
	// <total_time_waiting_for_write_buffer_flushes>+<delayed_close_timeout>.
	//
	// Delaying Envoy's connection close and giving the peer the opportunity to initiate the close
	// sequence mitigates a race condition that exists when downstream clients do not drain/process
	// data in a connection's receive buffer after a remote close has been detected via a socket
	// write(). This race leads to such clients failing to process the response code sent by Envoy,
	// which could result in erroneous downstream processing.
	//
	// If the timeout triggers, Envoy will close the connection's socket.
	//
	// The default timeout is 1000 ms if this option is not specified.
	//
	// .. NOTE::
	//
	//	To be useful in avoiding the race condition described above, this timeout must be set
	//	to *at least* <max round trip time expected between clients and Envoy>+<100ms to account for
	//	a reasonable "worst" case processing time for a full iteration of Envoy's event loop>.
	//
	// .. WARNING::
	//
	//	A value of 0 will completely disable delayed close processing. When disabled, the downstream
	//	connection's socket will be closed immediately after the write flush is completed or will
	//	never close if the write flush does not complete.
	DelayedCloseTimeout *duration.Duration `protobuf:"bytes,26,opt,name=delayed_close_timeout,json=delayedCloseTimeout,proto3" json:"delayed_close_timeout,omitempty"`
	// Configuration for :ref:`HTTP access logs <arch_overview_access_logs>`
	// emitted by the connection manager.
	AccessLog []*v31.AccessLog `protobuf:"bytes,13,rep,name=access_log,json=accessLog,proto3" json:"access_log,omitempty"`
	// .. attention::
	// This field is deprecated in favor of
	// :ref:`access_log_flush_interval
	// <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>`.
	// Note that if both this field and :ref:`access_log_flush_interval
	// <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.access_log_flush_interval>`
	// are specified, the former (deprecated field) is ignored.
	//
	// Deprecated: Marked as deprecated in envoy/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto.
	AccessLogFlushInterval *duration.Duration `` /* 132-byte string literal not displayed */
	// .. attention::
	// This field is deprecated in favor of
	// :ref:`flush_access_log_on_new_request
	// <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.flush_access_log_on_new_request>`.
	// Note that if both this field and :ref:`flush_access_log_on_new_request
	// <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.HcmAccessLogOptions.flush_access_log_on_new_request>`
	// are specified, the former (deprecated field) is ignored.
	//
	// Deprecated: Marked as deprecated in envoy/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto.
	FlushAccessLogOnNewRequest bool `` /* 149-byte string literal not displayed */
	// Additional access log options for HTTP connection manager.
	AccessLogOptions *HttpConnectionManager_HcmAccessLogOptions `protobuf:"bytes,56,opt,name=access_log_options,json=accessLogOptions,proto3" json:"access_log_options,omitempty"`
	// If set to true, the connection manager will use the real remote address
	// of the client connection when determining internal versus external origin and manipulating
	// various headers. If set to false or absent, the connection manager will use the
	// :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header. See the documentation for
	// :ref:`config_http_conn_man_headers_x-forwarded-for`,
	// :ref:`config_http_conn_man_headers_x-envoy-internal`, and
	// :ref:`config_http_conn_man_headers_x-envoy-external-address` for more information.
	UseRemoteAddress *wrappers.BoolValue `protobuf:"bytes,14,opt,name=use_remote_address,json=useRemoteAddress,proto3" json:"use_remote_address,omitempty"`
	// The number of additional ingress proxy hops from the right side of the
	// :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header to trust when
	// determining the origin client's IP address. The default is zero if this option
	// is not specified. See the documentation for
	// :ref:`config_http_conn_man_headers_x-forwarded-for` for more information.
	XffNumTrustedHops uint32 `protobuf:"varint,19,opt,name=xff_num_trusted_hops,json=xffNumTrustedHops,proto3" json:"xff_num_trusted_hops,omitempty"`
	// The configuration for the original IP detection extensions.
	//
	// When configured the extensions will be called along with the request headers
	// and information about the downstream connection, such as the directly connected address.
	// Each extension will then use these parameters to decide the request's effective remote address.
	// If an extension fails to detect the original IP address and isn't configured to reject
	// the request, the HCM will try the remaining extensions until one succeeds or rejects
	// the request. If the request isn't rejected nor any extension succeeds, the HCM will
	// fallback to using the remote address.
	//
	// .. WARNING::
	//
	//	Extensions cannot be used in conjunction with :ref:`use_remote_address
	//	<envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>`
	//	nor :ref:`xff_num_trusted_hops
	//	<envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.xff_num_trusted_hops>`.
	//
	// [#extension-category: envoy.http.original_ip_detection]
	OriginalIpDetectionExtensions []*v3.TypedExtensionConfig `` /* 153-byte string literal not displayed */
	// The configuration for the early header mutation extensions.
	//
	// When configured the extensions will be called before any routing, tracing, or any filter processing.
	// Each extension will be applied in the order they are configured.
	// If the same header is mutated by multiple extensions, then the last extension will win.
	//
	// [#extension-category: envoy.http.early_header_mutation]
	EarlyHeaderMutationExtensions []*v3.TypedExtensionConfig `` /* 153-byte string literal not displayed */
	// Configures what network addresses are considered internal for stats and header sanitation
	// purposes. If unspecified, only RFC1918 IP addresses will be considered internal.
	// See the documentation for :ref:`config_http_conn_man_headers_x-envoy-internal` for more
	// information about internal/external addresses.
	InternalAddressConfig *HttpConnectionManager_InternalAddressConfig `` /* 127-byte string literal not displayed */
	// If set, Envoy will not append the remote address to the
	// :ref:`config_http_conn_man_headers_x-forwarded-for` HTTP header. This may be used in
	// conjunction with HTTP filters that explicitly manipulate XFF after the HTTP connection manager
	// has mutated the request headers. While :ref:`use_remote_address
	// <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>`
	// will also suppress XFF addition, it has consequences for logging and other
	// Envoy uses of the remote address, so “skip_xff_append“ should be used
	// when only an elision of XFF addition is intended.
	SkipXffAppend bool `protobuf:"varint,21,opt,name=skip_xff_append,json=skipXffAppend,proto3" json:"skip_xff_append,omitempty"`
	// Via header value to append to request and response headers. If this is
	// empty, no via header will be appended.
	Via string `protobuf:"bytes,22,opt,name=via,proto3" json:"via,omitempty"`
	// Whether the connection manager will generate the :ref:`x-request-id
	// <config_http_conn_man_headers_x-request-id>` header if it does not exist. This defaults to
	// true. Generating a random UUID4 is expensive so in high throughput scenarios where this feature
	// is not desired it can be disabled.
	GenerateRequestId *wrappers.BoolValue `protobuf:"bytes,15,opt,name=generate_request_id,json=generateRequestId,proto3" json:"generate_request_id,omitempty"`
	// Whether the connection manager will keep the :ref:`x-request-id
	// <config_http_conn_man_headers_x-request-id>` header if passed for a request that is edge
	// (Edge request is the request from external clients to front Envoy) and not reset it, which
	// is the current Envoy behaviour. This defaults to false.
	PreserveExternalRequestId bool `` /* 142-byte string literal not displayed */
	// If set, Envoy will always set :ref:`x-request-id <config_http_conn_man_headers_x-request-id>` header in response.
	// If this is false or not set, the request ID is returned in responses only if tracing is forced using
	// :ref:`x-envoy-force-trace <config_http_conn_man_headers_x-envoy-force-trace>` header.
	AlwaysSetRequestIdInResponse bool `` /* 155-byte string literal not displayed */
	// How to handle the :ref:`config_http_conn_man_headers_x-forwarded-client-cert` (XFCC) HTTP
	// header.
	ForwardClientCertDetails HttpConnectionManager_ForwardClientCertDetails `` /* 251-byte string literal not displayed */
	// This field is valid only when :ref:`forward_client_cert_details
	// <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.forward_client_cert_details>`
	// is APPEND_FORWARD or SANITIZE_SET and the client connection is mTLS. It specifies the fields in
	// the client certificate to be forwarded. Note that in the
	// :ref:`config_http_conn_man_headers_x-forwarded-client-cert` header, “Hash“ is always set, and
	// “By“ is always set when the client certificate presents the URI type Subject Alternative Name
	// value.
	SetCurrentClientCertDetails *HttpConnectionManager_SetCurrentClientCertDetails `` /* 149-byte string literal not displayed */
	// If proxy_100_continue is true, Envoy will proxy incoming "Expect:
	// 100-continue" headers upstream, and forward "100 Continue" responses
	// downstream. If this is false or not set, Envoy will instead strip the
	// "Expect: 100-continue" header, and send a "100 Continue" response itself.
	Proxy_100Continue bool `protobuf:"varint,18,opt,name=proxy_100_continue,json=proxy100Continue,proto3" json:"proxy_100_continue,omitempty"`
	// If
	// :ref:`use_remote_address
	// <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.use_remote_address>`
	// is true and represent_ipv4_remote_address_as_ipv4_mapped_ipv6 is true and the remote address is
	// an IPv4 address, the address will be mapped to IPv6 before it is appended to “x-forwarded-for“.
	// This is useful for testing compatibility of upstream services that parse the header value. For
	// example, 50.0.0.1 is represented as ::FFFF:50.0.0.1. See `IPv4-Mapped IPv6 Addresses
	// <https://tools.ietf.org/html/rfc4291#section-2.5.5.2>`_ for details. This will also affect the
	// :ref:`config_http_conn_man_headers_x-envoy-external-address` header. See
	// :ref:`http_connection_manager.represent_ipv4_remote_address_as_ipv4_mapped_ipv6
	// <config_http_conn_man_runtime_represent_ipv4_remote_address_as_ipv4_mapped_ipv6>` for runtime
	// control.
	// [#not-implemented-hide:]
	RepresentIpv4RemoteAddressAsIpv4MappedIpv6 bool                                   `` /* 201-byte string literal not displayed */
	UpgradeConfigs                             []*HttpConnectionManager_UpgradeConfig `protobuf:"bytes,23,rep,name=upgrade_configs,json=upgradeConfigs,proto3" json:"upgrade_configs,omitempty"`
	// Should paths be normalized according to RFC 3986 before any processing of
	// requests by HTTP filters or routing? This affects the upstream “:path“ header
	// as well. For paths that fail this check, Envoy will respond with 400 to
	// paths that are malformed. This defaults to false currently but will default
	// true in the future. When not specified, this value may be overridden by the
	// runtime variable
	// :ref:`http_connection_manager.normalize_path<config_http_conn_man_runtime_normalize_path>`.
	// See `Normalization and Comparison <https://tools.ietf.org/html/rfc3986#section-6>`_
	// for details of normalization.
	// Note that Envoy does not perform
	// `case normalization <https://tools.ietf.org/html/rfc3986#section-6.2.2.1>`_
	// [#comment:TODO: This field is ignored when the
	// :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>`
	// is present.]
	NormalizePath *wrappers.BoolValue `protobuf:"bytes,30,opt,name=normalize_path,json=normalizePath,proto3" json:"normalize_path,omitempty"`
	// Determines if adjacent slashes in the path are merged into one before any processing of
	// requests by HTTP filters or routing. This affects the upstream “:path“ header as well. Without
	// setting this option, incoming requests with path “//dir///file“ will not match against route
	// with “prefix“ match set to “/dir“. Defaults to “false“. Note that slash merging is not part of
	// `HTTP spec <https://tools.ietf.org/html/rfc3986>`_ and is provided for convenience.
	// [#comment:TODO: This field is ignored when the
	// :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>`
	// is present.]
	MergeSlashes bool `protobuf:"varint,33,opt,name=merge_slashes,json=mergeSlashes,proto3" json:"merge_slashes,omitempty"`
	// Action to take when request URL path contains escaped slash sequences (%2F, %2f, %5C and %5c).
	// The default value can be overridden by the :ref:`http_connection_manager.path_with_escaped_slashes_action<config_http_conn_man_runtime_path_with_escaped_slashes_action>`
	// runtime variable.
	// The :ref:`http_connection_manager.path_with_escaped_slashes_action_sampling<config_http_conn_man_runtime_path_with_escaped_slashes_action_enabled>` runtime
	// variable can be used to apply the action to a portion of all requests.
	// [#comment:TODO: This field is ignored when the
	// :ref:`header validation configuration <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.typed_header_validation_config>`
	// is present.]
	PathWithEscapedSlashesAction HttpConnectionManager_PathWithEscapedSlashesAction `` /* 269-byte string literal not displayed */
	// The configuration of the request ID extension. This includes operations such as
	// generation, validation, and associated tracing operations. If empty, the
	// :ref:`UuidRequestIdConfig <envoy_v3_api_msg_extensions.request_id.uuid.v3.UuidRequestIdConfig>`
	// default extension is used with default parameters. See the documentation for that extension
	// for details on what it does. Customizing the configuration for the default extension can be
	// achieved by configuring it explicitly here. For example, to disable trace reason packing,
	// the following configuration can be used:
	//
	// .. validated-code-block:: yaml
	//
	//	:type-name: envoy.extensions.filters.network.http_connection_manager.v3.RequestIDExtension
	//
	//	typed_config:
	//	  "@type": type.googleapis.com/envoy.extensions.request_id.uuid.v3.UuidRequestIdConfig
	//	  pack_trace_reason: false
	//
	// [#extension-category: envoy.request_id]
	RequestIdExtension *RequestIDExtension `protobuf:"bytes,36,opt,name=request_id_extension,json=requestIdExtension,proto3" json:"request_id_extension,omitempty"`
	// The configuration to customize local reply returned by Envoy. It can customize status code,
	// body text and response content type. If not specified, status code and text body are hard
	// coded in Envoy, the response content type is plain text.
	LocalReplyConfig *LocalReplyConfig `protobuf:"bytes,38,opt,name=local_reply_config,json=localReplyConfig,proto3" json:"local_reply_config,omitempty"`
	// Determines if the port part should be removed from host/authority header before any processing
	// of request by HTTP filters or routing. The port would be removed only if it is equal to the :ref:`listener's<envoy_v3_api_field_config.listener.v3.Listener.address>`
	// local port. This affects the upstream host header unless the method is
	// CONNECT in which case if no filter adds a port the original port will be restored before headers are
	// sent upstream.
	// Without setting this option, incoming requests with host “example:443“ will not match against
	// route with :ref:`domains<envoy_v3_api_field_config.route.v3.VirtualHost.domains>` match set to “example“. Defaults to “false“. Note that port removal is not part
	// of `HTTP spec <https://tools.ietf.org/html/rfc3986>`_ and is provided for convenience.
	// Only one of “strip_matching_host_port“ or “strip_any_host_port“ can be set.
	StripMatchingHostPort bool `` /* 130-byte string literal not displayed */
	// Types that are assignable to StripPortMode:
	//
	//	*HttpConnectionManager_StripAnyHostPort
	StripPortMode isHttpConnectionManager_StripPortMode `protobuf_oneof:"strip_port_mode"`
	// Governs Envoy's behavior when receiving invalid HTTP from downstream.
	// If this option is false (default), Envoy will err on the conservative side handling HTTP
	// errors, terminating both HTTP/1.1 and HTTP/2 connections when receiving an invalid request.
	// If this option is set to true, Envoy will be more permissive, only resetting the invalid
	// stream in the case of HTTP/2 and leaving the connection open where possible (if the entire
	// request is read for HTTP/1.1)
	// In general this should be true for deployments receiving trusted traffic (L2 Envoys,
	// company-internal mesh) and false when receiving untrusted traffic (edge deployments).
	//
	// If different behaviors for invalid_http_message for HTTP/1 and HTTP/2 are
	// desired, one should use the new HTTP/1 option :ref:`override_stream_error_on_invalid_http_message
	// <envoy_v3_api_field_config.core.v3.Http1ProtocolOptions.override_stream_error_on_invalid_http_message>` or the new HTTP/2 option
	// :ref:`override_stream_error_on_invalid_http_message
	// <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.override_stream_error_on_invalid_http_message>`
	// “not“ the deprecated but similarly named :ref:`stream_error_on_invalid_http_messaging
	// <envoy_v3_api_field_config.core.v3.Http2ProtocolOptions.stream_error_on_invalid_http_messaging>`
	StreamErrorOnInvalidHttpMessage *wrappers.BoolValue `` /* 163-byte string literal not displayed */
	// [#not-implemented-hide:] Path normalization configuration. This includes
	// configurations for transformations (e.g. RFC 3986 normalization or merge
	// adjacent slashes) and the policy to apply them. The policy determines
	// whether transformations affect the forwarded “:path“ header. RFC 3986 path
	// normalization is enabled by default and the default policy is that the
	// normalized header will be forwarded. See :ref:`PathNormalizationOptions
	// <envoy_v3_api_msg_extensions.filters.network.http_connection_manager.v3.PathNormalizationOptions>`
	// for details.
	PathNormalizationOptions *HttpConnectionManager_PathNormalizationOptions `` /* 136-byte string literal not displayed */
	// Determines if trailing dot of the host should be removed from host/authority header before any
	// processing of request by HTTP filters or routing.
	// This affects the upstream host header.
	// Without setting this option, incoming requests with host “example.com.“ will not match against
	// route with :ref:`domains<envoy_v3_api_field_config.route.v3.VirtualHost.domains>` match set to “example.com“. Defaults to “false“.
	// When the incoming request contains a host/authority header that includes a port number,
	// setting this option will strip a trailing dot, if present, from the host section,
	// leaving the port as is (e.g. host value “example.com.:443“ will be updated to “example.com:443“).
	StripTrailingHostDot bool `` /* 127-byte string literal not displayed */
	// Proxy-Status HTTP response header configuration.
	// If this config is set, the Proxy-Status HTTP response header field is
	// populated. By default, it is not.
	ProxyStatusConfig *HttpConnectionManager_ProxyStatusConfig `protobuf:"bytes,49,opt,name=proxy_status_config,json=proxyStatusConfig,proto3" json:"proxy_status_config,omitempty"`
	// Configuration options for Header Validation (UHV).
	// UHV is an extensible mechanism for checking validity of HTTP requests as well as providing
	// normalization for request attributes, such as URI path.
	// If the typed_header_validation_config is present it overrides the following options:
	// “normalize_path“, “merge_slashes“, “path_with_escaped_slashes_action“
	// “http_protocol_options.allow_chunked_length“, “common_http_protocol_options.headers_with_underscores_action“.
	//
	// The default UHV checks the following:
	//
	// #. HTTP/1 header map validity according to `RFC 7230 section 3.2<https://datatracker.ietf.org/doc/html/rfc7230#section-3.2>`_
	// #. Syntax of HTTP/1 request target URI and response status
	// #. HTTP/2 header map validity according to `RFC 7540 section 8.1.2<https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2`_
	// #. Syntax of HTTP/2 pseudo headers
	// #. HTTP/3 header map validity according to `RFC 9114 section 4.3 <https://www.rfc-editor.org/rfc/rfc9114.html>`_
	// #. Syntax of HTTP/3 pseudo headers
	// #. Syntax of “Content-Length“ and “Transfer-Encoding“
	// #. Validation of HTTP/1 requests with both “Content-Length“ and “Transfer-Encoding“ headers
	// #. Normalization of the URI path according to `Normalization and Comparison <https://datatracker.ietf.org/doc/html/rfc3986#section-6>`_
	//
	//	without `case normalization <https://datatracker.ietf.org/doc/html/rfc3986#section-6.2.2.1>`_
	//
	// [#not-implemented-hide:]
	// [#extension-category: envoy.http.header_validators]
	TypedHeaderValidationConfig *v3.TypedExtensionConfig `` /* 147-byte string literal not displayed */
	// Append the “x-forwarded-port“ header with the port value client used to connect to Envoy. It
	// will be ignored if the “x-forwarded-port“ header has been set by any trusted proxy in front of Envoy.
	AppendXForwardedPort bool `` /* 127-byte string literal not displayed */
	// Whether the HCM will add ProxyProtocolFilterState to the Connection lifetime filter state. Defaults to “true“.
	// This should be set to “false“ in cases where Envoy's view of the downstream address may not correspond to the
	// actual client address, for example, if there's another proxy in front of the Envoy.
	AddProxyProtocolConnectionState *wrappers.BoolValue `` /* 161-byte string literal not displayed */
	// contains filtered or unexported fields
}

type HttpConnectionManagerMultiError []error

type HttpConnectionManagerValidationError struct {
	// contains filtered or unexported fields
}

type HttpConnectionManager_CodecType int32

type HttpConnectionManager_ForwardClientCertDetails int32

type HttpConnectionManager_HcmAccessLogOptions struct {

	// The interval to flush the above access logs. By default, the HCM will flush exactly one access log
	// on stream close, when the HTTP request is complete. If this field is set, the HCM will flush access
	// logs periodically at the specified interval. This is especially useful in the case of long-lived
	// requests, such as CONNECT and Websockets. Final access logs can be detected via the
	// “requestComplete()“ method of “StreamInfo“ in access log filters, or through the “%DURATION%“ substitution
	// string.
	// The interval must be at least 1 millisecond.
	AccessLogFlushInterval *duration.Duration `` /* 131-byte string literal not displayed */
	// If set to true, HCM will flush an access log when a new HTTP request is received, after request
	// headers have been evaluated, before iterating through the HTTP filter chain.
	// This log record, if enabled, does not depend on periodic log records or request completion log.
	// Details related to upstream cluster, such as upstream host, will not be available for this log.
	FlushAccessLogOnNewRequest bool `` /* 148-byte string literal not displayed */
	// If true, the HCM will flush an access log when a tunnel is successfully established. For example,
	// this could be when an upstream has successfully returned 101 Switching Protocols, or when the proxy
	// has returned 200 to a CONNECT request.
	FlushLogOnTunnelSuccessfullyEstablished bool `` /* 187-byte string literal not displayed */
	// contains filtered or unexported fields
}

type HttpConnectionManager_HcmAccessLogOptionsMultiError []error

type HttpConnectionManager_HcmAccessLogOptionsValidationError struct {
	// contains filtered or unexported fields
}

type HttpConnectionManager_InternalAddressConfig struct {

	// Whether unix socket addresses should be considered internal.
	UnixSockets bool `protobuf:"varint,1,opt,name=unix_sockets,json=unixSockets,proto3" json:"unix_sockets,omitempty"`
	// List of CIDR ranges that are treated as internal. If unset, then RFC1918 / RFC4193
	// IP addresses will be considered internal.
	CidrRanges []*v3.CidrRange `protobuf:"bytes,2,rep,name=cidr_ranges,json=cidrRanges,proto3" json:"cidr_ranges,omitempty"`
	// contains filtered or unexported fields
}

type HttpConnectionManager_InternalAddressConfigMultiError []error

type HttpConnectionManager_InternalAddressConfigValidationError struct {
	// contains filtered or unexported fields
}

type HttpConnectionManager_PathNormalizationOptions struct {

	// [#not-implemented-hide:] Normalization applies internally before any processing of requests by
	// HTTP filters, routing, and matching *and* will affect the forwarded “:path“ header. Defaults
	// to :ref:`NormalizePathRFC3986
	// <envoy_v3_api_msg_type.http.v3.PathTransformation.Operation.NormalizePathRFC3986>`. When not
	// specified, this value may be overridden by the runtime variable
	// :ref:`http_connection_manager.normalize_path<config_http_conn_man_runtime_normalize_path>`.
	// Envoy will respond with 400 to paths that are malformed (e.g. for paths that fail RFC 3986
	// normalization due to disallowed characters.)
	ForwardingTransformation *v36.PathTransformation `` /* 133-byte string literal not displayed */
	// [#not-implemented-hide:] Normalization only applies internally before any processing of
	// requests by HTTP filters, routing, and matching. These will be applied after full
	// transformation is applied. The “:path“ header before this transformation will be restored in
	// the router filter and sent upstream unless it was mutated by a filter. Defaults to no
	// transformations.
	// Multiple actions can be applied in the same Transformation, forming a sequential
	// pipeline. The transformations will be performed in the order that they appear. Envoy will
	// respond with 400 to paths that are malformed (e.g. for paths that fail RFC 3986
	// normalization due to disallowed characters.)
	HttpFilterTransformation *v36.PathTransformation `` /* 135-byte string literal not displayed */
	// contains filtered or unexported fields
}

type HttpConnectionManager_PathNormalizationOptionsMultiError []error

type HttpConnectionManager_PathNormalizationOptionsValidationError struct {
	// contains filtered or unexported fields
}

type HttpConnectionManager_PathWithEscapedSlashesAction int32

type HttpConnectionManager_ProxyStatusConfig struct {

	// If true, the details field of the Proxy-Status header is not populated with stream_info.response_code_details.
	// This value defaults to “false“, i.e. the “details“ field is populated by default.
	RemoveDetails bool `protobuf:"varint,1,opt,name=remove_details,json=removeDetails,proto3" json:"remove_details,omitempty"`
	// If true, the details field of the Proxy-Status header will not contain
	// connection termination details. This value defaults to “false“, i.e. the
	// “details“ field will contain connection termination details by default.
	RemoveConnectionTerminationDetails bool `` /* 168-byte string literal not displayed */
	// If true, the details field of the Proxy-Status header will not contain an
	// enumeration of the Envoy ResponseFlags. This value defaults to “false“,
	// i.e. the “details“ field will contain a list of ResponseFlags by default.
	RemoveResponseFlags bool `protobuf:"varint,3,opt,name=remove_response_flags,json=removeResponseFlags,proto3" json:"remove_response_flags,omitempty"`
	// If true, overwrites the existing Status header with the response code
	// recommended by the Proxy-Status spec.
	// This value defaults to “false“, i.e. the HTTP response code is not
	// overwritten.
	SetRecommendedResponseCode bool `` /* 144-byte string literal not displayed */
	// The name of the proxy as it appears at the start of the Proxy-Status
	// header.
	//
	// If neither of these values are set, this value defaults to “server_name“,
	// which itself defaults to "envoy".
	//
	// Types that are assignable to ProxyName:
	//
	//	*HttpConnectionManager_ProxyStatusConfig_UseNodeId
	//	*HttpConnectionManager_ProxyStatusConfig_LiteralProxyName
	ProxyName isHttpConnectionManager_ProxyStatusConfig_ProxyName `protobuf_oneof:"proxy_name"`
	// contains filtered or unexported fields
}

type HttpConnectionManager_ProxyStatusConfigMultiError []error

type HttpConnectionManager_ProxyStatusConfigValidationError struct {
	// contains filtered or unexported fields
}

type HttpConnectionManager_ProxyStatusConfig_LiteralProxyName struct {
	// If “literal_proxy_name“ is set, Proxy-Status headers will use this
	// value as the name of the proxy.
	LiteralProxyName string `protobuf:"bytes,6,opt,name=literal_proxy_name,json=literalProxyName,proto3,oneof"`
}

type HttpConnectionManager_ProxyStatusConfig_UseNodeId struct {
	// If “use_node_id“ is set, Proxy-Status headers will use the Envoy's node
	// ID as the name of the proxy.
	UseNodeId bool `protobuf:"varint,5,opt,name=use_node_id,json=useNodeId,proto3,oneof"`
}

type HttpConnectionManager_Rds struct {
	// The connection manager’s route table will be dynamically loaded via the RDS API.
	Rds *Rds `protobuf:"bytes,3,opt,name=rds,proto3,oneof"`
}

type HttpConnectionManager_RouteConfig struct {
	// The route table for the connection manager is static and is specified in this property.
	RouteConfig *v32.RouteConfiguration `protobuf:"bytes,4,opt,name=route_config,json=routeConfig,proto3,oneof"`
}

type HttpConnectionManager_ScopedRoutes struct {
	// A route table will be dynamically assigned to each request based on request attributes
	// (e.g., the value of a header). The "routing scopes" (i.e., route tables) and "scope keys" are
	// specified in this message.
	ScopedRoutes *ScopedRoutes `protobuf:"bytes,31,opt,name=scoped_routes,json=scopedRoutes,proto3,oneof"`
}

type HttpConnectionManager_ServerHeaderTransformation int32

type HttpConnectionManager_SetCurrentClientCertDetails struct {

	// Whether to forward the subject of the client cert. Defaults to false.
	Subject *wrappers.BoolValue `protobuf:"bytes,1,opt,name=subject,proto3" json:"subject,omitempty"`
	// Whether to forward the entire client cert in URL encoded PEM format. This will appear in the
	// XFCC header comma separated from other values with the value Cert="PEM".
	// Defaults to false.
	Cert bool `protobuf:"varint,3,opt,name=cert,proto3" json:"cert,omitempty"`
	// Whether to forward the entire client cert chain (including the leaf cert) in URL encoded PEM
	// format. This will appear in the XFCC header comma separated from other values with the value
	// Chain="PEM".
	// Defaults to false.
	Chain bool `protobuf:"varint,6,opt,name=chain,proto3" json:"chain,omitempty"`
	// Whether to forward the DNS type Subject Alternative Names of the client cert.
	// Defaults to false.
	Dns bool `protobuf:"varint,4,opt,name=dns,proto3" json:"dns,omitempty"`
	// Whether to forward the URI type Subject Alternative Name of the client cert. Defaults to
	// false.
	Uri bool `protobuf:"varint,5,opt,name=uri,proto3" json:"uri,omitempty"`
	// contains filtered or unexported fields
}

type HttpConnectionManager_SetCurrentClientCertDetailsMultiError []error

type HttpConnectionManager_SetCurrentClientCertDetailsValidationError struct {
	// contains filtered or unexported fields
}

type HttpConnectionManager_StripAnyHostPort struct {
	// Determines if the port part should be removed from host/authority header before any processing
	// of request by HTTP filters or routing.
	// This affects the upstream host header unless the method is CONNECT in
	// which case if no filter adds a port the original port will be restored before headers are sent upstream.
	// Without setting this option, incoming requests with host “example:443“ will not match against
	// route with :ref:`domains<envoy_v3_api_field_config.route.v3.VirtualHost.domains>` match set to “example“. Defaults to “false“. Note that port removal is not part
	// of `HTTP spec <https://tools.ietf.org/html/rfc3986>`_ and is provided for convenience.
	// Only one of “strip_matching_host_port“ or “strip_any_host_port“ can be set.
	StripAnyHostPort bool `protobuf:"varint,42,opt,name=strip_any_host_port,json=stripAnyHostPort,proto3,oneof"`
}

type HttpConnectionManager_Tracing struct {

	// Target percentage of requests managed by this HTTP connection manager that will be force
	// traced if the :ref:`x-client-trace-id <config_http_conn_man_headers_x-client-trace-id>`
	// header is set. This field is a direct analog for the runtime variable
	// 'tracing.client_enabled' in the :ref:`HTTP Connection Manager
	// <config_http_conn_man_runtime>`.
	// Default: 100%
	ClientSampling *v33.Percent `protobuf:"bytes,3,opt,name=client_sampling,json=clientSampling,proto3" json:"client_sampling,omitempty"`
	// Target percentage of requests managed by this HTTP connection manager that will be randomly
	// selected for trace generation, if not requested by the client or not forced. This field is
	// a direct analog for the runtime variable 'tracing.random_sampling' in the
	// :ref:`HTTP Connection Manager <config_http_conn_man_runtime>`.
	// Default: 100%
	RandomSampling *v33.Percent `protobuf:"bytes,4,opt,name=random_sampling,json=randomSampling,proto3" json:"random_sampling,omitempty"`
	// Target percentage of requests managed by this HTTP connection manager that will be traced
	// after all other sampling checks have been applied (client-directed, force tracing, random
	// sampling). This field functions as an upper limit on the total configured sampling rate. For
	// instance, setting client_sampling to 100% but overall_sampling to 1% will result in only 1%
	// of client requests with the appropriate headers to be force traced. This field is a direct
	// analog for the runtime variable 'tracing.global_enabled' in the
	// :ref:`HTTP Connection Manager <config_http_conn_man_runtime>`.
	// Default: 100%
	OverallSampling *v33.Percent `protobuf:"bytes,5,opt,name=overall_sampling,json=overallSampling,proto3" json:"overall_sampling,omitempty"`
	// Whether to annotate spans with additional data. If true, spans will include logs for stream
	// events.
	Verbose bool `protobuf:"varint,6,opt,name=verbose,proto3" json:"verbose,omitempty"`
	// Maximum length of the request path to extract and include in the HttpUrl tag. Used to
	// truncate lengthy request paths to meet the needs of a tracing backend.
	// Default: 256
	MaxPathTagLength *wrappers.UInt32Value `protobuf:"bytes,7,opt,name=max_path_tag_length,json=maxPathTagLength,proto3" json:"max_path_tag_length,omitempty"`
	// A list of custom tags with unique tag name to create tags for the active span.
	CustomTags []*v34.CustomTag `protobuf:"bytes,8,rep,name=custom_tags,json=customTags,proto3" json:"custom_tags,omitempty"`
	// Configuration for an external tracing provider.
	// If not specified, no tracing will be performed.
	//
	// .. attention::
	//
	//	Please be aware that “envoy.tracers.opencensus“ provider can only be configured once
	//	in Envoy lifetime.
	//	Any attempts to reconfigure it or to use different configurations for different HCM filters
	//	will be rejected.
	//	Such a constraint is inherent to OpenCensus itself. It cannot be overcome without changes
	//	on OpenCensus side.
	Provider *v35.Tracing_Http `protobuf:"bytes,9,opt,name=provider,proto3" json:"provider,omitempty"`
	// Create separate tracing span for each upstream request if true. And if this flag is set to true,
	// the tracing provider will assume that Envoy will be independent hop in the trace chain and may
	// set span type to client or server based on this flag.
	// This will deprecate the
	// :ref:`start_child_span <envoy_v3_api_field_extensions.filters.http.router.v3.Router.start_child_span>`
	// in the router.
	//
	// Users should set appropriate value based on their tracing provider and actual scenario:
	//
	//   - If Envoy is used as sidecar and users want to make the sidecar and its application as only one
	//     hop in the trace chain, this flag should be set to false. And please also make sure the
	//     :ref:`start_child_span <envoy_v3_api_field_extensions.filters.http.router.v3.Router.start_child_span>`
	//     in the router is not set to true.
	//   - If Envoy is used as gateway or independent proxy, or users want to make the sidecar and its
	//     application as different hops in the trace chain, this flag should be set to true.
	//   - If tracing provider that has explicit requirements on span creation (like SkyWalking),
	//     this flag should be set to true.
	//
	// The default value is false for now for backward compatibility.
	SpawnUpstreamSpan *wrappers.BoolValue `protobuf:"bytes,10,opt,name=spawn_upstream_span,json=spawnUpstreamSpan,proto3" json:"spawn_upstream_span,omitempty"`
	// contains filtered or unexported fields
}

type HttpConnectionManager_TracingMultiError []error

type HttpConnectionManager_TracingValidationError struct {
	// contains filtered or unexported fields
}

type HttpConnectionManager_Tracing_OperationName int32

type HttpConnectionManager_UpgradeConfig struct {

	// The case-insensitive name of this upgrade, e.g. "websocket".
	// For each upgrade type present in upgrade_configs, requests with
	// Upgrade: [upgrade_type]
	// will be proxied upstream.
	UpgradeType string `protobuf:"bytes,1,opt,name=upgrade_type,json=upgradeType,proto3" json:"upgrade_type,omitempty"`
	// If present, this represents the filter chain which will be created for
	// this type of upgrade. If no filters are present, the filter chain for
	// HTTP connections will be used for this upgrade type.
	Filters []*HttpFilter `protobuf:"bytes,2,rep,name=filters,proto3" json:"filters,omitempty"`
	// Determines if upgrades are enabled or disabled by default. Defaults to true.
	// This can be overridden on a per-route basis with :ref:`cluster
	// <envoy_v3_api_field_config.route.v3.RouteAction.upgrade_configs>` as documented in the
	// :ref:`upgrade documentation <arch_overview_upgrades>`.
	Enabled *wrappers.BoolValue `protobuf:"bytes,3,opt,name=enabled,proto3" json:"enabled,omitempty"`
	// contains filtered or unexported fields
}

type HttpConnectionManager_UpgradeConfigMultiError []error

type HttpConnectionManager_UpgradeConfigValidationError struct {
	// contains filtered or unexported fields
}

type HttpFilter struct {

	// The name of the filter configuration. It also serves as a resource name in ExtensionConfigDS.
	Name string `protobuf:"bytes,1,opt,name=name,proto3" json:"name,omitempty"`
	// Types that are assignable to ConfigType:
	//
	//	*HttpFilter_TypedConfig
	//	*HttpFilter_ConfigDiscovery
	ConfigType isHttpFilter_ConfigType `protobuf_oneof:"config_type"`
	// If true, clients that do not support this filter may ignore the
	// filter but otherwise accept the config.
	// Otherwise, clients that do not support this filter must reject the config.
	IsOptional bool `protobuf:"varint,6,opt,name=is_optional,json=isOptional,proto3" json:"is_optional,omitempty"`
	// If true, the filter is disabled by default and must be explicitly enabled by setting
	// per filter configuration in the route configuration.
	// See :ref:`route based filter chain <arch_overview_http_filters_route_based_filter_chain>`
	// for more details.
	//
	// Terminal filters (e.g. “envoy.filters.http.router“) cannot be marked as disabled.
	Disabled bool `protobuf:"varint,7,opt,name=disabled,proto3" json:"disabled,omitempty"`
	// contains filtered or unexported fields
}

type HttpFilterMultiError []error

type HttpFilterValidationError struct {
	// contains filtered or unexported fields
}

type HttpFilter_ConfigDiscovery struct {
	// Configuration source specifier for an extension configuration discovery service.
	// In case of a failure and without the default configuration, the HTTP listener responds with code 500.
	// Extension configs delivered through this mechanism are not expected to require warming (see https://github.com/envoyproxy/envoy/issues/12061).
	//
	// To support configuring a :ref:`match tree <arch_overview_matching_api>`, use an
	// :ref:`ExtensionWithMatcher <envoy_v3_api_msg_extensions.common.matching.v3.ExtensionWithMatcher>`
	// with the desired HTTP filter. This works for both the default filter configuration as well
	// as for filters provided via the API.
	ConfigDiscovery *v3.ExtensionConfigSource `protobuf:"bytes,5,opt,name=config_discovery,json=configDiscovery,proto3,oneof"`
}

type HttpFilter_TypedConfig struct {
	// Filter specific configuration which depends on the filter being instantiated. See the supported
	// filters for further documentation.
	//
	// To support configuring a :ref:`match tree <arch_overview_matching_api>`, use an
	// :ref:`ExtensionWithMatcher <envoy_v3_api_msg_extensions.common.matching.v3.ExtensionWithMatcher>`
	// with the desired HTTP filter.
	// [#extension-category: envoy.filters.http]
	TypedConfig *any1.Any `protobuf:"bytes,4,opt,name=typed_config,json=typedConfig,proto3,oneof"`
}

type LocalReplyConfig struct {

	// Configuration of list of mappers which allows to filter and change local response.
	// The mappers will be checked by the specified order until one is matched.
	Mappers []*ResponseMapper `protobuf:"bytes,1,rep,name=mappers,proto3" json:"mappers,omitempty"`
	// The configuration to form response body from the :ref:`command operators <config_access_log_command_operators>`
	// and to specify response content type as one of: plain/text or application/json.
	//
	// Example one: "plain/text" “body_format“.
	//
	// .. validated-code-block:: yaml
	//
	//	:type-name: envoy.config.core.v3.SubstitutionFormatString
	//
	//	text_format: "%LOCAL_REPLY_BODY%:%RESPONSE_CODE%:path=%REQ(:path)%\n"
	//
	// The following response body in "plain/text" format will be generated for a request with
	// local reply body of "upstream connection error", response_code=503 and path=/foo.
	//
	// .. code-block:: text
	//
	//	upstream connect error:503:path=/foo
	//
	// Example two: "application/json" “body_format“.
	//
	// .. validated-code-block:: yaml
	//
	//	:type-name: envoy.config.core.v3.SubstitutionFormatString
	//
	//	json_format:
	//	  status: "%RESPONSE_CODE%"
	//	  message: "%LOCAL_REPLY_BODY%"
	//	  path: "%REQ(:path)%"
	//
	// The following response body in "application/json" format would be generated for a request with
	// local reply body of "upstream connection error", response_code=503 and path=/foo.
	//
	// .. code-block:: json
	//
	//	{
	//	  "status": 503,
	//	  "message": "upstream connection error",
	//	  "path": "/foo"
	//	}
	BodyFormat *v3.SubstitutionFormatString `protobuf:"bytes,2,opt,name=body_format,json=bodyFormat,proto3" json:"body_format,omitempty"`
	// contains filtered or unexported fields
}

type LocalReplyConfigMultiError []error

type LocalReplyConfigValidationError struct {
	// contains filtered or unexported fields
}

type Rds struct {

	// Configuration source specifier for RDS.
	ConfigSource *v3.ConfigSource `protobuf:"bytes,1,opt,name=config_source,json=configSource,proto3" json:"config_source,omitempty"`
	// The name of the route configuration. This name will be passed to the RDS
	// API. This allows an Envoy configuration with multiple HTTP listeners (and
	// associated HTTP connection manager filters) to use different route
	// configurations.
	RouteConfigName string `protobuf:"bytes,2,opt,name=route_config_name,json=routeConfigName,proto3" json:"route_config_name,omitempty"`
	// contains filtered or unexported fields
}

type RdsMultiError []error

type RdsValidationError struct {
	// contains filtered or unexported fields
}

type RequestIDExtension struct {

	// Request ID extension specific configuration.
	TypedConfig *any1.Any `protobuf:"bytes,1,opt,name=typed_config,json=typedConfig,proto3" json:"typed_config,omitempty"`
	// contains filtered or unexported fields
}

type RequestIDExtensionMultiError []error

type RequestIDExtensionValidationError struct {
	// contains filtered or unexported fields
}

type ResponseMapper struct {

	// Filter to determine if this mapper should apply.
	Filter *v31.AccessLogFilter `protobuf:"bytes,1,opt,name=filter,proto3" json:"filter,omitempty"`
	// The new response status code if specified.
	StatusCode *wrappers.UInt32Value `protobuf:"bytes,2,opt,name=status_code,json=statusCode,proto3" json:"status_code,omitempty"`
	// The new local reply body text if specified. It will be used in the “%LOCAL_REPLY_BODY%“
	// command operator in the “body_format“.
	Body *v3.DataSource `protobuf:"bytes,3,opt,name=body,proto3" json:"body,omitempty"`
	// A per mapper “body_format“ to override the :ref:`body_format <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.LocalReplyConfig.body_format>`.
	// It will be used when this mapper is matched.
	BodyFormatOverride *v3.SubstitutionFormatString `protobuf:"bytes,4,opt,name=body_format_override,json=bodyFormatOverride,proto3" json:"body_format_override,omitempty"`
	// HTTP headers to add to a local reply. This allows the response mapper to append, to add
	// or to override headers of any local reply before it is sent to a downstream client.
	HeadersToAdd []*v3.HeaderValueOption `protobuf:"bytes,5,rep,name=headers_to_add,json=headersToAdd,proto3" json:"headers_to_add,omitempty"`
	// contains filtered or unexported fields
}

type ResponseMapperMultiError []error

type ResponseMapperValidationError struct {
	// contains filtered or unexported fields
}

type ScopedRds struct {

	// Configuration source specifier for scoped RDS.
	ScopedRdsConfigSource *v3.ConfigSource `` /* 128-byte string literal not displayed */
	// xdstp:// resource locator for scoped RDS collection.
	// [#not-implemented-hide:]
	SrdsResourcesLocator string `protobuf:"bytes,2,opt,name=srds_resources_locator,json=srdsResourcesLocator,proto3" json:"srds_resources_locator,omitempty"`
	// contains filtered or unexported fields
}

type ScopedRdsMultiError []error

type ScopedRdsValidationError struct {
	// contains filtered or unexported fields
}

type ScopedRouteConfigurationsList struct {
	ScopedRouteConfigurations []*v32.ScopedRouteConfiguration `` /* 138-byte string literal not displayed */
	// contains filtered or unexported fields
}

type ScopedRouteConfigurationsListMultiError []error

type ScopedRouteConfigurationsListValidationError struct {
	// contains filtered or unexported fields
}

type ScopedRoutes struct {

	// The name assigned to the scoped routing configuration.
	Name string `protobuf:"bytes,1,opt,name=name,proto3" json:"name,omitempty"`
	// The algorithm to use for constructing a scope key for each request.
	ScopeKeyBuilder *ScopedRoutes_ScopeKeyBuilder `protobuf:"bytes,2,opt,name=scope_key_builder,json=scopeKeyBuilder,proto3" json:"scope_key_builder,omitempty"`
	// Configuration source specifier for RDS.
	// This config source is used to subscribe to RouteConfiguration resources specified in
	// ScopedRouteConfiguration messages.
	RdsConfigSource *v3.ConfigSource `protobuf:"bytes,3,opt,name=rds_config_source,json=rdsConfigSource,proto3" json:"rds_config_source,omitempty"`
	// Types that are assignable to ConfigSpecifier:
	//
	//	*ScopedRoutes_ScopedRouteConfigurationsList
	//	*ScopedRoutes_ScopedRds
	ConfigSpecifier isScopedRoutes_ConfigSpecifier `protobuf_oneof:"config_specifier"`
	// contains filtered or unexported fields
}

type ScopedRoutesMultiError []error

type ScopedRoutesValidationError struct {
	// contains filtered or unexported fields
}

type ScopedRoutes_ScopeKeyBuilder struct {

	// The final(built) scope key consists of the ordered union of these fragments, which are compared in order with the
	// fragments of a :ref:`ScopedRouteConfiguration<envoy_v3_api_msg_config.route.v3.ScopedRouteConfiguration>`.
	// A missing fragment during comparison will make the key invalid, i.e., the computed key doesn't match any key.
	Fragments []*ScopedRoutes_ScopeKeyBuilder_FragmentBuilder `protobuf:"bytes,1,rep,name=fragments,proto3" json:"fragments,omitempty"`
	// contains filtered or unexported fields
}

type ScopedRoutes_ScopeKeyBuilderMultiError []error