Content Delivery Networks (CDN)

If you would like to user Microsoft Azure Blob storage as a source or destination, please follow these simple steps:

- Use a standard URL to access a source or destination locatlon: http(s)://[access_key]@[account].blob.core.windows.net/[container]/path
- Ensure to URL encode any special characters within the access_key 

Here is one example of a properly constructed URL:
http://P9DM47UTCF%2BQJZXl0uWy28J4jBdgnYv0SJPh%2FR%2AWCFOLPTBHuyeXtMfDOU75Wd0Yl2xm67vVTYGVAWSEDRdcw%3D%3D@[account].blob.core.windows.net/encoding/file.ext

Special notes for Azure Blob Storage:

- Your container name must consist of 3-63 characters, digits or sign "-". Please make sure to not have a "-" at the beginning or end of your container name.  
- If you do not include the access_key within your URL, they will be interpreted like casual urls. files in such urls should be public readable.

Encoding.com works with all of the major CDNs available.

Pick your favourite, plug in your delivery details and you're good to go!

If you're looking for a concise list of CDNs, please browse to http://www.cdnlist.com

When using encoding.com to generate video for hddn.com, video can be directly uploaded to the FTP service hddn provides. HDDN requires passive FTP mode, so the path will require the URL string to append ?passive=yes.

For example: ftp://username:password@ftp.hddn.com/path/filename.ext?passive=yes
This will solve any issues with upload errors from our service and get the files delivered to hddn.com properly. This also applies to watch folders.