Well, an easy to way to always redirect the user to secure connection (https://) can be accomplished with a .htaccess file containing the following lines:
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://www.example.com/$1 [R,L]
Make sure that the .htaccess file is placed in root folder of the domain.
You should not force your complete site to be SSL, if at all possible. Only pages that deal with personal/financial information should be SSL enabled, with very few exceptions.
You should not force your complete site to be SSL, if at all possible. Only pages that deal with personal/financial information should be SSL enabled, with very few exceptions.
Very true.. only necessary directories should be forced under SSL, as stated in this thread:
You shouldn't really allow crawling of https pages, as generally they're only used for internal pages, such as login and account information. Why would you want a bot to access a secure connection? (Rhetorical.) Additionally, there is a slight performance penalty for secure pages. There will be a performance loss on secure pages, which is why it is best not to use SSL on pages where you do not need it (i.e. you would need it via your company's client area, but not on a page which is purely to display the features of a product you are selling). It's not only the user experience you'd want to think about when it comes to the "performance loss", but also the fact that search engines will take into account the speed and responsiveness of your website (search engine optimisation) and using SSL where unnecessary can potentially affect your site's SEO in this regard.
Hence one should be careful when letting the entire site redirect to SSL pages.
Rock _a.k.a._ Jack Daniel
Follow eUKhost on Twitter || Join eUKhost Community on Facebook
Make sure you change the folder reference to the actual folder name and be sure to replace www.yourdomain.com/folder with your actual domain name and folder you want to force the HTTPS on.
Comment