XFF being populated with an Apigee internal private IP? (paid Edge Cloud, ELB with SSL pass-through to Apigee router)

[evan_scheessele]

Help! I need to see the actual client IP as a XFF header passed on to my target endpoint. Both client.ip and XFF are populating with a useless internal Apigee private IP, like 192.168.24.148. How can I get XFF to work for me? Context: this is Apigee Edge Cloud, paid, through an SSL-passthrough ELB terminating in an Apigee router/vhost.

[DChiesa]

I think I understand the situation you're describing. What do you mean by "get XFF to work for me"? Do you need the client_ip to have the original IP address?

[evan_scheessele]

I want my proxy to send an x-forwarded-for header to my target-server backend, and have that x-forwarded-for by the actual client IP address, as originally presented to my proxy front-end's ELB in Edge Cloud.

[DChiesa]

ok, can you show me what your X-F-F is, within the Edge proxy? I would expect it to include the original client IP as the last IP in the list.

is this not the case?