You have Cookie disabled in your browser. Displaying the site will be incorrect!
Back to Blog
Posted: 18.10.2017

A modern CDN service is not only global coverage, good connectivity, excellent performance and convenient control panel.

No matter how fast is content delivery, it should be secure and easily manageable.

We offer 7 options for secure content delivery in the modern day web. Some of them arose from specific customer needs.

1. Access by countries

Access to content can be limited to any number of countries.

Make sure that your webinars are available only to residents of the USA and Canada or to everyone, except for viewers from China. To do this, set an allowing or blocking policy for specific countries.

2. Access by domains

Sometimes it is necessary to limit using of valuable content on third-party sites. To do this, allow or deny access to the content for specific domains.

3. Access by IP addresses

Access to content can also be restricted to certain IP addresses.

4. User agents policy

CDN content can be inaccessible for user agents, i.e., for a specific browser or device).

Default restrictions

By default, no access restrictions are applied to countries, domains, IP addresses, and applications.

API for restriction lists

For large-scale access restrictions (list of countries, domains, IP addresses and user agents), use the API. In the control panel, you can add countries, domains, IP addresses and user agents one by one.

5. Access by secure token

Content can be protected from unwanted downloads. With secure token content can be downloaded only if request contains a hash key.

A token (hash key) is a result of a one-way hash function MD5 (String), where String is the parameter obtained by merging the following elements (in the specified sequence): <expires> <path> <ip> <key>:
<expires>: Link expiration time in the UNIX Timestamp format.
<path>: Original link to the file.
<key>: A key that contains 6 to 32 characters provided by the client.
<IP>: IP addresses for which access to the file is allowed (this parameter is optional).

6. Allowed HTTP methods

Content requests can be controlled by using allowed HTTP methods. By default, GET, HEAD, POST, PUT, PATCH, DELETE, OPTIONS methods are allowed and available. Thus we recommend to always keep GET, HEAD and POST methods.

7. Access-Control-Allow-Origin HTTP header

Content can be protected from using in third-party applications. For example, limit the use of unique video content in competitors' players on their sites.

The option uses the CORS (Cross-Origin Resource Sharing) technology which restricts content for browsers if the request does not contain the desired header. (Players will not be able to play the content if CDN headers do not contain a CORS header.)

When the option is activated, you can add a header to all requests or to requests from certain domains (up to 5 domains).

How to activate options?

Content protection options are free and can be found in the control panel in the CDN Resources section. You can easily manage them as you like.