W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 1995

HTTP/1.1 draft 00 : chunked transfer and proxies

From: Philip Thrift <thrift@osage.csc.ti.com>
Date: Sat, 25 Nov 1995 06:14:39 -0600 (CST)
Message-Id: <199511251214.GAA21080@osage.csc.ti.com>
To: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Cc: thrift@osage.csc.ti.com

Regarding the use of the "chunked" coding for persistent connections,
I am confused how this will work if the proxy must remove this
encoding according to the language below.

>From the draft:
> C.5  Introduction of Transfer-Encoding
>    HTTP/1.1 introduces the Transfer-Encoding header field 
>    (Section 10.39). Proxies/gateways must remove any transfer coding 
>    prior to forwarding a message via a MIME-compliant protocol. The 
>    process for decoding the "chunked" transfer coding (Section 3.6) 
>    can be represented in pseudo-code as:
Here the chunked transfer represents a single, potentially unbounded
POST request and the server can be concurrently transmitting response
data during the request.

Philip Thrift
Received on Saturday, 25 November 1995 04:18:32 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:42:56 UTC