If wordpress API gives you http instead of https it means that somewhere your data still contains HTTP, therefor you might need to take a more careful look at what urls are in your DB, for this specific functions you should look at your menus. But probably the simplest way to solve this issue to … Read more
Add the following to your .htaccess.. # force https on the front of the site RewriteEngine On RewriteCond %{HTTPS} !=on RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] ref https://stackoverflow.com/questions/4398951/force-ssl-https-using-htaccess-and-mod-rewrite if on nginx the advice is for the following.. server { listen 80; server_name yoursite.com www.yoursite.com; return 301 https://yoursite.com$request_uri; } refer to http://www.wpbeginner.com/wp-tutorials/how-to-add-ssl-and-https-in-wordpress/ for other areas such as the … Read more
Yeah you need to update more than just the siteurl values if you wish that every reference (post and attachment included) are updated properly. And you can’t update that with simple SQL queries because you are going to break the serialization of arrays. The best thing you can do is use Search Replace DB. Download … Read more
I also had this experience with chrome and firefox, they switch http to https and did not find a way to overcome it, so i used internet explorer in that windows machine. I don’t think you can have ssl on localhost or an ip address, i guess you know it as you used devfoo.pro. SSL … Read more
Please take a look at Administation Over SSL, particularly the “Using a Reverse Proxy” section.
An easy solution is to use .htaccess rules. #Redirect HTTP to HTTPS RewriteCond %{HTTPS} off RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
The answer to this came in part from this answer, which linked to the Codex, advising the following snippet to be placed at the top of the wp-config file: if (strpos($_SERVER[‘HTTP_X_FORWARDED_PROTO’], ‘https’) !== false) $_SERVER[‘HTTPS’]=’on’; Unfortunately, this didn’t quite solve it for me, but I noticed it worked if I removed the if and just … Read more
WordPress checks the return value of is_ssl() before creating URLs using get_bloginfo(). If the function returns true, it creates https URLs. If it returns false, it creates http URLs. From the WordPress source … function is_ssl() { if ( isset($_SERVER[‘HTTPS’]) ) { if ( ‘on’ == strtolower($_SERVER[‘HTTPS’]) ) return true; if ( ‘1’ == $_SERVER[‘HTTPS’] … Read more
Solution 1: Enable mod_header on the server and added this rule to my appache2.conf file: <IfModule mod_headers.c> RequestHeader unset HTTPS </IfModule> Solution 2: Or you need to add the code to fonction.php file of your current theme: function https_chrome44fix() { $_SERVER[‘HTTPS’] = false; } add_action(‘init’, ‘https_chrome44fix’,0);
There are 2 things you must do. If you are using Apache server go to .htaccess and change the Rewrite and RewriteBase engine to RewriteEngine On RewriteCond %{SERVER_PORT} ^443$ RewriteRule ^(.*)$ http://%{HTTP_HOST}/$1 [R=301,L] RewriteBase / RewriteRule ^index.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] If you are using Nginx something … Read more