Related

If i've disabled xml-rpc and can't update my theme anymore how do I reactivate it? Question Question
Hello. Unable to execute search on website zopodeals.com yet its working fine on another shared hosting provider. Question Question

Question

Redirect rules in .htaccess for multiple Wordpress installation

Posted July 4, 2017 5.7k views
ApacheWordPressUbuntu 16.04

I currently have 2 Wordpress installations as:

https://www.example.com
https://www.example.com/subdirectory

The .htaccess for https://www.example.com has the following rules:

RewriteEngine on
RewriteCond %{HTTP_HOST} ^example.com [NC]
RewriteRule ^(.*)$ https://www.example.com/$1 [L,R=301,NC]

RewriteEngine On
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

And the .htaccess of https://www.example.com/subdirectory looks like this:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

How do I force https re-direct as per the following:

  1. http://www.example.com/subdirectory to https://www.example.com/subdirectory
  2. http://example.com/subdirectory to https://www.example.com/subdirectory
  3. https://example.com/subdirectory to https://www.example.com/subdirectory
Add a comment
By:
shalintj
Add a comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer
hansen July 4, 2017

Hi @shalintj

Simply just add the following to the top of the .htaccess of /subdirectory:

RewriteEngine on
RewriteCond %{HTTP_HOST} ^example.com [NC]
RewriteRule ^(.*)$ https://www.example.com/$1 [L,R=301,NC]

RewriteEngine On
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]
Reply Report
  • shalintj July 4, 2017

    Tried that. It redirects to the root folder then. I mean if I add the rule that you mentioned in the sub-directory’s .htaccess, this is what happens:

    https://www.example.com/subdirectory to https://www.example.com

    Reply Report
    • hansen July 4, 2017

      That’s strange, it should use the full URL in the regular expression. Try this:

      RewriteEngine on
RewriteCond %{HTTP_HOST} ^example.com [NC]
RewriteRule ^(.*)$ https://www.example.com/subdirectory/$1 [L,R=301,NC]

RewriteEngine On
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^(.*)$ https://%{HTTP_HOST}/subdirectory/$1 [R=301,L]
      Reply Report
      • shalintj July 4, 2017

        It worked. Thanks a lot.

        Why do you think the earlier one didn’t work?

        Reply Report
        • hansen July 4, 2017

          I’m not sure. I haven’t used Apache for several years. Nginx is just easier to figure out, but takes a little time to get used to if you have used Apache for a long time.
          My guess would be that it might have something to do with RewriteBase, but that’s required for the other WordPress rewrites to work - otherwise those needs to be changed, so it’s tomato-tomato.

          Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help