Same here and it's already breaking our app today. We either give
users the browser mixed-ssl error (bad) or re-write to SSL which makes
images spin forever which also seems to break some javascript loads on
FF (also bad). Since Toucan runs inside salesforce, we are always on
SSL for every page.
A temporary fix is to run a proxy on your own SSL domain and pull the photos
through there.
Abraham
On Fri, Jul 10, 2009 at 02:18, Toucan toucan...@gmail.com wrote:
Same here and it's already breaking our app today. We either give
users the browser mixed-ssl error (bad) or re-write to SSL
Hi all,
I'm working with our ops folks now to get SSL fixed on twimg.com.
No need for running proxies … we're working on it.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On Jul 10, 2009, at 12:42 AM, Abraham Williams wrote:
A temporary fix is to run a proxy on your own SSL
All --
We are rolling back the twimg.com change because a number of issues became
apparent when we moved it into production -- one being the lack of SSL
support in the caching layer that many have noted. We do hope to make this
change rather soon, but we have problems to fix before moving forward
I'm still having issues with the profile_image_url attribute of users/show
updating in a timely fashion, any chance this issue be resolved with this
update?
+Clint
On Wed, Jul 8, 2009 at 11:55 PM, Doug Williams d...@twitter.com wrote:
Andrew Stone asked a great question off list and I wanted to
Are you going to shut off the S3 URLs immediately or will they still be
accessible for a time? I understand that newly updated avatar images would
not be updated at S3 after the switch but I'd like to know when we can
expect any S3 URLs we may have in our caches to all go dark.
Thanks.
Hayes
On
it seems there are some issues with the new pics server
the https is failed, please check it..
e.g. :
http://a0.twimg.com/profile_background_images/18156348/jessica_tiled.jpg.jpeg
is ok
but
https://a0.twimg.com/profile_background_images/18156348/jessica_tiled.jpg.jpeg
is failed..
I really appreciate it, Doug. Thanks.
Hayes
On Thu, Jul 9, 2009 at 4:43 PM, Doug Williams d...@twitter.com wrote:
I've asked the operation's teams to leave the old S3 hosted images
available for 2 weeks after the deploy. This should give you time to update
your caches.
Cheers,
Doug
Any chance you'll enable SSL access of these images? At @cotweet we
rely on s3's SSL when pages are being served via HTTPS (login, account
changes, permissions, etc) in order to prevent security zone issues in
IE. I'd imagine that other web-based clients may face similar issues.
Aaron
Hi, Doug,
Thanks for the heads up and all the hard work to keep us in the loop.
Any plans to offer something like:
http://twimg.com/pengwynn so people can always have my latest avatar
regardless of the filename?
Thanks,
Wynn Netherland
@pengwynn
On Wed, Jul 8, 2009 at 8:20 PM, Doug Williams
Andrew Stone asked a great question off list and I wanted to share the
answer here.
Images will be hosted from a number of sub-domains of twimg.com.
Therefore you should not expect all images to be served from a0.twimg.com
as in the examples provided, but instead should expect an
11 matches
Mail list logo
