original http request origin and host headers are overriden

[sht5]

when my client makes an http request to the Ingress domain i see that the request origin and host headers are sent correctly but on my backend i can see they are changed by Ingress to some internal ip. This is crucial for setting up CORS for my app ( checks domain and alters response headers accordingly).

[sabinthomas]

Any update on this? I've looked at all the request headers on the request forwarded from the GCE Ingress, and I can't find anything that exposes the origin IP?

x-forwarded-for
x-real-ip

In the absence of this ability, I may have to move to using the nginx ingress.

[rramkumar1]

/kind feature

[bowei]

Hi, can you post your headers that you are seeing on your application side?
According to this page: https://cloud.google.com/load-balancing/docs/https/, you should be seeing x-forwarded-for

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[synvestable]

Hi, can you guys add some insight to this? This is a security bug if there's no feature to cover it, can't use in prod.