Defining Requirements

Applies To:

HTTP LargeThis platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.

HTTP SmallLegacy. If you are currently serving traffic over this platform, then you may continue to do so. However, we recommend that you serve your traffic over our more robust HTTP Large platform.

ADNThe Application Delivery Network platform has been optimized to deliver dynamic content (e.g., login credentials, account information, etc.) over HTTP or HTTPS. Typically, user-specific and database-driven content are served over this platform.

TBAThe Token-Based Authentication feature enforces authentication prior to content delivery. Authentication takes place via an encoded token value that must be included in the request URL. This token value is then decrypted on an edge server. The requested content will only be delivered when the user meets the requirement(s) defined in the token.

A token value may consist of a set of requirements that the requester must satisfy before the requested content is delivered. These requirements may be mixed and matched as desired. Adding, modifying, or removing requirements simply involves generating another unique token. Clients that use the older token will still be able to access your content as long as they still meet its requirements and the encryption key used to generate it is still active.

Tokens can be specific to a particular folder or asset. Take advantage of this capability to prevent a token from being reused to access other protected content.
Learn more.

Invalidate old token values by changing the primary and backup encryption keys.
Learn more.

As previously noted, a token value is required for the delivery of content for which Token-Based Authentication has been applied. This token value may either be the same for all content or the set of requirements may vary according to the content being requested.

Defining Requirements

More Information