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

Re: HTTP/1.1 draft 00 : chunked transfer and proxies

From: Alexei Kosut <akosut@nueva.pvt.k12.ca.us>
Date: Sat, 25 Nov 1995 11:58:59 -0800 (PST)
To: Philip Thrift <thrift@osage.csc.ti.com>
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <Pine.HPP.3.91.951125115638.12029A-100000@ace.nueva.pvt.k12.ca.us>
On Sat, 25 Nov 1995, Philip Thrift wrote:

> 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.

I think you're misreading the line following the one you indicated:

> >    (Section 10.39). Proxies/gateways must remove any transfer coding 
>                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >    prior to forwarding a message via a MIME-compliant protocol. The 
                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Remember, HTTP is not a MIME-compliant protocol. But if you have a gateway
that's translating HTTP to, say, email, you need to "remove any transfer
coding", because MIME email agents won't know what to do with it.  That's
all that line is saying. If you've an HTTP proxy through and through, 
then there's no need whatsoever to remove the encoding.

Of course, I may be wrong. But that's my take on that sentance.

--/ Alexei Kosut <akosut@nueva.pvt.k12.ca.us> /--------/ Lefler on IRC
----------------------------/ <http://www.nueva.pvt.k12.ca.us/~akosut/>
The viewpoints expressed above are entirely false, and in no way
represent Alexei Kosut nor any other person or entity. /--------------
Received on Saturday, 25 November 1995 12:02:25 EST

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:31:36 EDT