[twitter-dev] Re: Changing domains for image hosting

[Doug Williams]

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 with
this change.

Updates to come as we learn about them. Thanks for your patience, here.
Twitter devs rock.

Doug



On Fri, Jul 10, 2009 at 9:49 AM, Matt Sanford  wrote:

> 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 domain and pull the
> photos through there.
>
> Abraham
>
> On Fri, Jul 10, 2009 at 02:18, Toucan  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 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.
>>
>> Can twitter turn on SSL for twimg, even if to buy time while we figure
>> it out? One day notice really isn't a lot of time to develop a fix and
>> try to get everyone to re-install their appespecially since for
>> those of us that must serve every page with SSL, there is no good fix.
>>
>> We really appreciate your help!
>> Diane
>>
>>
>>
>> On Jul 9, 9:47 pm, gotwalt  wrote:
>> > 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
>>
>
>
>
> --
> Abraham Williams | Community Evangelist | http://web608.org
> Hacker | http://abrah.am | http://twitter.com/abraham
> Project | http://fireeagle.labs.poseurtech.com
> This email is: [ ] blogable [x] ask first [ ] private.
>
>
>

[twitter-dev] Re: Changing domains for image hosting

[Matt Sanford]

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 domain and pull  
the photos through there.


Abraham

On Fri, Jul 10, 2009 at 02:18, Toucan  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 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.

Can twitter turn on SSL for twimg, even if to buy time while we figure
it out? One day notice really isn't a lot of time to develop a fix and
try to get everyone to re-install their appespecially since for
those of us that must serve every page with SSL, there is no good fix.

We really appreciate your help!
Diane



On Jul 9, 9:47 pm, gotwalt  wrote:
> 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



--
Abraham Williams | Community Evangelist | http://web608.org
Hacker | http://abrah.am | http://twitter.com/abraham
Project | http://fireeagle.labs.poseurtech.com
This email is: [ ] blogable [x] ask first [ ] private.

[twitter-dev] Re: Changing domains for image hosting

[Abraham Williams]

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  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 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.
>
> Can twitter turn on SSL for twimg, even if to buy time while we figure
> it out? One day notice really isn't a lot of time to develop a fix and
> try to get everyone to re-install their appespecially since for
> those of us that must serve every page with SSL, there is no good fix.
>
> We really appreciate your help!
> Diane
>
>
>
> On Jul 9, 9:47 pm, gotwalt  wrote:
> > 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
>



-- 
Abraham Williams | Community Evangelist | http://web608.org
Hacker | http://abrah.am | http://twitter.com/abraham
Project | http://fireeagle.labs.poseurtech.com
This email is: [ ] blogable [x] ask first [ ] private.

[twitter-dev] Re: Changing domains for image hosting

[Toucan]

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.

Can twitter turn on SSL for twimg, even if to buy time while we figure
it out? One day notice really isn't a lot of time to develop a fix and
try to get everyone to re-install their appespecially since for
those of us that must serve every page with SSL, there is no good fix.

We really appreciate your help!
Diane



On Jul 9, 9:47 pm, gotwalt  wrote:
> 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

[twitter-dev] Re: Changing domains for image hosting

[gotwalt]

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

[twitter-dev] Re: Changing domains for image hosting

[Hayes Davis]

I really appreciate it, Doug. Thanks.

Hayes


On Thu, Jul 9, 2009 at 4:43 PM, Doug Williams  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
>
>
>
>
> On Thu, Jul 9, 2009 at 6:09 AM, Hayes Davis  wrote:
>
>> 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 Thu, Jul 9, 2009 at 8:53 AM, Clint Shryock  wrote:
>>
>>> 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  wrote:
>>>
 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
 aribitrary sub-domain (*.twimg.com).

 Thanks,
 Doug


 On Jul 8, 2009, at 6:20 PM, Doug Williams  wrote:

 Folks --
 We are going to be moving images to a new domain ( 
 twimg.com) to streamline our image hosting and offer better
 performance. We hope this will have limited impact as will only change the
 image URL. Example URLs include:

 Profile images:


 
 http://s3.amazonaws.com/twitter_production/profile_images/35240332/2929920.gif

 
 http://a0.twimg.com/profile_images/35240332/2929920.gif
 Background images:

  
 http://s3.amazonaws.com/twitter_production/profile_background_images/18156348/jessica_tiled.jpg.jpeg

  
 http://a0.twimg.com/profile_background_images/18156348/jessica_tiled.jpg.jpeg

 Thanks,
 Doug



>>>
>>
>

[twitter-dev] Re: Changing domains for image hosting

[roamlog]

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..

[twitter-dev] Re: Changing domains for image hosting

[Doug Williams]

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



On Thu, Jul 9, 2009 at 6:09 AM, Hayes Davis  wrote:

> 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 Thu, Jul 9, 2009 at 8:53 AM, Clint Shryock  wrote:
>
>> 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  wrote:
>>
>>> 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
>>> aribitrary sub-domain (*.twimg.com).
>>>
>>> Thanks,
>>> Doug
>>>
>>>
>>> On Jul 8, 2009, at 6:20 PM, Doug Williams  wrote:
>>>
>>> Folks --
>>> We are going to be moving images to a new domain ( 
>>> twimg.com) to streamline our image hosting and offer better performance.
>>> We hope this will have limited impact as will only change the image URL.
>>> Example URLs include:
>>>
>>> Profile images:
>>>
>>>
>>> 
>>> http://s3.amazonaws.com/twitter_production/profile_images/35240332/2929920.gif
>>>
>>> 
>>> http://a0.twimg.com/profile_images/35240332/2929920.gif
>>> Background images:
>>>
>>>  
>>> http://s3.amazonaws.com/twitter_production/profile_background_images/18156348/jessica_tiled.jpg.jpeg
>>>
>>>  
>>> http://a0.twimg.com/profile_background_images/18156348/jessica_tiled.jpg.jpeg
>>>
>>> Thanks,
>>> Doug
>>>
>>>
>>>
>>
>

[twitter-dev] Re: Changing domains for image hosting

[Hayes Davis]

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 Thu, Jul 9, 2009 at 8:53 AM, Clint Shryock  wrote:

> 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  wrote:
>
>> 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.comas 
>> in the examples provided, but instead should expect an aribitrary
>> sub-domain (*.twimg.com).
>>
>> Thanks,
>> Doug
>>
>>
>> On Jul 8, 2009, at 6:20 PM, Doug Williams  wrote:
>>
>> Folks --
>> We are going to be moving images to a new domain ( 
>> twimg.com) to streamline our image hosting and offer better performance.
>> We hope this will have limited impact as will only change the image URL.
>> Example URLs include:
>>
>> Profile images:
>>
>>
>> 
>> http://s3.amazonaws.com/twitter_production/profile_images/35240332/2929920.gif
>>
>> 
>> http://a0.twimg.com/profile_images/35240332/2929920.gif
>> Background images:
>>
>>  
>> http://s3.amazonaws.com/twitter_production/profile_background_images/18156348/jessica_tiled.jpg.jpeg
>>
>>  
>> http://a0.twimg.com/profile_background_images/18156348/jessica_tiled.jpg.jpeg
>>
>> Thanks,
>> Doug
>>
>>
>>
>

[twitter-dev] Re: Changing domains for image hosting

[Clint Shryock]

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  wrote:

> 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 aribitrary sub-domain (*.
> twimg.com).
>
> Thanks,
> Doug
>
>
> On Jul 8, 2009, at 6:20 PM, Doug Williams  wrote:
>
> Folks --
> We are going to be moving images to a new domain ( 
> twimg.com) to streamline our image hosting and offer better performance.
> We hope this will have limited impact as will only change the image URL.
> Example URLs include:
>
> Profile images:
>
>
> 
> http://s3.amazonaws.com/twitter_production/profile_images/35240332/2929920.gif
>
> 
> http://a0.twimg.com/profile_images/35240332/2929920.gif
> Background images:
>
>  
> http://s3.amazonaws.com/twitter_production/profile_background_images/18156348/jessica_tiled.jpg.jpeg
>
>  
> http://a0.twimg.com/profile_background_images/18156348/jessica_tiled.jpg.jpeg
>
> Thanks,
> Doug
>
>
>

[twitter-dev] Re: Changing domains for image hosting

[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 aribitrary  
sub-domain (*.twimg.com).


Thanks,
Doug


On Jul 8, 2009, at 6:20 PM, Doug Williams  wrote:


Folks --
We are going to be moving images to a new domain (twimg.com) to  
streamline our image hosting and offer better performance. We hope  
this will have limited impact as will only change the image URL.  
Example URLs include:


Profile images:

http://s3.amazonaws.com/twitter_production/profile_images/35240332/2929920.gif

http://a0.twimg.com/profile_images/35240332/2929920.gif

Background images:
http://s3.amazonaws.com/twitter_production/profile_background_images/18156348/jessica_tiled.jpg.jpeg
http://a0.twimg.com/profile_background_images/18156348/jessica_tiled.jpg.jpeg
Thanks,
Doug

[twitter-dev] Re: Changing domains for image hosting

[Wynn Netherland]

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  wrote:

> Folks --
> We are going to be moving images to a new domain (twimg.com) to streamline
> our image hosting and offer better performance. We hope this will have
> limited impact as will only change the image URL. Example URLs include:
>
> Profile images:
>
>
> http://s3.amazonaws.com/twitter_production/profile_images/35240332/2929920.gif
>
> http://a0.twimg.com/profile_images/35240332/2929920.gif
> Background images:
>
> http://s3.amazonaws.com/twitter_production/profile_background_images/18156348/jessica_tiled.jpg.jpeg
>
> http://a0.twimg.com/profile_background_images/18156348/jessica_tiled.jpg.jpeg
>
> Thanks,
> Doug
>
>
>


-- 
Wynn Netherland
twitter: pengwynn