The site management screen allows you to quickly access all configuration items for a respective site.
Any configuration changes are applied to the CDN immediately. It also includes access to Cache-checking, File purging, the RAW Log files and the Advanced Rules Engine.
Table Of Contents
- General Settings
- Logs & Actions
- Extra Configuration
- Advanced Rules Engine (separate page)
This section holds the basic information that is required for your site.
This is the numeric ID for this specific site. When using the API, this ID is used when referring to this site.
Name, Aliases and SSL
This section allows you to set or change the name of your site, add/delete aliases and manage SSL certificates for both site and aliases
This name will be the pointer to your content. There are two ways to use it:
- In your DNS setup, create a CNAME record (i.e. cdn.your-domain.com) from your custom hostname to your account’s DNS record.
(It’s visible in your “Account Info”, formatted as “%variable%.c.stackcdn.io“)
Access content via http://cdn.your-domain.com/yourdirectory/yourfile
- Use the name as the first part of the file path with our domain: http://cdn.stackcdn.io/cdn.your-domain.com
Access content via http://cdn.stackcdn.io/cdn.your-domain.com/yourdirectory/yourfile
Clicking the Edit-button will present you with the dialogue, allowing you to set the name of your site.
Wildcards: set name to _.cdn.yourdomain.com and you can use any sub domain to access content e.g. images.cdn.yourdomain.com, video.cdn.yourdomain.com
To manage your site’s SSL certificates check “Set up SSL certificates” to see corresponding fields.
Aliases management is similar: simply go to “Aliases” tab and press “Add first Alias” button.
You will be offered to enter newly created alias name and (if you check “SSL” checkbox) SSL settings.
SSL Setup Information
This feature uses SNI to identify the site before the certificate is sent to client.
Both: Private key and Certificate texts should include BEGIN/END lines
(Contents of Certificate)
SSL Private Key:
—–BEGIN RSA PRIVATE KEY—–
(Contents of Private Key)
—–END RSA PRIVATE KEY—–
If your certificate requires a certificate chain, include the chain in the SSL Certificate field like this:
(Certificate #1 – Contents of main certificate)
(Certificate #2 – Contents of intermediate certificate used to sign certificate #1)
(Certificate #3 – Contents of intermediate certificate used to sign certificate #2)
Note: do not include the root certificate in the chain
This allows you to set the origin location for your CDN site.
The origin is the location where the original files are located that will be made available through the CDN.
Clicking the Edit-button will present you with the following dialogue, allowing you to set the origin location.
The CDN accepts:
- Full domain names like “http://yoururl.com”.
- Sub-domains like “http://origin.yoururl.com”.
- Full length URL’s like “http://origin.yoururl.com/video/1080p/”
- For a wildcard match: The origin may contain a ‘$’ which will be substituted with the value of ‘_’ from the site name. e.g.. a site named “_.cdn.yourdomain.com” may have an origin of “http://$.yourdomain.com” which will cause requests to video.cdn.yourdomain.com to use origin http://video.yourdomain.com
This allows you to set which protocol is active for the Site. Clicking the Edit-button will present you with the following dialogue, allowing you to set the protocol to be used. Options are HTTP, HTTPS+SPDY or Any
Accessing content on a protocol which is not enabled will return a HTTP 403 Forbidden response
Only available for Account Managers
This allows you to change the owner of the respective site. As an account manager you can assign a site to another user or account manager. Press “Change” to bring up the following dialogue
Select the user you want to assign as the new owner of the site and press “Set New Owner” to confirm and save your selection.
This section allows you to check if your Site’s DNS is properly set up. Hit “check” button to initiate check.
In case if your DNS is properly configured you should see confirmation
Otherwise you will see warning message and will need to check your DNS setup
Use this section to set limits to the use of the site in terms of speed or geo-access.
This allows you to set a limit to the speed files are served from the CDN to the end users.
Note: this is a limit for each individual client connection, not a global limit
Options include the possibility to send the first part of a file at full speed and applying the rate limit after that. (Tip: Useful in VOD streaming scenarios to fill initial buffers quickly but afterwards restrict the speed to match the bitrate of the video to avoid wasting bandwidth if the end user does not watch the whole video)
Clicking the Edit-button will present you with the following dialogue
“Limit After”: The size of portion that will be full speed. The rate limit will be applied after this portion. (Leave blank for the set rate limit to apply to all data.)
“Limit”: The rate limit that will be applied. (Leave blank to send data at maximum speed.)
This allows you to make the site and all its content on the CDN inaccessible to certain countries (based on Geo-IP). Users in any of the countries that have been blacklisted will not be allowed to view any content on this specific Site.
Clicking the Edit-button will present you with the following dialogue, allowing you to select which countries to blacklist:
Scroll down and select the countries that you want to blacklist one by one.
This allows you to restrict access to ALL countries except the ones that are whitelisted.
Selection of the countries works the same as described in the previous section about the Blacklisting feature.
Use this section set advanced configuration items for each respective site
Encrypted URL Key
This allows you to set the encryption key used to create encrypted links for your site.
Encrypted links are a way of protecting your content from “hot-linking” and also setting variables on a per-link basis (such as a speed limit).
See Encrypted Links Introduction for more information
Clicking the Edit-button will present you with the shown interface, allowing you to set the key to be used.
Leave the field blank if you do not want to use encrypted links.
Enter the chosen key in the text field and press to save.
This allows you to determine which file-types you would like to have compressed using Gzip before being sent to client.
Files will only be compressed if the client browser supports gzip Content-Encoding, otherwise they will remain uncompressed
Clicking the Edit-button will present you with the following interface, allowing you to select the file-types you would like compressed
Predefined file-types. File-types for “.js”, “.css”, “.html”, “.htm” and “.txt” have been pre-defined and will show up when the field is clicked. They can be selected one-by-one by clicking no them.
Custom file-types. You can add more file-types by entering the extension in the text field under “Custom extensions”. To enter multiple extensions please separate them using a comma. (Note: do not use spaces)
<?xml version="1.0" encoding="UTF-8" ?> <!DOCTYPE cross-domain-policy SYSTEM "http://www.adobe.com/xml/dtds/cross-domain-policy.dtd"> <cross-domain-policy> <allow-access-from domain="*" secure="false"/> <site-control permitted-cross-domain-policies="all"/> </cross-domain-policy>
If you would like to override this default response, enter your own crossdomain.xml here
Clicking the Edit-button will present you with the following dialogue, allowing you to enter (or paste) your crossdomain.xml code: Press to save for it to take effect
VOD Transmuxing types
Include the query string as part of the cache uniqueness
Pass the query string through to origin while caching
Allow single CDN loop
This sections contains a set of actions you can take to investigate your CDN site or intervene in what content has currently been cached.
This allows you to retrieve Raw CDN log files for this site. The Log files are formatted using the NCSA Common log format, containing the following information, in this order: $remote_addr – $remote_user [$time_local] “$request” $status $body_bytes_sent “$http_referer” “$http_user_agent”
Pressing the View-button will bring up the shown interface that lists the individual raw log files for each day.
Use the Download-button located on the right side to download the raw log file for that specific day.
This allows you to check the current cache-status of an individual file on the CDN. Click the “check” button to open the following dialogue.
Enter the Origin URL of the file you would like to check and press “Check” to show the status of the specific file across the different CDN pops. It will also show the time the file was last checked, modified and its size.
This allows you to purge files from the CDN cache. Options are to purge a single file, purge all cached content or to purge a list of files from a .csv file.
Note: Purging a very large number of files may take a few seconds to complete across the network.
This option allows you to purge individual files.
Enter the Origin URL of the file you would like to purge from the cache and click “Purge” to purge the file immediately.
This option allows you to purge all files matching given regular expression
This option allows you to purge all files from the CDN cache.
To proceed, check the check-box and click “Purge All Files” to purge all files from the CDN cache immediately.
This options allows you to purge files from the CDN cache using a CSV list.
To purge a list of files, please create a CSV file that holds all origin URL’s. Click “Choose file” to select the CSV file you created and click “Purge” to purge all files in the list from the CDN cache immediately.