I’m having a minor problem with Mixed-content on HTTPS served pages on our site, when we include the http://platform.twitter.com/widgets.js
Apparently Twitter doesn’t have a valid certificate — but hopefully I am mistaken.
Do any of you have a solution to the problem. I’ve searched here and on google for a related problem, and have found:
- Serve the file myself, via HTTPS (but this gives me something I’ll need to maintain)
- Exclude the file from my pages, when serving via HTTPS (which means I lose functionality)
Suggestions ?
Update
See resolution on accepted answer below.
Everything said here before is no longer true. The main culprit, the
widgets.jsfile from Twitter is now served via HTTPS with a valid certificate.See for yourself: https://platform.twitter.com/widgets.js
In other words, you can now have your Twitter buttons working over HTTPS without any problems!