Go "Live"

The Akamai platform requires that the subcustomer resource be CNAMEd to Akamai. So, we recommend that each subcustomer use a test domain to validate end-to-end CDN functionality via Akamai.

Let's assume the goal is to enable www.example.com via Akamai.
  1. Create a test hostname—such as test-www.example.com
  2. CNAME the test hostname to the same endpoint (that you provide as the cloud partner) for www.example.com
  3. Create a copy of the policy via the ACE API, so that it uses the same origin. If required, the policy can override the Host: header sent to the origin to use the “fixed” value, www.example.com as shown below:
Note: All other behaviors, such as time to live (TTL) settings should match what is set for www.example.com policy that was copied.
{ 
    "rules" : [
        {
            "matches" : [
                {
                    "name" : "url-wildcard",
                    "value" : "/*",
                }
            ],
            "behaviors" : [
                {
                    "name" : "origin",
                    "value" : "-",
                    "params" : {
                        "digitalProperty" : "test-www.example.com",
                        "originDomain" : "c1234567.cloudprovider.com",
                        "cacheKeyType" : "origin",
                        "cacheKeyValue" : "-"
                        "hostHeaderType" : "fixed",
                        "hostHeaderValue" : "www.example.com",
                    }
                }
            ]
        }
    ]
}

In the short term, this means fully-qualified URLs in the resulting HTML are not updated to reflect the test hostname, so browser-based testing will not suffice. Automated testing can be used to functionally test delivery of content via the Akamai platform.