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.
Got it solved. Turns out the server was hosted behind a reversed proxy, causing WordPress not knowing it was running over https. Once I knew this, I found the solutions in the official documentation: http://codex.wordpress.org/Administration_Over_SSL (under “Using a Reverse Proxy”) This was needed in my wp-config. define(‘FORCE_SSL_ADMIN’, true); if ($_SERVER[‘HTTP_X_FORWARDED_PROTO’] == ‘https’) $_SERVER[‘HTTPS’]=’on’
I had exactly the same problem and the solution for me was to add these lines to /etc/apache2/sites-enabled/default-ssl.conf, which is my SSL-enabled website’s configuration file: <Directory /var/www/html/> AllowOverride All </Directory> Of course, this assumes DocumentRoot /var/www/html. Change accordingly if is this is different in your setup. The thing is that WordPress uses .htaccess rules to … Read more
If you don’t have access to your cPanel, or don’t know how to make a database change, you can instead add these 2 lines to your wp-config.php file: define( ‘WP_SITEURL’, ‘http://example.com/’ ); define( ‘WP_HOME’, ‘http://example.com/’ ); You’ll of course want to change the urls to your actual urls. Just make sure you don’t have the … Read more
You either go site wide HTTPS, or should not bother with it in the first place. Should it be for all access or just for logged in users depends on the profile of your traffic. If most traffic will come from registered users, then just go unconditional HTTPS as doing it conditionaly just for logged … Read more
I have recently solved my issue, I went on wordpress support, found my issue and how to fix it. I installed the SSL Insecure Content Fixer plugin and chose in the plugin settings for SSL Detection, the setting that was recommended. Then, I went to the settings and set my WordPress and site URL to … Read more
Installing the WordPress HTTPS plugin should take care of it.
After a little more reading via the WordPress Codex, I discovered that I was calling the favicon incorrectly. It should be called like this: <link rel=”shortcut icon” href=”https://wordpress.stackexchange.com/questions/240069/<?php echo get_stylesheet_directory_uri(); ?>/favicon.ico” /> Using get_stylesheet_directory_uri() checks for SSL.
try installing this WordPress plugin. http://wordpress.org/extend/plugins/wordpress-https/installation/ but do read the installation instructions as it has some extra things to do after activating the plugin.