W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2014

Re: #445: Transfer-codings

From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 4 Apr 2014 14:23:54 -0700
Message-ID: <CABkgnnUcahLdFhNNO+NAH4EUUnm_m3ysi9B5YmO=34bmEMiwtg@mail.gmail.com>
To: Michael Sweet <msweet@apple.com>
Cc: Matthew Kerwin <matthew@kerwin.net.au>, HTTP Working Group <ietf-http-wg@w3.org>
On 4 April 2014 14:13, Michael Sweet <msweet@apple.com> wrote:
> FWIW, the way Transfer-Encoding is defined in p1-messaging, it makes it pretty clear that compression MAY or MAY NOT be end-to-end at the discretion of each recipient in the chain, but it is not explicitly a hop-by-hop header and it definitely is not a frame-by-frame header (which is what is being proposed.)


I suspect that that is only because it allows an intermediary to
forward TE if it doesn't intend to un-Transfer-Encode the response on
the way back.
Received on Friday, 4 April 2014 21:24:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:29 UTC