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: Roy T. Fielding <fielding@liege.ICS.UCI.EDU>
Date: Sat, 25 Nov 1995 15:12:52 -0800
To: Alexei Kosut <akosut@nueva.pvt.k12.ca.us>
Cc: Philip Thrift <thrift@osage.csc.ti.com>, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <9511251512.aa24455@paris.ics.uci.edu>
> 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.

And it is exactly the right take -- that is what Appendix C is all about.

Received on Saturday, 25 November 1995 15:17:56 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:15 UTC