In HTTP/1.1, the response could be sent with "Transfer-Encoding: chunked"
in which case a zero-length chunk (possibly followed by a trailer)
terminates the response. If there is no content length or chunked
transfer-coding, the server must terminate the response by closing the
connection. In HTTP/TCP/IP, the response could certainly be sent in
multiple IP packets.

-Carl




"Karr, David"
<david.karr@cach To:
"'http-compliance@yahoogroups.com'" <http-compliance@yahoogroups.com>
eflow.com> cc:
Subject: [http-compliance] How
do browsers detect end of response when no
10/04/2001 12:40 Content-Length hea der is
present?
PM
Please respond
to
http-compliance






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?


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/