Tencent Cloud Mesh
- Release Notes and Announcements
- Announcements
- Getting Started
- Application Configuration
- Traffic Control
- Service HA
- Multi-cluster Disaster Recovery and Multi-active
- Security Reinforcement
- Operation Guide
- Mesh Instance Management
- Service Discovery Management
- Traffic Management
- Observability
- Access Management
- Extended Features
- FAQs
Envoy Converts Headers to Lowercase
Last updated: 2023-12-26 14:32:23
Envoy will convert the key of an HTTP header to lowercase by default. For example, the HTTP header
Test-Upper-Case-Header: some-value will be changed to test-upper-case-header: some-value after passing through the Envoy proxy. This is not a problem under normal conditions. RFC 2616 also states that HTTP header processing is case-insensitive.Scenarios in Which HTTP Headers Are Case-sensitive
Usually, converting a header to lowercase does not bring any specification problem. However, in some cases, header case-sensitivity may cause some problems, for example:
Header parsing is case-sensitive.
The SDK used is sensitive to the letter case of headers. For example, when reading
Content-Length to determine the length of a response, the SDK depends on the capitalization of first letters.Rules Supported Envoy
Envoy supports only two rules:
All lowercase (rule used by default), for example,
test-upper-case-header: some-valueCapitalization of first letters (not enabled by default), for example,
Test-Upper-Case-Header: some-valueIf the letter case of an HTTP header of an application is completely irregular, for example,
Test-UPPER-CASE-Header: some-value, the header cannot be compatible.Workaround Solution
To work around this problem, forcibly specify the TCP protocol. To be specific, declare the protocol of the service as TCP to prevent Istio from performing 7-layer processing. In this way, Istio will not change the letter case of the HTTP header. However, it should be noted that the Istio's 7-layer capability will also become invalid.
If the service is deployed in a cluster, add a "tcp" prefix to the name of a port of the service. For example:
kind: Servicemetadata:name: myservicespec:ports:- number: 80name: tcp-web # Set the protocol used by the port to TCP.
If the service is deployed outside a cluster, you can forcibly specify the service as a TCP service through a ServiceEntry similar to the following to prevent Envoy from performing 7-layer processing on the service:
apiVersion: networking.istio.io/v1alpha3kind: ServiceEntrymetadata:name: qcloud-cosspec:hosts:- "private-1251349835.cos.ap-guangzhou.myqcloud.com"location: MESH_INTERNALaddresses:- 169.254.0.47ports:- number: 80name: tcpprotocol: TCPresolution: DNS
Best Practices
If you want Envoy to enable the first letter capitalization rule for headers in some requests, you can use EnvoyFilter to set the header rule to capitalization. For example:
apiVersion: networking.istio.io/v1alpha3kind: EnvoyFiltermetadata:name: http-header-proper-case-wordsnamespace: istio-systemspec:configPatches:- applyTo: NETWORK_FILTER # http connection manager is a filter in Envoymatch:# context omitted so that this applies to both sidecars and gatewayslistener:name: XXX # Listener name used by cos, which can be queried from config_dumpfilterChain:filter:name: "envoy.http_connection_manager"patch:operation: MERGEvalue:name: "envoy.http_connection_manager"typed_config:"@type": "type.googleapis.com/envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager"http_protocol_options:header_key_format:proper_case_words: {}
Note：
listener name must be set based on actual conditions.Suggestions
Applications should comply with RFC 2616 and follow the principle that HTTP header processing is case-insensitive.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No