We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Description:
Describe the issue.
Envoy allows you to use format strings https://www.envoyproxy.io/docs/envoy/latest/configuration/observability/access_log/usage#config-access-log-format-strings which can use set as header values.
here's an example where it can used to set the downstream addr value in the X-Proxy-Connection header.
X-Proxy-Connection
- filters: - type: URLRewrite urlRewrite: path: type: ReplacePrefixMatch replacePrefixMatch: / - type: RequestHeaderModifier requestHeaderModifier: set: - name: X-Proxy-Connection value: "%DOWNSTREAM_REMOTE_ADDRES%"
Would be great to add a similar example where users can access traffic attributes using this technique
and add this into https://gateway.envoyproxy.io/docs/tasks/traffic/http-request-headers/
[optional Relevant Links:]
Any extra documentation required to understand the issue.
The text was updated successfully, but these errors were encountered:
@arkodg hey, i'd like to work on this issue as my first contribution to the project - would you please assign it to me to prevent duplicate work?
Sorry, something went wrong.
mahdikhashan
No branches or pull requests
Description:
Envoy allows you to use format strings https://www.envoyproxy.io/docs/envoy/latest/configuration/observability/access_log/usage#config-access-log-format-strings which can use set as header values.
here's an example where it can used to set the downstream addr value in the
X-Proxy-Connection
header.Would be great to add a similar example where users can access traffic attributes using this technique
and add this into https://gateway.envoyproxy.io/docs/tasks/traffic/http-request-headers/
[optional Relevant Links:]
The text was updated successfully, but these errors were encountered: