We saw some intermittent cache corruption, but the problem has corrected itself. We're investigating to ensure it doesn't happen again, but all seems fine now.
On Thu, Oct 16, 2008 at 9:46 AM, Damon Clinkscales <[EMAIL PROTECTED]> wrote: > > I am also seeing 500 errors on /users/show, which is preventing new > user signups on SnapTweet. > > $ curl -I -u damon:wellyouknow "http://twitter.com/users/show/damon.xml"; > > HTTP/1.1 500 Internal Server Error > Date: Thu, 16 Oct 2008 16:39:51 GMT > Server: hi > Last-Modified: Thu, 16 Oct 2008 16:39:51 GMT > Status: 500 Internal Server Error > Pragma: no-cache > Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 > Content-Type: text/html; charset=utf-8 > Content-Length: 4491 > Expires: Tue, 31 Mar 1981 05:00:00 GMT > Set-Cookie: lang=en; path=/ > Set-Cookie: lang=en; path=/ > Set-Cookie: _twitter_sess=something; domain=.twitter.com; path=/ > Vary: Accept-Encoding > Connection: close > > -damon > > On Thu, Oct 16, 2008 at 11:14 AM, Shahid Faiz <[EMAIL PROTECTED]> wrote: >> Hi, >> >> Following API is returning complete HTML error page. Is it because of some >> maintenance activity? it was working fine previously. >> >> http://twitter.com/users/show/<user_id>.xml >> >> Thanks, >> - Shahid > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
