W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013

Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values?

From: Nico Williams <nico@cryptonector.com>
Date: Tue, 15 Jan 2013 17:22:40 -0600
Message-ID: <CAK3OfOj8G3gFbTK_vPSnjS0qij+SUB3t9CdG80FYW5tbGgKR3A@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: Karl Dubost <karld@opera.com>, Julian Reschke <julian.reschke@gmx.de>, Piotr Dobrogost <p@ietf.dobrogost.net>, ietf-http-wg@w3.org
On Tue, Jan 15, 2013 at 4:09 PM, Mark Nottingham <mnot@mnot.net> wrote:
> Saying that headers can only be combined under certain circumstances doesn't mean that they're required to be combined.

It might help to be able to say that all new headers must be
mergeable.  That is: how can a proxy or what have you, know whether
it's OK to merge a given header's multiple instances?  And I think the
answer is as Poul said: you should never do it.  But then shouldn't we
say so?

Whatever was the point of this feature in the first place?  Was it a
form of header compression?  If so, isn't it best to stop merging
multiple instances of headers and just go with whatever header
compression scheme we settle on?

Nico
--
Received on Tuesday, 15 January 2013 23:23:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 15 January 2013 23:23:08 GMT