Show search and navigation.
An environment identifies a CDN network that has a specialized purpose. Rules Engine allows a deploy request to be submitted to either of the following environments:
Only a single policy per environment may be active at any given time.
The Production environment identifies the traditional CDN network that is responsible for a live site's content delivery. All CDN settings (e.g., customer origin and edge CNAMEs), with the exception of deploy requests to the Staging environment, are applied to this environment.
Purge requests are applied to both the Staging and Production environments.
The recommended workflow for pushing a new Rules Engine configuration to the Production environment is described below.
The Staging environment provides a sandbox through which end-to-end tests of new CDN configurations may be performed without impacting live site traffic. This means that it allows mock site traffic to flow through our Staging network to an origin server. This environment emulates the architecture of the Production environment on a much smaller scale. It also replicates your CDN configuration (e.g., customer origins, edge CNAMEs, Token-based Authentication, etc.).
This environment allows:
The Staging environment is designed for functional testing and is of a much smaller scale than the Production CDN environment. Therefore, this environment should not be used to perform scale, volume, or throughput testing.
Please keep traffic below the following levels:
With regards to firewall configuration, the Staging environment does not require additional whitelisting. The IP blocks defined on the Customer Origin page include our staging POPs.
With regards to analytics, traffic generated for the Staging environment will be treated as standard traffic. Our reports will not make a distinction between production and staging traffic. However, it may be possible to view usage reports for the Staging environment by generating a report by:
Requests may be directed to the Staging environment by prepending staging. to the hostname defined in a CDN URL.
Sample CDN URL (Production):
Sample CDN URL (Staging):
Alternatively, traffic may be directed to the Staging environment via an edge CNAME URL.
This requires performing the following steps:
From your DNS service provider, create a CNAME record that points the above edge CNAME to: