Our CDN Basic service is made for ease of implementation. There is no API to learn and the default settings should work for you right out of the box. To start delivering your content via CDN Basic, just change paths on your web pages to point to your KisoLabs CDN hostname:
If you will be using CDN Basic within your SSL-protected (HTTPS) pages, you must use the method shown under Integrating Using Host Keys.
Let's take this very simple web page at which shows an MP4 video as an example:
To have the video delivered via CDN Basic, add your KisoLabs CDN hostname to the source path of the video:
If your site's content is hosted under the subdomain www, simply add the subdomain to the beginning of the CDN hostname. For example, if your content is hosted at:
Then you should use the CDN URL:
Ensure that www is listed under allowed subdomains in your configuration.
A host key is a unique 8-character indentifier for each host under your domain which will act as an origin for CDN Basic. Instead of the method described for integrating using the host and domain name, you can link to CDN content using your host key:
Let's take this very simple web page at which shows an MP4 video as an example:
To have the video delivered via CDN Basic, add your KisoLabs CDN host key URL to the source path of the video:
If you wish to access CDN content from your SSL-protected (HTTPS) pages, you must use the host key URL format. The URL would be the same as in the example above, but you would replace http:// with https:// .
You may add as many hosts as you wish to your list of host keys. By default, you will have the following host keys configured when you set up your CDN Basic service:
The first host listed ( @ ) is the root of your domain. If your domain were example.com and you have an image hosted at this URL:
You could retrieve that image from the CDN at this URL (where gnc74dia is the host key for @ in the sample screenshot above):
You can add host keys for any number of subdomains (providing that the total number of characters is 128 or less). For example, the following host key entries are all valid:
If your domain were example.com, then (using the sample screenshot above) the following three URLs would return the same image file. The first will return the image from the origin, the second from the CDN, and the third from the CDN using HTTPS:
The CDN Basic configuration is straightforward and easy to use. All of the options are listed below:
This is the number of seconds until your content is considered stale and is refreshed from your server. In other words, the CDN will not keep any content that is older than this number of seconds. If the CDN has a copy of your content that is older than the number of seconds specified, it will remove that content from its cache and obtain a new copy of the content from your sever.
The default cache timeout value is 604800 (seven days), and may have any value from 14400 seconds (four hours) through 604800 seconds (seven days). A smaller timeout value will mean that the KisoLabs CDN servers will request content from your servers more frequently. Likewise a longer timeout will result in fewer requests.
Checking this box and then pressing the Save button will result in the removal of all of your content from the KisoLabs CDN servers. The next time any of your content is requested by an end user, a fresh copy of that content will be cached in the CDN. This will have the effect of increasing traffic to your server(s), but may be necessary when making changes to content on your site.
Only 10 purges of your content are allowed in a 24-hour period. It may take up to 5 minutes for a purge request to propagate across the entire KisoLabs CDN infrastructure.
This is the date and time (in your timezone) on which your content was last purged.
Purge Count (24 hrs)
This is the number of times that your content has been purged in the last 24 hours.
At this time, CDN Basic supports the MIME types and extensions listed below. Attempting to deliver other types of files will result in an error when the files are requested from the CDN.
|MIME Type||Supported Extension(s)|
|text/html||htm, html, php, asp, aspx|
|image/jpeg||jpg, jpeg, jpe|
|audio/x-aiff||aif, aifc, aiff|
|application/postscript||ai, eps, ps|
1 The hosting of files with the extensions exe and msi is not permitted by default. If you need to deliver these file types via KisoLabs CDN, please contact support. They will be enabled for CDN services on a case-by-case basis.
Full text logs for your services are available here.
CDN Basic logs are formatted as space-delimited files with quotes enclosing any field that contains a space as content. The general format of the log is as follows:
Each of the fields is described below:
|Date||date||The UTC date and time of the request. The format is:
yyyy is the 4-digit year.
MM is the month (01-12) with leading zeroes.
dd is the day of the month with leading zeroes.
HH is the hour (00-23) with leading zeroes.
mm is minutes
ss is seconds
|Host||string||The host that was requested. This corresponds to the entry in your Host Keys configuration.
Your zone and the KisoLabs CDN zone are omitted from this value. For example, if a user requests an asset using the FQDN www.example.com.kisocdnb.net, the host field will contain www.
If the root of your zone was requested, the host will be displayed as an at sign (@).
|Host Key||string||The host key that was requested. This corresponds to the entry in your Host Keys configuration.|
|Host Key Requested?||boolean (integer)||This field indicates whether the asset was requested using the Host or Host Key listed in the previous two columns.
0 = Host name was used
1 = Host key was used
|Cache Disposition||string||A two-letter code indicating how the request was handled by the CDN cache:
CA (CAche) - The requested content was delivered from the CDN cache.
OR (ORigin) - The requested content was not found in the CDN cache and was delivered as it was fetched from the origin server.
ON (Origin file Not found) - The requested content was not found in the CDN cache and could not be obtained from the origin server. This indicates that the origin server did not provide the content requested, usually because it presented a 4XX or 5XX HTTP status code in response to the request made to it by the CDN.
DL (DownLoading) - The requested content was already in the process of being downloaded from the origin server, and was delivered from the CDN cache as content became available from the origin download.
OP (Origin Parital) - The requested content had already been partially downloaded from the origin server, but the original download had been interrupted. Part of the content was delivered from the CDN cache, and the remainder was delivered as it was fetched from the origin server. In cases where the origin server does not support byte ranges or the CDN determines that using a byte range would be inappropriate, the content will be downloaded from the origin server in full.
Requests that did not result in any content being delivered begin with an "N" as follows:
NC (No Configuration) - The configuration for the zone was not found. This usually occurs if an invalid host or host key was specified, or if traffic is directed to the CDN before a new service or changes to an existing service can propagate to all CDN servers.
NT (No Timeout / No access level) - The configuration for the zone was found, but it was incomplete and did not include a valid cache timeout and/or access level. This usually occurs if traffic is directed to the CDN before a new service or changes to an existing service can propagate to all CDN servers.
NF (No Favicon.ico permitted) - The file favicon.ico is not supported by the CDN.
NM (Not a valid Mime type) - The extension of the file requested indicates that it is not a valid MIME type. See Supported MIME Types in the CDN Basic documentation for more information.
NE (Not a valid Extension) - The CDN does not support files with the following extensions: .exe, .com, and .bat.
NU (Not a valid URI) - No file extension found or request URI is empty. The CDN does not support default documents.
ND (No Default documents) - No file extension found. The CDN does not support default documents.
If there is no cache disposition for a request, the field will be deliniated with a single dash (-). This is usually the case when the request made by the client is invalid and did not match any of the conditions descibed above.
|Client IP||IP (string)||The IP address of the client making the request.|
|Request Method||string||The HTTP method used to make the request (e.g. GET)|
|Requested Asset||string||The relative URL of the asset requested.
For example, if the client requested http://s3qs2m92.kisocdnb.net/example.html, this field would contain /example.html
|Status Code||integer||The HTTP status code generated by the CDN server in response to the request. Common status codes and their causes are:
200 = Asset found and passed to client.
403 = There was an error fetching the CDN configuration.
404 = Asset was not found on your server and could not be delivered.
|Content Length||integer||The length of the content returned in bytes.|
|Referer||string||The URL of the resource that caused the asset to be requested. Usually this will be the web page that references the asset being requested.|
|User Agent||string||The user agent string that the client's browser passed to the CDN server.|
For the sake of example, four log lines are shown below for the imaginary website located at http://www.example.com.
The meanings of each of the sample lines are discussed below:
A request was made on March 15, 2012 at 11:01:18 PM UTC for the asset at the URL http://www.example.com.kisocdnb.net/pics/products/DSCN00049.jpg. The server responded with the status code 200 (success) and delivered 285,474 bytes of data from the CDN cache. The request was referred by http://www.example.com/products/super_widget.html, and the client made the request using Internet Explorer 9 running on Windows 7.
A request was made on March 15, 2012 at 11:01:20 PM UTC for the asset at the URL http://pp778zr6.kisocdnb.net/pics/products/DSCN00667.jpg. The server responded with the status code 200 (success) and delivered 108,822 bytes of data from the origin via the CDN cache. The request was referred by http://www.example.com/products/amazing_wathcha.html, and the client made the request using FireFox 20 running on Windows 7.
A request was made on March 15, 2012 at 11:01:23 PM UTC for the asset at the URL http://example.com.kisocdnb.net/graphics/home/logo_head.png. The server responded with the status code 200 (success) and delivered 45,020 bytes of data from the CDN cache as the content was being downloaded from the origin. The request was referred by http://www.example.com/index.html, and the client made the request using FireFox 17 running on a Linux distribution.
A request was made on March 15, 2012 at 11:01:24 PM UTC for the asset at the URL http://www.example.com.kisocdnb.net/cgi-bin/incorrect_file.html. The server responded with the status code 404 (file not found) and delivered no data. The request had no referrer, and the client made the request using Google Chrome 26 running on Windows XP.