CDN HTTP PULL Resource  Print this Article

HTTP Pull is probably the most frequently used CDN method/protocol. It's recommended for the delivery of small static content via CDN edge servers - content like images, CSS and pdf files. With HTTP Pull, content is cached on edge servers when a user requests that content.  To set up an HTTP Pull resource:
  1. If you have not already done so, order CDN Service (use this guide);
  2. Navigate to your CDN Service and add a new CDN Resource of the type HTTP Pull (use this guide);
A configuration screen for the new CDN Resource will appear. Configure the settings as follows:

BASIC SETTINGS -

  1. CDN Hostname - the hostname from which you will serve static content. E.g. if your site (origin) is mysite.com, and you want to serve static content from the CDN and make it available at static.mysite.com, then static.mysite.com would be the CDN hostname;
  2. Origins - specify the content origin(s). You can optionally specify a custom port using standard 'host:port' notation (i.e. 'mysite:8080'). If you do not indicate a custom port, the system will use the default for SSL / non-SSL HTTP;
  3. SSL Mode - select whether or not you want to use SSL for this resource. Note that using SSL will require advanced configuration.
ADVANCED SETTINGS -
  1. Secondary CDN Hostnames - Submit secondary hostname(s) apart from the default one for HTTP based CDN sites. With these configured, users will be able to access the CDN site using secondary CDN hostname(s). You can add up to 7 secondary CDN hostnames to your CDN resource. NOTE: To be able to use a secondary hostname(s) for the CDN resource with SSL enabled, an SSL certificate for each secondary hostname(s) will be required. Please contact support for assistance.
  2. IP Access Policy - Configure a rule to enable/disable access to the CDN resource’s content for a range of IP addresses:
    1. Default - access is allowed for all IPs;
    2. Allow by Default - access is allowed for all IPs, excepting those listed in Except for IP Addresses;
    3. Block by Default - access is denied for all IPs, excepting those listed in Except for IP Addresses;
    4. Except for IP Addresses - the list of IPs to be allowed or blocked, depending upon your setting.
  3. Country Access - Configure a rule to enable/disable access to the CDN resource’s content for specified countries:
    1. Default - access is allowed for all countries;
    2. Allow by Default - access is allowed for all countries, excepting those listed in Except for Countries;
    3. Block by Default - access is denied for all countries, excepting those listed in Except for Countries;
    4. Except for Countries - the list of countries to be allowed or blocked, depending upon your setting. To select more than one country, hold Ctrl during selection.
  4. Hotlink Policy - Configure rules for hotlinking by other sites:
    1. Default - hotlinking is allowed for all sites;
    2. Block by Default - hotlinking is denied for all sites, excepting those listed in Except for Domains;
    3. Except for Domains - the list of sites to be allowed for hotlinking when policy is set to Block by Default.
  5. URL Signing - Tick the box to protect your files from unauthorized access with a key and optionally an expiration time. A signed URL looks like `http://example.com/filename?secure=DMF1ucDxtqgxwYQ==,1322659070`.
    1. URL Signing Key - fill in the key which will be used for URL signing. The secret key is similar to a password and can contain a minimum of 6 to a maximum of 32 characters. Symbols and spaces are not allowed. You can also specify the expiration time, that is the time when this URL becomes invalid. The time is passed in the URL itself in a Unix timestamp format and takes part in hash generation (see 1322659070 above).
  6. Cache Expiry - set the cache expiry time in minutes (min=1, max=35000000).
  7. Password - optionally restrict access to the resource (CDN hostname) by username/password authentication:
    1. Enable Password – tick the box to enable;
    2. Unauthorized HTML – fill in the text which will be displayed for unauthorized login;
    3. Username and Password – set a username and set a password for a user; click the Add Field button to add additional users;
  8. Pseudo Streaming - Allows viewers to seek and skip through a video even if it has not finished downloading. A suitable media player and a prepared video are required for pseudo-streaming.
    1. Enable MP4 pseudo streaming – tick the box to enable the pseudo-streaming support for MP4 file type;
    2. Enable FLV pseudo streaming – tick the box to enable pseudo streaming for FLV file type;
  9. Ignore Set-Cookie - tick the box to enable caching content with Set-Cookie response headers;
Complete the last two steps for adding a CDN resource (see this guide).

Was this answer helpful?

Related Articles

CDN HTTP PUSH Resource
The HTTP Push Resource can be compared to having a secondary server at your disposal: you upload...
CDN Live Streaming Resource
The Live Streaming CDN Resource is designed to deliver live streaming content via the CDN....
CDN Video On Demand (VOD) Resource
A VOD CDN Resource is meant to deliver static video files within the CDN. Supported protocols...