: What are the dis-advantages of installing the ssl certificate for the naked domain? I might buy an SSL certificate for my sie. I know that it will help me in many ways. But will there

@Murphy175

Using relative links (which in ssl is therefore ssl) is one method. Omitting the protocol from links is another, so your links would be:

//other-website.com


I use protocol relative links in my (personal/business) site just for that reason. I hope to convert it to all ssl before too long and why worry about it if it works?

Look into the SPDY protocol and also http(s) headers for caching your content or you might get into problems with site speed.

Vote Up Vote Down

@Carla537

You will absolutely run into issues if you are loading content outside of your secured URL. If it's from larger sources - such as loading jQuery from the Google servers, most of them have SSL so you can include that securely. Otherwise it's best not to have the entire site secured if you are going to include external content. Just secure the pages where sensitive information is being transmitted and don't include any external content on those pages.

If you are still running into trouble with unsecured content warnings, I highly recommend using Fiddler as a debugging tool to help you find the content that's not coming in secure.

If you will be using subdomains that need secure, you should consider a wildcard SSL certificate, which secures all subdomains of a single domain. They're a bit more expensive, but worth the price if you're going to be securing several subdomains.

Vote Up Vote Down