Today, I just added an SSL certificate to my website from GoDaddy.
. . . shortened . . .
I have no idea what to do about those and I don't know if the .htaccess file redirects these link to https:// or if I have to change them all. And if I do, will they all work.
- It is a private weather-website, not a company site selling goods and asking for creditcard and passwords
- It is a LOT of work as some essential information (images or iframes) displayed on our weather-sites come from other resources which do not have https either
- Some scrips are loaded from sites without https, so you have to copy those scripts and make available from your site. Questions: does the author allow that and are you prepared to update the scripts frequently. Yowindow is an example but it is also a Flash script and considered dangerous by default.
Is it doable:Yes, it is easy if you build your own website with only your content you serve directly from your own server.
Yes the forecast scripts a.s.o. can be run from your own site, as long as the icons are available via https.
Yes you can use Chrome inspect (right click => choose "inspect") and see all errors, then change all those http links mentioned to https
But even if you change all possible links to https you have to remove some images as they are not available via https :
http://images.blitzortung.org/Images/image_b_us.pnghttp://www.ssd.noaa.gov/goes/east/eaus/wv-animated.gifOnly when all links to images and .js files are available with https:// you will get the nice green closed lock next to the link
https://www.m82a1.us/wxforecast.phpBut better test with all browsers if they all agree and all of them serve the page with the green lock
===
Important (IMHO): Consider to do it step by step.
When converting from http: to https: you should remove the redcirect http => http in the .htaccess file.
Display every page with http in a browser window
Copy the url to another browser window and change it to https
That way you can compare if the errors are caused by invalid https content and not because a script was not updated.
An example:
https://www.m82a1.us/wxquake.php => does not work with https but also not with http.
You should make the page working under http first, before testing https.
It will take some time, but you will succeed.
===
The Leuven-Template is compatible with https for about 90% now, but I am still waiting for Blitzortung and other important providers to make the switch before releasing a maintenance update. And at this moment, the NWS-NOAA forecast change
(postponed to August) and the NOAA SOAP_server problems and the frequent unannounced changes of weather links have more priority.
Wim