Curl fails with a "transfer closed with * bytes remaining to read"
when Debian stable's thttpd responds with a 304 Not Modified. It
seems this is because of thttpd including Content-Length in the
response headers:

HTTP/1.1 304 Not Modified
Server: thttpd/2.21b 23apr2001
Content-Type: text/plain; charset=iso-8859-1
Date: Fri, 08 Apr 2005 09:20:08 GMT
Last-Modified: Wed, 06 Apr 2005 04:12:24 GMT
Accept-Ranges: bytes
Connection: close
Content-Length: 835767

I realise this is more of an oddity of thttpd (it has been removed in
a future version) but aren't HTTP clients supposed to ignore headers
that don't make sense for the response?

-- 
Cory Nelson
http://www.int64.org