Envoy Proxy doesn't add X-Forward-For header.

[gsingh-ds]

Summary We are currently using latest version of envoy proxy as a side car on App Mesh services. Our setup: [user]-->[lb]-->[virtual_gateway]-->[graphql_mesh](as app mesh service)-->[server] I have tried to get user IP at the back-end server. I can see the X-Forward-Proto header but not X-Forward-For header. Is there any way to do this?

Additional context Envoy proxy image: 840364872350.dkr.ecr.region-code.amazonaws.com/aws-appmesh-envoy:v1.22.0.0-prod

Attachments If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

[suniltheta]

Hi, we have a Feature Request: Unable to get the Client IP in the envoy logs using X-FORWARDED-FOR #349 for the same.

[gsingh-ds]

It seems like it has been 1 year since feature requested. Do you know when that will be added? Also if it already sends X-Forward-Proto why not X-Forward-For already has been added? Was there a specific reason it wasn't added?

[Stazz-Sphinx]

Hello Any information when this request will be added to work, we need have x-forwarded-for enabled?

[gsingh-ds]

@bendu @shsahu Any updates on this? or any timelines?

[hmvs]

@shsahu @suniltheta or anyone?

[bendu]

Hi. We are currently not working on this feature request. I have no timeline for when we may be start working on this.

[gsingh-ds]

@bendu any updates?

[Stazz-Sphinx]

@gsingh-ds We moved from the envoy to CloudFront and don't use it for any type of public faced traffic.