> From wessels@surf.scd.ucar.edu Mon Aug 2 14:51:07 1999
> Delivery-Date: Mon, 02 Aug 1999 14:51:07 -0700
> Return-Path: wessels@surf.scd.ucar.edu
> Date: Mon, 2 Aug 1999 15:50:31 -0600
> From: Duane Wessels <wessels@ircache.net>
> To: Joe Touch <touch@ISI.EDU>
> cc: wrec@cs.utk.edu
> Subject: Re: oh the irony
>
>
>
> 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?
Wouldn't that more correctly show up as an error on the socket,
rather than an EOF? I'm bothered by the notion that you have
to check length, if you correctly check for an EOF.
> 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.
OK- in this case it works, assuming no chunking (in which case, if so,
the chunks have length).
Joe
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:26 MST