Download overview

Downloading content can actually refer to two separate operations. You should have a good understanding of the difference between the two.

  • Downloads to manage content: This applies if you've uploaded content and wish to download it for management purposes.
  • Downloads to deliver content to end users: This is the URL you provide to your end users for access, based on the “digital property” defined in your account’s specific Edge configuration.

Downloads to manage content

These types of downloads are for content-management management purposes. It doesn't apply if you're looking to deliver content to your end users. Here, you login with the appropriate username followed by the Upload Domain Name. You would then use the applicable “download” operation available for use with your selected, NetStorage-supported protocol or service.

Here are some examples of this download use case:

  • To avoid any translations or restrictions that your associated Delivery Configuration may have in place.
  • To reuse the same connection.
Warning: Even though it is revealed in the NetStorage Groups UI, you DO NOT use the <domain prefix>.download.akamai.com domain name to perform downloads. This domain name is not used at all, unless you are specifically told to do so by your Account Representative.

Downloads to deliver content to end users

NetStorage is designed to store content that you then deliver to your end users via any of our associated content delivery products. End users obtain content through an EdgeServer, and in the case of a cache miss, the EdgeServer will retrieve the content directly from NetStorage.

Note: “Cache hit” and “cache miss” refer to whether or not EdgeServers hold the requested content in their cache.
Building the delivery URL

The Delivery URL is used to access the actual content. This is the URL you provide to your end users for access, based on the “digital property” defined in your account’s specific Edge configuration. The construction of this actual URL can vary, based on your selected delivery method (for example, our Adaptive Media Delivery or Download Delivery solutions).

Example: Content delivery to a browser

Once you have uploaded content to NetStorage and properly established delivery URLs into your web site, end-user browsers can request NetStorage content from EdgeServers.

Downloading NetStorage Content


Example delivery flow
  1. An end user requests content from the target web site via a properly formatted delivery URL, and the intelligent DNS system directs the browser to the optimal EdgeServer. In the event of a cache hit, the EdgeServer will simply return the content to the browser. In the event of a cache miss, the EdgeServer must retrieve the content from NetStorage.
  2. The Mapping System is used:
    1. A DNS Request for the appropriate Storage URL domain name is sent.
    2. The Storage URL domain name is resolved to the optimal NetStorage site based on real-time Internet traffic mapping.
  3. Interaction between the EdgeServer and NetStorage site:
    1. The EdgeServer processes the request from the Mapping System and requests content from the optimal NetStorage Site.
    2. Content from the NetStorage site is delivered to the requesting EdgeServer.
  4. The EdgeServer delivers the content to the browser and stores it in cache for future requests.