Always interesting to find weird broken shit in wire protocols. This from a hopscotch debugging session: $ curl -I http://www.ibm.com/social-business/us/en/newway/images/email/ipad_image.jpg HTTP/1.1 200 OK ... epKe-Alive: timeout=10, max=76 All other headers are correct. So I started poking around a bit: $ curl -I http://www.ibm.com/social-business/us/en/ HTTP/1.1 200 OK ... Kp-eeAlive: timeout=10, max=81 $ curl -I http://www.ibm.com/ HTTP/1.1 302 Moved Temporarily Server: AkamaiGHost Dunno ...
