What happens while Twitter’s down?

Specifically, what’s happening with the web server? I was curious, so I fetched the headers from Twitter during its scheduled downtime tonight. And, boy, this is the most bizarre thing I’ve seen in quite a while:
[Maturin:~] curl -I http://twitter.com/
HTTP/1.1 500 Internal Server Error
Date: Sun, 01 Aug 2010 06:46:21 GMT
Server: hi
Status: 500 Internal Server Error
X-Transaction: 1280645180-68145-10683
X-Transaction: 1280645180-68145-10683
Last-Modified: Sun, 01 Aug 2010 06:46:20 GMT
Last-Modified: Sun, 01 Aug 2010 06:46:20 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 3339
Content-Length: 3339
Pragma: no-cache
Pragma: no-cache
X-Revision: DEV
X-Revision: DEV
Expires: Tue, 31 Mar 1981 05:00:00 GMT
Expires: Tue, 31 Mar 1981 05:00:00 GMT
Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
Set-Cookie: k=71.92.250.150.1280645177242888; path=/; expires=Sun, 08-Aug-10 06:46:17 GMT; domain=.twitter.com
Set-Cookie: guest_id=128064518059134212; path=/; expires=Tue, 31 Aug 2010 06:46:20 GMT
Set-Cookie: auth_token=; path=/; expires=Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: param_q=; path=/; expires=Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: param_page=; path=/; expires=Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: param_status=; path=/; expires=Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: param_in_reply_to_status_id=; path=/; expires=Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: param_in_reply_to=; path=/; expires=Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: param_source=; path=/; expires=Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: param_user=; path=/; expires=Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: param_id=; path=/; expires=Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: dispatch_action=; path=/; expires=Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCLCsZiwqAToHaWQiJWI2MmRlN2QxMmM4MGM5%250AMzFlYWZlMzc1NDBhZThmZmNkIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--7636f5a633a890bc270255e9449bf0b600d7ff72; domain=.twitter.com; path=/
Vary: Accept-Encoding
Connection: close
What’s up with all those duplicated headers? And what does Server: hi mean?




Do you remember dial-up Internet access? It was terrible, especially if you were on a laptop: connect the phone card, start the dialer, wait, enter your ID and password, wait some more, and then, finally, you’re on.
At the suggestion of many, I’ve setup a