Before you deploy your property to production, we recommend you test and verify your property to make sure it works as expected. CDN360 has a dedicated staging environment for this purpose. To deploy the property to the staging environment, perform the steps in Deploying Your Property.
CDN360 provides a staging environment for you to test your property configurations without affecting production. Sending your test traffic to the servers in the staging environment is a way for you to make sure the behavior is what you expect. The staging servers can be found by the hostname staging.qtlcdn.com
. You can also see their IP addresses by issuing the following command:
$ dig staging.qtlcdn.com
...
;; ANSWER SECTION:
staging.qtlcdn.com. 19 IN A 163.171.228.89
staging.qtlcdn.com. 19 IN A 163.171.230.47
staging.qtlcdn.com. 19 IN A 115.223.12.247
...
There are several ways to send test traffic to the staging environment:
staging.qtlcdn.com
. For example:faster.mydomain.com CNAME staging.qtlcdn.com
If you use a smart DNS service, you can also direct a small portion of the production traffic to the staging hostname to have a more thorough test.
/etc/hosts
file to hard code the hostname to be accelerated to one of the staging server's IP addresses. For example:163.171.230.47 faster.mydomain.com
--resolve
to directly map the hostname to be accelerated to the IP address of the CDN360 staging server(s). For example:$ curl -v https://faster.mydomain.com/index.html --resolve faster.mydomain.com:443:163.171.230.47