contour
contour copied to clipboard
Support `X-Forwarded-Port` header
I tried to overwrite the X-Forwarded-Port header in a policy, but it seems like envoy ignores this policy. Therefore it would be nice to allow enabling the envoy append_x_forwarded_port option explicitly. Also see the envoy documentation: https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_conn_man/headers#x-forwarded-port
My contour configuration:
policy:
request-headers:
set:
X-Forwarded-Port: "443"
Environment:
- Contour version: 1.27.0
In my case I forgot to enable policies for ingresses. So the following did work:
policy:
applyToIngress: true
request-headers:
set:
X-Forwarded-Port: "443"
Still it would probably be nice if contour could set that header automatically.
The Contour project currently lacks enough contributors to adequately respond to all Issues.
This bot triages Issues according to the following rules:
- After 60d of inactivity, lifecycle/stale is applied
- After 30d of inactivity since lifecycle/stale was applied, the Issue is closed
You can:
- Mark this Issue as fresh by commenting
- Close this Issue
- Offer to help out with triage
Please send feedback to the #contour channel in the Kubernetes Slack
The Contour project currently lacks enough contributors to adequately respond to all Issues.
This bot triages Issues according to the following rules:
- After 60d of inactivity, lifecycle/stale is applied
- After 30d of inactivity since lifecycle/stale was applied, the Issue is closed
You can:
- Mark this Issue as fresh by commenting
- Close this Issue
- Offer to help out with triage
Please send feedback to the #contour channel in the Kubernetes Slack