Title: .htacces ready for https; integrate forwarding
Last modified: May 30, 2018

---

# .htacces ready for https; integrate forwarding

 *  Resolved [hermie1](https://wordpress.org/support/users/hermie1/)
 * (@hermie1)
 * [8 years ago](https://wordpress.org/support/topic/htacces-ready-for-https-integrate-forwarding/)
 * The problem: an http address stored as favorite in a browser, accesses http despite
   conversion to https.
    In the.htaccess the redirection to https is missing. Has
   anyone solved the problem? I can’t do this!
 * My Wp .htaccess:
 * # BEGIN WordPress
    <IfModule mod_rewrite.c> RewriteEngine On RewriteBase /HS/
   RewriteRule ^index\.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond%{
   REQUEST_FILENAME} !-d RewriteRule . /HS/index.php [L] </IfModule>
 * # END WordPress

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Moderator [Steven Stern (sterndata)](https://wordpress.org/support/users/sterndata/)
 * (@sterndata)
 * Volunteer Forum Moderator
 * [8 years ago](https://wordpress.org/support/topic/htacces-ready-for-https-integrate-forwarding/#post-10341316)
 * I use the first example from here:
 * [https://www.inmotionhosting.com/support/website/ssl/how-to-force-https-using-the-htaccess-file](https://www.inmotionhosting.com/support/website/ssl/how-to-force-https-using-the-htaccess-file)
 *  [Dion](https://wordpress.org/support/users/diondesigns/)
 * (@diondesigns)
 * [8 years ago](https://wordpress.org/support/topic/htacces-ready-for-https-integrate-forwarding/#post-10341735)
 * You should also consider adding the following line to your .htaccess file:
 *     ```
       Header always set Strict-Transport-Security "max-age=15768000"
       ```
   
 * [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security)
 *  Thread Starter [hermie1](https://wordpress.org/support/users/hermie1/)
 * (@hermie1)
 * [8 years ago](https://wordpress.org/support/topic/htacces-ready-for-https-integrate-forwarding/#post-10349777)
 * I could solve the problem by changing the.htacces as follows:
    # HTTPS rewrite
   <IfModule mod_rewrite.c> RewriteEngine On RewriteCond %{HTTPS} off RewriteRule(.*)
   [https://%](https://%){HTTP_HOST}%{REQUEST_URI} [R=301,L] </IfModule> # End HTTPS
   rewrite # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase/
   HS/ #This page is located in the subdirectory /HS/ RewriteRule ^index\.php$ –[
   L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule./
   HS/index.php [L] </IfModule> # END WordPress

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘.htacces ready for https; integrate forwarding’ is closed to new replies.

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 3 replies
 * 3 participants
 * Last reply from: [hermie1](https://wordpress.org/support/users/hermie1/)
 * Last activity: [8 years ago](https://wordpress.org/support/topic/htacces-ready-for-https-integrate-forwarding/#post-10349777)
 * Status: resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics