I have a similar problem. I am trying to upload a profile image with
the API with OAuth authentication. I get a 200 response and a valid
response body, indicating a path like
in the response for the uploaded image. However, when I try to access
this URL, I get HTTP 403 Forbidden. Is this expected in the current
state of things, or is the problem on my client side?


On Jun 15, 8:12 am, Taylor Singletary <taylorsinglet...@twitter.com>
> The image upload facilities at Twitter are in need of some love (and are
> being worked on!) -- they'll often throw a 500 error and actually update the
> image, or show a 500 error and not update the image.. it should, in general,
> function better and more reliably in the near future.  The current site
> issues make it sometimes difficult to have clarity on how something failed,
> and at what stage.
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod
> On Tue, Jun 15, 2010 at 7:00 AM, Roy Tanck <roy.ta...@gmail.com> wrote:
> > I'm trying to upload profile images using oAuth. This basically works
> > (I get the right return data, no errors), except that the image is not
> > updated. Sending tweets through the same library does work, so this
> > probably isn't an authentication issue.
> > As per the twitter-async documentation, I'm using:
> > $twitterObj->post('/account/update_profile_image.json', array('@image'
> > => '@'.$img_path));
> > $img_path is the correct path (+filename) for the file, I've checked
> > the folder name using phpinfo, used a test image, etc.
> > Since I'm not getting errors, this issue is very hard to troubleshoot
> > from my end. Suggestions on how to tackle this very welcome.
> > (More info on twitter-async is here:
> >http://github.com/jmathai/twitter-async
> > , on sending images here
> >http://wiki.github.com/jmathai/twitter-async/#multipart)

Reply via email to