You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched the internet for almost 4 hours and could not find a concrete answer to this question.
I have deployment that exposes a app listening on the HTTP/1.1. Since communication between Ingress and a client can be secure, I hoped that the Ingress would include the X-Forwarded-For and X-Forwarded-Proto headers, however I am not getting them at all. Is there any option for this be activated?
I searched the internet for almost 4 hours and could not find a concrete answer to this question.
I have deployment that exposes a app listening on the HTTP/1.1. Since communication between Ingress and a client can be secure, I hoped that the Ingress would include the
X-Forwarded-For
andX-Forwarded-Proto
headers, however I am not getting them at all. Is there any option for this be activated?I saw on the Ingress with HTTP/2 documentation page (https://cloud.google.com/kubernetes-engine/docs/how-to/ingress-http2) that these headers should be included in such scenario. However, my app can not support HTTP/2 at the moment and thus I can not test this.
Any concrete answer would help. Thank you.
The text was updated successfully, but these errors were encountered: