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

Issue

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