Setting an Expiration Date

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.

Time-sensitive content may be assigned a token that expires after a specified time period. Requests that are submitted after the expiration date will be denied.

The Expire parameter (i.e., ec_expire) defines an expiration date and time by the number of seconds that have elapsed since Unix time (a.k.a. POSIX time or Unix epoch). Unix time starts on 1970-01-01 at 00:00:00 GMT.

Language-specific functions that provide Unix time conversions are widely available. However, at times it may be necessary to manually set this parameter or to troubleshoot an existing token. There are a variety of websites that provide conversion to and from standard time conventions to Unix time.

Sample Scenario

Set the Expire parameter to the following value to expire the token at 12/31/2015 12:00:00 GMT:

ec_expire=1451563200

A request submitted after 12/31/2015 12:00:00 GMT will be denied if it leverages a token generated using the above parameter.