Has this been fixed yet... I have this problem also :)
On Nov 5, 4:20 pm, Marcel Molina <mar...@twitter.com> wrote:
> To follow up I've been told that this is the most critical bug they
> are working on right now. So it's being worked on. I'll pass along
> updates as provided.
>
>
>
> On Wed, Nov 4, 2009 at 1:57 PM, Marcel Molina <mar...@twitter.com> wrote:
> > Thanks for reporting this. I've forwarded this to the team responsible
> > for the S3 uploading.
>
> > On Wed, Nov 4, 2009 at 10:28 AM, Kevin <kevinh...@gmail.com> wrote:
>
> >> We are uploading Twitter backgrounds via the API. We noticed today new
> >> attempts to upload seem to be successful, but the profiles show no
> >> background image. Looking at the page source, it shows a new
> >> background image URL:
> >> background: ... url('http://a0.twimg.com/profile_background_images/
> >> bg12573586264055.jpg') ...;
>
> >> However, opening that URL returns an error:
> >> <?xml version="1.0" encoding="UTF-8"?>
> >> <Error><Code>AccessDenied</Code><Message>Access Denied</
> >> Message><RequestId>20FB3BC5AEC2A2D5</RequestId><HostId>KheAYU8E/puKx
> >> +qm5jtF9YeLLfc/NHcoCr6q2iOWZy2OR3tbtouA3Fo5aTrHUrZn</HostId></Error>
>
> >> It would appear Twitter is not adding the S3 access key query string
> >> to these background image URLs, or the images are being put into S3 as
> >> private items.
>
> >> Hope to see a fix soon.
> >> Regards,
> >> Kevin Hunt
> >> Bubble Fusion Labs
>
> > --
> > Marcel Molina
> > Twitter Platform Team
> >http://twitter.com/noradio
>
> --
> Marcel Molina
> Twitter Platform Teamhttp://twitter.com/noradio
