Thanks for the reply Adam. We're already forwarding the IP address as a request header, but Google doesn't derive lat-long, country etc. using the forwarded IP. It uses the IP of the nginx machine to derive the lat long, country and other data.
So my question is if there exists a way to tell GAE to use a particular header for extracting the IP address. On Monday, 4 January 2016 01:14:12 UTC+5:30, Adam (Cloud Platform Support) wrote: > > You could try forwarding them as extra custom headers, as in this example > <https://easyengine.io/tutorials/nginx/forwarding-visitors-real-ip/>, and > then check for these different headers on App Engine. > > On Friday, January 1, 2016 at 2:39:45 AM UTC-5, Mayank Bhagya wrote: >> >> >> Hello, >> >> I am using nginx as a reverse proxy in front of my appengine app. >> >> So the client's IP doesn't turn up in the remote_addr of the request that >> reaches app engine. >> Instead, remote_addr has the ip of the machine running nginx. >> >> So lat-lng, country and other headers are not getting populated correctly. >> Is there anyway I can tell appengine to use the forwarded IP to compute >> lat-lng, country etc? >> >> Thanks. >> -mayank >> > -- 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/e1d78479-2905-4333-941d-342063262ef7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
