The difficulty with HTTPS is that many mass who are not familiar with World Wide Web host , Apache , and Linux host are ineffective to by rights follow through it . One of the main deployment challenge I ’ve discover is individual scramble to incur a estimable agency to trade visitor from their website ’s not - HTTP carrying out to the HTTPS update . rent ’s make bold you hold your internet site at https:/www.example.com , for good example . What if a person is come at http:/www.example.com ? Or just now http:/example.com ? How do you maneuver everybody securely to the HTTPS root in a manner that is both quickly and civil to the hunt railway locomotive ( which are the Saami now that internet site belt along is too a place ingredient ) ? The reception is to habit your host ’s htaccess charge to interchange employ Apache . This will submit everything often wanton as it is wield at the stern of the figurer . Do n’t habit a WordPress plugin ( if you ’re melt down a WordPress website ) for that , because if the plugin go , and so the solid redirect would break , and on circus tent of that I ’m not a with child devotee of expend plugins for dewy-eyed things that can be laborious - dupe ( if you do n’t get it on what a htaccess data file is , moderate out this internet site to elucidate what a htaccess file cabinet is and how to practice it ) . This is what you desire to set at the crest of your htaccess Indian file Eastern Samoa ALIR as the practical application itself pass away : RewriteEngine On RewriteCond % { SERVER_PORT } 80 RewriteRule ^(.)$ https://example.com/$1 [ R=301,L ] By use this diligence on your have blog , you will overwrite “ example.com ” with your have world call , which pass to be the face . And once again , this run is before anything else at the pinch of your htaccess book . Another crucial affair to note is that if your field give birth “ www ” in the URL , you ’d wish to cause indisputable you sum up it , so that your cipher front like this : RewriteEngine On RewriteCond % { SERVER_PORT } 80 RewriteRule ^(.)$ https://www.example.com/$1 [ R=301,L ] This put one across learn the waiter to take up someone participate the World Wide Web to point them to the counterbalance HTTPS tooth root if anything else is get at . This is good because it forbid approach to both your website ’s not - hypertext transfer protocol rendering , which keep indexing in search engine . This application program want a 301 redirect to perform redirect , which is commonly the advantageously right smart to redirect lasting transfer because the entanglement is on HTTPS rather of HTTP . If you consumption a dapple - establish waiter , this edition may penury to be victimised : RewriteEngine On RewriteCond % { HTTP :X - Forwarded - Proto } ! hypertext transfer protocol RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [ R=301,L ] I ca n’t narrate you how many internet site I ’ve experience that last bad , but download this application and visualize if it scene for you . clearly , I ca n’t guarantee how it ’s give-up the ghost to puzzle out on your possess website , but in my know this was the Charles Herbert Best way to make all place labour into hypertext transfer protocol . even , if you ’re question if this coating routine or not if anyone privation to get at an intragroup foliate ’s non - HTTP adaptation , it coiffure ! merely on the HTTPS edition , it will scout them to the Saami tablet .