Re: #305 Header ordering

I think you're getting the proposal mixed up a little here.

1. We're creating special rules for Cookie, but those rules are
separable.  One value emitted only (multiple carried).  No nulls
needed there.

2. Set-Cookie is already special, but since ordering doesn't matter,
allow the compressor to emit these in any order, no concatenation.  It
remains as a perpetual gotcha, but no proposal was going to change
that characteristic.

3. Everything else already has rules for handling multiple header
field name-value pairs.  Leverage those existing rules and require
concatenate on encode to preserve order (unless you know that order
doesn't matter, which might let you get some compression efficiency,
c.f. cache-control).

On 21 November 2013 14:08, Roberto Peon <> wrote:
> We need a mechanism one way or another for fields where order might matter.

Received on Thursday, 21 November 2013 22:20:40 UTC