And users have nothing to do with vulnerabilities on server and they of course use XP. 😀
I’m planning to buy a well certified ssl 🙂
Hello,
I am SSL-ing my entire site and am running into these four open issues so far:
Insecure URL: http://fonts.googleapis.com/css?family=Amarante
Found in: https://tribyoot.org/
I’m not sure how to ssl the fonts. You would think this would be handled by the functions.php file (protocol relative links).
Insecure URL: http://tribyoot.org/Tribyoot/wp-content/uploads/2014/07/logo-tribyoot-300×1004.png
Found in: https://tribyoot.org/
The above image is determined in the Theme Panel, and the actual link to the image is https://tribyoot.org/Tribyoot/wp-content/uploads/2014/07/logo-tribyoot-300×1004.png, but my “WhyNoPadlock” scan is insisting it’s and http file and not an https file.
Insecure URL: http://tribyoot.org/Tribyoot/wp-content/themes/Newspaper/images/header/elements-menu.png
Found in: https://tribyoot.org/
In the theme files, the elements-menu file seems to be a blank file, but obviously it’s used and output by the theme on my page. How can I SSL that image?
Insecure URL: http://fonts.gstatic.com/s/amarante/v4/7QYOnlvGMVlAzj6iP9gUMPesZW2xOQ-xsNqO47m55DA.ttf
Found in: http://fonts.googleapis.com/css?family=Amarante
I’m guessing this is essentially the same issue as the first one of these four?
I hope you can help me find a way to secure them.
Philip
You need to change site address and home address in wp general settings. Further in admin panel change the urls for logo etc. I you still have problems with the fonts, you ave the full functions.php file to heck around. 🙂
In functions.php the fonts files already choose http or https based on what you use. May be tagDiv team can help.
Cheers
“Force SSL” can cause loop issues.
Ideally you should set redirect option in your .htaccess file if running Apache
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
Google wants ALL pages on a website to load via https, not just home page, as post pages are what mobile users follow from social media shares/links, and more likely found in SERPS, etc.
For the near term, Google is expecting a “transition period” … so, you will be fine if
a) you have changed your default wordpress structure to https (e.g,. via wp-config.php)
b) *all* your canonical links now say https://yoursite.xyz
c) you have SSL cert or pages loaded from CDN with SSL, so lock engages in browser; Chrome will do better job of warning about insecure pieces than Internet Explorer
d) you update your sitemaps with Google
e) setup 301 redirect schema from http to https (as in my example, or similar)
f) you put in a “site change of address” with Google to TELL THEM that the site is officially now https://yoursite.xyz and no longer http://yoursite.xyz
Thought I’d share my redirect code in my htaccess file for having an SSL site. I am redirecting www, http:// etc to https://
RewriteCond %{HTTP_USER_AGENT} libwww-perl.*
RewriteRule .* ? [F,L]
Header set Strict-Transport-Security "max-age=31536000" env=HTTPS
RewriteCond %{HTTP_HOST} ^90\.28\.006\.21 [OR]
RewriteCond %{HTTP_HOST} ^www\.yourdomain\.com
RewriteRule (.*) https://yourdomain.com/$1 [R=301,L]
RewriteCond %{SERVER_PORT} 80
RewriteRule (.*) https://yourdomain.com/$1 [R=301,L]
