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

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.