This is about CDN, not proxy, not sure if it would work for you, but it's easy to try.
http://world.episerver.com/documentation/developer-guides/CMS/Deployment/content-delivery-network-cdn-configuration/
BR,
Marija
Marija, that is about CDN, but also load balancing like products like A10 and F5 are also hiding the true caller id, so if you are using one of theses (or maybe also a proxy server) then it should work with the article you linked.
Thanks for the reply. Sorry to say that it did not work. Although when reading the doc (link) it looked very promising.
I am using EPiServer.CMS.Core 9.12.0.
<package id="EPiServer.CMS.Core" version="9.12.0" targetFramework="net452" />
Added this to appsettings
<add key="episerver:ClientIPAddressHeader" value="X-Forwarded-For" />
When i use this in a controller
Log.Info("X-Forwarded-For IS: " + Request.Headers.Get("X-Forwarded-For")); //Returns my real Ip
Log.Info("request.UserHostAddress: " + Request.UserHostAddress); //Return proxy Ip
When i create a visitor group that has Ip Range condition = "Proxyip" and use it on a block. That block is always visible.
If i change visitor group condition to my ip the block is never visible.
hi
It works if i do something like this in web.config. Good/Bad ?
<rule name="Map true incoming IP address" patternSyntax="Wildcard"> <match url="*" /> <action type="None" /> <serverVariables> <set name="REMOTE_ADDR" value="{C:0}" /> </serverVariables> <conditions> <add input="{HTTP_X-Forwarded-For}" pattern="*.*" /> </conditions> </rule>
Hi
When using IPRangeCriterion in VisitorGroupsCriteriaPack it just reads the httpContext.Request.UserHostAddress witch in my case is the ip of my netscaler proxy server. The clients ip is in request X-Forwarded-For . What is the best way to handle this?
Regards Øyvind