Hi Erik,

This is a known issue which is being tracked on our issue tracker. The
way Twitter is setup the solution isn't as straight forward as one
would hope - but the team is working on it.

The issue is being tracked here:
    http://code.google.com/p/twitter-api/issues/detail?id=942

Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris



On Tue, Oct 12, 2010 at 9:25 AM, Erik Michaels-Ober <sfe...@gmail.com> wrote:
> When the Twitter API responds with an HTTP 500 error, as was occurring
> for a brief period yesterday, the response body is an XHTML document
> (http://twitter.com/500) as opposed to JSON, as I requested. This is
> not the case for HTTP 4xx errors, which respond in the requested
> format, for example:
>
> {"error":"Not Found","request":"/1/statuses/show/1.json"}
>
> I would ask that 5xx responses be made conditional on the requested
> format, so that I can parse Twitter API responses consistently.
>
> Note: in addition to affecting the API, this problem could be seen on
> the new twitter.com.
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to