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
