Draft

The first step towards customizing how the CDN handles requests is to create a draft of a policy. A draft must contain one or more rules that will eventually be applied to either test or live site traffic.

A draft consists of rules, match conditions, features, and select first match sections. The relationship between these elements is illustrated below.

Key information:

• A draft allows the administration of rules without impacting Production traffic.
• A draft may be viewed and/or modified at any time.
• A draft may be saved in any state. In other words, rule validation will not be enforced when saving a draft.
• Frequent updates may be applied to a draft.

• Once a draft accurately reflects the desired configuration, it should be converted into a read-only policy. This step is a precursor to submitting a deploy request to the Staging or Production environment.

  • This conversion process is irreversible and will prevent additional changes from being applied to it.
  • A new draft may be created from a read-only policy by copying it. In essence, a policy may be used as a template for a new draft. This allows you to easily fine-tune your configuration even after creating a read-only policy.

More Information

• Creating a Draft
• Rule
• Identifying Requests by Type (Match Conditions)
• Defining Actions by Request Type (Features)
• Getting to Know Rules Engine: Setup Workflow

Edgecast CDN