My favorites | Sign in
Project Logo
       
New issue | Search
for
| Advanced search | Search tips
Issue 509: Enhancement: Search API error (404, etc) not formatted for the API
1 person starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  m...@twitter.com
Closed:  Jun 24
Type-Defect
Priority-Low
Component-Search


Sign in to add a comment
 
Reported by daniel.berlinger, Apr 22, 2009
If you make a request with an expired "since" ("since: will return a HTTP 404 if it is too old") and the 
request was made with search.atom or search.json, the response is always an html page, not an 
xml or json payload.

I think it should be since the format was requested.

'best,

d.


Comment 1 by m...@twitter.com, Apr 23, 2009
(No comment was entered for this change.)
Status: Accepted
Owner: m...@twitter.com
Labels: -Priority-Medium Priority-Low Component-Search
Comment 2 by m...@twitter.com, Jun 03, 2009
Triage: Updating the title so this jumps out at me more.
Summary: Enhancement: Search API error (404, etc) not formatted for the API
Comment 3 by m...@twitter.com, Jun 23, 2009
A fix for this is waiting to be deployed.
Comment 4 by m...@twitter.com, Jun 24, 2009
This was deployed late yesterday. Error cases caused by invalid parameters should now return non-200 and a 
formatted error.
Status: Fixed
Sign in to add a comment

Hosted by Google Code