Found a problem. Basically there were 2 options that forced my permalinks to https: Settings > General: change the site url from https to http. SEO by Yoast plugin, under section permalinks needed to change Canonical Settings to force HTTP.
I know this is a rather old question but I’ll leave my findings in case someone else needs to make this work. Your approach helped me implement a similar setup. In order for Varnish to keep a separate cache for http and https versions of the same page you simply need to add the X-Forwarded-Proto … Read more
FORCE_SSL_LOGIN is marked as deprecated since 4.0 in source (you might have jumped over that bit). So it does now force all of admin to SSL and past behavior for it seems to no longer be available.
Switch to full SSL for everything. Seriously, it’s way easier than dealing with mixed content.
First one of your variations is the cleanest. You can test your htaccess rewrite rules here: https://htaccess.madewithlove.be/ Important thing about R=301, this means the redirection is permanent.
In the active theme I found the redirection in header.php Once commented out the issue was resolved. if($_SERVER[“HTTPS”] != “on”) { header(“Location: https://” . $_SERVER[“HTTP_HOST”] . $_SERVER[“REQUEST_URI”]); exit(); }
you’d be better not using a plugin and editing the .htaccess file (in root of website) something like this at the top: RewriteEngine On RewriteCond %{HTTP_HOST} ^somesite.com [NC] RewriteRule ^(.*)$ https://www.somesite.com/$1 [L,R=301] so your .htaccess file might look something like this: RewriteEngine On RewriteCond %{HTTP_HOST} ^somesite.com [NC] RewriteRule ^(.*)$ https://www.somesite.com/$1 [L,R=301] # BEGIN WordPress <IfModule … Read more
This is somewhat of a guess, but it is probably a result of the web server configuration. What your server probably does is to see that the request want to load the blog url of the site. It checks out and sees that blog is a directory adds a slash and redirects to it. Now … Read more
RewriteCond %{HTTP_HOST} ^xxxz.com.qa [NC,OR] RewriteCond %{HTTP_HOST} ^www.xxxz.com.qa [NC] RewriteRule ^(.*)$ https://www.xxxz.com.qa/$1 [L,R=301,NC] This will result in a redirect loop as it will repeatedly redirect https://www.xxxz.com.qa/<url> to https://www.xxxz.com.qa/<url> again and again… If you want to redirect from HTTP then you need to check that the request was for HTTP before redirecting to HTTPS. For example: RewriteCond … Read more
You can use the define(‘FORCE_SSL_LOGIN’, true); options provided by WP. You just have to add the line in wp-config.php. Here is the link to wordpress codex, in case that you need more examples.