Using Content Delivery Networks (CDN)

You have the option of using your existing CDN to serve your translated sites, or install the proxies in your own datacenter.

Without a CDN, a GlobalLink Web Proxy translated website will be accessible and behave just like any other website on the internet. You may choose to publish your DNS entries for your translated sites through a CDN like Akamai and extend the benefits of your existing CDN relationship to your translated websites. Billing for those services is not handled by TransPerfect.com.

When adding translated sites to a CDN configuration, the GlobalLink Web Proxy localized website should be set up as an additional origin site and managed by the CDN in the same manner as the source language website. Requests and responses under this configuration flow in the following manner:

Request: End User's Browser >CDN Edge Cache > OneLink Proxy Servers > Origin Website
Response: Origin Website > OneLink Proxy Servers >CDN Edge Cache > End User Browser

If your localized site supports secure pages, the security certificates should be installed on the CDN layer, not the GlobalLink Web Proxy layer. Additionally, if the source site makes use of end-user IP information for geo-targeting features, the GlobalLink Web Proxy proxy will pass through any CDN header to your origin servers in the form of the X-Forwarded-For IP header. 

Typical CDN (e.g. Akamai) Data Flow

A CDN (Akamai) with the GlobalLink Web Proxy Platform

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.