I've been getting this too. I had a long-running process that was
going back in time paging through Twitter search data (search API). It
was using oAuth. I just assumed I had gotten all the data search was
willing to give me and aborted the process after three consecutive

If you want me to try to reproduce this, send me an email - I'm not
going to be testing this process again until I've had a chance to look
at the data I collected. The request was a search with a geocode
parameter and an "until_id" parameter.

On Jan 11, 11:02 pm, Raffi Krikorian <ra...@twitter.com> wrote:
> hi andrew.
> can you give me some more information so i can track this down?  any chance
> you would be willing to share what request you made to Twitter that caused
> this return?
> thanks!
> On Sun, Jan 10, 2010 at 10:11 AM, Andrew Arnott <andrewarn...@gmail.com>wrote:
> > Twitter sends this in response to an OAuth message it deems unworthy.  Note
> > that *all* that I copied below is part of the response *body*.  The first
> > two lines *look* like they belong in the response headers.  But in fact
> > they are not (two preceding \r\n before the start). And the response is a
> > 200 OK response, actually (perhaps because no status is included?  I don't
> > know).  Also note that the the entire body is included *twice*.
> > Status: 500 Internal Server Error
> > Content-Type: text/html
> > <html><body><h1>500 Internal Server Error</h1></body></html>Status: 500
> > Internal Server Error
> > Content-Type: text/html
> > <html><body><h1>500 Internal Server Error</h1></body></html>
> > --
> > Andrew Arnott
> > "I [may] not agree with what you have to say, but I'll defend to the death
> > your right to say it." - S. G. Tallentyre
> --
> Raffi Krikorian
> Twitter Platform Teamhttp://twitter.com/raffi

Reply via email to