Skip to main content

CDN Control

CDN Control

In order to access your objects through the web, you must enable the CDN for each container you wish to make public.  The first thing to do is to visit the CDN Control page where you will see a list of all your containers and a brief summary of whether they've been made public (i.e. CDN has been enabled or not), if there is a TTL (time-to-live) figure specified, whether directory listings are enabled and whether indexes are enabled.

Status of CDNs

Enabling and using CDNs

  • Click on the Manage link to visit the container's CDN properties page.
  • To enable the CDN, click the Enable CDN tickbox - the URL listed above is the URL that your content will be delivered to.
  • The TTL (time to live) setting specifies how long the content in the container will be cached.  If the data in your container doesn't change very frequently, you should set a higher figure.  3600 seconds is about average.
  • If you want to allow people to browse the directory contents of each container via the web, click the Directory Listing tickbox.
  • If you want to serve a very basic index file (HTML code ONLY) within the root of each directory, click the Index File tickbox and then fill in the name of the index file in the Index Filename textbox.
  • A customised "not found" (HTTP 404) page can be served if required. Tick the Custom 404 tickbox and stipulate either an absolute or a relative path in the 404 file path textbox.  If an absolute path is provided, the file on this path will be shown if any requested file is not found throughout the whole container. If a relative path is provided, the 404 file will be served from the same directory as the requested file.  Providing a relative path allows you to serve different "not found" pages for different directories. The 404 file should contain HTML only.
  • Cross-Origin Resource Sharing (CORS) can be enabled per container, setting the content of the header that will be sent by the CDN. Please read how to enable CORS (external site).

Mapping your own domain to the CDN URL

If you want to access your content using a custom domain (e.g. rather than the generic:

you'll need to create a CNAME in DNS to point to  An example of this using Memset's DNS Manager is shown below:

Using the CDN in a secure site

We currently don't support the installation of third party certificates to access to the CDN service over HTTPS, but you can still use the default domain that includes its own valid SSL certificate.

Following out previous example the secure URL for this container would be:

All this information is available in the CDN Control page, including the specific URL for your container.

Last updated 18 January 2016, 09:59 GMT