Chad, Thanks. That works for me.
Dewald On Oct 8, 12:22 pm, Chad Etzel <c...@twitter.com> wrote: > There is a workaround for this from an earlier thread: > > In order to accomplish retrieving the assets over ssl to avoid > security warnings in browsers, you will need to replace > > http://a1.twimg.com/ (or a2, a3, ...etc) > withhttps://s3.amazonaws.com/twitter_production/ > > in your > example:https://s3.amazonaws.com/twitter_production/profile_images/361430672/... > > I realize this isn't the easiest workaround, but it works... and > enabling SSL on twimg is not high priority for Ops right now. > > -Chad > > On Thu, Oct 8, 2009 at 11:13 AM, Dewald Pretorius <dpr...@gmail.com> wrote: > > > Running SSL encryption on one's site and displaying Twitter profile > > images is causing a lot of grief for people who use Internet Explorer. > > They constantly get that pop-up box that tells them there are insecure > > elements on the page, and it is because profile images currently > > cannot be pulled from the Twitter image servers over https. > > > Works:http://a1.twimg.com/profile_images/361430672/twitterProfilePhoto_norm... > > > Does not > > work:https://a1.twimg.com/profile_images/361430672/twitterProfilePhoto_nor... > > > Can you please implement SSL on your Twitter image servers so that > > those of us who use SSL can pull in the profile images over SSL. > > > The standard links don't need to change. I'm quite happy to hack the > > link from http to https when I want to pull in an image on a page of > > mine that is encrypted. > > > Dewald
