you can probably simulate certain error conditions (when we throw 404s and the like), and you can probably force it to get to a rate limit error - but a particular 500 error, no.
On Wed, Dec 23, 2009 at 4:43 PM, Tim Dorr <timd...@gmail.com> wrote: > Is there a way to force Twitter's API to respond with a particular > HTTP response code? I'd like to make sure that if there happens to be > a 500 error, my app isn't going to crash/infinite loop/collapse into a > black hole and consume the Earth. I can probably fake it in my app, > but I wanted to test the full stack of things to be sure. > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi