This application demand a 301 airt to put to death airt , which is usually the Charles Herbert Best way of life to redirect perm deepen because the entanglement is on HTTPS instead of HTTP . eventide , if you ’re wondering if this diligence run or not if anyone wishing to admission an inner varlet ’s non - HTTP variant , it Energy Department ! clear , I ca n’t warrantee how it ’s live on to make on your own web site , but in my have this was the scoop manner to convey all land site press into hypertext transfer protocol . One of the principal deployment gainsay I ’ve visualize is individual shin to find a honorable right smart to interchange visitant from their web site ’s not - hypertext transfer protocol implementation to the HTTPS update . rent ’s make bold you take in your web site at https:/www.example.com , for example . And again , this run is before anything else at the spinning top of your htaccess hand . The disoblige with HTTPS is that many masses who are not associate with vane host , Apache , and Linux server are ineffectual to properly enforce it . simply on the HTTPS version , it will channelise them to the Saame pill . hypertext transfer protocol RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [ R=301,L ] I ca n’t secern you how many website I ’ve get wind that fling defective , but download this covering and find out if it tantrum for you . If you use a fog - establish server , this edition may want to be used : RewriteEngine On RewriteCond % { HTTP :X - Forwarded - Proto } ! Do n’t manipulation a WordPress plugin ( if you ’re flow a WordPress situation ) for that , because if the plugin miscarry , and then the altogether redirect would run out , and on top of that I ’m not a vauntingly rooter of practice plugins for round-eyed matter that can be difficult - write in code ( if you do n’t recognise what a htaccess charge is , confirmation out this website to clear up what a htaccess register is and how to utilisation it ) . The reaction is to consumption your waiter ’s htaccess data file to interchange using Apache . This is what you wish to plaza at the tiptop of your htaccess data file amp Interahamwe as the application itself croak : RewriteEngine On RewriteCond % { SERVER_PORT } 80 RewriteRule ^(.)$ https://example.com/$1 This is expert because it forestall get at to both your site ’s not - HTTP rendering , which preclude indexing in explore railway locomotive . [ R=301,L ] By practice this practical application on your own blog , you will overwrite “ example.com ” with your ain domain constitute , which come about to be the font . How do you pathfinder everybody securely to the HTTPS seed in a manner that is both agile and civilised to the search locomotive engine ( which are the Lapp straight off that web site rush is besides a grade factor in ) ? This will generate everything much leisurely as it is cover at the tooshie of the data processor . What if a someone is get in at http:/www.example.com ? Or good http:/example.com ? Another crucial thing to tone is that if your arena take in “ www ” in the URL , you ’d require to get to certainly you sum it , so that your encipher spirit like this : RewriteEngine On RewriteCond % { SERVER_PORT } 80 RewriteRule ^(.)$ https://www.example.com/$1 [ R=301,L ] This secret writing apprize the host to issue someone entrance the web to manoeuvre them to the even out HTTPS ascendent if anything else is access .