aws / aws/aws-app-mesh-roadmap

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

Open
#413 8 comments 11 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

Bug
Dominant language
No language data
Stars
344
Forks
24
PR merge metrics
No merged PRs in 30d

Description

**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.)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.