4 ms·

We had some issues integrating 3rd party systems, such as the Twitter button, which has had an invalid certificate for months now. If your site can live without

by rdin 16y ago

We had some issues integrating 3rd party systems, such as the Twitter button, which has had an invalid certificate for months now. If your site can live without these bells & whistles, then you should investigate and see if your site can take the performance hit.

rubyskills 16y ago
Wow, I didn't think about twitter's button. :-/ We use the twitter widget.. Do you know if the twitter js is behind a valid cert?
- deleted 16y ago
  [deleted]
- deleted 16y ago
  [deleted]
- BallinBige 16y ago
  if only everyone had the twitter bar in their chrome browser :)
- rdin 16y ago
  Unfortunately, it's been invalid for awhile. You can check it out for yourself here: http://platform.twitter.com/widgets.js http://platform.twitter.com/widgets.js vs https://platform.twitter.com/widgets.js https://platform.twitter.com/widgets.js
  - rubyskills 16y ago
    Drat! Someone over at twitter should fix this. :( Luckily, we don't use that js, we use: http://twitter.com/javascripts/blogger.js http://twitter.com/javascripts/blogger.js and I just checked the certificate behind this and it's valid (I should hope twitter's main cert is valid!): https://twitter.com/javascripts/blogger.js https://twitter.com/javascripts/blogger.js and we use the json API: http://api.twitter.com/statuses/user_timeline/healpay.json?callback=twitterCallback2&count=5 http://api.twitter.com/statuses/user_timeline/healpay.json?c... which also happens to have a valid cert: https://api.twitter.com/statuses/user_timeline/healpay.json?callback=twitterCallback2&count=5 https://api.twitter.com/statuses/user_timeline/healpay.json?... So it looks like we're in the clear for this at least :)