We've launched a new support center at help.smartling.com. This site will continue to be maintained into January 2017. Please update your bookmarks.

Effects of GDN load-balancing on user IP addresses and workarounds

The following article applies to Global Delivery Network project types. 

The Smartling Global Delivery Network typically includes load-balanced network components. Under certain conditions, the user’s source IP address as received by your alternative language site(s) may resolve to the load balancer, rather than the user’s actual IP address. Incorrect IP addresses may negatively impact your website, especially for IP address logging or location-based services that geo-encode based on IP address.

Smartling load balancers issue an additional header: “X-FORWARDED-FOR” in the format:

            X-FORWARDED-FOR: [Client ip], [Smartling ip]

The best-practice approach to resolving the client’s IP address is to check for the existence of the X-FORWARDED-FOR http header:

  • If the header exists and is not empty, use the client IP address provided in this header
  • If the X-FORWARDED-FOR does not exist or is empty, use the Remote Address for the client IP address
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Powered by Zendesk