This section provides parameter descriptions of mandatory OTA Updates behaviors that you can configure in the default rule or custom rules.
Mandatory behaviors are the necessary behaviors that are automatically part of the default rule.
With this behavior, you can control the primary settings the edge network uses when contacting the origin server to retrieve content. Available settings vary whether you select NetStorage or Your Origin as the origin type.
For more information on origin server parameters, see the "Origin Server" section in Property Manager online help.
Origin server parameters
The type of origin that content is retrieved from.
Range: Your Origin/NetStorage
Used to select the NetStorage download domain. This is the name of the domain set up for use with this application on your NetStorage account. Once you assign the download domain, Property Manager automatically assigns the root directory, for example /R3131, so that content can be retrieved from the appropriate location.
This field is available only if Origin Type is set to NetStorage.
Origin Server Hostname
Used to define the origin-server hostname or IPv4/IPv6 addresses of your origin server so content can be retrieved by the edge network.
It must follow a specific naming convention:
origin-original origin hostname
Forward Host Header
Used to select which host header you want the product to pass to your origin server. Referred to as the forward host header because it is the hostname the product forwards to the origin Server in the HTTP HOST request header. The web server on your origin server uses this value to determine what content to send. Typically, the expected host is the same name as the property hostname received in the request, or it can be customized.
Incoming Host Header
Property hostname received in the request is used. For example, a request for
www.example.combeing sent in the host header.
The origin server hostname is sent in the request to your origin server. Used if the origin server is configured to listen for the origin-server hostname. For example, end-user requests for
origin-www.example.combeing sent in the Host header in the request to the origin server.
The property hostname is a different name than the one the origin server expects. For example, an end-user request for
www.example.comas the value sent in the Host header to your origin server.
Cache Key Hostname
The cache key is the information the product uses to identify the content in caches. If your application includes at least some cacheable content—the edge network uses keys based on the entire origin server URI path and query string, if such exists.
All objects requested using this origin-server hostname and the same path and query string are treated as the same object, including the content served from any other configuration with the same origin-server hostname. For example, once cached,
http://www.example.co.uk/logo.gifare treated as the same object.
Incoming Host Header (Virtual Server Option)
Objects requested with the same path and query string are given a unique cache key by property hostname. Used if your origin server is a virtual server. For example, once cached,
http://www.example.co.uk/logo.gifare treated as different objects.
Supports Gzip Compression
Compression is important in optimizing performance. You can disable this option only if your origin server does not support delivery of content using Gzip compression; or, if you want to have content served uncompressed. When this feature is enabled, the product will send an
Accept-Encoding: gzipheader in requests to the origin server to support Gzip compression.
Send True Client IP Header
Used to send a custom header containing the IP address of the immediate client connecting to the product server. This usually provides more useful information than the standard
X-Forward-Forheader, which is often modified by proxies.
Origin SSL Certificate Verification
These options are revealed if configuring secure delivery (HTTPS). Origin SSL Certificate Verification is a mechanism for controlling how your origin server is authenticated. It is intended to prevent man-in-the-middle attacks, where a malicious entity directs end-user traffic to the attacker's server instead of the expected origin server. To confirm that your origin server is, in fact, your origin server, the product checks that the certificate your origin server sent during the SSL handshake either exactly matches a certificate, or is signed by a certificate authority listed in your property.
The settings you choose in Origin SSL Certificate Verification override the default settings for your property.
Use Platform Settings
Allows edge servers to choose settings on your behalf, trusting certificates signed by any authority listed in the Akamai Certificate Store. These settings are subject to change at any time.
Choose Your Own (Recommended)
Allows you to maximize security by directly controlling which certificates Akamai's edge servers should trust.
Third Party Settings
Allows you to use an Amazon AWS origin.
Use SNI TLS Extension
Used to send the Server Name Indication (SNI) header in the SSL request to the origin. The SNI header value is the same as the Forward Host Header value.
The port on your origin server that you want the edge server to connect to for HTTP requests. The standard port is 80.
The port on your origin server that you want the edge server to connect to for HTTPS (SSL) requests. The standard port is 443.
Content provider (CP) codes are numeric IDs assigned to client requests in your product configuration. These codes are used to identify your content for billing, logging, reporting, and cache purging. CP codes are assigned by your account representative, and associated with one contract only.
Do not share CP codes assigned to OTA Updates with other product configurations. This may result in double billing.
Content provider code parameters
|Content Provider Code||CP code assigned to your product configuration.|
Updated about 2 years ago