Right now when my users try to use the geolocation feature to present different content to different people, the feature is not working at all.
I suspect that this has to do with IIS getting the internal IP, so there is no value in the ip database that matches it. Reading the AWS documentation, it shows that they populate the original ip in the X-forwarded-for http header.
Do I have to let EpiServer know to look for this header? I assume this is some kind of configuration?
Thanks in advance
I blogged about something similar when using a CDN and you should be able to use the same approach to fix your problem: