-
Notifications
You must be signed in to change notification settings - Fork 441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
expose httpConnectionManager.http_protocol_options.header_key_format Gloo API #2940
Comments
The envoy ProperCaseWords HeaderKeyFormat: https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/core/protocol.proto#envoy-api-msg-core-http1protocoloptions-headerkeyformat Formats the header by proper casing words: the first character and any character following a special character will be capitalized if it’s an alpha character. For example, “content-type” becomes “Content-Type”, and “foo$b#$are” becomes “Foo$B#$Are”. Note that while this results in most headers following conventional casing, certain headers are not covered. For example, the “TE” header will be formatted as “Te”. There is no option to preserve the case of the response headers if they look like: If that is the case, based on the envoy issue here: envoyproxy/envoy#8463, it is unlikely that we'll be able to upstream an envoy change that exactly preserves the header case formatting from the upstream. The general consensus from the envoy devs is that "even the non-intrusive version IMO is going to be hairy to survive H2 hops, header additions and header removals."
|
This may also be applicable: envoyproxy/envoy#8463 |
Requirement is to preserve the case of response headers. Assume this should be added to httpGateway.options.httpConnectionManagerSettings
The text was updated successfully, but these errors were encountered: