We've been seeing 408's since the DOS attack back in July/August. They feel like rate limiting on Twitter's part when overloaded.
Cannot tell since 408 isn't listed as an error they throw at api.twitter.com JEff On Sep 6, 8:51 am, bosher <[email protected]> wrote: > Random 408 errors are being returned when users are attempting to > "Sign in with Twitter" on my site TweetMeNews.com. > > Has anyone else been seeing this? Twitter, is there any way you can > expand on the error message instead of just saying 408? That would > help us better Understand & Report what's breaking... > > Thanks, > > Bretthttp://twitter.com/TweetMeNews/
