For the last three days I've had half or more of my site's posts fail to go through. I don't yet have full debugging results to show what I was receiving each time it failed, but I want to share this bit now. This server is not yet on the API whitelist. It makes 3-5 API requests every hour for most of the day, and several thousand search requests during the very early morning.
Check out this set of consecutive 'curl' calls from this evening: curl -I 'http://twitter.com/users/show.xml?screen_name=dougw' HTTP/1.0 200 OK Connection: Close Pragma: no-cache cache-control: no-cache Refresh: 0.1 Content-Type: text/html; charset=iso-8859-1 curl -I 'http://twitter.com/users/show.xml?screen_name=dougw' HTTP/1.1 200 OK Date: Tue, 08 Sep 2009 00:52:08 GMT Server: hi Last-Modified: Tue, 08 Sep 2009 00:52:08 GMT Status: 200 OK X-RateLimit-Limit: 150 ETag: "99ae783e1715c8b08029dd1fe876576c" X-RateLimit-Remaining: 149 Pragma: no-cache Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Content-Type: application/xml; charset=utf-8 X-RateLimit-Reset: 1252374728 Content-Length: 1880 Expires: Tue, 31 Mar 1981 05:00:00 GMT X-Revision: 7049adb008908242a7a3c2fe1ebe55e640e3e9fc X-Transaction: 1252371128-41890-18859 Set-Cookie: lang=en; path=/ Set-Cookie: _twitter_sess=BAh7CDoRdHJhbnNfcHJvbXB0MDoHaWQiJWVlYjJhYzY4MmMwMmRlZjg5MjU2%250AN2U0NTY2OGI0MjYzIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFz %250AaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--3228a79ee32dfd0c8d0808acb82e8e715999594f; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close Anyone know what's up with that first request? Has anyone seen that? Perhaps it's part of the DoS prevention tools recently deployed by Twitter. Josh
