The Wayback Machine - https://web.archive.org/web/20131021093601/https://dev.twitter.com/issues/5

Skip to Main Content Area

Issue #5: REST API responds with HTML instead of JSON or XML for certain error conditions

When certain kinds of 500-class errors occur on the Twitter API, the exception thrown is not of the same content-type being requested by the client.

Updates

See Making API responses match the request Content-Type for recent developments in this area.
Merging with Many 500-series errors do not respect requested response format

Issue Information

Status	In progress
ETA	Within a month
Reported	Tue, 2011-09-13 14:45
Updated	Wed, 2012-03-28 09:11

Related Documentation

Error Codes & Responses

Related Discussions

Discussion Thread for "Making API responses match the request Content-Type"

Tags

Errors (9)
JSON (11)
XML (2)