Doug, we're using our whitelisted socialtoo account, on our whitelisted IP. Other requests for users are going through fine, but when I get to page 255 with the URL http://twitter.com/statuses/followers/scobleizer.json?page=255it gives this response with a 500 server error:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" " http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en" xml:lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Language" content="en-us" /> <title>Twitter / Error</title> <link rel="icon" href="http://static.twitter.com/favicon.ico"; type="image/ico" /> <style type="text/css"> body{background:#9AE4E8 url(http://static.twitter.com/images/bg.gif) no-repeat fixed left top;color:#333;font:0.75em Helvetica,Arial,sans-serif;text-align:center} #container { width: 755px; margin: 0 auto; padding: 0px 0; text-align: left; position: relative; } #content { width: 100%; margin-top: 0px; float: left; padding-bottom: 15px; background: transparent url(http://static.twitter.com/images/arr2.gif) no-repeat scroll 25px 0px;} .subpage #content .wrapper { background: #fff; padding: 10px 10px 15px 10px; -moz-border-radius: 5px;-webkit-border-radius: 5px;} .subpage #content h1, .subpage #content h2, .subpage #content h3, .subpage #content h4, .subpage #content h5 { margin: 3px 0pt 4px; } .subpage #content p { line-height: 1.2; margin: 5px 0; } .subpage #content ul { padding-left: 30px; } .subpage #content ol, #side ol { padding-left: 30px; } a{text-decoration:none;color: #0084b4;} #content div.desc { margin: 11px 0px 10px 0px; } a img{border:0;} ul{list-style:square;padding-left:20px;} #navigation { position: absolute; top: 12px; right: 0; padding: 0px 5px 0px 5px; line-height: 0.5em; text-align: center; } #navigation ul { list-style:none margin: 0; padding: 0px; width: auto; height: 100%; } #navigation li { display:inline; padding: 0 0 0 5px; } #navigation li:before { content: ' '; padding-right: 0; } #navigation li.first:before { content: ''; padding-right: 0; } #navigation, #footer { background: #fff; -moz-border-radius: 5px;-webkit-border-radius: 5px;} #footer { clear: left; width: 555px; text-align: center; padding: 1px 0; line-height: 1; } #footer li { display: inline; padding: 0 0 0 5px; } #footer li.first:before { content: ''; padding-right: 0; } </style> </head> <body> <div id="container" class="subpage"> <div id="navigation"> <ul> <li class="first"><a href="http://twitter.com";>Home</a></li> <div id="content"> <div class="desc"></div> <div class="wrapper"> <span style="font-size:1.8em; font-weight:bold">Something is technically wrong.</span><br /> <div style="font-size:1.2em;margin-top:2px;color:#b6b6a3">Thanks for noticing—we're going to fix it up and have things back to normal soon.</div><br /> <p style="margin-bottom:10px;text-align:center"><img src=" http://static.twitter.com/images/please_fix.png"; /></p> </div> </div> <div id="footer" style="width:100%"> <ul> <li class="first">© 2009 Twitter</li> <li><a href="/help/aboutus">About Us</a></li> <li><a href="/help/contact">Contact</a></li> <li><a href="http://blog.twitter.com/";>Blog</a></li> <li><a href="http://status.twitter.com/";>Status</a></li> <li><a href="/help/api">API</a></li> <li><a href="http://help.twitter.com/";>Help</a></li> <li><a href="/help/jobs">Jobs</a></li> <li><a href="/help/tos">TOS</a></li> <li><a href="/help/privacy">Privacy</a></li> </ul> </div> </div> <!-- BEGIN google analytics --> <script type="text/javascript"> var gaJsHost = (("https:" == document.location.protocol) ? " https://ssl."; : "http://www.";); document.write(unescape("%3Cscript src='" + gaJsHost + " google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E")); </script> <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-30775-6"); pageTracker._setDomainName("twitter.com"); pageTracker._trackPageview('500 Error'); </script> <!-- END google analytics --> </body> </html> On Wed, Jan 21, 2009 at 8:12 AM, dougw <[email protected]> wrote: > > Jesse, > Doing what you say you are doing should work. Can you provide more > details what URL you are using, how you are making the requests, what > exactly is coming back, etc...? > > @dougw > > On Jan 21, 12:41 am, Jesse Stay <[email protected]> wrote: > > Speaking of going through Scoble's followers, I'm trying to process > Scoble's > > followers right now and keep getting a 500 server error. Sometimes it > says > > too many Tweets, and other times it's saying something's technically > wrong > > with the default HTML return message. I'm using our whitelisted IP and > > sending the followers request via our whitelisted user - is something > going > > wrong on Twitter's end? This didn't start happening until I started > > processing Scoble. Don't tell me Scoble broke Twitter again, please. ;-) > > > > Jesse >
![http://static.twitter.com/images/please_fix.png"](http://static.twitter.com/images/please_fix.png"){kind=link}