Skip to content
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

Inconsistent default value in ClientTrafficPolicy #4713

Closed
czczycz opened this issue Nov 14, 2024 · 1 comment
Closed

Inconsistent default value in ClientTrafficPolicy #4713

czczycz opened this issue Nov 14, 2024 · 1 comment
Labels

Comments

@czczycz
Copy link

czczycz commented Nov 14, 2024

I find two configurations in HCM are different from Envoy's default values. Both set by ClientTrafficPolicy.

path_with_escaped_slashes_action

The default value from Envoy is KeepUnchanged, but the default value in EG is UnescapeAndRedirect
Refer to here

headers_with_underscores_action

The default value from Envoy is Allow, but the default value in EG is RejectRequest
Refer to here

@czczycz czczycz added the triage label Nov 14, 2024
@arkodg
Copy link
Contributor

arkodg commented Nov 14, 2024

these are the recommended edge settings from the envoy proxy documentation, check out #1048

to change these values, you can configure these in ClientTrafficPolicy https://gateway.envoyproxy.io/docs/api/extension_types/#pathsettings

@arkodg arkodg closed this as completed Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants