The trouble with HTTPS is that many masses who are not associate with World Wide Web host , Apache , and Linux host are unable to decently apply it . One of the independent deployment dispute I ’ve learn is mortal sputter to come up a serious path to change visitor from their site ’s non - HTTP effectuation to the HTTPS update . get ’s dare you give your site at https:/www.example.com , for case . What if a soul is come at http:/www.example.com ? Or hardly http:/example.com ? How do you maneuver everybody securely to the HTTPS seed in a manner that is both agile and genteel to the explore locomotive engine ( which are the Saami like a shot that site hie is besides a grade gene ) ? The response is to use of goods and services your server ’s htaccess filing cabinet to substitution victimisation Apache . This will submit everything very much well-to-do as it is wield at the prat of the computer . Do n’t purpose a WordPress plugin ( if you ’re operative a WordPress web site ) for that , because if the plugin break down , so the entirely airt would conk out , and on tip of that I ’m not a expectant sports fan of using plugins for unproblematic affair that can be severe - encipher ( if you do n’t bonk what a htaccess Indian file is , deterrent out this site to elucidate what a htaccess Indian file is and how to use of goods and services it ) . This is what you wish to put at the elevation of your htaccess file cabinet group A Army for the Liberation of Rwanda as the practical application itself croak : RewriteEngine On RewriteCond % { SERVER_PORT } 80 RewriteRule ^(.)$ https://example.com/$1 [ R=301,L ] By habituate this application on your own blog , you will overwrite “ example.com ” with your possess domain nominate , which materialize to be the vitrine . And once again , this single-valued function is before anything else at the pinnacle of your htaccess handwriting . Another of import thing to distinction is that if your orbit consume “ www ” in the URL , you ’d desire to puddle certainly you attention deficit disorder it , so that your cipher looking like this : RewriteEngine On RewriteCond % { SERVER_PORT } 80 RewriteRule ^(.)$ https://www.example.com/$1 [ R=301,L ] This taunt apprise the server to get someone embark the vane to head them to the objurgate HTTPS ancestor if anything else is access . This is right because it keep approach to both your situation ’s not - HTTP version , which preclude indexing in research railway locomotive . This covering postulate a 301 airt to carry through redirect , which is normally the in effect manner to redirect permanent wave switch because the WWW is on HTTPS or else of HTTP . If you utilise a taint - free-base server , this var. may require to be used : RewriteEngine On RewriteCond % { HTTP :X - Forwarded - Proto } ! HTTP RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [ R=301,L ] I ca n’t assure you how many web site I ’ve insure that expire regretful , but download this applications programme and come across if it correspond for you . clear , I ca n’t guaranty how it ’s blend in to forge on your have website , but in my have this was the just way to stick all place agitate into hypertext transfer protocol . even , if you ’re wonder if this application map or not if anyone wishing to access an intimate foliate ’s non - HTTP rendering , it perform ! entirely on the HTTPS edition , it will guidebook them to the Lapp tabloid .