We’re not far into having SSL at our disposal and before I go any farther I just want to say once again, thank you Carson and Kyle. Those are some mighty big doors that you opened with that one!

Spy Thriller, Anyone?

Occasionally I’m seeing some people having issues with turning SSL on only to have the “green padlock” evade them. Hmm, Green Padlock. Sounds almost like a super-hero or a spy novel, doesn’t it?

Typically the browser would indicate that the site is/was insecure because something somewhere was still being served up through http which resulted in the “mixed content” messages. We’ve got secure stuff that requires the secret ring-knock to let it pass back and forth. And then we’ve got non-secure stuff that makes us leave the back door unlocked. Not good.

A lot of us have found our solutions and I’m guessing that for every thousand of us there are a thousand ways to fix it. Some used plug-ins. Some used external websites to locate the mixed content offenders.

Blame it on my IT background, but I’ve got to look at the nuts and bolts of why things happen. Sure, I could have taken that URL and had it all fixed in a few seconds. But I wouldn’t understand the “why” and the “what.”

What I ended up with is what I want to share in this training: a brief overview of locating the non-secure content using Chrome and fixing it. So let’s get to it!