Thread: Load Balancing Question

We have a site running 7.0.2.5 SP1 (yes...still) which is load-balanced across two servers behind an ACE load-balancer. The way the load-balancer is set up, we do not get real IP addresses sent in the REMOTE_ADDR header, we get it as HTTP_X_FORWARD. I've added this method to CommonLogic:

C#/VB.NET Code:

        public static string GetIP()
        {
            String ret = String.Empty;
            if (HttpContext.Current.Request.ServerVariables["HTTP_X_FORWARD"] != null)
            {
                ret = HttpContext.Current.Request.ServerVariables["HTTP_X_FORWARD"];
            }
            else
            {
                ret = HttpContext.Current.Request.ServerVariables["REMOTE_ADDR"];
            }
            return ret;
        } 


I have replaced calls for CommonLogic.ServerVariables("REMOTE_ADDR") with CommonLogic.GetIP() throughout the code, yet I still see the LastIPAddress in the Customer table set as the IP Address of our router. Is there something in the code that you do not provide source access to that is still using CommonLogic.ServerVariables("REMOTE_ADDR")? If so, is there a way for me to override the method that is doing it?

Can I get a little love here? This IP address issue is a huge pain. Everyone shows up with the same IP Address to our store so we have to keep flushing the FailedTransactions table to keep people from getting order declined messages.

The logic for customer ip tracking is located on the ASPDNSFApplication assembly, which we don't ship source with.
What you can do is, put a hook inside CommonLogic.ServerVariables, since we also call that routine to get the remote ip.

i.e.

C#/VB.NET Code:

public static String ServerVariables(String paramName)
if(paramName == "REMOTE_ADDR")
{
   return CommonLogic.GetIP();
}
else.... 


On another note, we've already addressed this issue on the next major release of ML.

Oh jeez... I don't know why I didn't just do that.

Originally Posted by ASPDNSF Staff - Mark

On another note, we've already addressed
this issue on the next major release of ML.

Waiting for the powers that be to break out the checkbook and get us multi-store.

Thanks, Mark.

So, we made that change, but we're still not seeing real IP addresses in our orders table. Is there some other place I should be looking that is grabbing Request.ServerVariables["REMOTE_ADDR"] instead of CommonLogic.ServerVariables("REMOTE_ADDR")?

I made a page that shows what the CommonLogic.ServerVariables("REMOTE_ADDR") method is returning, and it's the real IP, but nothing in the database seems to be reflecting this change.

The changes will only affect newly created orders,
previous orders will still maintain the previous ip address logged for that customer.
Customer ipaddress is only copied over at the point of order creation.