There is no filter when a script is registered, so it is hard to track that down. Use a full text search in all your theme and plugin files to find the source. In addition, you can filter the URL before it is printed: add_filter( ‘script_loader_src’, function( $url ) { if ( 0 !== strpos( … Read more
To globally redirect all your pages to HTTPS add the following lines to your .htaccess: # Globally force SSL. RewriteCond %{HTTPS} off RewriteCond %{HTTP:X-Forwarded-Proto} !https RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] This should be placed directly after RewriteEngine on if you have no previous rewrites.
This really belongs on ServerFault, StackOverflow or Webmasters… But basically, you need to add something along these lines before the WP rules begin: RewriteEngine on RewriteCond %{HTTPS} off RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]
Not sure what plugin you are using to enforce SSL, but I would disable it to prevent conflicts with the possible solution below. To make sure you’ve updated all of your URLs to the HTTPS, do the following: Go and download Interconnect IT’s Database Search & Replace Script here Unzip the file and drop the … 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
If possible, you should try and fix the cause of this error – invalid SSL certificates. But there are some instances where this is not possible or desirable. One obvious one being development sites using a self-signed SSL certs. One way around this is to set $ssl_verify to false before line 1161 of wp-includes/class-http.php: curl_setopt( … Read more
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.