Skip to content

Quantil Documentation

Testing a Property permalink

Before you deploy your property to production, we recommend you test and verify your property to make sure it works as expected. CDN Pro has a dedicated staging environment for this purpose. To deploy the property to the staging environment, perform the steps in Deploying Your Property.

Note: You can also use the Test Suites page to test properties deployed to the staging and/or production environments.

Testing Your Property in Staging permalink

CDN Pro 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 before they hit your production environment. The staging servers can be found on the Properties list page. When you hover over the icon beside the Staging Version column header, you will see a popover showing a list of staging servers.

staging servers

You can also get a list of current IP addresses by calling our staging servers API.

Pick one of the IP addresses. The corresponding location field indicates the country where the staging server is located. If your property hostname has an ICP Beian license, you can use an IP address in China. Otherwise, choose an IP address in another country to avoid getting an HTTP 451 'Unavailable for Legal Reasons' status error.

Once you have selected a staging IP address, use one of the following ways to send test traffic to the staging environment:

  • Modify the hosts file to hard code the hostname to be accelerated to one of the staging server's IP addresses.

    On Windows-based systems, edit %SystemRoot%\System32\drivers\etc\hosts

    On Unix-based systems, edit /etc/hosts

    For example:

163.171.84.5 cdnpro.mydomain.com
  • If you use the cURL command, you can use the --connect-to option to directly map the hostname to be accelerated to the IP address of the CDN Pro staging server(s). For example:
$ curl -v https://cdnpro.mydomain.com/index.html --connect-to ::163.171.84.5:443

Note that the --connect-to option is introduced to cURL starting from version 7.49.0. If you're using an earlier version, use the --resolve option instead.

$ curl -v https://cdnpro.mydomain.com/index.html --resolve cdnpro.mydomain.com:443:163.171.84.5