: Why do CDNs charge so much for private SSL? I've been looking at various CDN services, and many of them seem to charge a pretty hefty fee compared to the free shared SSL offering. One in
I've been looking at various CDN services, and many of them seem to charge a pretty hefty fee compared to the free shared SSL offering. One in particular, CDN77, is offering private SSL for 0/year.
Why is the price so high? Isn't the only technical difference between a private/public SSL the ability to use a custom domain name? From what I gather, the only difference would be having to send the key/certificate to them yourself, which shouldn't cost nearly 0 a year.
Do they just charge this price because they can?
More posts by @Radia820
1 Comments
Sorted by latest first Latest Oldest Best
Originally, each IP address could only handle one SSL certificate as the incoming SSL connection request didn't specify which host it was trying to access. This has been addressed with the introduction of SNI. While all modern browsers support SNI, older browsers do not and I imagine that the CDN services are still supporting those browsers and not using SNI.
Without SNI, offering a private SSL is costlier as they'll have to assign unique IP addresses to you. IP addresses are a finite resource at this point.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.