Hi Alex,
As I re-read this and think back to last week I may know the
cause. Are you by chance still using summize.com? As part of our move
to the Twitter data center we changed the logic of summize.com to
redirect to search.twitter.com rather than handle requests to /search.
If this is the case please change the host name and everything should
work fine.
Thanks;
— Matt Sanford (@mzsanford)
On Dec 8, 2008, at 07:17 AM, Alex wrote:
We noticed that around midnight 00:00 GMT on Saturday we started
getting 301 redirects for our search queries. Responses such as:
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="http://search.twitter.com/
search.json?q=junk&since_id=1034606772&rpp=20">here</a>.</p>
</body></html>
Have there been changes to the Twitter Search API?
