X-Forwarded-For header not passed or respected on Service Mesh HTTPS gateway configurations
Issue
- Secure routes created from
HTTPS
Istiogateway
configurations are not passingX-Forwarded
headers or expected values, even if gateway topology is configured on theSMCP
. - The traffic logs showed in the
istio-proxies
for the values captured in theX-Forwarded-For
seem inconsistent for different routes, where the original clientIP
is displayed and on others is not.
Environment
- Red Hat OpenShift Container Platform
- 4.10 and newer
- Red Hat OpenShift Service Mesh
- 2.1 and newer
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.