On Mon, 2 Aug 1999, Joe Touch wrote:
> Seems like a browser might not care - just read until EOF.
> Ditto for caches. Why is it necessary to trust this information
> in the header?
You don't want caches saving partial responses (and then giving them
out as cache hits). Often its hard or impossible to tell if an EOF on
a socket is intentional or not. Did the origin server really close the
connection? Or was there a protocol/network error?
Correct content lengths are critical for persistent connections.
An HTTP agent must know where the response body ends and where
the next headers begin, or when the persistent connection can be
used for the next request.
Duane W.
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:26 MST