Hmm, it is complaining about the status line (the first one). I think it is choking on the HTTP 1.0 response with a Connection header. That header was added in

Hmm, it is complaining about the status line (the first one). I think it is choking on the HTTP 1.0 response with a Connection header. That header was added in HTTP 1.1, but lots of people use it with HTTP 1.0 and pretty much everyone supports it. (edit: by which I mean they ignore it, because connection: close is the default behavior in HTTP 1.0) That said, you should add an ETag to the response. Hacker News changes often enough that timed expiration won't help, but ETags might get you a lot of 304 Not Modified responses.