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

Re: Fragmentation for headers: why jumbo != continuation.

From: Johnny Graettinger <jgraettinger@chromium.org>
Date: Sun, 13 Jul 2014 13:06:46 -0400
Message-ID: <CAEn92TrULC1rniqaG-vFYw9K77d2g97=ANywW3x5UyPfPSR=jA@mail.gmail.com>
To: Amos Jeffries <squid3@treenet.co.nz>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
On Fri, Jul 11, 2014 at 7:53 AM, Amos Jeffries <squid3@treenet.co.nz> wrote:

> Given the size of a large frame up-front a proxy can actually stream the
> start of that frame before the end has arrived if you trust the sender
> will complete it cleanly.
>

The proxy cannot know the encoded size of the block until it's run that
complete block through it's send-side HPACK context. That context is
different than the recv-side context, and it will almost certainly result
in a different block length.

Announcing the length of an encoded header-block is incompatible with
streaming.
Received on Sunday, 13 July 2014 17:07:14 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:09 UTC