HTTP連接管理 · ENVOY 智能代理中文參考文檔

## HTTP連接管理 - [filter.network.HttpConnectionManager](#filternetworkhttpconnectionmanager) - [filter.network.HttpConnectionManager.Tracing](#filternetworkhttpconnectionmanagertracing) - [filter.network.HttpConnectionManager.Tracing.OperationName (Enum)](#filternetworkhttpconnectionmanagertracingoperationname-enum) - [filter.network.HttpConnectionManager.SetCurrentClientCertDetails](#filternetworkhttpconnectionmanagersetcurrentclientcertdetails) - [filter.network.HttpConnectionManager.CodecType (Enum)](#filternetworkhttpconnectionmanagercodectype-enum) - [filter.network.HttpConnectionManager.ForwardClientCertDetails (Enum)](#filternetworkhttpconnectionmanagerforwardclientcertdetails-enum) - [filter.network.Rds](#filternetworkrds) - [filter.network.HttpFilter](#filternetworkhttpfilter) HTTP連接管理[配置概述](../../../Configurationreference/HTTPconnectionmanager.md)。 ### filter.network.HttpConnectionManager [filter.network.HttpConnectionManager proto](https://github.com/envoyproxy/data-plane-api/blob/master/api/filter/network/http_connection_manager.proto#L19) ``` { "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": "{...}", "generate_request_id": "{...}", "forward_client_cert_details": "...", "set_current_client_cert_details": "{...}" } ``` - **codec_type** ([filter.network.HttpConnectionManager.CodecType](#filternetworkhttpconnectionmanagercodectype)) 應用與連接管理器的編解碼器類型。 - **stat_prefix** ([string](https://developers.google.com/protocol-buffers/docs/proto#scalar), REQUIRED) 連接管理器發布的統計信息所使用的前綴。有關更多信息，請參閱[統計文檔](../../../Configurationreference/HTTPconnectionmanager/Statistics.md)。 - **rds** ([filter.network.Rds](#filternetworkrds)) 通過RDS API動態加載連接管理器的路由表。必須正確設置`rds`，`route_config`其中一個。 - **route_config** ([RouteConfiguration](../v2APIreference/HTTProutemanagementandRDS.md#routeconfiguration)) 在此屬性中指定靜態的連接管理器的路由表。必須正確設置`rds`，`route_config`其中一個。 - **http_filters** ([filter.network.HttpFilter](#filternetworkhttpfilter)) 構成連接管理器請求的過濾器鏈，包括各個HTTP過濾器的列表。當請求發生時，將按照順序處理過濾器。 - **add_user_agent** ([BoolValue](https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#boolvalue)) 連接管理器是否處理[user-agent](../../../Configurationreference/HTTPconnectionmanager/HTTPheadermanipulation.md#user-agent)和[x-envoy-downstream-service-cluster](../../../Configurationreference/HTTPconnectionmanager/HTTPheadermanipulation.md#x-envoy-downstream-service-cluster)頭。有關更多信息，請參閱相應的鏈接。默認為false。 - **tracing** ([filter.network.HttpConnectionManager.Tracing](#filternetworkhttpconnectionmanagertracing)) 是否定義對象，決定連接管理器是否將跟蹤數據發送到已配置的跟蹤服務程序中。 - **http_protocol_options** ([Http1ProtocolOptions](#http1protocoloptions)) 傳遞給HTTP/1編解碼器，額外的HTTP/1設置選項。 - **http2_protocol_options** ([Http2ProtocolOptions](#http2protocoloptions)) 額外的HTTP/2設置選項，直接傳遞給HTTP/2編解碼器。 - **server_name** ([string](https://developers.google.com/protocol-buffers/docs/proto#scalar)) 連接管理器將在響應頭中寫入響應的服務名。如果未設置，則默認為Enovy。 - **idle_timeout** ([Duration](https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#duration)) 由連接管理器管理的連接空閑超時時長。在沒有活動的請求時，持續的時間超過設定的閾值，則認為連接超時。如果沒有設置，則沒有空閑超時。當達到空閑超時后，連接將被關閉。如果連接是HTTP/2連接，則在關閉連接之前會發生順序排空。看[drain_timeout](#drain_timeout)。 - **drain_timeout** ([Duration](https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#duration)) Envoy將在發送HTTP/2“關閉通知”（GOAWAY幀與最大流ID）和最終GOAWAY幀之間等待的時間。這是為了讓Envoy支持與最后GOAWAY幀競爭的新的流處理，所提供的寬限期。在這個寬限期間，Envoy將繼續接受新的流。在寬限期之后，最終GOAWAY幀被發送，Envoy將開始拒絕新的流。在連接遇到空閑超時或通用服務器耗盡時都會發生排空。如果未指定此選項，則默認寬限期為5000毫秒（5秒）。 - **access_log** ([filter.accesslog.AccessLog](#filteraccesslogaccesslog)) 從連接管理器發出的HTTP訪問日志的配置。 - **use_remote_address** ([BoolValue](https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#boolvalue)) 如果設置為true，連接管理器將在確定內部和外部源以及操作各種頭部時使用客戶端連接的真實遠程地址。如果設置為false或不存在，連接管理器將使用`x-forwarded-for`HTTP頭。有關更多信息，請參閱[x-forwarded-for](../../../Configurationreference/HTTPconnectionmanager/HTTPheadermanipulation.md#x-forwarded-for)，[x-envoy-internal](../../../Configurationreference/HTTPconnectionmanager/HTTPheadermanipulation.md#x-envoy-internal)和[x-envoy-external-address](../../../Configurationreference/HTTPconnectionmanager/HTTPheadermanipulation.md#x-envoy-external-address)的文檔。 - **generate_request_id** ([BoolValue](https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#boolvalue)) 連接管理器是否會自動生成[x-request-id](../../../Configurationreference/HTTPconnectionmanager/HTTPheadermanipulation.md#x-request-id)頭，如果該頭不存在。默認為true。生成一個隨機的UUID4（性能代價比較大），所以在高吞吐量的情況下，這個功能是不需要的，它可以被禁用。 - **forward_client_cert_details** ([filter.network.HttpConnectionManager.ForwardClientCertDetails](#filternetworkhttpconnectionmanagerforwardclientcertdetails)) 如何處理[x-forward-client-cert](../../../Configurationreference/HTTPconnectionmanager/HTTPheadermanipulation.md#x-forward-client-cert)（XFCC）HTTP頭。 - **set_current_client_cert_details** ([filter.network.HttpConnectionManager.SetCurrentClientCertDetails](#filternetworkhttpconnectionmanagersetcurrentclientcertdetails)) 只有在[forward_client_cert_details](#forward_client_cert_details)為`APPEND_FORWARD`或`SANITIZE_SET`且客戶端連接為`mTLS`時，此字段才有效。它指定要轉發的客戶端證書中的字段。請注意，在[x-forwarded-client-cert](../../../Configurationreference/HTTPconnectionmanager/HTTPheadermanipulation.md#x-forward-client-cert)頭中，始終設置`Hash`，并在客戶端證書顯示SAN值時始終設置`By`。 ### filter.network.HttpConnectionManager.Tracing [filter.network.HttpConnectionManager.Tracing proto](https://github.com/envoyproxy/data-plane-api/blob/master/api/filter/network/http_connection_manager.proto#L65) ``` { "operation_name": "...", "request_headers_for_tags": [] } ``` - **operation_name** ([filter.network.HttpConnectionManager.Tracing.OperationName](#filternetworkhttpconnectionmanagertracingoperationname-enum)) span名將由此字段生成。 - **request_headers_for_tags** ([string](https://developers.google.com/protocol-buffers/docs/proto#scalar)) 用于為活動span創建標簽的標題名稱列表。該標題名用于填充span標記名，標題值用于填充span標記值。如果指定頭的名稱出現在請求頭中，則會創建該標簽。 ### filter.network.HttpConnectionManager.Tracing.OperationName (Enum) [filter.network.HttpConnectionManager.Tracing.OperationName proto](https://github.com/envoyproxy/data-plane-api/blob/master/api/filter/network/http_connection_manager.proto#L66) - INGRESS (DEFAULT) 標記HTTP監聽器用于入站/入口請求。 - EGRESS 標記HTTP監聽器用于出站/出口請求。 ### filter.network.HttpConnectionManager.SetCurrentClientCertDetails (Enum) [filter.network.HttpConnectionManager.SetCurrentClientCertDetails proto](https://github.com/envoyproxy/data-plane-api/blob/master/api/filter/network/http_connection_manager.proto#L164) ``` { "subject": "{...}", "san": "{...}" } ``` - **subject** ([BoolValue](https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#boolvalue)) 是否轉發客戶端證書的標題。默認為false。 - **san** ([BoolValue](https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#boolvalue)) 是否轉發客戶端證書的SAN。默認為false。 ### filter.network.HttpConnectionManager.CodecType (Enum) [filter.network.HttpConnectionManager.CodecType proto](https://github.com/envoyproxy/data-plane-api/blob/master/api/filter/network/http_connection_manager.proto#L20) - **AUTO** (DEFAULT) 對于每個新的連接，連接管理器將自行決定使用哪個編解碼器。此模式支持TLS監聽器的ALPN以及監聽器明文的協議。如果ALPN數據可用，則優選，否則使用協議解析。在幾乎所有情況下，這是優選的設置。 - **HTTP1** 連接管理器將假定客戶端使用HTTP/1.1協議。 - **HTTP2** 連接管理器將假定客戶端使用HTTP/2（Envoy不需要通過TLS發送HTTP/2或者使用ALPN，事先預知的）。 ### filter.network.HttpConnectionManager.ForwardClientCertDetails (Enum) [filter.network.HttpConnectionManager.ForwardClientCertDetails proto](https://github.com/envoyproxy/data-plane-api/blob/master/api/filter/network/http_connection_manager.proto#L138) 如何處理[x-forward-client-cert](#x-forward-client-cert)（XFCC）HTTP頭。 - **SANITIZE** (DEFAULT) 不要將XFCC頭部發送到下一跳。這是默認值。 - **FORWARD_ONLY** 當客戶端連接是mTLS（Mutual TLS）時，轉發請求中的XFCC頭。 - **APPEND_FORWARD** 當客戶端連接是mTLS時，將客戶端證書信息附加到請求的XFCC頭并轉發它。 - **SANITIZE_SET** 當客戶端連接是mTLS時，使用客戶端證書信息重置XFCC頭，并將其發送到下一個躍點。 - **ALWAYS_FORWARD_ONLY** 始終在請求中轉發XFCC頭，而不管客戶端連接是否為mTLS。 ### filter.network.Rds [filter.network.Rds proto](https://github.com/envoyproxy/data-plane-api/blob/master/api/filter/network/http_connection_manager.proto#L181) ``` { "config_source": "{...}", "route_config_name": "..." } ``` - **config_source** ([ConfigSource](#configsource), REQUIRED) RDS的配置源描述符。 - **route_config_name** ([string](https://developers.google.com/protocol-buffers/docs/proto#scalar), REQUIRED) 配置的路由名稱。這個名字將被傳遞給`RDS API`。這允許配置多個HTTP監聽器（和關聯的HTTP連接管理器）使用不同的路由配置。 ### filter.network.HttpFilter [filter.network.HttpFilter proto](https://github.com/envoyproxy/data-plane-api/blob/master/api/filter/network/http_connection_manager.proto#L192) ``` { "name": "...", "config": "{...}" } ``` - **name** ([string](https://developers.google.com/protocol-buffers/docs/proto#scalar), REQUIRED) 要實例化的過濾器的名稱。該名稱必須與支持的過濾器匹配。內置的過濾器有： - [envoy.buffer](../../../Configurationreference/HTTPfilters/Buffer.md) - [envoy.cors](../../../Configurationreference/HTTPfilters/CORSfilter.md) - [envoy.fault](../../../Configurationreference/HTTPfilters/FaultInjection.md) - [envoy.http_dynamo_filter](../../../Configurationreference/HTTPfilters/DynamoDB.md) - [envoy.grpc_http1_bridge](../../../Configurationreference/HTTPfilters/gRPCHTTP11bridge.md) - [envoy.grpc_json_transcoder](../../../Configurationreference/HTTPfilters/gRPCJSONtranscoderfilter.md) - [envoy.grpc_web](../../../Configurationreference/HTTPfilters/gRPCWebfilter.md) - [envoy.health_check](../../../Configurationreference/HTTPfilters/Healthcheck.md) - [envoy.lua](../../../Configurationreference/HTTPfilters/Lua.md) - [envoy.rate_limit](../../../Configurationreference/HTTPfilters/Ratelimit.md) - [envoy.router](../../../Configurationreference/HTTPfilters/Router.md) - **config** ([Struct](https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#struct)) 指定的過濾器配置，這取決于被實例化的過濾器。有關更多文檔，請參閱支持的過濾器。 ## 返回 - [上一級](../Networkfilters.md) - [首頁目錄](../../../README.md)