HTTP connection manager¶

HTTP connection manager configuration overview.

config.filter.network.http_connection_manager.v2.HttpConnectionManager¶

[config.filter.network.http_connection_manager.v2.HttpConnectionManager proto]

{
  "codec_type": "...",
  "stat_prefix": "...",
  "rds": "{...}",
  "route_config": "{...}",
  "http_filters": [],
  "add_user_agent": "{...}",
  "tracing": "{...}",
  "http_protocol_options": "{...}",
  "http2_protocol_options": "{...}",
  "server_name": "...",
  "idle_timeout": "{...}",
  "drain_timeout": "{...}",
  "access_log": [],
  "use_remote_address": "{...}",
  "xff_num_trusted_hops": "...",
  "generate_request_id": "{...}",
  "forward_client_cert_details": "...",
  "set_current_client_cert_details": "{...}",
  "proxy_100_continue": "...",
  "represent_ipv4_remote_address_as_ipv4_mapped_ipv6": "..."
}

codec_type: (config.filter.network.http_connection_manager.v2.HttpConnectionManager.CodecType) Supplies the type of codec that the connection manager should use.

stat_prefix: (string, REQUIRED) The human readable prefix to use when emitting statistics for the connection manager. See the statistics documentation for more information.

rds

(config.filter.network.http_connection_manager.v2.Rds) The connection manager’s route table will be dynamically loaded via the RDS API.

Precisely one of rds, route_config must be set.

route_config

(RouteConfiguration) The route table for the connection manager is static and is specified in this property.

Precisely one of rds, route_config must be set.

http_filters: (config.filter.network.http_connection_manager.v2.HttpFilter) A list of individual HTTP filters that make up the filter chain for requests made to the connection manager. Order matters as the filters are processed sequentially as request events happen.

add_user_agent: (BoolValue) Whether the connection manager manipulates the user-agent and x-envoy-downstream-service-cluster headers. See the linked documentation for more information. Defaults to false.

tracing: (config.filter.network.http_connection_manager.v2.HttpConnectionManager.Tracing) Presence of the object defines whether the connection manager emits tracing data to the configured tracing provider.

http_protocol_options: (core.Http1ProtocolOptions) Additional HTTP/1 settings that are passed to the HTTP/1 codec.

http2_protocol_options: (core.Http2ProtocolOptions) Additional HTTP/2 settings that are passed directly to the HTTP/2 codec.

server_name: (string) An optional override that the connection manager will write to the server header in responses. If not set, the default is envoy.

idle_timeout: (Duration) The idle timeout for connections managed by the connection manager. The idle timeout is defined as the period in which there are no active requests. If not set, there is no idle timeout. When the idle timeout is reached the connection will be closed. If the connection is an HTTP/2 connection a drain sequence will occur prior to closing the connection. See drain_timeout.

drain_timeout: (Duration) 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.

access_log: (config.filter.accesslog.v2.AccessLog) Configuration for HTTP access logs emitted by the connection manager.

use_remote_address: (BoolValue) 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 x-forwarded-for HTTP header. See the documentation for x-forwarded-for, x-envoy-internal, and x-envoy-external-address for more information.

xff_num_trusted_hops: (uint32) The number of additional ingress proxy hops from the right side of the 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 x-forwarded-for for more information.

generate_request_id: (BoolValue) of the client connection as the origin client address if use_remote_address is true Whether the connection manager will generate the 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.

forward_client_cert_details: (config.filter.network.http_connection_manager.v2.HttpConnectionManager.ForwardClientCertDetails) How to handle the x-forwarded-client-cert (XFCC) HTTP header.

set_current_client_cert_details: (config.filter.network.http_connection_manager.v2.HttpConnectionManager.SetCurrentClientCertDetails) This field is valid only when 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 x-forwarded-client-cert header, Hash is always set, and By is always set when the client certificate presents the SAN value.

proxy_100_continue: (bool) 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.

represent_ipv4_remote_address_as_ipv4_mapped_ipv6: (bool) If 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 for details. This will also affect the x-envoy-external-address header. See http_connection_manager.represent_ipv4_remote_address_as_ipv4_mapped_ipv6 for runtime control.

config.filter.network.http_connection_manager.v2.HttpConnectionManager.Tracing¶

[config.filter.network.http_connection_manager.v2.HttpConnectionManager.Tracing proto]

{
  "operation_name": "...",
  "request_headers_for_tags": [],
  "client_sampling": "{...}",
  "random_sampling": "{...}",
  "overall_sampling": "{...}"
}

operation_name: (config.filter.network.http_connection_manager.v2.HttpConnectionManager.Tracing.OperationName) The span name will be derived from this field.

request_headers_for_tags: (string) A list of header names used to create tags for the active span. The header name is used to populate the tag name, and the header value is used to populate the tag value. The tag is created if the specified header name is present in the request’s headers.

client_sampling: (type.Percent) Target percentage of requests managed by this HTTP connection manager that will be force traced if the x-client-trace-id header is set. This field is a direct analog for the runtime variable ‘tracing.client_sampling’ in the HTTP Connection Manager. Default: 100%

random_sampling: (type.Percent) 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 HTTP Connection Manager. Default: 100%

overall_sampling: (type.Percent) 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 HTTP Connection Manager. Default: 100%

Enum config.filter.network.http_connection_manager.v2.HttpConnectionManager.Tracing.OperationName¶

[config.filter.network.http_connection_manager.v2.HttpConnectionManager.Tracing.OperationName proto]

INGRESS: (DEFAULT) ⁣The HTTP listener is used for ingress/incoming requests.

EGRESS: ⁣The HTTP listener is used for egress/outgoing requests.

config.filter.network.http_connection_manager.v2.HttpConnectionManager.SetCurrentClientCertDetails¶

[config.filter.network.http_connection_manager.v2.HttpConnectionManager.SetCurrentClientCertDetails proto]

{
  "subject": "{...}",
  "san": "{...}",
  "cert": "..."
}

subject: (BoolValue) Whether to forward the subject of the client cert. Defaults to false.

san: (BoolValue) Whether to forward the SAN of the client cert. Defaults to false.

cert: (bool) 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.

Enum config.filter.network.http_connection_manager.v2.HttpConnectionManager.CodecType¶

[config.filter.network.http_connection_manager.v2.HttpConnectionManager.CodecType proto]

AUTO: (DEFAULT) ⁣For every new connection, the connection manager will determine which codec to use. This mode supports both ALPN for TLS listeners as well as protocol inference for plaintext listeners. If ALPN data is available, it is preferred, otherwise protocol inference is used. In almost all cases, this is the right option to choose for this setting.

HTTP1: ⁣The connection manager will assume that the client is speaking HTTP/1.1.

HTTP2: ⁣The connection manager will assume that the client is speaking HTTP/2 (Envoy does not require HTTP/2 to take place over TLS or to use ALPN. Prior knowledge is allowed).

Enum config.filter.network.http_connection_manager.v2.HttpConnectionManager.ForwardClientCertDetails¶

[config.filter.network.http_connection_manager.v2.HttpConnectionManager.ForwardClientCertDetails proto]

How to handle the x-forwarded-client-cert (XFCC) HTTP header.

SANITIZE: (DEFAULT) ⁣Do not send the XFCC header to the next hop. This is the default value.

FORWARD_ONLY: ⁣When the client connection is mTLS (Mutual TLS), forward the XFCC header in the request.

APPEND_FORWARD: ⁣When the client connection is mTLS, append the client certificate information to the request’s XFCC header and forward it.

SANITIZE_SET: ⁣When the client connection is mTLS, reset the XFCC header with the client certificate information and send it to the next hop.

ALWAYS_FORWARD_ONLY: ⁣Always forward the XFCC header in the request, regardless of whether the client connection is mTLS.

config.filter.network.http_connection_manager.v2.Rds¶

[config.filter.network.http_connection_manager.v2.Rds proto]

{
  "config_source": "{...}",
  "route_config_name": "..."
}

config_source: (core.ConfigSource, REQUIRED) Configuration source specifier for RDS.

route_config_name: (string, REQUIRED) 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.

config.filter.network.http_connection_manager.v2.HttpFilter¶

[config.filter.network.http_connection_manager.v2.HttpFilter proto]

{
  "name": "...",
  "config": "{...}"
}

name

(string, REQUIRED) The name of the filter to instantiate. The name must match a supported filter. The built-in filters are:

config: (Struct) Filter specific configuration which depends on the filter being instantiated. See the supported filters for further documentation.