hey guys, i'm having an issue with my ssl and here is the story. i got a ssl from godaddy and my hosting tech guys installed it for me. a day after that i was told by friend of mine that installing a ssl on my index page is a mistake because this will literally "kill" the site. so after few more consultations i was convinced to revoke the ssl and get another one which will be for secure.domain.com aka login page. next day i got new ssl(already assigned for secure.domain.com) and asked my hosting guys to create the sub-domain where the same will be installed. so far, everything after that was fine. now, this issue i'm having right now is when i asked the hosting guys why the site isn't show properly when i type www.domain.com they told me "The ssl is successfully setup for the secure sub-domain. You should remove the https://domain.com from the links on your front page because this will cause issues with the page loading". and here, i'm completely lost. i thought it's some kind of misconfiguration of the .htaccess file that caused me the problem or may be i have to create a forder "secure" under public_html...i'm in desperate need of your valuable tips and help, guys. thank you so much in advance. p.s. if somebody have an extra spare time i'd love to do 'remote-desktop' session in order to escape from this annoyance. pm me.
If you have installed SSL on sub-domain then you can not access your main domain using https. It will only work for your sub-domain (https://sudomain.domain.com) only. If you want to use SSL on domain as well as all subdomains then you will need to purchase wild card SSL certificate. Kailash
Hey Kailash, the SSL I bought suppose to have only one mission to secure the connection after the user login/sign up and everything from there on. So the home page can be without SSL which means a normal http connection. I value your time answering to my post so Thank you very much!
Your friend was probably misinformed. SSL pages require some extra CPU activity to encrypt and decrypt the communications but the amount of extra CPU activity is not all that great. Certainly not enough to "kill" your site. If it ever does become a problem, you can get crypto accelerators (like 3D video accelerators in your desktop machine) that can handle the SSL encryption and decryption. We got to benchmark some of these at my previous work and they increased the number of SSL connections we could handle by 35x. There is no reason that http://www.domain.com, https://www.domain.com, https://secure.domain.com, http://domain.com and https://domain.com can't all work at the same time. The only catch is that you need a separate certificate for each domain or subdomain so it's best (cheapest) to restrict it to just one. If requesting https://domain.com doesn't work and you have a certificate for that domain, it is the fault of your tech guys and they need to pull their fingers out and do a competent job. What they probably meant was that you should request http://domain.com rather than https://domain.com because your certificate is currently only valid for https://secure.domain.com. If you have any links on your site that point to https://domain.com you should change them to http://domain.com.