Content. Global Delivery Network: Folders

Transcription

1 An alternative to using translated domains, is to host your translations in folders. I.e. language When hosting your translation in a sub-folder, the traffic will need to be split between requests for source content (going to your web server) and translated content (going to the Smartling GDN). Your options to split traffic are using the Smartling Global Delivery Network, a Content Delivery Network, or web server or network appliance (ie Netscaler, F5) with proxy capabilities. Content The Smartling Global Delivery Network A Content Delivery Network (CDN) An HTTP server with proxy capabilities

2 Smartling Global Delivery Network At the core the Global Delivery Network is a proxy solution, and as a result Smartling has the ability to let traffic pass through the GDN or translate it. To use the Smartling GDN, create a CNAME for your source domain such as www. mycompanysite.com pointing to the Smartling CNAME so that Smartling can route all your site traffic. We then create rules and configure domains to: Let any traffic for the source language pass through the GDN to then be pointed to the server hosting your content in the Source Language using either an origindomain or an IP. Translate the content coming through in specific folders, as well as rewrite all links to the correct target folder. SSL Implications: If encryption is required, a certificate will need to be deployed in the Smartling infrastructure. Content Delivery Network (CDN) A CDN is a proxy solution that also lets you split traffic between different origin hosts for the content that is optimized for delivery. In this configuration, Rules are set up in the CDN configuration to split traffic to Smartling instead of the regular origin-host. Cloudflare As of June 2014 Cloudflare does not support this approach. Sample rules for Akamai 1. Click on the non-obvious Choose Optional Features link about 6 lines down from Configuration Attributes and Digital Properties. 2. Select the Modify Path Rules option. A new section of the configuration is enabled 3. Modify path rule / Match Criteria /Component Path: /FOLDERNAME/ (Ignore Case) Relative (Remove Original Path): /FOLDERNAME/ Modified Origin Server: mycompany.sl.smartling.com Forward HOST header: Digital Property Cache Key: Origin Server (mycompany.sl.smartling.com)

3 Other CDNs: Limelight, Fastly, ChinaCache, etc.: Please contact your CDN provider. SSL Implications: IIf encryption is required the certificates are deployed in the CDN infrastructure, traffic between the CDN and Smartling is encrypted using unsigned certificates, so no certificates will be needed in the GDN. HTTP Server with proxy capabilities Just like you can leverage the GDN to split the traffic, an HTTP server with proxy capabilities (Apache, Nginx) has the ability to split the traffic to Smartling for translated folders, and to another location for source content. Sample rules for nginx location ~* ^/(langfolder1 langfolder2 lang3)/? { break; proxy_pass } Sample rules for Apache (with Mod_proxy) <VirtualHost REPLACEWITHIPADDRESS:80> ServerName domain.com ServerAlias <Proxy Allow from all </Proxy> <LocationMatch /langfolder1 > ProxyPass ProxyPassReverse ProxyPreserveHost On Header add Host RequestHeader set Host </LocationMatch> </VirtualHost>

4 Other web servers and appliances For all other web servers and appliances, please contact the company s technical support team. SSL Implications:If encryption is required the certs are deployed on your server; traffic between the proxy and Smartling is encrypted using unsigned certs, so certs will not be needed on the Smartling proxies.

5 help center For more information visit the Smartling Help Center. Contact the Smartling Support Team at SMART Disclaimer All training materials are for your own personal and not for commercial use. They may not be reproduced, distributed, transmitted, displayed, published or broadcasted without the prior permission of Smartling.