This has already been discussed on the list. If you want to use HTTPS, for
now, you have to replace the twimg host with the amazonaws host.

On Tue, Aug 18, 2009 at 08:54, Alex <aybarb...@gmail.com> wrote:

>
> Our app uses https during the user session and in order to prevent
> errors in some browsers we must make sure that all files (including
> images) are loading via https as well.
>
> Up until now we were just taking the profile image URL and swapping
> http for https in the URL, and everything worked fine. For example:
>
> https://s3.amazonaws.com/twitter_production/profile_images/52714790/aj_normal.gif
>
> However I am noticing that as profile images get migrated to twimg.com
> the SSL is no longer working, and as a result we are not able to load
> the images for those users.
>
> For example, @garyvee's profile image is:
> http://a3.twimg.com/profile_images/333261519/twitterProfilePhoto_normal.jpg
>
> But it will not load if we request:
>
> https://a3.twimg.com/profile_images/333261519/twitterProfilePhoto_normal.jpg
>
> Do you have plans to support https requests on the twimg.com
> subdomains?
>
> Thanks.
>



-- 
Internets. Serious business.

Reply via email to