You might not have noticed, hopefully it went smoothly for everyone.
It seems like a small change, just an extra s, but it means that the connection between your browser and the server running this site is now encrypted.
Every page on both TheBeachcats.com and Catsailor.com should load as https://www... and show the secure lock or key icon in the browser address bar. I had to change thousands of hard-coded non-secure links from http: to https: to avoid "not secure" or "Mixed Content" warnings. So if you spot any pages that don't show the lock, then let me know.
On desktop browsers you should see in the address bar.
Chrome: solid green Lock Icon and the word Secure
Firefox: solid green Lock Icon
Internet Explorer: silhouette lock icon
Microsoft Edge: lock outline icon
Safari: solid lock icon
Mobile device browsers have various ways to distinguish between secure and insecure connections.
If you type the url without the https or the www it should automatically convert to
https://www.thebeachcats.com or https://www.catsailor.com .
If you have links or bookmarks to either site, please update them to use the secure link.
For the fellow geeks out there, I am using Let's Encrypt on my servers to provide security certificates.
https://letsencrypt.org/
If you have a website, it should be using a secure connection, and not just for security since Google is now ranking secure sites higher.
If you need help with this or need a new "web guy" please contact me through website.
https://www.MemphisGuru.com
i have an odd error (chorme on a pc)
"This page is trying to load scripts from unauthenticated sources - left side of url bar
doesn't seem to be effecting anything on the website, but i think it's making my catamaran slower
perhaps you are still calling scripts from an http
Try clearing your browser cache for the domain.
I did have to change tons of css and script references in the code and in the css files to prevent that type of mixed-content warnings so I could easily have missed some.
Please take a look at view-source and see if you spot anything being loaded by http:// I can't find anythng.
A side-effect of the work on this is that, for me, the forums are not throwing JSON errors any more when I post.
Anyone else notice any difference?
Saw lots of links to on site http: references
i.e line 340
Recommended signature format and instructions.
http://www.thebeachcats.c…/Forums/Forum-Signatures
only one calling a script was your google one (line 626)
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
Cool, thanks!