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
A good solution for this kind of thing is to leave the http:
or https:
out of the src
or href
attributes of included content. Usually the browser can figure out which protocol to use.
In your case, you can use //platform.twitter.com/widgets.js
as the url to the file now that Twitter serves things over https
.