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 On Sunday, August 14, 2016 at 6:54:32 PM UTC-4, Karl Hiramoto wrote: > > > 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? > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/6991f4ae-a0a3-4cc6-886a-ec0081093154%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
