If you don’t know already, HTTPS–a secure way for users to connect to any website via SSL–is pretty important. For instance, if you’re not using it while logged into, well, anything, your private data can be up for grabs?
Don’t believe us? Read this. Yikes.
In Facebook’s case, the development team reported months ago an emphasis on HTTPS security for Facebook Applications–and now, finally, a deadline to phase out any HTTP, October 1st. Plus, it helps to know that up to 10% of current Facebook users enable HTTPS browsing–and that, coincidentally, non-secure apps won’t even appear when HTTPS is enabled.
If you develop your own apps, but haven’t made the switch yet, it’s a good idea to get moving; the switch is happening fast. Despite great tutorials online to migrate currently existing apps–alongside new ones–to fit within HTTPS specifications (like this one, here), many users are being left behind. And, unsurprisingly, we just figured out how to make the transition.
We weren’t the first, however, to be frustrated with the transition. Here’s a screenshot of the Facebook developer blog:
Whoops!
Facebook application development used to be simple–anyone could make them. What we’re using today is a definite upgrade, but requiring an SSL security certificate is just making it harder and harder for inexperienced users to make anything work on a smaller scale.
Our problem? This guy:
We use Hostgator hosting, and, besides loving it, our hosting plan comes with an SSL security certificate–a free one! Awesome? Yes. Does it come installed? No. Did I know that? No, I thought it was ready to go–and I spent most of my time tweaking code, trying to fix a problem that didn’t exist in the first place. After a quick email and a few hours of upgrade time, all of our apps (20-30) were HTTPS secure–no more blank tabs!
If you’re having any trouble with an unsecure application, the problem most likely lies with file hosting. And here’s where it really hurts: free hosting with SSL security is impossible to find.
A business owner that doesn’t have an SSL-secured web server isn’t going to pay for one anytime soon; we wouldn’t expect them to. Then again, SSL and HTTPS are a must for Facebook (seriously, did you watch that video? Are all websites that unsecure?).
It’s a Catch-22. Of course, you can just have Bit Social develop and maintain all of your Facebook apps–we finally just figured out HTTPS ourselves.
I think this catch 22 can be solved with the following service – http://www.social-server.com.