x-forwared-for not set correcty on node.js

[Karl Hiramoto]

The documentation at  https://cloud.google.com/appengine/docs/flexible/nodejs/runtime  

Says: " The user's IP address is available in the standard X-Forwarded-For header "

However this is not the case,   doing some debugging the HTTP request headers I always see are:

    "x-real-ip": "169.254.160.2",

    "x-forwarded-for": "169.254.160.2",

    "x-google-real-ip": "169.254.160.2",

These are link local IP addresses and can not be correct. 

Documentation bug or   app engine bug?

[Evan Jones]

I noticed this as well, using Python and Go with the Flexible environment. Its definitely a bug if you can't get the actual IP somehow. I think I can get the actual IP in the REMOTE_ADDR "environment variable" in Python (also as self.request.remote_addr), and I *thought* I was getting the actual IP in the X-Google-Real-Ip header in Go, but I might not be remembering correctly and I check check right now. I guess I'm saying: poke around and you might find a workaround. Hope that helps,

Evan

[Nick (Cloud Platform Support)]

Hey Folks,

We're aware of multiple reports of this and we're taking a look at it. We'll post updates to this thread as we continue to investigate.

Cheers,

Nick
Cloud Platform Community Support

On Sunday, August 14, 2016 at 6:54:32 PM UTC-4, Karl Hiramoto wrote:

[Nick (Cloud Platform Support)]

Just an update with no details to report as yet: we continue to investigate this behaviour and hope to have something more concrete to share soon.

Sincerely,

Nick
Cloud Platform Community Support