I haven't gotten a feedback yet. I might just cache the image on our server and show it https. Please let me know if there is a better solution.
On Jul 12, 1:44 pm, Amir <finda...@gmail.com> wrote: > Ok, but I am using REST api to pull tweets. I am using a https url for > the javascript call. But the images that are in the json data are not > https. IE7 throws this funny error saying "some resources on this page > is not secured would you like to still display them." I can search > replace in my loop but not sure if that is the best implementation. > Any thoughts? > > On Jul 12, 12:03 pm, John Adams <j...@twitter.com> wrote: > > > What the main site currently does is to provide SSL images directly from s3 > > when a user is on https and to provide images over our CDN (twimg.com) when > > using a non-ssl connection. > > > i.e.:https://s3.amazonaws.com/twitter_production/profile_images/64195496/I... > > > vs.http://a1.twimg.com/profile_images/64195496/IMG_1875_normal.JPG > > > This may change in the future if we put a valid cert on twimg,com, though. > > > -j > > > On Mon, Jul 12, 2010 at 6:42 AM, Amir <finda...@gmail.com> wrote: > > > Hi, > > > > We are trying to use https for twitter images but the certs seem to be > > > broken. > > > >https://a1.twimg.com/profile_images/517692382/box_normal.jpg > > > > Can someone confirm that is going to be fixed or if its already known > > > bug?