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

Re: HTTP/1.1 Contradiction

From: Daniel DuBois <dan@spyglass.com>
Date: Fri, 13 Dec 1996 15:04:26 -0800
Message-Id: <>
To: Patrick Montelo <pmontelo@rafiki.spyglass.com>, swingard@spyglass.com, dladd@spyglass.com, ddubois@spyglass.com
Cc: pharring@spyglass.com, mlambert@spyglass.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/2075
>19.4.6 Introduction of Transfer-Encoding
>... Proxies/gateways MUST remove any transfer coding prior to forwarding a
>message via a MIME-compliant protocol.
>(Sounds good, not only can we remove it [per 4.3], we MUST remove it, but)

IIRC, HTTP is not a MIME compliant protocol.  The spec writers are talking
here about proxies that forward messages to a mail gateway.  (And yeah, a
proxy that has that feature would need to remove Trasnfer-Encoding, since
such a beast will choke any mail software out there.)

>13.5.2 Non-modifiable Headers
>... A cache or non-caching proxy MUST NOT modify or add any of the following
>fields in a response that contains  the no-transform Cache-Control
>directive, or in any request:
>Now if we MUST remove Transfer coding, seems like we MUST add a
>Content-Length header?

Seems to me if you remove the transfer encoding, you would have to add a
Content-Length.  I don't understand why they included that header amongst
those that couldn't be added/modified couldn't be added.  Let's ask them....

Hey HTTP-WG, why can't proxies modify/change Content-Length on no-transform

Daniel DuBois, Traveling Coderman        www.spyglass.com/~ddubois
   o  The Heroes of Might and Magic II Bible is here!
Received on Friday, 13 December 1996 15:09:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:16:21 UTC