Issue with SSL

The plugin works fine with SSL (I am running it on 3 sites with SSL enabled right now).

Can you tell me a little more about your install – WP version, Plugin Version, theme, etc. Also how many and what type of redirects you have – and an example of one that does not work?

If you do not want to post here, send to [email protected] and reference this post.

Regards,
Don

I am also experiencing an issue with this plugin and SSL. All quick 301 redirect requests redirect to my 404.

Right now, I have to directly edit my htaccess and enter Redirect rules to get redirects working.

I am running WP multisite 4.0. Using your plugin 5.0.6.

I have configured my site to use SSL following this guide: https://prosauce.org/blog/2010/08/enable-complete-support-for-ssl-on-wordpress/

I have added this to my htaccess:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^mydomain\.com [NC]
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://mydomain.com/$1 [R,L]

Please advise.

With the rewrite rules mentioned above in htaccess – HTTPS is forced:

Doing this…
Request: /slug/
Destination: https://google.com
… would result in a 404 when the slug url is accessed.

Removing the rewrite rules to unforce HTTPS…
The redirect would only work with using HTTP to access the slug page. Will not work with HTTPS for that slug page.

The only work to get the redirects to work is to actually specify the ENTIRE HTTPS URL in the request field:

i.e. https://mydomain.com/slug/

So it looks like the paths in the request field relative to ROOT does not work for HTTPS.

I did some more testing on a freshly installed WP site and discovered that the issue is actually something else.

The plugin WORKS fine with SSL. The problem is that the redirect slugs are NOT interchangeable between HTTP and HTTPS.

For instance, if my WP site is installed as a HTTPS site with domain https://domain.com….

Doing this…
Request: /slug/
Destination: anywhere

…will work as long as https://domain.com/slug/ is called.

However, https://domain.com/slug WILL not work and will result in a 404.

The workaround is to enter a second redirect for the HTTP with the full URL path like this:

Request: https://domain.com/slug/
Destination: anywhere

Then this will work when http is called.

If the dev sees this, is it possible to add a feature where HTTP and HTTPS can be interchangeable?

Or is this something that’s more related to htaccess? Please advise. I’d definitely do not want to enter two sets of redirection rules each time…