Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top


I need to host some files on our CDN (edgecast) which will be available over HTTPS. I would usually accomplish this by using the provided CDN url, i.e.

The Problem

I recently tried to use a CNAME so instead of using an ugly URL I could use a sub domain of the current site. I have tried to set this up but keep getting a certificate error as the certificate seems to only be issued to the * url and not the edgecast CDN url its resolving too.

I have tried to contact edgecast but they have been disgustingly slow at responding. Maybe if I bought an SSL certificate for the edgecast domain name from them, but then I figured it would invalidate due to the CNAME that was pointing too it.

share|improve this question

Unless you're a large enterprise customer, getting a CDN to set up an SSL on their systems for you is very unlikely. This isn't something you can do for them, their servers need to be configured with your SSL certificate and private key to present it on your behalf.

No one really cares about the URLs of the images on your site, anyways.

share|improve this answer
It's not for a website, the URL is being placed into an application and this way I can have control over the URL. If, for example, I wanted to change CDN providers I wouldn't need to update my application on peoples devices. – Hzmy Apr 18 '13 at 21:13
It would cost you a bit in latency, but you could have application point at a server (or servers) you control that does nothing other than sends out HTTP redirects to the CDN. – Zoredache Apr 18 '13 at 21:19
But then the resources would be served over HTTP which sort of defeats the purpose. Otherwise I would have just used the HTTP CDN URL. – Hzmy Apr 18 '13 at 21:27
@Hzmy I'd suggest having the CDN URL being an application setting. Have your app periodically check a URL for an update to the CDN path. – ceejayoz Apr 18 '13 at 21:28

It turned out that I needed a wildcard HTTPS certificate for * and this then needed to be placed on the CDN server.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.