I wouldn’t recommend disabling ssl verification – that leaves your system vulnerable to potential man in the middle attacks as explained in this SO post. Also, your use of sslv3 is most likely causing this issue now SPECIFICALLY because Authorize.net identified it as vulnerable to the POODLE compromise. Since that happened, many vendors removed the … Read more
There’s no need to do it the way you mean. There are ways to host multiple SSL websites on a single domain both with Apache and Nginx, and it’s much easier to implement than your idea. Check out these tutorials: https://www.digitalocean.com/community/tutorials/how-to-set-up-multiple-ssl-certificates-on-one-ip-with-apache-on-ubuntu-12-04 https://www.digitalocean.com/community/tutorials/how-to-set-up-multiple-ssl-certificates-on-one-ip-with-nginx-on-ubuntu-12-04
Change the site URL to be HTTPS based instead of HTTP. In other words go fully HTTPS on your site. If you need mixed content solution for serving your HTML both as HTTP and HTTPS you will need some dynamic detection and manipulation of URLs in the contents or serve as protocol neutral url. very … Read more
You can’t right now. This needs to be fixed in wordpress core. Probably this can be temporarily circumvented for a fraction of the problems with a plugin, but it’s much more valuable to invest the time developing something in an actual fix of wordpress.
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.
I just figured out the issue. You need to add the HTTPS/SSL settings before require_once(ABSPATH . ‘wp-settings.php’); in your wp-config.php So the relevant part of your wp-config.php should look like this. define( ‘FORCE_SSL_ADMIN’, true ); // in some setups HTTP_X_FORWARDED_PROTO might contain // a comma-separated list e.g. http,https // so check for https existence if( … Read more
This is a late answer but this works for me: Change the RewriteCond to this RewriteCond %{HTTP:X-Forwarded-Proto} !https Should be like this: RewriteEngine On RewriteCond %{HTTP:X-Forwarded-Proto} !https RewriteRule ^(.*)$ https://yourdomain.com/$1 [R,L]
Use the developer tools in Firefox (or Firebug) or Chrome or Safari or IE to see the errors with specific images. 1) You may need to change URLs of media items in the post/page content to https. Search RegEx is a good plugin to be able to search and replace (optionally with grep) through all … Read more