I started to read that earlier, but I missed the short "closing the
connection" point.

So, how exactly do you detect the closing of the connection? If you're
using a non-blocking "select" loop, would you get a SIGPIPE?

> -----Original Message-----
> From: Alex Rousskov [mailto:rousskov@...]
> Sent: Thursday, October 04, 2001 12:01 PM
> To: 'http-compliance@yahoogroups.com'
> Subject: Re: [http-compliance] How do browsers detect end of response
> when no Content-Length hea der is present?
>
>
> On Thu, 4 Oct 2001, Karr, David wrote:
>
> > How do browsers figure out a response is "Complete" if the
> origin server
> > doesn't send a "Content-Length" header? What is the normal
> strategy for
> > that? The response could be sent in more than one packet, correct?
>
> RFC 2616 defines browsers behavior in this case. There are several
> scenarios like Chunked Encoding and end-of-file/connection detection.
> See a lengthy discussion in Section 4.4 of the RFC.
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.4
>
> Alex.
>
>
> ------------------------ Yahoo! Groups Sponsor
> ---------------------~-->
> Pinpoint the right security solution for your company- Learn
> how to add 128- bit encryption and to authenticate your web
> site with VeriSign's FREE guide!
> http://us.click.yahoo.com/yQix2C/33_CAA/yigFAA/CefplB/TM
> --------------------------------------------------------------
> -------~->
>
> To unsubscribe from this group, send an email to:
> http-compliance-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/