Glossary
The following definitions can help you follow the instructions in this document.
Term | Definition |
---|---|
Behavior | An element in a rule that specifies a feature to apply to requests. A rule can have many behaviors or only one. |
Content Provider (CP) Code | An identifier for a particular subset of content on your origin server. Some IoT features are applied individually to particular CP codes. CP codes are also used to provide additional granularity in reports and to track billing. You will have at least one CP code per contract; a CP code is associated with one contract only. |
Edge Hostname | A customer-specific subdomain on a domain that maps incoming requests to edge servers. Typically, customers specify edge hostnames in Canonical Name (CNAME) records. |
Edge Server | An Akamai-owned server that receives end-user requests and provides an integrated suite of services for content and application delivery, content targeting, edge processing, and business intelligence. |
Hosts File | A file that maps hostnames to IP addresses. When you prepare to test your OTA Updates configuration, you temporarily change your computer’s hosts file to point directly to an edge server. |
Match Criteria | The part of a rule identifying the requests that the rule applies to. A match criteria is essentially the “IF” that pairs with the “THEN” specified in the rule’s behaviors. |
Origin Server | The server where you keep your content. Akamai retrieves content from the origin server and serves it from edge servers. |
Origin Server Hostname | The hostname mapping to the customer’s origin server where Akamai retrieves your content. |
Rule | An instruction that controls how Akamai applies features to requests. Rules consist of two parts: match criteria and behaviors. If a request fulfills the requirements given in a rule’s match criteria, Akamai applies the features configured in that rule’s behaviors. A configuration typically has multiple rules. |
Updated about 3 years ago