W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2012

Re: Using HTTP Trailers [was: Content-Integrity header]

From: Zhong Yu <zhong.j.yu@gmail.com>
Date: Wed, 11 Jul 2012 02:51:21 -0500
Message-ID: <CACuKZqEXktN+d+q7PiKX9q-Ob8M_yUgPGjEroMVyMsSOLyvFFw@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
We can also define a new content encoding for integrity check.

It's easy to program an individual content encoding (if it focuses on
just one thing), and it's easy to compose different content encodings.
For example, in Java servlet API, integrity check can be easily
implemented as a filter, and it's easy to install the filter.

The overhead of extra framing due to new content encoding should be marginal.

On "Transfer-Encoding: chunked": Its primary function was to mark the
end of message. While it's tempting to piggyback other features on it,
the lack of support of chunk-extension and trailer suggests that the
complexity they introduce exceeds what engineers are willing to
handle. I think we should leave it at that - the sole function of
chunking is to mark end of message; don't stuff other features in it.

Zhong Yu
Received on Wednesday, 11 July 2012 07:51:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 11 July 2012 07:51:57 GMT