X-Forwarded-For header not passed or respected on Service Mesh HTTPS gateway configurations

Solution Verified - Updated -


  • Secure routes created from HTTPS Istio gateway configurations are not passing X-Forwarded headers or expected values, even if gateway topology is configured on the SMCP.
  • The traffic logs showed in the istio-proxies for the values captured in the X-Forwarded-For seem inconsistent for different routes, where the original client IP is displayed and on others is not.


  • 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.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content