- From: Henrik Nordstrom <henrik@henriknordstrom.net>
- Date: Mon, 12 May 2008 12:06:59 +0200
- To: Yves Lafon <ylafon@w3.org>
- Cc: Mark Nottingham <mnot@mnot.net>, ietf-http-wg@w3.org
On mån, 2008-05-12 at 05:42 -0400, Yves Lafon wrote: > > 3. If a Transfer-Encoding header field (Section 14.41) is present, and > > has a value other than "identity", then the transfer-length > > is defined by closing the connection. > > And in that case, you have no guarantee that the message in complete or > not (unless you use a Transfer-Encoding that gives that property, if the > recipient knows about this encoding, which is not granted. Ofcourse, except for the last part. Closing the connection as delimiting method is only possible on responses and there any transfer encoding other than chunked is negotiated using TE. Both gzip & deflate (zlib) is self delimiting and checksummed by the way, giving you this property. So the only transfer encoding available today in HTTP/1.1 not having this property is the "identity" non-encoding without content-length. Regards Henrik
Received on Monday, 12 May 2008 10:07:50 UTC