Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API Gateway is not populating/appending x-forwarded/forwarded headers. Currently APIM simply forward those headers as is. Hence what back-end receives as the x-forwarded (say x-forwarded-host) information is, that of the client, not of the API gateway. #4953

Open
sanjeewa-malalgoda opened this issue Jan 15, 2018 · 1 comment

Comments

@sanjeewa-malalgoda
Copy link
Contributor

Description:
API Gateway is not populating/appending x-forwarded/forwarded headers. Currently APIM simply forward those headers as is. Hence what back-end receives as the x-forwarded (say x-forwarded-host) information is, that of the client, not of the API gateway. We need to discuss this across team and come to conclusion about behavior. Logging this issue for recording purpose.

Suggested Labels:
apim,3.0.0

Suggested Assignees:

Affected Product Version:
2.2.0

OS, DB, other environments details and versions:

Steps to reproduce:

Related Issues:

@deepak21singh
Copy link

I am facing the same issue... please suggest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants