Welcome to Object Delivery
Object Delivery (OD) accelerates the delivery of content such as images, CSS, JS, and other files by caching them in our Edge servers that are near to your end users. OD offers you self-sufficient set up and product maintenance through Akamai's Property Manager interface in Control Center.
OD is designed to deliver non-HTML cacheable objects (that is, objects that aren't text/html content type) that are under 100 MB in size. For delivery of HTML pages, whole web sites or dynamic applications, or for the delivery of objects larger than 100 MB, you can use our Dynamic Site Delivery, Application Acceleration, Download Delivery, or Adaptive Media Delivery solutions.
Object Delivery is built on a network of over 150,000 servers in thousands of networks, controlled by network intelligence systems that route requests, balance load, and ensure up-time.
You should be familiar with these terms
If this is the first time you're configuring edge network services, you should read the following table to familiarize yourself with some terms used with the process.
|Content Provider (CP) Code||This is an identifier for a particular subset of content on your Origin Server. Some features are applied individually to particular CP codes. CP codes are also used to provide additional granularity in reports and to track billing. You'll have at least one CP code per contract. Also, a CP code is associated with a single contract.|
|Property Hostname||This is an
identifier that indicates which Property file and product to use
when processing incoming HTTP/HTTPS requests. Often, the Property
Hostname is the full, end-user-facing hostname or fully qualified
Domain Name of your application or site. For instance,
|DNS Record||This is a record that associates a Domain Name to an IP address.|
|Edge Hostname||This describes
your customer-specific subdomain on an Edge network domain. It maps
incoming requests to our Edge servers. Typically, you specify Edge
hostnames in your Canonical Name (CNAME) records. You associate your
Property hostname with an Edge Hostname in Property Manager when
creating the Property Configuration file for Object Delivery. For
example, your site (Property hostname),
|Edge Server||This is a server in the Akamai Edge network that ultimately receives your end-user requests (end user requests to your Property Hostname are redirected to an associated Edge Hostname which resolves to the Edge Server). The Edge Server reads from the Property Configuration tied to the Property Hostname/Edge Hostname association, in order to determine how your site/application is to be delivered (via Rules and Behaviors established within that configuration)|
|Forward HOST Header||The name the Edge Server forwards (often to the Origin Server) in the HTTP Host request header, sometimes also referred to as the expected host. Often, this is the same name as the Property Hostname.|
|Origin Server||The Server where you keep your content to be served to end users (where your site/application resides). Edge servers read from an applicable Property Configuration file to determine Origin Server parameters (that you provide when creating the configuration).|
|Origin-server Hostname||The Hostname that maps to your Origin Server from which Edge Servers retrieve your content. The usual syntax of the Origin-server Hostname is the Property Hostname preceded by “origin” and a hyphen.|
|Property file||This is your Akamai delivery configuration
that includes all of the common rules for processing end-user
requests. You can use the Property Manager API or UI application
(via Control Center) to configure properties used for OD.
Note: Most often, this is simply referred to as your "OD property," but the terms "property configuration file," "property configuration," "configuration," and "configuration file" are used interchangeably to describe this component.