Preserve X-Forwarded-Host in Ingress

[shaun-nx]

Is your feature request related to a problem? Please describe.
If I have an Ingress Resource deployed, and I send a request with X-Forwarded-Host header, the value in the header is not preserved

Describe the solution you'd like
The command below should return ‘bogus.example.com’:

$ curl --header "X-Forwarded-Host: bogus.example.com"  https://www.example.com
            "x-forwarded-host": "bogus.example.com",
            "host": "www.example.com"

Instead, it returns ‘www.example.com’ for both ‘x-forwarded-host’ and ‘Host’:

$ curl --header "X-Forwarded-Host: bogus.example.com"  https://www.example.com
            "x-forwarded-host": "www.example.com",
            "host": www.example.com

Describe alternatives you've considered
We would have to create a custom annotation, which is less than desirable

Additional context
N/A

[github-actions]

Hi @shaun-nx thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!

[crampeca]

+1, feature needed

[hamelchRIT]

maybe do the same like in the "virtualServer" tmpl?

{{- if not ($custom_headers | hasCIKey "X-Forwarded-Host") }}
{{ $proxyOrGRPC }}_set_header X-Forwarded-Host $host;
{{- end }}

[chris8205]

@shaun-nx what do you think about @hamelchRIT‘s idea?
Or can it customized like described in
https://github.com/nginx/kubernetes-/tree/main/examples/shared-examples/custom-templates

[chris8205]

@vepatel what do you think about to let also act the ingress template like the virtual server template to be able to override the X-Forwarded-Host

Actually if set the header over an annotation
It will add a second entry, and both hosts are listed instead to override it.
In some cases ( cascaded ingresses / proxies ) we have to override the source host value to the real external URL