On Mon, 2009 Aug 24 21:42+0100, Mark Hindley wrote: > > I have just been going through the RFCs. Even if thttpd is only doing > HTTP/1.0, it says > > Applications should use this field to indicate the size of the Entity- > Body to be transferred, regardless of the media type of the entity. A > valid Content-Length field value is required on all HTTP/1.0 request > messages containing an entity body. > > So, I think this is a thttpd bug, not apt-cacher.
Are you sure that quote is from an RFC? I see it in draft-ietf-http-v10-spec-05 (on the w3.org site), but not in any RFC docs. In any event, though it could be more explicit on this point, I think it's stating that a Content-Length field is required on [POST] requests, not necessarily server responses. I'm pretty sure that Content-Length can't be required for all HTTP/1.0/1.1 responses... what about CGI scripts, or HTTP streaming? As it is, I believe thttpd leaves out Content-Length for 404 errors because it generates a 404 page on the fly containing the not-found path, and doesn't bother to measure the size of it. There's going to be a lot of other situations like this, where computing the size is either inconvenient or infeasible. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
