HTTP/1.1 response with no headers?

Just curious - if a client receives the response:

  HTTP/1.1 200 OK<CRLF>
  <CRLF>

should it be treated as a response with no message body, or a message
body delimited by an EOF?

Mozilla seems to opt for the latter; as far as I could work out from
2616 the former is correct - a request may or may not include a message
body... the presence of a message body is signalled by a
Transfer-Encoding or Content-Length header (or implicit for HEAD, 204,
304 etc)... so no T-E or C-L implies no message body.

joe

Received on Wednesday, 10 July 2002 16:04:13 UTC